Answer-first summary for fast verification
Answer: Create a new customer-managed prefix list. Add all VPC CIDR ranges to the new prefix list. Update the route tables in each VPC to use the new prefix list ID as the destination and the appropriate transit gateway ID as the target.
The most operationally efficient way to add new VPC CIDR ranges to the route tables in each VPC, given the scenario, is to use a customer-managed prefix list. This approach allows for centralized management of CIDR ranges. By creating a new customer-managed prefix list and adding all VPC CIDR ranges to it, you can then update the route tables in each VPC to use the new prefix list ID as the destination and the appropriate transit gateway ID as the target. This method simplifies the process of adding new VPCs, as you only need to update the prefix list with the new CIDR ranges, and the changes will automatically propagate to all route tables that reference the prefix list. Option A is the correct choice because it provides a scalable and manageable solution for updating route tables with new VPC CIDR ranges. Options B, C, and D do not offer the same level of operational efficiency or scalability for managing route tables with a growing number of VPCs.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company utilizes transit gateways to facilitate traffic routing between its VPCs. Each transit gateway is configured with a single route table, which includes attachments and routes for VPCs within the same AWS Region. The VPC route tables also contain routes to all other VPC CIDR ranges accessible through the transit gateways, with some VPCs routing traffic through local NAT gateways.
The company anticipates adding numerous new VPCs and requires a solution to efficiently update the route tables in each VPC with the new VPC CIDR ranges.
What is the most operationally efficient solution to meet these requirements?
A
Create a new customer-managed prefix list. Add all VPC CIDR ranges to the new prefix list. Update the route tables in each VPC to use the new prefix list ID as the destination and the appropriate transit gateway ID as the target.
B
Turn on default route table propagation for the transit gateway route tables. Turn on route propagation for each route table in each VPC.
C
Update the route tables in each VPC to use 0.0.0.010 as the destination and the appropriate transit gateway ID as the target.
D
Turn on default route table association for the transit gateway route tables. Turn on route propagation for each route table in each VPC.