AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A multinational SaaS provider is launching a stateless microservice that stores user session data in Amazon DynamoDB. Identical stacks will be deployed in the us-east-1 and eu-west-1 Regions, each fronted by an Application Load Balancer (ALB). Business-continuity requirements are:
Both Regions must actively accept read and write traffic during normal operation.
End users should automatically connect to the Region that offers the lowest latency.
If an entire Region becomes unavailable, all new client connections must shift to the remaining Region within 60 seconds without waiting for a DNS TTL to expire.
The recovery-point objective (RPO) for session data must be under 1 second.
Which architecture meets these requirements with the LEAST operational overhead?
Provision AWS Global Accelerator with endpoint groups for the two Regional ALBs, enable health checks, and store session data in an Amazon DynamoDB global table replicated between us-east-1 and eu-west-1.
Create Amazon Route 53 latency-based alias records that point to the two ALBs and associate health checks. Use an Amazon Aurora Global Database with a writer in us-east-1 and a read-only secondary in eu-west-1; promote the secondary to writer during failover.
Front the ALBs with a third-party anycast CDN that performs health-probe-based failover. Replicate session state between self-managed PostgreSQL databases in each Region using logical replication and AWS Lambda functions to promote the standby database when required.
Configure Amazon Route 53 failover routing with a primary alias record for the us-east-1 ALB and a secondary alias record for the eu-west-1 ALB. Persist session data in Amazon S3 and enable cross-Region replication.
AWS Global Accelerator provides two anycast static IP addresses that route each new connection over the AWS global network to the optimal Regional endpoint based on health, client location, and configured weights. Because Global Accelerator keeps its own health-check data plane, failover to a healthy endpoint group typically occurs within 30 seconds and is not limited by client-side DNS caching, satisfying the 60-second requirement.
DynamoDB global tables use an active-active replication model in which every replica table can accept writes and usually propagates changes to the other Region in under a second, giving an RPO of < 1 s while eliminating custom replication logic.
The alternative designs all fall short: Route 53 latency-based routing (with Aurora Global Database) still relies on DNS TTLs and supports writes in only one Region; Route 53 failover plus S3 replication is active-passive and cannot meet the RPO; the third-party CDN and self-managed databases introduce higher operational overhead and slower, manual failover steps. Therefore, the Global Accelerator + DynamoDB global tables solution is the only option that satisfies every stated requirement with minimal operational effort.
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.
Why is AWS Global Accelerator preferred over Route 53 for Region failover in this scenario?
Open an interactive chat with Bash
What makes DynamoDB global tables suitable for active-active architectures?
Open an interactive chat with Bash
How do health checks work with AWS Global Accelerator?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access