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 ALSet up the same configuration in the us-west-1 VPC. Create an Amazon Route 53 hosted zone. Create separate records for each ALEnable 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 VPCreate an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in the us-east-1 VPPlace the Auto Scaling group behind the ALB. Set up the same configuration in the us-west-1 VPCreate 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:
The solution suggests VPC peering between the us-east-1 and us-west-1 VPCs. However, this does not meet the requirement of having a disaster recovery environment with active-passive failover, as traffic cannot be routed to instances in a different VPC without specific routing and inter-region configurations.
While this option provides an ALB and Auto Scaling group in the us-east-1 region, it lacks a proper disaster recovery setup in us-west-1. The description implies having a similar configuration in us-west-1, but it fails to mention the routing and failover mechanisms needed for true active-passive setup.
This option correctly implements ALBs and Auto Scaling groups in both regions with health checks and a failover routing policy through Amazon Route 53. This meets the requirements for high availability and disaster recovery by ensuring traffic can be rerouted to the us-west-1 region during failures in us-east-1.
Similar to option A, this option involves VPC peering and extends the ALB across both VPCs. However, it does not adequately address the disaster recovery requirement since it lacks separate configurations for handling traffic and failover in an active-passive setup.
I classify 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 VPCreate an Auto Scaling group that deploys the EC2 instances across the multiple Availability Zones in the us-east-1 VPPlace the Auto Scaling group behind the ALB. Set up the same configuration in the us-west-1 VPCreate an Amazon Route 53 hosted zone. Create separate records for each ALB. Enable health checks and configure a failover routing policy for each record.