AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A company is migrating a 20 TiB on-premises PostgreSQL 12 database that uses custom C-language extensions which require superuser privileges. The database team must retain full operating-system and database-level control after the migration. The workload sustains 10 000 random read/write IOPS with sub-millisecond latency.
Business requirements include an RPO of 10 seconds and an RTO of 2 minutes for an Availability Zone failure; automated daily full and hourly incremental backups retained for 30 days and stored durably across AZs; encryption of data at rest and in transit; and the lowest possible ongoing operational effort.
Which solution will meet these requirements?
Run a primary and standby EC2 instance that share the same Multi-Attach enabled io2 EBS volume across Availability Zones; use Amazon Data Lifecycle Manager to snapshot the shared volume.
Migrate the database to an Amazon Aurora PostgreSQL Multi-AZ cluster and rely on Aurora automated backups with 30-day retention.
Launch two EC2 instances in different Availability Zones with gp3 EBS volumes provisioned for 10 000 IOPS. Configure asynchronous logical replication from primary to standby and schedule nightly pg_dump exports to Amazon S3 with lifecycle rules for retention.
Deploy two Amazon EC2 instances in separate Availability Zones. Attach encrypted Provisioned IOPS io2 Block Express EBS volumes sized for at least 10 000 IOPS. Configure synchronous PostgreSQL streaming replication between the instances. Use AWS Backup to create crash-consistent, encrypted EBS snapshots with a 30-day retention policy, and publish a Route 53 DNS failover record that points clients to the healthy instance.
Running the database on two Amazon EC2 instances in different Availability Zones and storing data on encrypted Provisioned IOPS io2 Block Express volumes delivers the required 10 000-IOPS performance and gives administrators full OS-level control. Enabling synchronous PostgreSQL streaming replication keeps the standby instance within a few seconds of the primary, satisfying the RPO target, and permits automated failover within the RTO when used together with a Route 53 DNS failover record. AWS Backup can create encrypted, crash-consistent EBS snapshots on the required schedule; because EBS snapshots are stored in Amazon S3 and automatically replicated across all AZs, the backup durability and retention goals are met with minimal maintenance.
Aurora PostgreSQL (distractor B) does not allow superuser privileges needed for the custom extensions, so the requirement for full control is not met. Using a single Multi-Attach io2 volume shared across AZs (distractor C) leaves storage in only one AZ, so an AZ outage would fail both nodes and violate RPO/RTO. Asynchronous logical replication on gp3 volumes (distractor D) allows data loss beyond the 10-second RPO and relies on manual dump/restore procedures that lengthen RTO and increase operational overhead.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a Provisioned IOPS io2 Block Express EBS volume, and why is it suitable for this use case?
Open an interactive chat with Bash
How does synchronous PostgreSQL streaming replication support the RPO and RTO requirements?
Open an interactive chat with Bash
Why is AWS Backup used instead of manual backup methods, and how does it meet the backup requirements?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Accelerate Workload Migration and Modernization
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access