Palo Alto Networks SD-WAN Engineer SD-WAN-Engineer Exam Questions

Answer : C

For a massive rollout involving 1,000 branch sites, Prisma SD-WAN (formerly CloudGenix) provides a specialized workflow known as Bulk Site Configuration. This method is designed to minimize manual intervention and maximize deployment velocity by leveraging Site Templates and Device Shells.

In this scenario, the primary architectural advantage of Option C is the use of Pre-Staging. By exporting an empty SD-WAN device CSV from the Prisma SD-WAN Controller and populating it with data from the corporate CMDB, administrators can perform a bulk upload to create hundreds or thousands of sites and device shells simultaneously in the management portal. A 'Device Shell' acts as a placeholder for a physical ION device that has not yet connected to the cloud. It contains all the site-specific configuration---such as interface roles, circuit labels, and IP addressing---waiting for a serial number to be associated with it.

When the field technician performs the physical 'rack and stack,' they simply connect the ION device to the internet (via ISP modem or cellular). Through Zero Touch Provisioning (ZTP), the device automatically 'phones home' to the Prisma SD-WAN Cloud Controller using its Manufacturer Installed Certificate (MIC). Because the configuration was pre-created via the CSV bulk upload, the controller recognizes the device (once assigned to its shell) and immediately pushes the complete configuration. This eliminates the need for the field tech to access a console port or perform local configuration, reducing their on-site time to the bare minimum. While APIs (Option D) can be used for automation, the built-in CSV template workflow is the standard, documented 'best practice' for rapidly translating CMDB data into a functioning SD-WAN fabric at this scale.

Answer : A, B, C

Comprehensive and Detailed Explanation

The AppX (Application Experience) score is a proprietary metric used by Prisma SD-WAN to provide a holistic view of user experience, rather than just network statistics. It is calculated based on three key components:

Transaction Failure Rate (A): The percentage of application transactions that failed (e.g., TCP resets, HTTP 500 errors). This indicates availability.

Network Transfer Time (B): The time taken for packets to traverse the network (WAN/LAN latency). This indicates network health.

Server Response Time (C): The time taken by the application server to respond to a request. This indicates backend performance.

Why not D or E?

Bandwidth Utilization (D) is a capacity metric, not a direct measure of quality. A link can be 90% full but still deliver packets quickly (good AppX), or 10% full but dropping packets (bad AppX).

Jitter (E) is a network-layer metric primarily relevant for UDP Real-Time media. While important, the high-level 'AppX' score for general TCP apps focuses on the 'Time-to-Glass' metrics (NTT/SRT) and success rates.

Answer : B

Comprehensive and Detailed Explanation

According to the Prisma SD-WAN Performance Policy Default Behavior documentation, the default action configured for applications (including real-time media) when a path experiences poor performance (violates the SLA thresholds for latency, jitter, or packet loss) is to Move Flows.

The Prisma SD-WAN ION device continuously monitors the health of all available paths. If the active path for a media application degrades and fails to meet the specified SLA, the default policy dictates that the traffic should be steered (moved) to an alternate, compliant path that meets the performance criteria.

While Forward Error Correction (FEC) is a powerful feature available in Prisma SD-WAN to mitigate packet loss for real-time applications, it is an optional action that must be explicitly enabled or configured within the performance policy rules. It is not the default action in the base system configuration; the primary default mechanism for handling performance issues is to leverage the multi-path fabric to switch to a better link.

Answer : C

In the Prisma SD-WAN (Instant-On Network) management framework, administrators can customize how events are handled and prioritized across different sites through Event Policies. An organization that requires 'elevated incident notifications' for a critical site like its headquarters needs a way to differentiate those alerts from standard branch notifications in the management portal and integrated third-party tools.

The most direct and effective method to achieve this is by configuring an Event Policy Rule specifically for the headquarters site. Within the incident policy framework, administrators can create rules that match specific resources---in this case, the headquarters site---and apply an action to set the priority. Priority levels typically range from P1 (highest) to P5 (lowest).1 By setting these to the highest level (P1), any generated incident for that site will immediately stand out on the dashboard as a high-priority event.

