nerdexam
Amazon

SOA-C03 · Question #150

A web application runs on Amazon EC2 instances in the us-east-1 Region and the us-west-2 Region. The instances run behind an Application Load Balancer (ALB) in each Region. An Amazon Route 53 hosted…

The correct answer is A. Implement a Route 53 health check and a failover routing policy for the hosted zone. Configure. The requirement is classic active-passive (production in us-east-1, DR in us-west-2 "only for failover"). The most operationally efficient and purpose-built solution is Route 53 failover routing combined with health checks. With failover routing, Route 53 designates one record…

Submitted by brentm· Mar 5, 2026Reliability and business continuity

Question

A web application runs on Amazon EC2 instances in the us-east-1 Region and the us-west-2 Region. The instances run behind an Application Load Balancer (ALB) in each Region. An Amazon Route 53 hosted zone controls DNS records. The instances in us-east-1 are production resources. The instances in us-west-2 are for disaster recovery. EC2 Auto Scaling groups are configured based on the ALBRequestCountPerTarget metric in both Regions. A SysOps administrator must implement a solution that provides failover from us-east-1 to us- west-2. The instances in us-west-2 must be used only for failover. Which solution will meet these requirements?

Options

  • AImplement a Route 53 health check and a failover routing policy for the hosted zone. Configure
  • BImplement a Route 53 health check and a latency routing policy for the hosted zone. Configure
  • CIn us-east-1, create an Amazon CloudWatch alarm that enters ALARM state when an EC2
  • DIn us-west-2, create an Amazon CloudWatch alarm that enters ALARM state when resources in

How the community answered

(20 responses)
  • A
    75% (15)
  • B
    15% (3)
  • C
    5% (1)
  • D
    5% (1)

Explanation

The requirement is classic active-passive (production in us-east-1, DR in us-west-2 "only for failover"). The most operationally efficient and purpose-built solution is Route 53 failover routing combined with health checks. With failover routing, Route 53 designates one record as PRIMARY (us- east-1) and another as SECONDARY (us-west-2). Route 53 continuously evaluates the health check associated with the primary endpoint (commonly the ALB DNS name or a specific health-check path). If the primary fails, Route 53 automatically returns the secondary record, directing client DNS resolution to the DR region. This ensures us-west-2 is used only when us- east-1 is unhealthy, directly matching the requirement.

Topics

#Route 53#failover routing#health checks#disaster recovery

Community Discussion

No community discussion yet for this question.

Full SOA-C03 Practice