AWS Transit Gateway Route Propagation for Dynamic CIDR Updates
Short answer
A Configure route propagation for VPC-A to the VPN attachment route table.
Question
Key Takeaways
The core concept is that enabling route propagation allows the Transit Gateway to dynamically learn new prefixes from attached VPCs without manual intervention or complex automation.
This question tests the capability of AWS Transit Gateway route propagation to automatically update routes when VPC CIDR blocks change, ensuring seamless on-premises connectivity.
Common mistake: Candidates often choose options involving Lambda or EventBridge (C/D) thinking they need custom logic to detect changes, failing to realize that native route propagation handles this automatically.
Expert Analysis
Why the Answer Is Correct
Enabling route propagation for a specific VPC attachment on the Transit Gateway's route table causes the TGW to automatically advertise all associated VPC CIDR ranges to connected VPN attachments. When the VPC owner adds a secondary CIDR block, the route propagation mechanism automatically includes this new range in the updates sent to the Site-to-Site VPN, allowing the on-premises router to learn the new path. This meets the requirement for operational efficiency as it requires zero code or manual steps.
Why the Other Options Are Wrong
Option B requires manual updates every time a CIDR changes, violating the 'future-proof' and 'operational efficiency' requirements. Options C and D involve creating unnecessary infrastructure (Lambda, EventBridge/CloudWatch) to monitor for changes. While technically possible, this introduces significant operational overhead, complexity, and potential points of failure compared to the native feature provided by AWS.
Community Comment Notes
Comments [1], [2], and [3] unanimously support Option A, highlighting that route propagation automatically handles the addition of new CIDRs to the VPN attachment route table without manual intervention.
Exam Strategy
Always look for native AWS features that handle automation before considering custom solutions with Lambda or CloudWatch. If a service can natively propagate routes or states, using native capabilities is almost always the most operationally efficient choice.
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
woorkim 👍 1 Answered ABy enabling route propagation for VPC-A to the VPN attachment route table, any new CIDR ranges added to VPC-A will automatically be propagated to the VPN attachment route table. This ensures that on-premises networks can reach the new workloads in VPC-A without manual updates.
-
ashk123456 👍 1 Answered AWhen VPC-A adds a new CIDR, the route should automatically propagate to the VPN attachment route table, ensuring that the on-premises network learns the new CIDR without manual updates.
-
c1193d4 👍 1 Answered AThe 2nd CIDR will be automatically added to the VPC-A and will be propagated to the VPN attachment RT.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All ANS-C01 Questions
Access 137 questions with complete answers and detailed explanations.
View Full ANS-C01 Practice Test →