Sample question 1 — Design for New Solutions
A modernization delivery group supporting a rapidly growing global workload must tolerate an Availability Zone failure without interrupting a public application. Which specific AWS service or approach is the right choice for this architecture?
- A. Place an Application Load Balancer in multiple Availability Zones and run Auto Scaling instances across those zones.
- B. Use AWS Elastic Disaster Recovery to continuously replicate servers and launch recovery instances when needed.
- C. Store credentials in AWS Secrets Manager and enable rotation using a supported rotation function.
- D. Run Amazon ECS tasks in private subnets behind an internal or internet-facing load balancer as required.
Answer: A. Option A is correct: "Place an Application Load Balancer in multiple Availability Zones and run Auto Scaling instances across those zones." This is the AWS-recommended way to address Highly available web tier, which is exactly what the scenario requires. Option C is incorrect because Selecting Secrets rotation architecture would apply "Store credentials in AWS Secrets Manager and enable rotation using a…", which fits a different production need than the one above. Option B is incorrect because Disaster recovery replication addresses a team that must provide rapid recovery for an existing server estate after a…, not the failure mode this stem describes for Highly available web tier. Option D is incorrect because Private container platform is the wrong control here — it is built for a team that must run containerized services without assigning public IP…, not this scenario's constraint.
