
Ultimate access to all questions.
A company has an AWS Site-to-Site VPN connection between AWS and its branch office, terminating at a transit gateway with static routing. The transit gateway route table contains multiple static route entries targeting specific subnets at the branch office. A network engineer identifies that the connectivity issues stem from the expansion of underlying subnet ranges at the branch office during routine maintenance.
What solution will resolve this issue with the MINIMAL administrative overhead for future subnet expansions?
A
Determine a supernet for the branch office. In the transit gateway route table, add an aggregate route that targets the VPN attachment. Replace the specific subnet routes in the transit gateway route table with the new supernet route.
B
Create an AWS Direct Connect gateway and a transit VIF. Associate the Direct Connect gateway with the transit gateway. Create a propagation for the Direct Connect attachment to the transit gateway route table.
C
Create a dynamically routed VPN connection on the transit gateway. Connect the dynamically routed VPN connection to the branch office. Create a propagation for the VPN attachment to the transit gateway route table. Remove the existing static VPN connection.
D
Create a prefix list that contains the new subnets and the old subnets for the branch office. Remove the specific subnet routes in the transit gateway route table. Create a prefix list reference in the transit gateway route table.