NCP-NS-7.5 Nutanix Certified Professional - Network and Security (NCP-NS) 7.5 Questions and Answers

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 B, meaning “The Allow All IPv6 option in the policy was selected.”. 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.” Application Policies are the most appropriate way to model legitimate workload communication in a tiered application. They allow administrators to express which sources, destinations, and services are required instead of relying on broad network access. 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. 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 sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. C sounds plausible, but it does not align with the specific.

What makes this a strong certification question is that several answers look technically related, but only one aligns with the exact behavior of Flow networking or Flow security. The correct response is B, meaning “Mismatch in ERP configuration in user and Transit VPC”. A Floating IP is the normal mechanism for exposing a workload in an overlay-backed VPC to external clients. It preserves internal VM addressing while publishing a reachable external address through the VPC’s north-south path. Externally Routable Prefixes determine which overlay prefixes are advertised beyond the VPC. If the ERP does not cover the workload subnet, upstream devices never learn a valid return path, even when the local VPC appears healthy. 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. 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. C addresses exposure of a single VM, not the broader routing or security behavior under discussion. Seen operationally, the correct response is the least disruptive and most deterministic.

This item is best solved by thinking like an operator in Prism Central: first identify whether the problem is design, control-plane state, or policy logic, then pick the option tied to that layer. The correct response is B, meaning “Use VM categories to define the secured and allowed entities.”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. 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. 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 sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. C sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. In practice, administrators who anchor their decisions to Prism Central constructs—such as VPCs,.

What makes this a strong certification question is that several answers look technically related, but only one aligns with the exact behavior of Flow networking or Flow security. The correct response is BD, which corresponds to The source ip address is 10.38.174.5 and source port is TCP/123. and 10.38.174.57 is sending a packet destined to UDP 123.. Policy hitlogs provide precise evidence of what Flow evaluated, including source, destination, protocol, and rule outcome. In troubleshooting, that makes hitlogs one of the best places to confirm whether traffic matched an allow or deny decision. From a troubleshooting standpoint, the validation path is policy scope first, then categories or identity mapping, then hitlog evidence, service definition, and finally policy precedence. 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. C 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.

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 C, meaning “Increase the MTU by an additional 58 bytes for the Geneve header.”. 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. Service insertion introduces an additional dataplane hop through a network function VM. That makes correct vNIC pairing, health monitoring, and MTU sizing essential, because steering can fail even when the firewall appliance itself appears powered on. 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. 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 A does not fit because it targets a different layer of the Nutanix networking and security stack than the one causing the outcome.

What makes this a strong certification question is that several answers look technically related, but only one aligns with the exact behavior of Flow networking or Flow security. The correct response is B, meaning “Blocks all traffic that is not allowed”. Policy hitlogs provide precise evidence of what Flow evaluated, including source, destination, protocol, and rule outcome. In troubleshooting, that makes hitlogs one of the best places to confirm whether traffic matched an allow or deny decision. 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. C 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.

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 D, meaning “Change policy mode from Monitor to Enforce.”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. 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.

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 sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. B sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. For exam preparation, remember that Nutanix usually separates discovery from enforcement, routing from NAT, and access policy from identity mapping. Choosing the layer that truly owns the function is what leads to the right answer.

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 C, meaning “Check the security policies again to ensure that the rule allowing port 3306 from Web - > Database is applied and active, then check the policy enforcement mode to ensure it is in Enforcement Mode.”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. From a troubleshooting standpoint, the validation path is policy scope first, then categories or identity mapping, then hitlog evidence, service definition, and finally policy precedence. 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 sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. The key takeaway is that Flow is intentionally.

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 “Destination prefix: 172.16.2.0/24, Next-Hop: Ext_Net_Internal”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. 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.

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 is not appropriate because NAT changes addressing behavior and does not solve the routing or policy condition described in the scenario. B is not appropriate because NAT changes addressing behavior and does not solve the routing or policy condition described in the scenario. 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.

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 “Review the Alerts and Events in Prism Central to confirm if the affected host shows NIC or uplink errors.”. 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.

Notice that B is a disruptive action and does not address the actual control-plane or policy requirement being tested. C 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.

This item is best solved by thinking like an operator in Prism Central: first identify whether the problem is design, control-plane state, or policy logic, then pick the option tied to that layer. The correct response is A, meaning “Use Flow Network Visualization to capture observed flows and convert them into microsegmentation security policies.”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. 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.

