AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company hosts its application in the AWS Cloud. The application runs on Amazon EC2 instances behind an Elastic Load Balancer in an Auto Scaling group and with an Amazon DynamoDB table. The company wants to ensure the application can be made available in another AWS Region with minimal downtime.
What should a solutions architect do to meet these requirements with the LEAST amount of downtime?
Other
Community
UAnonymous
A
Create an Auto Scaling group and a load balancer in the disaster recovery Region. Configure the DynamoDB table as a global table. Configure DNS failover to point to the new disaster recovery Region's load balancer.
B
Create an AWS CloudFormation template to create EC2 instances, load balancers, and DynamoDB tables to be launched when needed. Configure DNS failover to point to the new disaster recovery Region's load balancer.
C
Create an AWS CloudFormation template to create EC2 instances and a load balancer to be launched when needed. Configure the DynamoDB table as a global table. Configure DNS failover to point to the new disaster recovery Region's load balancer.
D
Create an Auto Scaling group and load balancer in the disaster recovery Region. Configure the DynamoDB table as a global table. Create an Amazon CloudWatch alarm to trigger an AWS Lambda function that updates Amazon Route 53 pointing to the disaster recovery load balancer.
Explanation:
Explanation
Correct Answer: A
Why Option A is correct:
- Auto Scaling group and load balancer in DR Region: This ensures compute resources are already running and ready in the disaster recovery region, minimizing downtime during failover.
- DynamoDB global table: DynamoDB global tables provide multi-region replication with automatic conflict resolution, ensuring data is synchronized across regions in near real-time.
- DNS failover: Route 53 health checks and DNS failover provide a quick way to redirect traffic to the DR region when the primary region fails.
Why other options are incorrect:
Option B: Creating resources "when needed" (on-demand) introduces significant downtime as EC2 instances, load balancers, and DynamoDB tables need to be provisioned during the disaster event. DynamoDB tables cannot be created instantly and require data migration.
Option C: Similar to B, creating EC2 instances and load balancers "when needed" introduces provisioning delays. While using DynamoDB global tables is correct, the on-demand provisioning of compute resources adds unnecessary downtime.
Option D: While having pre-provisioned resources in the DR region is good, using CloudWatch alarms and Lambda functions for DNS updates is more complex and potentially slower than using Route 53's built-in health checks and DNS failover capabilities.
Key Principles for Minimal Downtime Disaster Recovery:
- Pre-provision resources in the DR region (warm standby)
- Use managed services with built-in multi-region capabilities (DynamoDB global tables)
- Leverage AWS DNS services (Route 53) for quick traffic redirection
- Automate failover using AWS-native health monitoring and routing mechanisms
Comments
Loading comments...