AdventureWorks plans a dual-stack VNet in West Europe with both IPv4 (10.50.0.0/16) and IPv6 (2001:db8:abcd::/48) address spaces. They deployed two VMs but the team cannot ping over IPv6 between the VMs. Which requirement or limitation most likely explains the lack of IPv6 connectivity?
Choose an answer
Tap an option to check your answer.
Correct answer: Each VM NIC must be configured with an IPv6 address (Azure does not automatically assign an IPv6 to a VM NIC) and the VM OS must have IPv6 enabled; additionally, NSG rules for IPv6 must allow the traffic separately from IPv4 rules..
Why this is the answer
The correct answer highlights three crucial aspects for IPv6 connectivity in Azure VMs. First, Azure does not automatically assign IPv6 addresses to VM NICs; you must explicitly configure them. Second, the VM's operating system must have IPv6 enabled, as some OS images might disable it by default. Third, Network Security Group (NSG) rules are protocol-specific. If IPv4 rules allow traffic, separate IPv6 rules are still required to permit IPv6 traffic. The other options are incorrect. Azure dual-stack VNets fully support IPv6 for VMs, not just PaaS services. IPv6 in Azure does not use NAT64 by default for internal VNet communication, and Azure NAT Gateway is primarily for outbound IPv4 connectivity. Finally, Global VNet peering is unrelated to IPv6 functionality within a single VNet.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed