ANS-C01 · Question #198
A company has a hybrid IT setup that includes services that run in an on-premises data center and in the AWS Cloud. The company is using AWS Direct Connect to connect its data center to AWS. The…
The correct answer is A. Create a new Site-to-Site VPN tunnel for the IPv6 traffic. D. Add a new IPv6 peer in the existing VIF. Use the IPv6 address provided by Amazon on the peer. To transition hybrid connectivity to IPv6 with minimal downtime, the company should add a new IPv6 peer to the existing Direct Connect virtual interface and create new Site-to-Site VPN tunnels specifically for IPv6 traffic.
Question
A company has a hybrid IT setup that includes services that run in an on-premises data center and in the AWS Cloud. The company is using AWS Direct Connect to connect its data center to AWS. The company is using one AWS Site-to-Site VPN connection as backup and requires a backup connectivity option to always be present. The company is transitioning to IPv6 by implementing dual-stack architectures. Which combination of steps will transition the data center's connectivity to AWS in the LEAST amount of time? (Choose two.)
Options
- ACreate a new Site-to-Site VPN tunnel for the IPv6 traffic.
- BCreate a new dual-stack Site-to-Site VPN connection between the data center and AWS.
- CAssociate a new dual-stack public VIF with the Direct Connect connection. Migrate the Direct
- DAdd a new IPv6 peer in the existing VIF. Use the IPv6 address provided by Amazon on the peer
- ESend IPv6 traffic between the data center and AWS in a tunnel inside the existing IPv4 tunnels.
How the community answered
(37 responses)- A57% (21)
- B11% (4)
- C27% (10)
- E5% (2)
Why each option
To transition hybrid connectivity to IPv6 with minimal downtime, the company should add a new IPv6 peer to the existing Direct Connect virtual interface and create new Site-to-Site VPN tunnels specifically for IPv6 traffic.
Creating new Site-to-Site VPN tunnels specifically for IPv6 traffic is a non-disruptive way to introduce IPv6 support to the backup VPN connectivity without affecting the existing IPv4 VPN connection, thereby minimizing downtime during the transition.
Creating an entirely new dual-stack Site-to-Site VPN connection might involve more configuration and potential disruption compared to simply adding specific IPv6 tunnels, depending on whether the existing IPv4 connection can be augmented or if a completely separate connection is mandated.
Public VIFs are designed for accessing public AWS services over Direct Connect, not for private connectivity to customer VPCs or data centers, and creating a new VIF might take longer than just adding an IPv6 peer to an existing private VIF.
Adding a new IPv6 peer to an existing Direct Connect virtual interface (VIF) is the most efficient and least disruptive method to enable dual-stack (IPv4 and IPv6) support for Direct Connect, allowing the existing IPv4 traffic to continue uninterrupted while IPv6 is introduced.
Sending IPv6 traffic in a tunnel inside existing IPv4 tunnels (IPv6-in-IPv4 encapsulation) adds overhead and complexity, and is not the native, least-time method for transitioning to a dual-stack architecture supported by Direct Connect and Site-to-Site VPN.
Concept tested: Hybrid connectivity dual-stack IPv6 transition
Source: https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVIFs.html
Community Discussion
No community discussion yet for this question.