Which three components are relevant for installing a VM-Series firewall in an OpenStack environment? (Choose three )

Question

Options

• Abootstrap files including init-cfg.txt. bootstrap.xml, and VM-Series auth codes
• Ba valid VM-Series gcow2 image
• CHypervisor: ESX
• Da valid OpenStack heat template in json format
• Ea valid vmseries vhd image
• Fa valid OpenStack heat template in yaml format

• A
  91% (31)
• E
  3% (1)
• F
  6% (2)

Explanation

Installing VM-Series on OpenStack requires bootstrap files (A) containing init-cfg.txt, bootstrap.xml, and auth codes to configure and license the firewall at first boot. You need a qcow2 image (B) because OpenStack runs on KVM/QEMU hypervisors, which use the QEMU Copy-On-Write (qcow2) disk format natively. A JSON-format Heat template (D) is required because Palo Alto Networks provides and validates their VM-Series OpenStack deployment templates in JSON format using Heat orchestration.

Why the distractors are wrong:

• C (ESX): ESX is VMware's proprietary hypervisor - OpenStack uses KVM, not VMware.
• E (VHD): VHD is Microsoft Hyper-V's disk image format, incompatible with OpenStack/KVM deployments.
• F (YAML): While OpenStack Heat does support YAML templates generally, Palo Alto's official VM-Series Heat templates for OpenStack are delivered in JSON format - YAML is not the validated format for this use case.

Memory tip: Think "BQJ" - Bootstrap, Qcow2, JSON - the three things that make OpenStack "Queue the firewall properly." The wrong answers map to competing platforms: ESX=VMware, VHD=Hyper-V, YAML=wrong format.

No community discussion yet for this question.