Using Transit Gateway Route Tables for VPC Segmentation
A company has a central networking account that hosts a transit gateway (TGW). Multiple VPCs from various accounts are attached to the TGW. The security team wants to ensure that only specific VPCs can communicate with each other, but all VPCs need access to a shared services VPC. Which configuration should be used?
Quick Answer
The correct answer is to create separate transit gateway route tables for each VPC and only propagate the shared services VPC routes. This works because transit gateway route tables control which VPCs can communicate through transitive routing; by isolating each VPC into its own route table and selectively propagating only the shared services routes, you prevent any two non-shared VPCs from learning each other’s routes, while still granting all VPCs access to the shared services VPC. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of transit gateway route tables for VPC segmentation, a common pattern for multi-account network isolation. A frequent trap is assuming a single route table with route propagation from all VPCs will work, but that would allow full mesh connectivity. Instead, remember the memory tip: “One table per VPC, only share the services.” This ensures strict isolation while preserving shared access.
⚠ Common exam trap
Candidates often assume a single TGW route table with security groups can control inter-VPC traffic, but security groups cannot be applied to transit gateway attachments—they only work at the instance or ENI level, and TGW route tables control routing, not filtering.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create separate TGW route tables for each VPC and only propagate the shared services VPC routes.
Using separate TGW route tables for each VPC allows you to control which VPCs can communicate by selectively propagating only the shared services VPC routes into each VPC's route table. This ensures all VPCs can reach the shared services VPC, while VPCs that do not have each other's routes in their respective route tables cannot communicate directly. This approach leverages the transitive routing capability of the transit gateway while maintaining strict isolation between non-shared VPCs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a VPC peering connection between each pair of VPCs that need to communicate.
Why it's wrong here
This does not leverage the TGW and is not scalable.
- ✗
Use AWS PrivateLink to connect VPCs to the shared services VPC.
Why it's wrong here
PrivateLink is for accessing services, not for routing between VPCs.
- ✗
Use a single TGW route table for all attachments and control traffic with security groups.
Why it's wrong here
A single route table would allow all VPCs to communicate by default.
- ✓
Create separate TGW route tables for each VPC and only propagate the shared services VPC routes.
Why this is correct
This isolates VPCs from each other while allowing all to reach shared services.
Go deeper
Related to this question
About these practice questions
This SAP-C02 question is part of Courseiva's 1,660-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SAP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses AWS Organizations with a multi-account setup. The central IT team manages a shared services VPC in the network account, which hosts a NAT gateway, a VPN connection to the on-premises network, and a transit gateway. Several application accounts have VPCs attached to the transit gateway. Recently, the application teams report that they cannot reach the on-premises network through the VPN. The network team confirms that the VPN is up and routes are propagated in the transit gateway route tables. However, the application VPCs are not receiving the routes. What is the MOST likely cause?
hard- A.The application VPCs have route tables that override the transit gateway routes with local routes.
- B.The VPN connection is not configured to advertise the on-premises CIDR to the transit gateway.
- C.The application VPCs have security groups that block traffic to the on-premises network.
- ✓ D.The transit gateway route tables are not associated with the application VPC attachments.
Why D: The most likely cause is that the transit gateway route tables are not associated with the application VPC attachments. Even if the VPN routes are propagated into the transit gateway route tables, the application VPCs will not receive those routes unless their VPC attachments are explicitly associated with the correct transit gateway route table. Without this association, the transit gateway does not propagate routes to the attached VPCs, leaving them unable to reach the on-premises network.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.