A company has two VPC networks named VPC A and VPC B. The VPC A CIDR block is 10.0.0.0/16 and the VPC B CIDR block is 172.31.0.0/16. The company wants to establish a VPC peering connection named pcx-12345 between both VPCs.
Which rules should appear in the route table of VPC A after configuration? (Choose two.)
To enable routing between VPC A and VPC B via the VPC peering connection, VPC A's route table must include two key rules: First, it must contain a local route for its own CIDR block (10.0.0.0/16, Target: Local) to handle internal traffic within VPC A. Second, it needs a route for the CIDR block of VPC B (172.31.0.0/16, Target: pcx-12345) to direct traffic to VPC B via the peering connection pcx-12345.
Yes, A and D. lookthe table on this doc https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-routing.html
I agree with A and D
A and D
A and D are the right answers
While AD is correct, the question itself is not quite clear. Option A - routes already are there, they not "will appear" after configuring VPC peering
Ans: D
Local Route: Destination: VPC A CIDR (10.0.0.0/16) Target: Local (implicitly points to the VPC itself) Explanation: This route ensures that traffic within VPC A (between instances with IP addresses in the 10.0.0.0/16 range) stays local and doesn’t need to go through the peering connection. Route to Peer VPC B: Destination: VPC B CIDR (172.31.0.0/16) Target: VPC peering connection ID (pcx-12345) Explanation: This route directs traffic destined for VPC B (IP addresses in the 172.31.0.0/16 range) to the VPC peering connection, allowing communication between instances in VPC A and VPC B.