The most professional way to evaluate this question is to map the symptom to the Nutanix feature responsible for that function rather than reacting to secondary details in the prompt. The correct response is D, meaning
"Static routes for remote subnets on the VPC". A VPN showing an "Up" state confirms tunnel establishment, but it does not guarantee end-to-end reachability. Actual traffic flow still depends on route advertisement or static routing, proper prefixes, and correct MTU considerations. MTU planning matters because encapsulation adds overhead. When overlay, Geneve, VXLAN, or IPSec is present, a path that looks healthy at 1500 bytes can still fragment or drop larger frames unless the underlay and endpoints are sized correctly. Operationally, Flow Virtual Networking should be checked from the control plane outward: gateway health, peering state, route advertisement, ERP coverage, external path, and MTU when encapsulation is involved. A strong exam habit is to ask which Nutanix construct would have to change for the symptom or requirement to change. That mental shortcut usually separates the real answer from distractors that mention generic networking steps, disruptive resets, or unrelated configuration objects. Notice that A is not appropriate because NAT changes addressing.

A reliable method here is to translate the scenario into Nutanix terms-VPC routing, external connectivity, policy scope, identity mapping, or upgrade readiness-and then choose the answer that directly addresses that domain. The correct response is D, meaning "Create a VPC with subnets for each tier and configure the Externally Routable Prefix to include only web subnets.". The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. In lifecycle terms, Nutanix expects administrators to respect prerequisites, compatibility, and dependency order before enabling or upgrading Flow-related services. A strong exam habit is to ask which Nutanix construct would have to change for the symptom or requirement to change. That mental shortcut usually separates the real answer from distractors that mention generic networking steps, disruptive resets, or unrelated configuration objects. Notice that A does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. B does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. Seen operationally, the correct response is.

The clean way to read this scenario is to separate what is merely present in the environment from the single Nutanix construct that actually satisfies the requirement. The correct response is C, meaning "Associate a NAT external network for 0.0.0.0/0 and a NONAT external network for 10.50.0.0/16, 172.20.32.0/20.". The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. In practice, this falls into virtual network design: VPC structure, subnet type, external network behavior, routing intent, and address exposure are what determine the result.
Seen from a design perspective, the correct answer is the least ambiguous and most supportable implementation path inside Prism Central and AHV. Notice that A does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. B does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. Seen operationally, the correct response is the least disruptive and most deterministic one. It changes the exact Nutanix setting that governs the outcome instead of introducing workarounds elsewhere in the stack.

From a Nutanix exam perspective, this question is really testing whether the administrator understands the control point that actually governs the behavior shown in the scenario. The correct response is C, meaning
"Isolation Policy". An Isolation Policy is built to stop communication between defined groups. Unlike an application policy, it is intended to create a hard boundary, making it the correct choice when the requirement is "no traffic between these entities." Quarantine is the fastest containment mechanism in Flow Network Security. It is specifically intended for suspected or compromised workloads that must be isolated immediately without redesigning broader application rules. This is a Flow policy design question, so categories, secured entities, rule direction, policy mode, and policy precedence matter more than simple IP connectivity assumptions. By contrast, A does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. B does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. For exam preparation, remember that Nutanix usually separates discovery from enforcement, routing from NAT, and access policy from identity mapping..