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 ALDeploy 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:
Inter-Region VPC peering cannot be used to span an Application Load Balancer (ALB) across both VPCs. Each ALB can only be associated with instances in a single VPC, and deploying EC2 instances in different VPCs managed by a single ALB is not feasible.
This option correctly outlines the deployment of an ALB in the us-east-1 Region and an Auto Scaling group across multiple AZs in both regions. Using Route 53 with a failover routing policy ensures high availability by directing traffic to the active region while performing health checks.
This option incorrectly suggests using inter-Region VPC peering to connect VPCs for an ALB that spans both VPCs. Like option A, an ALB cannot span multiple VPCs. The routing would also not be efficient, as it relies on VPC peering, which does not facilitate a multi-region disaster recovery model effectively.
While this option correctly mentions deploying separate ALBs in each region, it suggests creating separate Route 53 records for each region pointing to their respective ALBs. However, this does not utilize a failover mechanism effectively, which is necessary for an active-passive disaster recovery setup. Instead, a single Route 53 record with failover routing should be used.