Notice that B sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. C 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.

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 A, meaning “Network Controller must be enabled in Prism Central.”. 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. 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 “Create the Policy in Monitor mode, review the discovered traffic, allow the required traffic flows, and move Policy to Enforce mode.”. Monitor mode is designed for observation rather than enforcement. In Nutanix Flow, it discovers and visualizes matching traffic so an administrator can validate real application behavior before converting the policy to active enforcement. That is why the correct response focuses on visibility, not blocking. Enforce mode is the stage where Flow stops acting like a discovery tool and starts behaving like a stateful control point. Traffic allowed by the policy continues normally, while traffic that does not match an allowed rule is denied according to policy logic. 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. Notice that A sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. B sounds plausible, but it does not.

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 C, meaning “Assign a NAT External Network & ERP 10.1.0.0/22”. Externally Routable Prefixes determine which overlay prefixes are advertised beyond the VPC. If the ERP does not cover the workload subnet, upstream devices never learn a valid return path, even when the local VPC appears healthy. 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 is not appropriate because NAT changes addressing behavior and does not solve the routing or policy condition described in the scenario. B is not appropriate because NAT changes addressing behavior and does not solve the routing or policy condition described in the scenario. That is the underlying Nutanix principle being validated: solve the issue at the feature that owns the behavior, not by changing unrelated infrastructure settings that happen to sound network-oriented. A strong exam habit is to ask which Nutanix construct would have to change for.

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 D, meaning “Create a Layer 2 connectivity between the subnets and perform live migration.”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. 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.

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. That is the underlying Nutanix principle being validated: solve the issue at the feature that owns the behavior, not by changing unrelated infrastructure settings that happen to sound network-oriented.

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 C, meaning “4 GB of memory and 3 vCPUs”. 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. 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.

This item is best solved by thinking like an operator in Prism Central: first identify whether the problem is design, control-plane state, or policy logic, then pick the option tied to that layer. The correct response is D, meaning “Ensure all CVMs have network connectivity to Prism Central.”. 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.

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 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. That is the underlying Nutanix principle being validated: solve the issue at the feature that owns the behavior, not by changing unrelated infrastructure settings that happen to sound network-oriented.

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 A, meaning “Overlay subnets”. A Transit VPC acts as the routing hub for spoke VPCs and is commonly used when administrators want shared services or inter-VPC communication without pushing route complexity into the physical network. 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.

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. That is the underlying Nutanix principle being validated: solve the issue at the feature that owns the behavior, not by changing unrelated infrastructure settings that happen to sound network-oriented.

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 B, meaning “Create an Intra-Tier Rule specifying the mysql service as the allowed traffic.”. Application Policies are the most appropriate way to model legitimate workload communication in a tiered application. They allow administrators to express which sources, destinations, and services are required instead of relying on broad network access. 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. C 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.

What makes this a strong certification question is that several answers look technically related, but only one aligns with the exact behavior of Flow networking or Flow security. The correct response is A, meaning “Update the policy to disallow the unwanted traffic.”. 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. From a troubleshooting standpoint, the validation path is policy scope first, then categories or identity mapping, then hitlog evidence, service definition, and finally policy precedence. 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 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 sounds plausible, but it does not align with the specific Flow policy object or precedence rule that controls this case. The key takeaway is that Flow is intentionally.

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 D, meaning “Create an Isolation Policy blocking traffic between (Environment: Production + Site: Branch-001) and (Environment: Development + Site: Branch-001).”. 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. 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.

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 B, meaning “On the AHV host's physical network interfaces”. 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. 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. C 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.

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 “Security Policy Hit logs”. The winning option is the one tied to the native Nutanix object or control that governs the outcome described in the scenario. 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. 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. That is the underlying Nutanix principle being validated: solve the issue at the feature that owns the behavior, not by changing unrelated infrastructure settings that happen to sound network-oriented.

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 second BGP gateway requires a BGP session configured to peer with the external router.”. With BGP in Flow Virtual Networking, route exchange depends on both gateway objects and a correctly defined peering session. A healthy gateway alone is not enough; the session, peer parameters, and advertised prefixes must all align. 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. 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 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 C, meaning “Reduce MTU to 1356 on guest VMs”. 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. 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.

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.

What makes this a strong certification question is that several answers look technically related, but only one aligns with the exact behavior of Flow networking or Flow security. The correct response is D, meaning “It manages configuration, monitoring, and optimization of network resources.”. With BGP in Flow Virtual Networking, route exchange depends on both gateway objects and a correctly defined peering session. A healthy gateway alone is not enough; the session, peer parameters, and advertised prefixes must all align. 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. 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. In practice, administrators who anchor their decisions to.

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 B, meaning “Configure the transit VPC with one NAT External Subnet and one No-NAT External Subnet, each serving different traffic types.”. A Transit VPC acts as the routing hub for spoke VPCs and is commonly used when administrators want shared services or inter-VPC communication without pushing route complexity into the physical network. 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 is not appropriate because NAT changes addressing behavior and does not solve the routing or policy condition described in the scenario. C is not appropriate because NAT changes addressing behavior and does not solve the routing or policy condition described in the scenario. 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.