You are asked to configure Azure virtual machine (VM) connectivity between two virtual networks (VNets) in the same Azure Resource Group.
The solution must support an application that requires connectivity using IPv6 and may not fall back to IPv4 for compliance reasons within the application being hosted. The application must also support IPv6 clients on the public Internet.
You need to implement these requirements.
What three actions should you perform? Each correct answer presents part of the solution.
Within Azure IPv6 is supported but is limited to certain restrictions and requires carful configuration and planning. In this case you should add an IPv6 endpoint to each VM in the application because IPv6 address are not added by default and must be explicitly defined.
You should also deploy two load balancers. In Azure networking IPv6 to IPv6 communication is not supported, so you have to configure routing to first pass to a load balancer, which can communicate to another load balancer to complete the connectivity.
You also need to add a public IPv6 address to one of the load balancers to support connectivity to the Internet based IPv6 based machines.
You should not add an NSG to subnets hosting the VMs to block IPv4 connectivity. Cross VNet connectivity is not possible without the use of a load balancer. In this case because the load balancer will route the traffic, you do not need to consider IPv4 blocking here.
You should not add one Azure Load Balancer to the resource group because this will not support connectivity between to disparate VNets over IPv6.