When deploying VM series on NSX platform to support micro-segmentation, which statement is NOT correct?

Question

Options

• AVM-Series uses NetX API to receive and send packets
• BTraffic steering rules could be defined on Panorama and pushed to NSX Manager
• CVM-Series provide Multi-tenancy support with multiple zones
• DOne panorama could support to connect with only one NSX manager

• A
  75% (41)
• B
  7% (4)
• C
  4% (2)
• D
  15% (8)

Explanation

Option A is the incorrect statement because VM-Series on VMware NSX does not use the NetX API to receive and send packets. The NetX API was part of VMware's legacy vShield/vCloud Networking and Security (vCNS) framework. On the NSX platform, VM-Series integrates using NSX's service insertion framework, where traffic is redirected to the VM-Series service VM through NSX's Distributed Firewall (DFW), and packets traverse standard data-plane vNIC interfaces - not the NetX API.

Why the distractors are true (and therefore not the answer):

• B is correct: Panorama can define traffic steering rules and push them to NSX Manager, which is a core feature of the Panorama-NSX orchestration model.
• C is correct: VM-Series does support multi-tenancy through multiple security zones, enabling segmented policy enforcement per tenant.
• D is correct: A single Panorama instance can only connect to one NSX Manager - this is a documented architectural constraint of the integration.

Memory tip: Think "NSX killed NetX" - when VMware replaced vCNS/vShield with NSX, the NetX API was superseded. If a question pairs "NSX" with "NetX API," that's your red flag. Also remember the Panorama-to-NSX-Manager relationship as 1:1, like a dedicated manager-to-manager handshake.

No community discussion yet for this question.