Which two configurations are required when creating deployment profiles to migrate a perpetual VM-Series firewall to a flexible VM? (Choose two.)

When migrating a VM-Series firewall from a perpetual license to a flexible, credit-based license, the primary goal is to ensure functional and performance parity. This is achieved by creating a deployment profile in the Customer Support Portal (CSP) that precisely mirrors the specifications of the original perpetual license. The deployment profile must allocate the same number of vCPUs to match the performance capacity and include the identical set of security service subscriptions (e.g., Threat Prevention, WildFire) to maintain the existing security posture. This ensures a seamless transition without any degradation in performance or loss of security features.

A. The migration is to a flexible model, so the deployment profile must be configured for flexible vCPUs, not the legacy "Fixed vCPU Models" type.
D. While Panorama is a common management tool for VM-Series firewalls, its use is not a mandatory configuration requirement for the license migration process itself.

1. Palo Alto Networks, VM-Series Deployment Guide for VMware ESXi, "Migrate from a Perpetual License to a Software NGFW Credit-Based License" section.

This official guide explicitly states: "To migrate from a perpetual license to a software NGFW credit-based license, you must create a deployment profile that matches the capacity and subscriptions of your perpetual license. When you create the deployment profile, you must select the same number of vCPUs and the same security subscriptions that are on your perpetual license." This directly validates answers B and C.

2. Palo Alto Networks, Get Started with Software NGFW Credits, "Create a Deployment Profile" section.

This document details the function of a deployment profile, explaining that it is used to define the firewall model, the number of vCPU cores, and the specific security subscriptions. This reinforces that vCPUs and security services are the core components configured in a deployment profile.