Cloud NGFW for Azure is designed to secure network traffic within and between Azure environments:
A . Azure Kubernetes Service (AKS): While CN-Series firewalls are designed for securing Kubernetes environments like AKS, Cloud NGFW is not directly deployed within AKS. Instead, Cloud NGFW secures traffic flowing to and from AKS clusters.
B . Azure Virtual WAN: Cloud NGFW can be deployed to secure traffic flowing through Azure Virtual WAN hubs. This allows for centralized security inspection of traffic between on-premises networks, branch offices, and Azure virtual networks.
C . Azure DevOps: Azure DevOps is a set of development tools and services. Cloud NGFW is a network security solution and is not directly related to Azure DevOps.
D . Azure VNET: Cloud NGFW can be deployed to secure traffic within and between Azure Virtual Networks (VNETs). This is its primary use case, providing advanced threat prevention and network security for Azure workloads.
Reference:
The Cloud NGFW for Azure documentation clearly describes these deployment scenarios:
Cloud NGFW for Azure Documentation: Search for “Cloud NGFW for Azure” on the Palo Alto Networks support portal. This documentation explains how to deploy Cloud NGFW in VNETs and integrate it with Virtual WAN.
This confirms that Azure VNETs and Azure Virtual WAN are the supported deployment environments for Cloud NGFW.

A . DNS sinkholing: DNS sinkholing redirects DNS requests for known malicious domains to a designated server, preventing users from accessing those sites. It doesn’t inherently protect or hide an internal network in outbound flows. It’s more of a preventative measure against accessing malicious external resources.
B . User-ID: User-ID maps network traffic to specific users, enabling policy enforcement based on user identity. It provides visibility and control but doesn’t hide the internal network’s addressing scheme in outbound connections.
C . App-ID: App-ID identifies applications traversing the network, allowing for application-based policy enforcement. Like User-ID, it doesn’t mask the internal network’s addressing.
D . NAT (Network Address Translation): NAT translates private IP addresses used within an internal network to a public IP address when traffic leaves the network. This effectively hides the internal IP addressing scheme from the external network. Outbound connections appear to originate from the public IP address of the NAT device (typically the firewall), thus protecting and hiding the internal network’s structure.
Reference:
Therefore, NAT is the element that protects and hides an internal network in an outbound flow.

The scenario describes a need for programmatic and automated updating of a custom URL category on a Palo Alto Networks firewall. The XML API is specifically designed for this kind of task. It allows external systems and scripts to interact with the firewall’s configuration and operational data.
Here’s why the XML API is the appropriate solution and why the other options are not:
* D. XML API: The XML API provides a well-defined interface for making changes to the firewall’s configuration. This includes creating, modifying, and deleting URL categories and adding or removing URLs within those categories. A script can be written to retrieve the list of “bad sites” from the company’s application and then use the XML API to push those URLs into the custom URL category on the firewall. This process can be automated on a schedule. This is the most efficient and recommended method for this type of integration.
Why other options are incorrect:
* A. Dynamic User Groups: Dynamic User Groups are used to dynamically group users based on attributes like username, group membership, or device posture. They are not relevant for managing URL categories.
* B. SNMP SET: SNMP (Simple Network Management Protocol) is primarily used for monitoring and retrieving operational data from network devices. While SNMP can be used to make some configuration changes, it is not well-suited for complex configuration updates like adding multiple URLs to a category. The XML API is the preferred method for configuration changes.
* C. Dynamic Address Groups: Dynamic Address Groups are used to dynamically populate address groups based on criteria like tags, IP addresses, or FQDNs. They are intended for managing IP addresses and not URLs, so they are not applicable to this scenario.
Palo Alto Networks References:
The primary reference for this is the Palo Alto Networks XML API documentation. Searching the Palo Alto Networks support site (live.paloaltonetworks.com) for “XML API” will provide access to the latest documentation. This documentation details the various API calls available, including those for managing URL categories.
Specifically, you would look for API calls related to:
* Creating or modifying custom URL categories.
* Adding or removing URLs from a URL category.
The XML API documentation provides examples and detailed information on how to construct the XML requests and interpret the responses. This is crucial for developing a script to automate the URL updates.

CN-Series firewalls are containerized firewalls designed for Kubernetes environments. They support key next-generation firewall features:
A . App-ID: This is SUPPORTED. App-ID is a core technology of Palo Alto Networks firewalls, enabling identification and control of applications regardless of port, protocol, or evasive techniques. CN-Series firewalls leverage App-ID to provide granular application visibility and control within containerized environments.
Reference:
B . Decryption: This is SUPPORTED. CN-Series firewalls can perform SSL/TLS decryption to inspect encrypted traffic for threats and enforce security policies on decrypted content.
C . GlobalProtect: This is NOT SUPPORTED. GlobalProtect is primarily designed for endpoint security and remote access. While there are integrations with containerized applications in the context of securing access to them, GlobalProtect is not a core feature of the CN-Series firewall itself.
D . Content-ID: This is SUPPORTED. Content-ID provides threat prevention capabilities, including antivirus, anti-spyware, vulnerability protection, and URL filtering. CN-Series firewalls utilize Content-ID to protect containerized workloads from known and unknown threats.
E . IPSec: While CN-Series can participate in secure communication with other systems, they don’t directly terminate IPSec tunnels in the same way a traditional firewall might. Their focus is on securing traffic within the Kubernetes cluster and between the cluster and external networks through other means (like service meshes or ingress controllers).

* A . VM-Series firewalls cannot be used to protect container environments: This is incorrect. While CN-Series is specifically designed for container environments, VM-Series can also be used in certain container deployments, often in conjunction with other container networking solutions. For example, VM-Series can be deployed as a gateway for a Kubernetes cluster.
* B . All NGFW platforms support API integration: This is correct. Palo Alto Networks firewalls, including PA-Series (hardware), VM-Series (virtualized), CN-Series (containerized), and Cloud NGFW, offer robust API support for automation, integration with other systems, and programmatic management. This is a core feature of their platform approach.
* C . Panorama is the only unified management console for all NGFWs: This is incorrect. While Panorama is a powerful centralized management platform, it’s not the only option. Individual firewalls can be managed locally via their web interface or CLI. Additionally, Cloud NGFW has its own management interface within the cloud provider’s console.
* D. CN-Series firewalls are used to protect virtualized environments: This is incorrect. CN-Series is specifically designed for containerized environments (e.g., Kubernetes, OpenShift), not general virtualized environments. VM-Series is the appropriate choice for virtualized environments (e.g., VMware vSphere, AWS EC2).

The question asks about Cloud NGFW management tasks performed inherently by the service within AWS and Azure. This means we are looking for tasks that are automated and handled by the Cloud NGFW service itself, not by the customer.
Here’s a breakdown of why A, B, and C are correct and why D and E are incorrect, referencing relevant Palo Alto Networks documentation where possible (though specific, publicly accessible documentation on the inner workings of the managed service is limited, the principles are consistent with their general cloud and firewall offerings):
A: Horizontally scaling out to meet increased traffic demand: This is a core feature of cloud-native services.
Cloud NGFW is designed to automatically scale its resources (compute, memory, etc.) based on traffic volume. This eliminates the need for manual intervention by the customer to provision or de-provision resources. This aligns with the general principles of cloud elasticity and autoscaling, which are fundamental to cloud-native services like Cloud NGFW. While explicit public documentation detailing the exact scaling mechanism is limited, it’s a standard practice for cloud-based services and is implied in the general description of Cloud NGFW as a managed service.
B: Installing new content (applications and threats): Palo Alto Networks maintains the threat intelligence and application databases for Cloud NGFW. This means that updates to these databases, which are crucial for identifying and blocking threats, are automatically pushed to the service by Palo Alto Networks. Customers do not need to manually download or install these updates. This is consistent with how Palo Alto Networks manages its other security services, such as Threat Prevention and WildFire, where content updates are delivered automatically.
C: Installing new PAN-OS software updates: Just like content updates, PAN-OS software updates are also managed by Palo Alto Networks for Cloud NGFW. This ensures that the service is always running the latest and most secure version of the operating system. This removes the operational burden of managing software updates from the customer. This is a key advantage of a managed service.
D: Blocking high-risk S2C threats in accordance with SOC2 compliance: While Cloud NGFW does block threats, including server-to-client (S2C) threats, the management of this blocking is not inherently performed by the service in the context of SOC2 compliance. SOC2 is an auditing framework, and compliance is the customer’s responsibility. The service provides the tools to achieve security controls, but demonstrating and maintaining compliance is the customer’s task. The service does not inherently manage the compliance process itself.
E: Decrypting high-risk SSL traffic: While Cloud NGFW can decrypt SSL traffic for inspection (SSL Forward Proxy), the question asks about tasks inherently performed by the service. Decryption is a configurable option. Customers choose whether or not to enable SSL decryption. It is not something the service automatically does without explicit configuration. Therefore, it’s not an inherent management task performed by the service.
In summary, horizontal scaling, content updates, and PAN-OS updates are all handled automatically by the Cloud NGFW service, making A, B, and C the correct answers. D and E involve customer configuration or compliance considerations, not inherent management tasks performed by the service itself.

When using Software NGFW credits and deploying PAN-OS VMs, specific deployment models apply.
* Why B and D are correct:
* B. Fixed vCPU models: These are pre-defined VM sizes with a fixed number of vCPUs and memory. Examples include VM-50, VM-100, VM-200, etc. When using fixed vCPU models, you consume a fixed number of credits per hour based on the chosen model.
* D. Flexible vCPUs: This option allows you to dynamically allocate vCPUs and memory within a defined range. Credit consumption is calculated based on the actual resources used. This provides more granular control over resource allocation and cost.
* Why A and C are incorrect:
* A. VM-100: While VM-100 is a valid fixed vCPU model, it’s not a type of VM selection. It’s a specific instance within the “Fixed vCPU models” type. Choosing “VM-100” is choosing a specific fixed vCPU model.
* C. Flexible model of working memory: While you do configure the memory alongside vCPUs in the flexible model, the type of selection is “Flexible vCPUs.” The flexible model encompasses both vCPU and memory flexibility.
Palo Alto Networks References:
The Palo Alto Networks documentation on VM-Series firewalls in public clouds and the associated licensing models (including the use of credits) explicitly describe the “Fixed vCPU models” and “Flexible vCPUs” as the two primary deployment options when using credits. The documentation details how credit consumption is calculated for each model.
Specifically, look for information on:
* VM-Series Deployment Guide for your cloud provider (AWS, Azure, GCP): These guides detail the different deployment options and how to use credits.
* VM-Series Licensing and Credits Documentation: This documentation provides details on how credits are consumed with fixed and flexible models.
For example, the VM-Series Deployment Guide for AWS states:
* Fixed vCPU models: These are pre-defined VM sizes… You select a specific VM model (e.g., VM-50, VM-100, VM-300), and you are billed a fixed number of credits per hour.
* Flexible vCPUs: This option allows you to specify the number of vCPUs and amount of memory…
You are billed based on the actual resources you use.

Cloud NGFW for Azure and VM-Series share certain functionalities due to their common PAN-OS foundation.
* Why A, C, and D are correct:
* A. Panorama management: Both Cloud NGFW for Azure and VM-Series firewalls can be managed by Panorama, providing centralized management and policy enforcement.
* C. Transparent inspection of private-to-private east-west traffic that preserves client source IP address: Both platforms support this type of inspection, which is crucial for security and visibility within Azure virtual networks.
* D. Inter-VNet inspection through a transit VNet: Both can be deployed in a transit VNet architecture to inspect traffic between different virtual networks.
* Why B and E are incorrect:
* B. Inter-VNet inspection through Virtual WAN hub: While VM-Series can be integrated with Azure Virtual WAN, Cloud NGFW for Azure is directly integrated and doesn’t require a separate transit VNet or hub for basic inter-VNet inspection. It uses Azure’s native networking.
* E. Use of routing intent policies to apply security policies: Routing intent is specific to Cloud NGFW for Azure’s integration with Azure networking and is not a feature of VM-Series. VM- Series uses standard security policies and routing configurations within the VNet.
Palo Alto Networks References:
* Cloud NGFW for Azure Documentation: This documentation details the architecture and integration with Azure networking.
* VM-Series Deployment Guide for Azure: This guide covers deployment architectures, including transit VNet deployments.
* Panorama Administrator’s Guide: This guide explains how to manage both platforms using Panorama.

The question is about offline registration of a software NGFW (specifically VM-Series) when there’s no internet connectivity.
A . Authcode and serial number of the VM-Series firewall: This is the correct answer. For offline registration, you need to generate an authorization code (authcode) from the Palo Alto Networks Customer Support Portal. This authcode is tied to the serial number of the VM-Series firewall. You provide both the authcode and the serial number to complete the offline registration process on the firewall itself.
Why other options are incorrect:
B . Hypervisor installation ID and software version: While the hypervisor and software version are relevant for the overall deployment, they are not the specific pieces of information required in the customer support portal for generating the authcode needed for offline registration.
C . Number of data plane and management plane interfaces: The number of interfaces is a configuration detail on the firewall itself and not information provided during the offline registration process in the support portal.
D . CPUID and UUID of the VM-Series firewall: While UUID is important for VM identification, it is not used for generating the authcode for offline registration. The CPUID is also not relevant in this context. The authcode is specifically linked to the serial number.

Comprehensive and Detailed In-Depth Step-by-Step Explanation:The customer’s AWS environment, with multiple VPCs protected by a cloud-native firewall, experienced a breach due to malware spreading across VPCs, indicating inadequate segmentation and visibility. The Palo Alto Networks Systems Engineer Professional – Software Firewall documentation provides guidance on securing multi-VPC AWS environments with Cloud NGFW, focusing on preventing lateral movement and enhancing threat prevention.
* Implement a Cloud NGFW for each VPC (Option D): Deploying a Cloud NGFW instance in each VPC ensures localized traffic inspection, segmentation, and control, preventing malware from spreading laterally across VPCs. Cloud NGFW for AWS supports a distributed deployment model, allowing each VPC to have its own firewall instance integrated with AWS services (e.g., VPC routing, Security Groups) to enforce policies, block threats, and maintain visibility. The documentation recommends this approach for multi-VPC environments to minimize risk exposure and ensure granular security, addressing the customer’s breach scenario by isolating and securing each VPC independently.
Options A (Purchase a software credit pool for flexible Cloud NGFW deployment across the VPCs), B (Deploy a single Cloud NGFW), and C (Subscribe to Palo Alto Networks Advanced Threat Protection for the cloud-native firewall) are incorrect. A software credit pool (Option A) is a licensing mechanism, not a deployment solution, and does not address the need for multiple VPC protection. A single Cloud NGFW (Option B) cannot effectively secure multiple VPCs without introducing latency or complexity (e.g., centralized routing), failing to prevent lateral movement as seen in the breach. Advanced Threat Protection (Option C) enhances threat detection but does not resolve the segmentation issue; it requires a distributed deployment (like Option D) to prevent malware spread across VPCs.
References: Palo Alto Networks Systems Engineer Professional – Software Firewall, Section: Cloud NGFW for AWS Deployment, Multi-VPC Security Architecture, Advanced Threat Prevention Documentation.

Securing a technical win involves demonstrating value, understanding customer needs, and providing tangible solutions.
Why A, C, and D are correct:
A: Providing a link to the PAYG Cloud NGFW in the Azure Marketplace (or AWS Marketplace) offers a direct, easy way for customers to explore and potentially trial the solution. This lowers the barrier to entry and facilitates quick evaluation.
C: Network Security Design workshops are crucial for understanding the customer’s environment, challenges, and requirements. This collaborative approach allows for tailored solutions and builds trust.
D: Proof of Value (POV) product evaluations allow customers to test the solution in their own environment, demonstrating its effectiveness and addressing specific concerns. This is a powerful way to secure a technical win.
Why B is incorrect: Unsolicited proposals that disregard customer needs are ineffective and can damage credibility. It’s essential to understand the customer’s context before proposing solutions.
Palo Alto Networks Reference: Palo Alto Networks sales enablement materials and partner training emphasize the importance of needs discovery, solution selling, and demonstrating value through POVs.

This question asks about common characteristics of Cloud NGFW (specifically referring to Cloud NGFW for AWS and Azure) and VM-Series firewalls.
* B. In Azure and AWS, both offerings can be managed by Panorama. This is correct. Panorama is the centralized management platform for Palo Alto Networks firewalls, including both VM-Series and Cloud NGFW deployments in AWS and Azure. Panorama allows for consistent policy management, logging, and reporting across these different deployment models.
* D. In Azure, inbound destination NAT configuration also requires source NAT to maintain flow symmetry. This is accurate specifically within the Azure environment. Due to how Azure networking functions, when performing destination NAT (DNAT) for inbound traffic to resources behind a firewall (whether VM-Series or Cloud NGFW), it’s typically necessary to also implement source NAT (SNAT) to ensure return traffic follows the same path. This maintains flow symmetry and prevents routing issues. This is an Azure networking characteristic, not specific to the Palo Alto offerings themselves, but it applies to both in Azure.
* E. In Azure and AWS, internal (east-west) flows can be inspected without any NAT. This is generally true. For traffic within the same Virtual Network (Azure) or VPC (AWS), both VM-Series and Cloud NGFW can inspect traffic without requiring NAT. This is a key advantage for microsegmentation and internal security. The firewalls can act as transparent security gateways for internal traffic.
Why other options are incorrect:
* A. In Azure, both offerings can be integrated directly into Virtual WAN hubs. While VM-Series firewalls can be integrated into Azure Virtual WAN hubs as secured virtual hubs, Cloud NGFW for Azure is not directly integrated into Virtual WAN hubs in the same way. Cloud NGFW for Azure uses a different architecture, deploying as a service within a virtual network.
* C. In AWS, both offerings can be managed by AWS Firewall Manager. AWS Firewall Manager is a service for managing AWS WAF, AWS Shield, and network firewalls (AWS Network Firewall).
While AWS Firewall Manager can be used to manage AWS Network Firewall, it is not the management plane for Palo Alto Networks VM-Series or Cloud NGFW for AWS. These are managed by Panorama.
Palo Alto Networks References:
To validate these points, refer to the following documentation areas on the Palo Alto Networks support site (live.paloaltonetworks.com):
* Panorama Administrator’s Guide: This guide details the management capabilities of Panorama, including managing VM-Series and Cloud NGFW deployments in AWS and Azure.
* Cloud NGFW for AWS/Azure Documentation: This documentation outlines the architecture and deployment models of Cloud NGFW, including its management and integration with cloud platforms.
* VM-Series Deployment Guides for AWS/Azure: These guides describe the deployment and configuration of VM-Series firewalls in AWS and Azure, including networking considerations and integration with cloud services.

Comprehensive and Detailed In-Depth Step-by-Step Explanation:The CN-Series firewall is a containerized next-generation firewall designed to secure workloads in containerized environments, particularly those running on Kubernetes. According to the Palo Alto Networks Systems Engineer Professional – Software Firewall documentation, the primary tool for deploying CN-Series firewalls is Kubernetes, as it integrates natively with Kubernetes clusters to provide security for containerized applications.
* Kubernetes (Option B): Kubernetes is the orchestration platform used to deploy, manage, and scale CN- Series firewalls within containerized environments. It allows for dynamic scaling and integration with container workloads, ensuring security policies are applied consistently across pods and services.
Options A (GCP Automated Deployment Services), C (Docker Swarm), and D (Terraform Automated Deployment Services) are incorrect. While GCP Automated Deployment Services and Terraform can be used for automation, they are not specific to CN-Series deployment in the context of Kubernetes. Docker Swarm, while a container orchestration platform, is not supported for CN-Series firewalls, as Palo Alto Networks focuses on Kubernetes for CN-Series deployment.
References: Palo Alto Networks Systems Engineer Professional – Software Firewall, Section: CN-Series Deployment Guide, Kubernetes Integration Documentation.

CN-Series firewalls are specifically designed for containerized environments.
Why A, C, and E are correct:
A . Prevention of sensitive data exfiltration from Kubernetes environments: CN-Series provides visibility and control over container traffic, enabling the prevention of data leaving the Kubernetes cluster without authorization.
C . Inbound, outbound, and east-west traffic between containers: CN-Series secures all types of container traffic: ingress (inbound), egress (outbound), and traffic between containers within the cluster (east-west).
E . Enforcement of segmentation policies that prevent lateral movement of threats: CN-Series allows for granular segmentation of containerized applications, limiting the impact of breaches by preventing threats from spreading laterally within the cluster.
Why B and D are incorrect:
B . All Kubernetes workloads in the public and private cloud: While CN-Series can protect Kubernetes workloads in both public and private clouds, the statement “all Kubernetes workloads” is too broad. Its focus is on securing the network traffic around those workloads, not managing the Kubernetes infrastructure itself.
D . All workloads deployed on-premises or in the public cloud: CN-Series is specifically designed for containerized environments (primarily Kubernetes). It’s not intended to protect all workloads deployed in any environment. That’s the role of other Palo Alto Networks products like VM-Series, PA-Series, and Prisma Access.
Palo Alto Networks Reference: The Palo Alto Networks documentation on CN-Series firewalls clearly outlines these use cases. Look for information on:
CN-Series Datasheets and Product Pages: These resources describe the key features and benefits of CN-Series, including its focus on container security.
CN-Series Deployment Guides: These guides provide detailed information on deploying and configuring CN-Series in Kubernetes environments.
These resources confirm that CN-Series is focused on securing container traffic within Kubernetes environments, including data exfiltration prevention, securing all traffic directions (inbound, outbound, east-west), and enforcing segmentation

