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 A, meaning “Enable microsegmentation and network controller on the cluster.”. The Network Controller supplies the control-plane services required for Flow Virtual Networking. Without it, Prism Central cannot build and manage overlays, gateways, and related virtual networking constructs consistently across the cluster. In lifecycle terms, Nutanix expects administrators to respect prerequisites, compatibility, and dependency order before enabling or upgrading Flow-related services.

In other words, this is less about broad infrastructure suspicion and more about finding the exact Nutanix decision point that explains the behavior. Notice that B does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. C does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome here. In practice, administrators who anchor their decisions to Prism Central constructs—such as VPCs, external networks, ERPs, categories, and policy modes—arrive at the correct answer faster and avoid unnecessary changes.