An administrator has created a new overlay network. Which is intended for the company’s user VMs. The cluster has these characteristics: *…

For VMs within a VPC to access external networks, a route must exist to direct traffic outside the overlay network. Since the VMs cannot reach external resources even by IP address, the issue is with routing, not DNS. In a standard configuration using NAT for external access, a default route (0.0.0.0/0) must be configured in the VPC's route table. This route directs all traffic not destined for another subnet within the VPC to the external network connection, enabling outbound communication.

A. While possible, a missing default route for the specific new network is a more direct and common cause for this isolated issue than a cluster-wide underlying network problem.

B. The problem states that resources are unreachable "even by IP address," which explicitly indicates the issue is not related to DNS name resolution.

C. This option is too vague. The VPC and its subnet are created; the issue lies in the routing configuration that allows traffic to exit the VPC.

1. Nutanix Flow Virtual Networking Guide v6.7, "Configuring Virtual Private Cloud (VPC) > Creating a Route Table". The guide specifies: "To provide external network access for a VPC, you must configure a default route (destination prefix 0.0.0.0/0)."

2. Nutanix Bible, "Flow Virtual Networking" chapter. This resource details that for a VM to communicate externally, its VPC must have a route table with a default route pointing to the NAT or No-NAT external network.