This approach is superior to other options because it changes the inherent importance of the alert within the Prisma SD-WAN logic itself. For example, a 'WAN Link Down' event at a small retail branch might be a P3, but the same event at the HQ could be elevated to a P1 via a custom policy rule. This elevation ensures that the Network Operations Center (NOC) is alerted more urgently and that external integrations, such as ServiceNow or PagerDuty, receive the correct priority mapping for immediate escalation. Options such as aggressive SLA thresholds (Option B) only increase the frequency of alerts, not necessarily their notification priority, while global syslog or SNMP settings (Options A and D) lack the site-specific granularity required for this use case.

Answer : B

Comprehensive and Detailed Explanation

The transition from 'Claimed' to 'Online' depends entirely on the ION device's ability to establish a secure, persistent management tunnel to the Prisma SD-WAN Controller.

Connectivity Requirements: The ION device initiates an outbound connection to the controller on TCP Port 443 (HTTPS). It also requires accurate time synchronization to validate SSL certificates, necessitating access to NTP (UDP Port 123).

Scenario Analysis: Since the installer can browse the internet from the LAN, we know the physical link and basic routing/NAT are functional. The issue is specific to the management plane traffic.

Root Cause: If an upstream firewall (e.g., a corporate edge firewall or ISP filter) is inspecting SSL traffic or blocking specific FQDNs/Ports required by the ION, the device cannot complete the handshake. Consequently, it remains 'Claimed' (registered in the database) but cannot go 'Online' (active management session). Options A, C, and D prevent provisioning (configuration push) but generally do not prevent the device from initially checking in and going 'Online' if the pipe is open.

Answer : C

Comprehensive and Detailed Explanation

The best practice for managing upgrades in a large-scale Prisma SD-WAN environment is the Canary or Phased Rollout approach, utilizing Site Tags.

Risk Mitigation: Upgrading all sites simultaneously (Option B) is highly risky. If the new software version has an unforeseen bug or compatibility issue with a specific circuit type, the entire network could face an outage.

Tag-Based Management: Administrators should create tags such as 'Upgrade-Phase-1' (Pilot sites) or 'Region-North'. By assigning the specific Software Version to the Tag (rather than the individual site or the global default), the controller pushes the update only to that subset of devices.

Procedure:

Apply update to 'Pilot' tag (5 sites). Monitor for 24-48 hours.

Apply update to 'Region-1' tag (50 sites). Monitor.

Eventually, update the Global default once confidence is high.

Option A is unscalable, and Option D is incorrect as the administrator retains full control over when upgrades occur; they are not forced automatically without policy configuration.

Answer : A

Comprehensive and Detailed Explanation

In a Prisma SD-WAN Data Center deployment, the operational state of the Secure Fabric VPNs (overlay tunnels) is directly tied to the health of the BGP Core Peer configuration.4

Core Peer Dependency: DC ION devices typically peer with the data center core switch (Core Router) via BGP to learn the subnets (prefixes) for the applications hosted in the DC. The Prisma SD-WAN controller monitors this BGP peering status.5

Controller Logic: If the BGP Core Peer on a DC ION goes down (or is not established), the controller automatically marks the VPN tunnels terminating at that specific ION as 'Inactive'.6 This is a fail-safe mechanism designed to prevent remote branches from sending traffic to a DC ION that has lost conne7ctivity to the internal data center network (and thus the applications).

Scenario Analysis: In this scenario, DC ION-1 has active VPNs, meaning its BGP Core Peer is UP and it is successfully advertising reachability. DC ION-2 has no active VPNs, which strongly indicates that its BGP Core Peer is down.8 Because the controller sees the peer is down, it suppresses the tunnel establishment or marks existing tunnels as inactive to ensure traffic is only directed to the healthy node (ION-1).