How does Palo Alto Networks integrate with VXLAN tagging?

Question

Options

• Adoes not integrate with VXLAN tagging, so virtual appliances cannot be provided, but
• Bintegrates with VXLAN. but scripting is necessary, and Professional Services should be
• Cintegrates fully into VXLAN architectures if they are provided by VMware
• Ddoes not integrate natively with VXLAN tagging, network equipment can convert VXLAN flows

• B
  8% (2)
• C
  88% (22)
• D
  4% (1)

Explanation

C is correct because Palo Alto Networks VM-Series firewalls natively integrate with VMware NSX, which uses VXLAN as its underlying network virtualization protocol. When VMware provides the VXLAN architecture (via NSX), Palo Alto can be automatically provisioned, deployed, and steered traffic through policy - making the integration seamless and fully supported without manual scripting.

Why the distractors are wrong:

• A is wrong because Palo Alto does integrate with VXLAN - it's a supported, documented capability in VMware NSX environments.
• B is wrong because it implies the integration requires manual scripting and Professional Services, overstating the complexity; VMware NSX handles orchestration automatically.
• D is misleading - while VXLAN-to-VLAN conversion can work as a workaround in non-VMware environments, it incorrectly frames the VMware-native integration as non-existent.

Memory tip: Think "PAN + VMware = VXLAN yes; PAN alone = VXLAN no." The VMware (NSX) context is the key condition - if the question mentions VMware providing the architecture, Palo Alto integrates fully. Without VMware NSX as the orchestrator, native VXLAN support is not guaranteed.

No community discussion yet for this question.