Which three steps are valid for deploying a VM-Series firewall on NSX? (Choose three )

Question

Options

• Acreate steering policies to redirect traffic to the VM-Series firewall
• Bcreate a vDC and a vApp that includes the VM-Series firewall
• Cregister the VM-Series firewall as a service
• Dobtain the AMI from market place
• Eenable communication between Panorama and the NSX Manager

• A
  88% (36)
• D
  10% (4)
• E
  2% (1)

Explanation

Deploying a VM-Series firewall on VMware NSX follows a specific on-premises virtualization workflow: you must register the VM-Series as a service (C) so NSX Manager recognizes it for service insertion, create a vDC and vApp (B) within the VMware/vCloud Director environment to host the firewall, and create steering policies (A) to redirect traffic through the firewall for inspection - these three steps form the core deployment sequence.

Option D is wrong because an AMI (Amazon Machine Image) is an AWS-specific artifact used when deploying VM-Series on EC2; it has no relevance to VMware NSX, which is an on-premises network virtualization platform.

Option E is wrong in this context because while Panorama can integrate with NSX Manager via a plugin, enabling that communication is an optional management/automation enhancement - not one of the foundational steps required to deploy and activate the firewall on NSX.

Memory tip: Think of the three steps as Register → Build → Redirect (C → B → A). You register the service first so NSX knows about it, build the virtual environment to house it, then redirect traffic to it. If you see "AMI," think AWS - not NSX.

No community discussion yet for this question.