Which solution will meet these requirements?
Create a VPC in us-east-1 and a VPC in us-west-1. Configure VPC peering. In the us-east-1 VPC, create an Application Load Balancer (ALB) that extends across multiple Availability Zones in both VPCs. Create an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in both VPCs. Place the Auto Scaling group behind the ALB.
Create a VPC in us-east-1 and a VPC in us-west-1. In the us-east-1 VPC, create an Application Load Balancer (ALB) that extends across multiple Availability Zones in that VPC. Create an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in the us-east-1 VPC. Place the Auto Scaling group behind the ALB. Set up the same configuration in the us-west-1 VPC. Create an Amazon Route 53 hosted zone. Create separate records for each ALB. Enable health checks to ensure high availability between Regions.
Create a VPC in us-east-1 and a VPC in us-west-1. In the us-east-1 VPC, create an Application Load Balancer (ALB) that extends across multiple Availability Zones in that VPC. Create an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in the us-east-1 VPC. Place the Auto Scaling group behind the ALB. Set up the same configuration in the us-west-1 VPC. Create an Amazon Route 53 hosted zone. Create separate records for each ALB. Enable health checks and configure a failover routing policy for each record.
Create a VPC in us-east-1 and a VPC in us-west-1. Configure VPC peering. In the us-east-1 VPC, create an Application Load Balancer (ALB) that extends across multiple Availability Zones in both VPCs. Create an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in both VPCs. Place the Auto Scaling group behind the ALB. Create an Amazon Route 53 hosted zone. Create a record for the ALB.
Explanations:
VPC peering cannot be used to extend an Application Load Balancer (ALB) across multiple VPCs. ALBs must be within the same VPC. Additionally, the setup described does not address disaster recovery since it does not involve separate configurations in both regions or health checks for failover.
This option sets up an ALB and Auto Scaling group in us-east-1 and replicates the same configuration in us-west-1, which is a good approach for high availability. However, it lacks the failover mechanism needed for active-passive disaster recovery, as it does not utilize Route 53 health checks or a routing policy to manage failover between the two regions effectively.
This option correctly establishes a separate ALB and Auto Scaling group in both us-east-1 and us-west-1, ensuring high availability in both regions. By creating Route 53 records for each ALB with health checks and a failover routing policy, it effectively enables disaster recovery, allowing traffic to failover to the secondary region when needed.
Similar to option A, this option incorrectly suggests VPC peering to extend an ALB across VPCs, which is not supported. It also does not properly address the need for active-passive failover since it only creates a single record for the ALB without health checks or routing policies to manage traffic failover.
I organize that the answer is:
Create a VPC in us-east-1 and a VPC in us-west-1. In the us-east-1 VPC, create an Application Load Balancer (ALB) that extends across multiple Availability Zones in that VPC. Create an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in the us-east-1 VPC. Place the Auto Scaling group behind the ALB. Set up the same configuration in the us-west-1 VPC. Create an Amazon Route 53 hosted zone. Create separate records for each ALB. Enable health checks and configure a failover routing policy for each record.