An administrator needs to use Prism Central to identify a subnet belonging to a VPC.

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 “The subnet will be identified as type Overlay.”. 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. 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. The key takeaway is that Flow is intentionally modular. Networking objects determine reachability, security objects determine permission, and lifecycle steps determine supportability. Mixing those layers usually produces the distractor answers. A strong exam habit is to ask which Nutanix construct would have to change for the symptom or requirement to change. That mental shortcut.