Which steps should a solutions architect take after creating a VPC in the us-east-1 Region?
Create a VPC in the us-west-1 Region. Use inter-Region VPC peering to connect both VPCs. Deploy an Application Load Balancer (ALB) spanning multiple Availability Zones (AZs) to the VPC in the us-east-1 Region. Deploy EC2 instances across multiple AZs in each Region as part of an Auto Scaling group spanning both VPCs and served by the ALB.
Deploy an Application Load Balancer (ALB) spanning multiple Availability Zones (AZs) to the VPC in the us-east-1 Region. Deploy EC2 instances across multiple AZs as part of an Auto Scaling group served by the ALB. Deploy the same solution to the us-west-1 Region. Create an Amazon Route 53 record set with a failover routing policy and health checks enabled to provide high availability across both Regions.
Create a VPC in the us-west-1 Region. Use inter-Region VPC peering to connect both VPCs. Deploy an Application Load Balancer (ALB) that spans both VPCs. Deploy EC2 instances across multiple Availability Zones as part of an Auto Scaling group in each VPC served by the ALB. Create an Amazon Route 53 record that points to the ALB.
Deploy an Application Load Balancer (ALB) spanning multiple Availability Zones (AZs) to the VPC in the us-east-1 Region. Deploy EC2 instances across multiple AZs as part of an Auto Scaling group served by the ALB. Deploy the same solution to the us-west-1 Region. Create separate Amazon Route 53 records in each Region that point to the ALB in the Region. Use Route 53 health checks to provide high availability across both Regions.
Explanations:
This option suggests using inter-Region VPC peering, which is not necessary for this setup. An Application Load Balancer (ALB) cannot span multiple VPCs across different Regions. The EC2 instances need to be deployed in each Region and managed independently, making this solution unfeasible for disaster recovery.
This option correctly outlines deploying an ALB in the us-east-1 Region and EC2 instances in multiple AZs. It also proposes replicating the solution in the us-west-1 Region. The use of Amazon Route 53 with a failover routing policy and health checks ensures high availability and disaster recovery, making it a valid approach.
This option incorrectly suggests deploying an ALB that spans both VPCs, which is not supported. Each VPC should have its own ALB, and the use of Route 53 should focus on routing to the correct ALB per Region rather than creating an inter-Region ALB.
While this option correctly mentions deploying separate ALBs in both Regions, it suggests creating separate Route 53 records that point to the ALB in each Region. This setup does not provide a true failover capability since it would not automatically switch traffic based on health checks unless explicitly configured with a failover policy, making it less effective for disaster recovery compared to option B.
As far as I’m aware, the answer is:
Deploy an Application Load Balancer (ALB) spanning multiple Availability Zones (AZs) to the VPC in the us-east-1 Region. Deploy EC2 instances across multiple AZs as part of an Auto Scaling group served by the ALB. Deploy the same solution to the us-west-1 Region. Create an Amazon Route 53 record set with a failover routing policy and health checks enabled to provide high availability across both Regions.