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 perpetual VM-Series firewall to a flexible Software NGFW license, the deployment profile must be configured to ensure operational and security parity. This involves two key steps. First, you must allocate the same number of vCPU cores in the deployment profile as were present in the original perpetual VM-Series model to maintain equivalent performance. Second, you must select the same security services (e.g., Threat Prevention, WildFire, DNS Security) that were active on the perpetual license to ensure the security posture remains unchanged after the migration. These settings directly map the old license's capabilities to the new flexible credit-based license.

A. Choose “Fixed vCPU Models” for configuration type.

This is incorrect. "Fixed vCPU Models" refers to the perpetual licensing model you are migrating from, not the flexible model you are migrating to, which uses selectable vCPU cores.

D. Deploy virtual Panorama for management.

This is incorrect. While Panorama is a common management tool for VM-Series firewalls, it is not a mandatory requirement for creating a deployment profile or for the migration process itself.

1. Palo Alto Networks Documentation

"Migrate from a Perpetual VM-Series License to a Software NGFW License": This guide explicitly details the migration process. In the "Create a Deployment Profile" section

it instructs the user to:

"Select the number of vCPU cores to match the vCPU cores on your perpetual license." (Supports Answer B)

"Select the security services to match the subscriptions on your perpetual license." (Supports Answer C)

The guide also shows that the configuration type is based on selecting a number of "vCPU Cores

" not "Fixed vCPU Models." (Refutes Answer A)

2. Palo Alto Networks Documentation

"VM-Series Deployment Guide": The chapter on "VM-Series Models" describes the perpetual models with their fixed vCPU counts (e.g.

VM-300 has 4 vCPUs). The chapter on "Software NGFW Credits" explains that the flexible model is based on allocating vCPU cores and associated subscriptions

which are configured in a deployment profile. This distinction supports the reasoning for choosing B and C and rejecting A.