AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A company runs a mission-critical mobile application that currently stores all user-generated data in an Amazon RDS for PostgreSQL instance located in us-east-1. Traffic has grown rapidly, and the database now experiences write saturation during peak hours, causing latency spikes for users in Europe and Asia-Pacific. New business requirements specify that the re-architected data layer must:
Provide single-digit-millisecond read and write latency for users in us-east-1, eu-west-1, and ap-southeast-1.
Allow each Region to continue accepting reads and writes if another Region becomes unavailable.
Scale automatically to absorb unpredictable surges up to 10× the previous peak traffic without manual capacity changes.
Minimize day-to-day operational overhead and database administration effort.
Which approach best satisfies all of these requirements?
Keep the existing RDS instance as the primary writer and configure AWS Database Migration Service (AWS DMS) to perform ongoing replication to read-only PostgreSQL instances in the other two Regions.
Deploy an Amazon ElastiCache for Redis cluster with Global Datastore across the three Regions and direct all writes to the primary Redis cluster.
Migrate the data to Amazon DynamoDB, configure a global table spanning us-east-1, eu-west-1, and ap-southeast-1, and use on-demand capacity mode (with adaptive capacity).
Create an Aurora PostgreSQL global database with secondary clusters in eu-west-1 and ap-southeast-1 and enable write forwarding.
Moving the workload to Amazon DynamoDB and enabling a global table that spans the three Regions meets every stated requirement. DynamoDB global tables replicate data automatically in a multi-active fashion, so each Region can serve local reads and writes even if another Region is unavailable. On-demand capacity mode eliminates capacity planning and instantly scales to new traffic peaks, while adaptive capacity protects against "hot" partitions without manual tuning. The alternative options all fail to meet one or more of the goals:
Aurora global databases have a single writable primary Region; secondary Regions (even with write-forwarding) incur cross-Region round-trips, so they cannot guarantee sub-10 ms local writes and become unavailable for writes if the primary fails.
Using AWS DMS to replicate RDS instances makes secondary databases read-only and still leaves a single write Region and capacity-planning burden.
ElastiCache for Redis Global Datastore is an in-memory cache, not a durable primary data store; it is limited by node memory size, incurs higher operational management for large persistent datasets, and does not automatically scale storage.
Therefore, migrating to DynamoDB with global tables and on-demand capacity is the only option that fully addresses performance, availability, scalability, and operational requirements.
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 are DynamoDB global tables and how do they work?
Open an interactive chat with Bash
What is the difference between on-demand capacity mode and provisioned capacity mode in DynamoDB?
Open an interactive chat with Bash
Why is DynamoDB suitable for unpredictable workloads compared to Amazon RDS or ElastiCache?
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