SOA-C02 · Question #747
A company hosts applications in private subnets across multiple Availability Zones within a VPC. The company has established a VPC peering connection between an application VPC and a second VPC. The…
The correct answer is B. Update the route tables of each VPC to point to the peer VPC. A VPC peering link doesn’t add routes automatically. You must add routes in each VPC’s route tables that target the peering connection for the other VPC’s CIDR range so traffic can flow
Question
A company hosts applications in private subnets across multiple Availability Zones within a VPC. The company has established a VPC peering connection between an application VPC and a second VPC. The peering connection is active. However, resources in the application VPC cannot communicate with resources in the second VPC. A SysOps administrator must resolve the connectivity issue. Which solution will meet this requirement?
Options
- AUse AWS Resource Access Manager (AWS RAM) to share the private subnets.
- BUpdate the route tables of each VPC to point to the peer VPC.
- CEnable default route propagation in the route tables of both VPCs.
- DUpdate both VPCs to be in the same AWS Region.
How the community answered
(38 responses)- A3% (1)
- B79% (30)
- C8% (3)
- D11% (4)
Explanation
A VPC peering link doesn’t add routes automatically. You must add routes in each VPC’s route tables that target the peering connection for the other VPC’s CIDR range so traffic can flow
Topics
Community Discussion
No community discussion yet for this question.