Route Table Question

[JordanP]

Hello, and thank you for the great bank of questions!

In the following question, I’m hoping someone could explain how a single route table would be able to achieve the desired outcome. The answer to this question states “Create a new route table for VPC A, with unique route entries for the two EC2 servers in VPC B and VPC C.”

I do not understand how a single route table could work for this setup…You would need at least 2. The VPC peering connections are unique (with unique IDs) and must be referenced uniquely. You’d have x2 /32 routes to 10.0.0.10 in the same shared route table and that isn’t possible.

I could only see this working with 2 unique route tables. x2 with 10.0.0.10/32 routes to VPC A and B accordingly.

First sentence of question (for reference)

<b style=”font-family: inherit; font-size: inherit;”>Category: ANS – Network Design

A company is setting up a central Virtual Private Cloud named VPC A with one subnet and two VPC peering connections.

[Carlo-TutorialsDojo]

Hello JordanP,

We appreciate your feedback.

Yes, we can’t have two identical entries in a single RT, so there must be 2 RTs in the VPC A, each having an association with different subnets. Both RTs will contain destination routes to 10.0.0.0/16 with different peering targets.

For example:

VPC A -subnet1 RT:

10.0.0.0/16 : pcx-aaabbb

VPC A -subnet2 RT:

10.0.0.0/16 : pcx-aaaccc

We’ll improve the wording of the given answer.

I hope this helps. Let me know if you have further questions.

Regards,

Carlo @ Tutorials Dojo