Comprehensive and Detailed In-Depth Step-by-Step Explanation:The customer’s request for multi-cloud Layer 7 network security in AWS and Azure, with full management control, VPN termination, and BGP routing, requires a flexible and feature-rich firewall solution. The Palo Alto Networks Systems Engineer Professional – Software Firewall documentation outlines the capabilities of its firewall products for multi- cloud environments.
* VM-Series (Option A): The VM-Series firewall is a virtualized next-generation firewall (NGFW) ideal for multi-cloud deployments in AWS and Azure. It provides Layer 7 application visibility and control, full management control through tools like Panorama or Strata Cloud Manager, VPN termination (e.g., IPSec site-to-site VPNs), and BGP dynamic routing to peer with cloud and on-premises routers. The documentation highlights VM-Series as a versatile solution for public clouds, supporting custom configurations, policy enforcement, and advanced routing protocols, meeting all the customer’s requirements without the limitations of cloud-native or container-specific firewalls.
Options B (CN-Series), C (Cloud NGFW), and D (PA-Series) are incorrect. CN-Series firewalls are designed for containerized environments (e.g., Kubernetes) and do not support VPN termination or BGP routing natively, making them unsuitable for this multi-cloud, Layer 7 security use case. Cloud NGFW, while cloud- native for AWS and Azure, offers limited management control (as it is a managed service) and does not natively support VPN termination or BGP routing, as these features are handled by the cloud provider or require VM-Series integration. PA-Series firewalls are physical appliances, not virtualized or cloud-native, and cannot be deployed in AWS or Azure to meet the multi-cloud requirement.
References: Palo Alto Networks Systems Engineer Professional – Software Firewall, Section: Multi-Cloud Security, VM-Series Deployment Guide for AWS and Azure, VPN and BGP Routing Documentation.

The question focuses on how VM licenses are created when a company has purchased software NGFW credits and wants to deploy VM-Series firewalls in AWS.
D . Access the Palo Alto Networks Customer Support Portal and create a software NGFW credits deployment profile. This is the correct answer. The process starts in the Palo Alto Networks Customer Support Portal. You create a deployment profile that specifies the number and type of VM-Series licenses you want to deploy. This profile is then used to activate the licenses on the actual VM-Series instances in AWS.
Why other options are incorrect:
A . Access the AWS Marketplace and use the software NGFW credits to purchase the VMs. You do deploy the VM-Series instances from the AWS Marketplace (or through other deployment methods like CloudFormation templates), but you don’t “purchase” the licenses there. The credits are managed separately through the Palo Alto Networks Customer Support Portal. The Marketplace deployment is for the VM instance itself, not the license.
B . Access the Palo Alto Networks Application Hub and create a new VM profile. The Application Hub is not directly involved in the license creation process. It’s more focused on application-level security and content updates.
C . Access the Palo Alto Networks Customer Support Portal and request the creation of a new software NGFW serial number. You don’t request individual serial numbers for each VM. The deployment profile manages the allocation of licenses from your pool of credits. While each VM will have a serial number once deployed, you don’t request them individually during this stage. The deployment profile ties the licenses to the deployment, not individual serial numbers ahead of deployment.
Palo Alto Networks Reference:
The Palo Alto Networks Customer Support Portal documentation and the VM-Series Deployment Guide are the primary references. Search the support portal (live.paloaltonetworks.com) for “software NGFW credits,” “deployment profile,” or “VM-Series licensing.” The documentation will describe the following general process:
Purchase software NGFW credits.
Log in to the Palo Alto Networks Customer Support Portal.
Create a deployment profile, specifying the number and type of VM-Series licenses (e.g., VM-Series for AWS, VM-Series for Azure, etc.) you want to allocate from your credits.
Deploy the VM-Series instances in your cloud environment (e.g., from the AWS Marketplace).
Activate the licenses on the VM-Series instances using the deployment profile.
This process confirms that creating a deployment profile in the customer support portal is the correct way to manage and allocate software NGFW licenses.