AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company runs a latency-sensitive payment-processing workload in the us-east-1 Region. The workload uses an Amazon ECS cluster (EC2 launch type) with stateless microservices behind an Application Load Balancer, an Amazon Aurora MySQL DB cluster, and an Amazon ElastiCache for Redis cluster that stores session data.
Compliance rules require a recovery point objective (RPO) of 1 minute and a recovery time objective (RTO) of 5 minutes for a complete Regional failure. Management insists on a solution that is less costly than an active-active multi-Region deployment but still meets the objectives.
Which solution meets these requirements?
Implement a pilot-light strategy that replicates only the Aurora database to another Region, stores container images in Amazon ECR with cross-Region replication, and creates the ECS cluster, Redis nodes, and load balancer with AWS CloudFormation when a disaster is declared.
Deploy a fully active-active architecture in two Regions with separate Aurora writer clusters, application-level replication for the Redis data, full-sized ECS services, and weighted Amazon Route 53 routing between the Regions.
Deploy a warm-standby environment in a second Region: add an Aurora global database secondary cluster and a Redis Global Datastore replica, run a scaled-down copy of the ECS services (one task per service) behind an Application Load Balancer, enable cross-Region image and data replication, and use Amazon Route 53 failover routing to switch traffic when health checks fail.
Use AWS Elastic Disaster Recovery (AWS DRS) to continuously replicate the ECS instances and Redis nodes to a second Region, convert the Aurora cluster to an Aurora global database, and rely on AWS DRS orchestration to launch all recovered resources after a disaster.
A warm-standby pattern keeps a scaled-down but fully functional copy of the entire stack running in a second Region. Aurora Global Database and ElastiCache for Redis Global Datastore replicate data with typical latencies of less than 1 second, so the RPO is well under 1 minute. Because the ECS services, ALB, and other infrastructure are already deployed (albeit at minimal size), the environment only needs to scale out and Route 53 needs to redirect traffic, which can be completed within the 5-minute RTO.
With AWS Elastic Disaster Recovery, compute resources are provisioned only after failover; its typical RTO is 5-20 minutes, so it cannot guarantee a 5-minute target. A pilot-light strategy runs no application tier at all, so provisioning the full stack usually takes tens of minutes, exceeding the RTO. An active-active design would meet the objectives but costs significantly more because both Regions run at full production scale at all times. Therefore, the warm-standby solution is the most cost-effective option that satisfies both the 1-minute RPO and 5-minute RTO.
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 warm-standby pattern in AWS architectures?
Open an interactive chat with Bash
How does Aurora Global Database ensure low replication latency?
Open an interactive chat with Bash
What is the difference between a warm-standby and an active-active architecture?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design Solutions for Organizational Complexity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access