PSE-PRISMACLOUD · Question #94
What are two ways to initially deploy a VM-Series NGFW in Microsoft Azure? (Choose two.)
The correct answer is A. through ARM Templates in the GitHub Repository B. through Solution Templates in the Azure Marketplace. Deploying a VM-Series NGFW in Azure is officially supported via ARM (Azure Resource Manager) Templates hosted in Palo Alto's GitHub repository (A) and via Solution Templates available directly in the Azure Marketplace (B) - both are documented, production-ready deployment paths…
Question
What are two ways to initially deploy a VM-Series NGFW in Microsoft Azure? (Choose two.)
Options
- Athrough ARM Templates in the GitHub Repository
- Bthrough Solution Templates in the Azure Marketplace
- Cthrough Expedition in the Customer Success Portal
- Dthrough Iron Skillets in the GitHub Repository
How the community answered
(54 responses)- A87% (47)
- C9% (5)
- D4% (2)
Explanation
Deploying a VM-Series NGFW in Azure is officially supported via ARM (Azure Resource Manager) Templates hosted in Palo Alto's GitHub repository (A) and via Solution Templates available directly in the Azure Marketplace (B) - both are documented, production-ready deployment paths that Microsoft and Palo Alto jointly support.
Why the distractors are wrong:
- C (Expedition): Expedition is a migration tool used to convert third-party firewall configs to PAN-OS format - it's not a deployment mechanism for Azure VMs.
- D (Iron Skillets): Iron Skillet is a configuration framework for applying security best practices after deployment; it doesn't deploy infrastructure.
Memory tip: Think "deploy first, configure later" - ARM Templates and Marketplace get the VM into Azure; Expedition and Iron Skillet are tools you use after you have a firewall running.
Topics
Community Discussion
No community discussion yet for this question.