What are three requirements to automate service deployment of a VM-Series firewall from an NSX Manager? (Choose three.)

Question

Options

• AvCenter has been given Palo Alto Networks subscription licenses for VM-Series firewalls
• BThe deployed VM-Series firewall can establish communications with Panorama.
• CPanorama has been configured to recognize both the NSX Manager and vCenter.
• DPanorama can establish communications to the public Palo Alto Networks update servers.
• EThe NSX Manager completed the host preparation prior to the VM-Series firewall service

• A
  89% (16)
• B
  6% (1)
• E
  6% (1)

Explanation

Automating VM-Series firewall service deployment from NSX Manager requires three things working in concert: vCenter must hold the Palo Alto Networks subscription licenses (A) so NSX Manager can provision firewalls without manual license intervention; Panorama must be configured to recognize both NSX Manager and vCenter (C) because Panorama acts as the orchestration bridge that coordinates deployment between the two platforms; and Panorama must reach Palo Alto Networks public update servers (D) to pull the VM-Series software images and license validations needed during automated provisioning.

Why the distractors are wrong: Option B is backwards in causality - the VM-Series communicating with Panorama is a result of a successful deployment, not a prerequisite to trigger one. Option E (NSX host preparation) is indeed an NSX prerequisite step, but it's part of the general NSX infrastructure setup rather than one of the three specific automation requirements the question targets.

Memory tip: Think "L-P-U" - Licenses in vCenter, Panorama configured with both managers, Update server reachability. If any of those three are missing, the automated deployment pipeline breaks before a firewall ever spins up.

No community discussion yet for this question.