Get New 2026 Valid Practice To your SD-WAN-Engineer Exam (Updated 88 Questions)
Network Security Administrator SD-WAN-Engineer Exam Practice Test Questions Dumps Bundle!
NEW QUESTION # 11
Network segmentation is required due to overlapping IP address space and M&A scenarios. Which Prisma SD-WAN feature will achieve the desired segmentation and end-to-end connectivity in this use case?
- A. Virtual Routing and Forwarding (VRF) profiles with proper site bindings to achieve desired isolation locally and across the secure fabric
- B. Multiple virtual routers with interface segmentation to achieve desired isolation across the secure fabric
- C. Multiple contexts with interface segmentation to achieve desired isolation across the underlay
- D. Virtual Routing and Forwarding (VRF) profiles with proper site bindings to achieve desired isolation across the underlay
Answer: A
Explanation:
In modern enterprise environments, particularly those undergoing Mergers and Acquisitions (M&A), engineers often face the challenge of overlapping IP address space.4 Prisma SD-WAN addresses this by utilizing Virtual Routing and Forwarding (VRF) profiles.5 A VRF creates a separate routing table instance within the ION device, allowing multiple networks to coexist on the same physical hardware even if they use the same IP ranges.
To achieve end-to-end connectivity while maintaining strict segmentation, these VRF profiles must be correctly associated with site bindings.7 When a VRF is "bound" to a site, the ION device ensures that traffic belonging to that specific segment remains isolated not only locally (on the LAN) but also across the secure SD-WAN fabric. Prisma SD-WAN achieves this by encapsulating the traffic within the overlay tunnels and tagging it with a unique VRF identifier.8 This ensures that a "Corporate" VRF at Site A can only communicate with the "Corporate" VRF at Site B, effectively keeping "Guest" or "Acquisition" traffic completely separate.
This architectural approach is superior to traditional underlay segmentation (Option A) or simple interface- based virtual routers (Option D) because it provides a centralized, software-defined method to manage multi- tenancy. By using VRF profiles, administrators can define a global security and routing posture once and push it to all relevant sites.9 This simplifies the integration of new business units with conflicting IP schemes, as the Prisma SD-WAN controller handles the complex orchestration required to maintain path selection and security policies uniquely for each VRF across the entire global network.
NEW QUESTION # 12
Which configuration requirement must be met to allow two branch ION devices to automatically establish a direct Dynamic VPN (branch-to-branch) connection for traffic flow, bypassing the Data Center?
- A. The "Standard VPN" path policy must be selected.
- B. A static "Gre Tunnel" must be manually configured between the two sites.
- C. The Data Center ION must be offline to trigger the dynamic failover.
- D. Both ION devices must be members of the same VPN Cluster.
Answer: D
Explanation:
Comprehensive and Detailed Explanation
Dynamic VPNs (also known as ION-to-ION or Branch-to-Branch VPNs) allow Prisma SD-WAN devices to establish direct, on-demand secure tunnels between branch sites to optimize latency for peer-to-peer traffic (e.
g., VoIP calls between offices).
To enable this capability, the primary architectural requirement is the configuration of VPN Clusters.
A VPN Cluster defines a logical group of devices that are authorized to communicate with one another.
* By default, or if devices are in different clusters without peering, the topology typically defaults to Hub- and-Spoke, where branches only talk to the Data Center.
* When two branch ION devices are placed into the same VPN Cluster (or peered clusters), the controller shares the necessary reachability and cryptographic information between them.
Once in the same cluster, the ION devices monitor traffic. If a user at Branch A tries to contact a server at Branch B, the ION devices detect this interest. If a direct path is available (e.g., via public internet), they will dynamically negotiate a direct VPN tunnel, bypassing the Data Center hub. This offloads the hub and reduces latency. Option B is incorrect because SD-WAN eliminates manual GRE config. Option C is incorrect because dynamic VPNs are a performance feature, not just a disaster recovery feature.
NEW QUESTION # 13
An administrator has configured a Zone-Based Firewall (ZBFW) policy on a branch ION. They created a rule to "Allow" traffic from the "Guest" zone to the "Internet" zone. However, users in the "Guest" zone are reporting they cannot reach a specific public website, and the Flow Browser shows the flow state as
"REJECT".
What is the most likely reason for this specific rejection, assuming the "Allow" rule is correctly placed at the top of the list?
- A. The implicit default action at the bottom of the security policy is "Deny All".
- B. The "Allow" rule does not have the specific "Application" defined (it is set to Any), causing a mismatch.
- C. The ION device does not support firewalling for HTTP traffic.
- D. There is a "Deny" rule in the "Global" policy stack that is taking precedence over the "Local" site rule.
Answer: D
Explanation:
Comprehensive and Detailed Explanation
In Prisma SD-WAN, security policies can be applied via Policy Stacks, which often have a hierarchy.
* Stack Precedence: A common configuration involves a Global Security Stack (applied to all sites) and a Local/Site Security Stack (specific to one site). If the administrator configured a "Global" rule that says "Deny Access to Gambling Sites" (or a specific IP list), and that rule is higher in the binding order or part of a higher-priority stack, it will enforce the block before the local "Allow Guest to Internet" rule is processed.
* Specifics of "REJECT": The state REJECT specifically implies a policy enforcement action (sending a TCP RST or ICMP Unreachable) rather than a silent drop or a routing failure.
* Why not A? If the "Allow" rule is at the top and matches the traffic parameters (Zone/IP), the Default Deny at the bottom would never be reached. The issue implies a higher priority Deny exists.
NEW QUESTION # 14
An administrator is configuring an ION 2000 device for a deployment where high availability is required, but the site has only a single internet circuit. The administrator configures a Bypass Pair (Fail-to-Wire) on ports 1 and 2 connecting the ISP modem to the legacy firewall.
If the ION device loses power, what is the resulting behavior of the traffic flowing through this Bypass Pair?
- A. The internal relay closes, physically bridging Port 1 and Port 2, allowing traffic to flow transparently between the modem and firewall.
- B. Traffic is rerouted to the LTE modem automatically.
- C. The device reboots into "Safe Mode" and acts as a Layer 2 switch.
- D. Traffic is blocked to prevent uninspected packets from entering the network (Fail-to-Block).
Answer: A
Explanation:
Comprehensive and Detailed Explanation
The Bypass Pair feature on Prisma SD-WAN ION devices (specifically supported models like ION 2000,
3000, 7000, 9000) is a hardware-based resiliency mechanism known as Fail-to-Wire.
* Operation: A "Bypass Pair" logically groups two physical interfaces (e.g., WAN 1 and LAN 1). Under normal operation, the ION processes traffic between them.
* Power Loss: In the event of a total power loss (or critical software failure), a mechanical relay inside the device physically closes the circuit between the two ports.
* Result: This creates a direct electrical connection (like a patch cable) between the upstream device (ISP Modem) and the downstream device (Legacy Firewall or Router). This ensures that internet connectivity is preserved for the site, even if the SD-WAN appliance is completely dead. This is critical for single-point-of-failure deployments where maintaining basic dial-tone is more important than SD- WAN optimization during a hardware outage.
NEW QUESTION # 15
A remote branch site is reporting intermittent connectivity to the Data Center. The administrator checks the System > Alarms page and sees a "VPN_DOWN" alarm for the tunnel to the DC. However, the internet circuit status is "Up".
Which specific log file or diagnostic tool in the Prisma SD-WAN portal would provide the IKE (Internet Key Exchange) error codes (e.g., "NO_PROPOSAL_CHOSEN" or "AUTH_FAILED") to pinpoint the cause of the tunnel failure?
- A. Site Summary > Topology
- B. Link Quality Graphs
- C. Event Logs > System
- D. Flow Browser
Answer: C
Explanation:
Comprehensive and Detailed Explanation
To diagnose specific VPN negotiation failures (Phase 1 or Phase 2 IPSec issues), the Event Logs (specifically filtered for System or VPN events) are the correct resource.
Event Logs: This section records the control plane signaling messages. If a VPN tunnel fails to establish, the Event Log will generate an entry containing the specific IKE failure reason sent by the peer or generated locally. Common errors found here include INVALID_COOKIE, NO_PROPOSAL_CHOSEN (mismatch in encryption algorithms), or PRE_SHARED_KEY_MISMATCH.
Flow Browser (A): This shows user traffic (TCP/UDP sessions). If the VPN is down, user traffic won't even enter the tunnel, so the Flow Browser will just show dropped flows or blackholes, but it won't explain why the tunnel itself is broken.
Link Quality (D): This shows latency/loss graphs for established tunnels. It cannot diagnose why a tunnel failed to form in the first place.
NEW QUESTION # 16
1000 branches are to be deployed on Prisma SD-WAN with the following constraints:
* Devices will be shipped in batches directly to the site
* Configuration Management Database (CMDB) has all the necessary details for a site deployment
* Field tech will be responsible for rack, stack, and cabling of the IONs at each site
* Field tech will need to spend minimum amount of time at each branch site to reduce the cost
* The NOC operates in shifts and is responsible for remote cutover support Which method will achieve the mass deployment in shortest possible time?
- A. Connect the device to the ISP modem or use cellular, use device shell to pre-create the configuration for a site, assign the device to the template when device is online, and connect the LAN switch to the ION.
- B. Use site templates and device shells to pre-create the configuration using CSV bulk upload, connect the device to the ISP modem or using cellular, assign the device to the template when device is online, and connect the LAN switch to the ION.
- C. Connect the ION to the LAN switch to bring it online, configure the device using the legacy network, connect the ISP modem or cellular, and cutover the site once the ION is configured.
- D. Connect the device to the ISP modem or use cellular, use Prisma SD-WAN Software Development Kit (SDK) using API method for site deployment once the device is online, connect the LAN switch to the ION.
Answer: B
Explanation:
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.
NEW QUESTION # 17
Two branch sites, "Branch-A" and "Branch-B", are both behind active NAT devices (Source NAT) on their local internet circuits.
What requirement must be met for these two branches to successfully establish a direct Dynamic VPN (ION-to-ION) tunnel over the internet?
- A. Both sites must disable NAT and use public IPs on the ION interface.
- B. The ION devices automatically use STUN (Session Traversal Utilities for NAT) to discover their public IPs and negotiate the connection.
- C. One of the sites must have a Static Public IP (1:1 NAT) to act as the initiator.
- D. Dynamic VPNs are not supported if both sides are behind NAT.
Answer: B
Explanation:
Comprehensive and Detailed Explanation
Prisma SD-WAN supports Dynamic VPNs (Branch-to-Branch) even when both endpoints are behind Source NAT (e.g., typical broadband connections).
To achieve this, the ION devices utilize standard NAT Traversal techniques, specifically leveraging STUN (Session Traversal Utilities for NAT).
Discovery: Each ION communicates with the Cloud Controller (which acts as a STUN server/signaling broker). Through this communication, the controller observes the public IP and Port that the ION's traffic is coming from (the post-NAT address).
Signaling: The controller shares this public reachability information with the peer ION.
Hole Punching: The IONs then attempt to initiate connections to each other's discovered public IP/Port. This "UDP Hole Punching" allows them to establish a direct IPSec tunnel through the NAT devices without requiring static 1:1 NAT mapping or manual port forwarding on the provider routers, enabling mesh connectivity in commodity internet environments.
NEW QUESTION # 18
When integrating Prisma SD-WAN with Prisma Access, what is the specific role of the Service Connection (SC)?
- A. It is the peering link between different Prisma Access regions to optimize global traffic.
- B. It is the SSL VPN portal used by mobile users to connect to the network.
- C. It connects the Prisma Access cloud infrastructure back to the customer's Headquarters or Data Center for access to internal private resources (e.g., AD, DNS, Intranet).
- D. It is the IPSec tunnel that connects a Branch site to the Prisma Access gateway for internet access.
Answer: C
Explanation:
Comprehensive and Detailed Explanation
In the Prisma Access architecture (integrated with SD-WAN), distinct connection types serve different purposes.
Remote Networks: These are the connections from your Branch sites (using ION devices) into the cloud. They allow branches to get to the internet or other branches.
Service Connections (SC): This is a specialized high-bandwidth connection used to bridge the Prisma Access Cloud to your Private Data Center or Headquarters.
The primary use case for a Service Connection (Option A) is to allow mobile users and branch users (who are connected to the Prisma cloud) to reach private, centralized resources that still reside on-premise, such as Active Directory controllers, legacy databases, or mainframes. Without a Service Connection, users in the cloud would be able to reach the internet and each other, but not the servers physically located in your HQ data center. The CloudBlade automates the creation of these tunnels, but architecturally, the "Service Connection" is the "cloud-to-HQ" bridge.
NEW QUESTION # 19
An organization has provided the following technical requirements and details:
* High availability (HA) at all data center and branch locations
* Two geographically separate main data center locations
* One small data center location that contains local users and applications requiring policies
* 50 branch locations
* ISP capacities for all branch locations but no accurate measurement of the actual bandwidth consumption Based on Palo Alto Networks best practices and recommendations, which two licensing options will meet the customer objectives? (Choose two.)
- A. Aggregate bandwidth subscription
- B. Six data center subscriptions
- C. Branch subscription per site
- D. Four data center subscriptions
Answer: A,B
Explanation:
Prisma SD-WAN licensing is structured to provide flexibility while ensuring that all components of the secure fabric are correctly accounted for. To meet the requirements of this organization, we must calculate the necessary subscriptions for both the data center hubs and the distributed branch network.
First, we address the Data Center Subscriptions. The organization has two main geographically separate data centers and one small data center, all of which require High Availability (HA). In a Prisma SD-WAN deployment, HA at a site is achieved by deploying two ION devices in a cluster. Palo Alto Networks licensing requires a separate Data Center subscription for each ION device acting as a hub. Therefore, with three data center locations (2 main + 1 small) each requiring an HA pair (2 devices per site), a total of six data center subscriptions (Option A) are required to license all six hub appliances.
Second, we address the Branch Subscriptions. The organization has 50 branches but lacks accurate measurements of actual bandwidth consumption. Palo Alto Networks' best practice for such scenarios is the Aggregate Bandwidth Subscription model (Option B). Instead of purchasing a fixed "Branch subscription per site" (Option D)-which requires knowing the exact throughput needs for every individual location-the aggregate model allows the customer to purchase a total pool of bandwidth (e.g., 5 Gbps) that is shared across all 50 branch sites.
This "pay-as-you-grow" approach is ideal when consumption patterns are unknown or inconsistent. As branches utilize the bandwidth, it is deducted from the central pool. This avoids the risk of over-provisioning licenses at low-usage sites or under-provisioning at high-usage sites. Together, the six DC subscriptions and the aggregate bandwidth pool provide a fully licensed, HA-capable SD-WAN environment that aligns with Palo Alto Networks' scaling recommendations.
NEW QUESTION # 20
A network installer is attempting to claim a new ION device using the "Claim Code" method. The device is connected to the internet, but the status in the portal remains stuck at "Claimed" and does not transition to "Online". The installer connects a laptop to the LAN port of the ION and can successfully browse the internet, confirming the uplink is active.
What is the most likely cause of the device failing to reach the "Online" state?
- A. The device is missing the "Site" assignment in the portal.
- B. The "Circuit Label" has not been applied to the WAN interface.
- C. The upstream firewall is blocking outbound TCP port 443 or UDP port 123 (NTP).
- D. The device has not yet downloaded the latest software image.
Answer: C
Explanation:
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.
NEW QUESTION # 21
There are periodic complaints about the poor performance of a real-time application.
What can be inferred about the performance issue, based on the Network Transfer Time (NTT) and Server Response Time (SRT) image below?
- A. The SRT value drops periodically due to Application Server side issues.
- B. The NTT value increases periodically resulting in higher SRT.
- C. The SRT value increases periodically due to Application Server side issues.
- D. The NTT value drops periodically due to network related issues.
Answer: C
Explanation:
In Prisma SD-WAN, application performance is monitored through distinct metrics that separate network health from application health. The provided graph displays Network Transfer Time (NTT) in blue and Server Response Time (SRT) in orange. NTT measures the round-trip time of packets traversing the WAN fabric, while SRT measures the time elapsed from when the server receives a request to when it sends the first response packet.
Analysis of the telemetry data shows that the NTT (blue line) remains consistently low and stable, generally staying below 100 milliseconds throughout the capture period. This indicates that the SD-WAN path and underlying network circuits are not the source of the latency. Conversely, the SRT (orange line) exhibits significant and erratic spikes, reaching as high as 450 to 475 milliseconds. These spikes occur while the network latency (NTT) remains flat.
Because the latency increases are isolated to the SRT metric, the root cause is confirmed to be on the Application Server side. This pattern typically suggests that the server is struggling with resource exhaustion, high CPU utilization, or database query delays during peak processing times. For a real-time application, these SRT spikes translate directly to jitter and "lag" for the end-user. By distinguishing between these two metrics, Prisma SD-WAN allows network administrators to prove that the network is performing within SLA and shift the troubleshooting focus to the application or server management teams, significantly reducing mean time to innocence (MTTI).
NEW QUESTION # 22
A site has two internet circuits: Circuit A with 500 Mbps capacity and Circuit B with 100 Mbps capacity.
Which path policy configuration will ensure traffic is automatically shifted from a saturated circuit to the circuit with available bandwidth?
- A. Both circuits under active path
- B. Circuit B as an active, Circuit A as a backup
- C. Circuit A as an active, Circuit B as a backup
- D. Circuit B as an L3 failure path
Answer: A
Explanation:
Comprehensive and Detailed Explanation
In Prisma SD-WAN (CloudGenix), Path Policies control how application traffic is steered across WAN links. To ensure that traffic is automatically shifted from a saturated circuit to another circuit with available bandwidth, both circuits must be configured as Active Paths within the policy rule.
When multiple paths are designated as "Active," the ION device treats them as a shared pool of available resources. The system continuously monitors the bandwidth utilization (capacity) and health (latency, jitter, loss) of all active links. If "Circuit A" (500 Mbps) becomes saturated or approaches its defined bandwidth limit, the ION's intelligent scheduler will automatically direct new application flows to "Circuit B" (100 Mbps) because it is a valid, healthy Active path with available capacity. This achieves effective load balancing and bandwidth aggregation.
In contrast, configuring "Circuit B" as a Backup Path (Option A or B) creates a strict priority relationship. Traffic would only move to the Backup path if the Active path completely failed or violated its configured SLA (Path Quality Profile) significantly enough to be considered "down." Mere bandwidth saturation might not trigger an SLA failure immediately, potentially leading to dropped packets on the saturated link while the backup link remains idle. Therefore, placing Both circuits under active path is the correct configuration for dynamic capacity management.
NEW QUESTION # 23
In which modes can a Prisma SD-WAN branch be deployed?
- A. Testing, Control, POV
- B. Disabled, Analytics, Control
- C. Production, Control, Disabled
- D. POV, Production, Analytics
Answer: B
Explanation:
Comprehensive and Detailed Explanation
Prisma SD-WAN (formerly CloudGenix) defines three distinct Operational Modes for a branch site, which determine how the ION device processes traffic and interacts with the network.
* Analytics Mode (Monitor): In this mode, the ION device is typically deployed inline or in a
"promiscuous" monitor state to gain visibility into network traffic without actively enforcing path selection policies.1 It "learns" applications, bandwidth usage, and network characteristics (auditing) but does not steer traffic or block flows.2 This is often used during Proof of Concepts (POVs) or the initial
"burn-in" phase of a deployment to generate reports without risking network disruption.
* Control Mode: This is the full production state. In Control Mode, the ION device actively enforces Path Policies, QoS Policies, and Security Policies. It builds Secure Fabric VPN tunnels, steers traffic based on application SLAs (e.g., sending voice over MPLS and bulk data over Broadband), and handles failover events.3 This is the required mode for a fully functional SD-WAN site.
* Disabled Mode: This mode effectively shuts down the site's SD-WAN functionality from the controller's perspective. It is an administrative state used when a site is being decommissioned, provisioned but not yet live, or isolated for troubleshooting. In this state, the device does not participate in the fabric.
NEW QUESTION # 24
When identifying devices for IoT classification purposes, which two methods does Prisma SD-WAN use to discover devices that are not directly connected to the branch ION? (Choose two.)
- A. CDP
- B. SNMP
- C. Syslog
- D. LLDP
Answer: B,C
Explanation:
Comprehensive and Detailed Explanation
Prisma SD-WAN (formerly CloudGenix) integrates with Palo Alto Networks IoT Security to provide comprehensive visibility into all devices at a branch, including those that are not directly connected to the ION device. While the ION automatically detects and classifies devices connected directly to its interfaces via traffic inspection (DPI), DHCP, and ARP analysis, gaining visibility into off-branch devices (devices connected to downstream switches or access points) requires additional discovery mechanisms that can query the network infrastructure or ingest its logs.
1. SNMP (Simple Network Management Protocol): This is the primary active discovery method for off- branch devices. The Prisma SD-WAN ION device acts as a sensor that actively polls local network switches and wireless controllers using SNMP. By querying the ARP tables and MAC address tables (Bridge MIBs) of these intermediate network devices, the ION can identify endpoints that are connected to the switch ports, even if those endpoints are not currently sending traffic through the ION. This allows the system to map the topology and discover silent or lateral-traffic-only devices.
2. Syslog: In conjunction with SNMP, the IoT Security solution can utilize Syslog messages to discover and profile devices. Network infrastructure devices (like switches and WLAN controllers) can be configured to send Syslog messages to the collection point (which enables the IoT Security service) whenever a device connects or disconnects (e.g., port up/down events, DHCP snooping logs, or 802.1x authentication logs).
These logs provide real-time data about device presence and identity (MAC/IP mappings) for devices that are not directly adjacent to the ION, ensuring 100% visibility across the branch network segments. LLDP (A) and CDP (B) are typically Link Layer discovery protocols used for discovering directly connected neighbors and do not propagate beyond the immediate link, making them unsuitable for discovering devices multiple hops away or behind a switch.
NEW QUESTION # 25
What is the number and structure of Prisma SD-WAN QoS queues supported per WAN interface?
- A. 16 queues
4 classes
4 application criteria with each class - B. 12 queues
4 classes1
3 application criteria within each class - C. 8 queues
1 priority queue
7 non-priority queues - D. 8 queues
2 classes
4 application criteria within each class
Answer: A
Explanation:
Comprehensive and Detailed Explanation
The Prisma SD-WAN (ION) QoS engine utilizes a hierarchical queuing structure designed to provide granular control over application performance. Each WAN interface on an ION device supports a total of 16 QoS queues.
This 16-queue structure is derived from a matrix of 4 Classes (often referred to as Priority Classes) multiplied by 4 Application Criteria (Traffic Types).2
4 Priority Classes: The system defines four high-level business priority categories:3 Platinum (Highest priority)4 Gold Silver Bronze (Lowest priority/Best Effort)5
4 Application Criteria (Sub-queues): Within each of the four priority classes, the system further categorizes traffic into four specific application types to ensure proper handling (e.g., ensuring voice doesn't get stuck behind bulk data even within the same priority level):6 Real-Time Video Real-Time Audio Transactional Bulk7 Calculation: 4 Priority Classes × 4 Application Types = 16 Total Queues per interface. This structure allows the scheduler to ensure that a "Platinum" voice call is prioritized over "Platinum" bulk data, and both are prioritized over "Gold" traffic.
NEW QUESTION # 26
Which condition, when configured within a performance policy, is a trigger for generating an incident related to application performance or path degradation?
- A. Violation of defined service-level agreement (SLA) thresholds for application performance or link quality.
- B. Physical WAN interface transitioning from an "up" to a "down" state, resulting in a NETWORK_ANYNETLINK_DOWN event.
- C. Loss of a BGP peering session on a data center ION device, leading to potential routing instability.
- D. Exceeding the configured threshold for total concurrent flows in the ION device, resulting in a SYSTEM_CONCURRENT_FLOW_THRESHOLD_EXCEEDED incident.
Answer: A
Explanation:
In Prisma SD-WAN, Performance Policies are the primary mechanism used to define the expected quality of experience for specific applications. Unlike traditional monitoring that relies solely on "up/down" interface states, Prisma SD-WAN focuses on the actual health of the application path. An incident is triggered when the system detects a violation of defined service-level agreement (SLA) thresholds, such as excessive latency, jitter, or packet loss, even if the physical link remains active.
When an administrator configures a performance policy, they set specific bounds for these metrics. For example, a VoIP application might have an SLA requiring latency below 150ms and packet loss below 1%. If the ION device detects that the current path (e.g., a broadband circuit) exceeds these limits, it generates a performance incident. This incident serves two purposes: first, it alerts the administrator to the degradation; second, it triggers the Path Selection engine to proactively steer the application traffic to a more suitable
"Backup" or "Available" path that currently meets the SLA requirements.
Options B, C, and D represent system-level or network-level events that generate different types of alerts or incidents (System or Network incidents), but they are not the triggers defined within a Performance Policy.
Performance policies are specifically concerned with the application's perceived performance across the fabric. By focusing on SLA violations rather than just physical link status, Prisma SD-WAN ensures that business-critical applications remain functional even during "brownout" conditions where a circuit is technically "up" but performing poorly.
NEW QUESTION # 27
......
Palo Alto Networks SD-WAN-Engineer Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
Fully Updated Dumps PDF - Latest SD-WAN-Engineer Exam Questions and Answers: https://www.prep4pass.com/SD-WAN-Engineer_exam-braindumps.html
Updated SD-WAN-Engineer PDF for the SD-WAN-Engineer Tests Free Updated Today: https://drive.google.com/open?id=10VzmKHEQBIzLSB4jqzlqTUQHLmaYBYmx
