Which configuration will meet these requirements?
Deploy a copy of the stack in the us-west-2 Region. Create a single start of authority (SOA) record in Route 53 that includes the IP address from each ELB. Configure the SOA record with health checks. Use the ELB in us-east-1 as the primary record and the ELB in us-west-2 as the secondary record.
Deploy a copy of the stack in the us-west-2 Region. Create an additional A record in Route 53 that includes the ELB in us-west-2 as an alias target. Configure the A records with a failover routing policy and health checks. Use the ELB in us-east-1 as the primary record and the ELB in us-west-2 as the secondary record.
Deploy a new group of EC2 instances in the us-west-2 Region. Associate the new EC2 instances with the existing ELB, and configure load balancer health checks on all EC2 instances. Configure the ELB to update Route 53 when EC2 instances in us-west-2 fail health checks.
Deploy a new group of EC2 instances in the us-west-2 Region. Configure EC2 health checks on all EC2 instances in each Region. Configure a peering connection between the VPCs. Use the VPC in us-east-1 as the primary record and the VPC in us-west-2 as the secondary record.
Explanations:
Route 53 does not support creating an SOA record with IP addresses of ELBs. Health checks are not available for SOA records, and using a primary and secondary record for failover is not supported for this type of record.
This configuration correctly deploys a second stack in the us-west-2 Region and uses Route 53 failover routing policy with health checks. The A record setup ensures that traffic is routed to the primary ELB (us-east-1) and fails over to the secondary ELB (us-west-2) when necessary.
EC2 instances cannot be directly associated with an ELB in different Regions. The ELB in one region cannot manage EC2 instances in another region, and the configuration described is not possible in terms of cross-Region ELB and EC2 management.
While peering connections can be established between VPCs, this does not help with high availability or traffic failover across Regions. Additionally, EC2 health checks across VPCs cannot be used in the manner described here for routing decisions.
I strategize that the answer is:
Deploy a copy of the stack in the us-west-2 Region. Create an additional A record in Route 53 that includes the ELB in us-west-2 as an alias target. Configure the A records with a failover routing policy and health checks. Use the ELB in us-east-1 as the primary record and the ELB in us-west-2 as the secondary record.