Important Palo Alto Networks SD-WAN-Engineer Exam Questions

Answer: C

Explanation:

In the Prisma SD-WAN architecture, the Controller serves as the centralized management and control plane for the entire fabric. While the Cloud Identity Engine (CIE) is the component responsible for collecting and consolidating user-to-IP mappings from various identity providers (such as Active Directory, Okta, or Azure AD), it does not directly manage the distribution of this operational data to the individual ION devices at the branch level.

Instead, the Prisma SD-WAN Controller integrates with the Cloud Identity Engine to ingest these identity mappings. Once the Controller has synchronized the User-IP and user-group information, it acts as the primary orchestrator. It is responsible for distributing these mappings down to the ION devices across all sites. This distribution ensures that when an ION device sees traffic from a specific source IP, it can accurately associate that traffic with a specific user or group based on the metadata provided by the Controller.

By centralizing this distribution through the Controller, Prisma SD-WAN ensures consistency across the network. Branch ION devices can then apply Application-Based Path Selection and security policies based on user identity rather than just IP addresses. This architectural design offloads the processing requirements of maintaining direct connections to identity providers from the branch hardware, allowing the Controller to handle the heavy lifting of orchestration and global synchronization of identity data.

Answer: C

Explanation:

Comprehensive and Detailed Explanation

The SITE_CONNECTIVITY_DOWN alarm is a high-severity alert indicating a total loss of overlay connectivity for a site.

It does not trigger if just one circuit fails (Option B), provided that other circuits are still up and maintaining VPNs. A single link failure would typically trigger a 'Link Down' or 'VPN Down' alarm, but the Site connectivity would remain 'Up' (degraded).

It does not simply mean the device rebooted (Option A), although a reboot would cause it temporarily; the alarm specifically tracks the state of the VPN fabric.

The SITE_CONNECTIVITY_DOWN alarm specifically generates when all Secure Fabric Links (VPN tunnels) on the device are in the 'Down' state. This means the branch is completely isolated from the rest of the SD-WAN network (Data Centers and other branches), even if the device itself might still be powered on and reachable via the controller (management plane). It signifies a 'Blackout' of the data plane for that location.

Answer: A

Explanation:

Palo Alto Networks IoT Security relies on rich metadata and traffic logs to identify, classify, and secure devices across the network. A critical component of this discovery process is the ingestion of DHCP (Dynamic Host Configuration Protocol) traffic. DHCP packets contain vital information about a device, such as the MAC address, vendor-specific identifiers (Option 60), and hostnames, which are used by the machine learning engine to create a precise device profile.

In a Prisma SD-WAN environment, if the ION devices are not involved in the DHCP process, the necessary logs cannot be forwarded to the Strata Logging Service (SLS) for analysis by the IoT Security cloud. To ensure successful discovery, the ION device at the branch must be explicitly configured as either the DHCP Server for the local segment or as a DHCP Relay Agent. When the ION handles DHCP traffic, it automatically extracts and sends the relevant metadata to the cloud.

If the ION is bypassed---for example, if a local Layer 3 switch is handling DHCP internally without relaying it to the ION---the IoT Security service will lack the context needed to move beyond basic IP-level visibility. Without these DHCP-derived 'fingerprints,' the system cannot perform the full classification required to apply granular security policies or identify potential vulnerabilities. Therefore, verifying that the ION device is correctly integrated into the DHCP lifecycle is the primary troubleshooting step for incomplete IoT device discovery in the Prisma SD-WAN portal.

Answer: A

Explanation:

In a Prisma SD-WAN deployment, the routing of traffic between branches and Data Centers (DCs) relies on the proper synchronization between the AppFabric (the overlay) and the local routing protocols (the underlay/LAN side). In this scenario, the branch can successfully reach DC1, indicating the branch ION is correctly participating in the fabric. However, traffic to DC2 (10.2.2.22) is failing.

The DC2 site has the site prefix 10.2.2.0/23 configured. In Prisma SD-WAN, defining a site prefix informs the Controller that this specific subnet 'belongs' to that site, causing the Controller to advertise reachability for this prefix to all other ION devices in the fabric. Consequently, when the branch ION (192.168.1.123) attempts to reach 10.2.2.22, it correctly identifies DC2 as the destination and encapsulates the traffic toward the DC2 ION.

The bottleneck occurs once the packet arrives at the DC2 ION. While the ION is advertising the branch subnet (192.168.1.0/24) to the DC Core (ensuring the return path), the ION itself must know how to forward the incoming traffic from the branch to the internal DC network. If the DC2 ION does not have a specific route in its local routing table for the 10.2.2.0/23 subnet pointing to the DC Core's internal interface, the packet will be dropped.

According to Palo Alto Networks best practices for Data Center ION deployment, a static default route (0.0.0.0/0) should be configured on the ION device pointing toward the DC Core's next-hop IP address. This ensures that any traffic received from the AppFabric destined for internal DC resources---which are not directly connected to the ION---is successfully handed off to the core switching fabric for final delivery. Adding this default route (Option A) resolves the reachability issue by providing the 'last-hop' routing instruction within the DC.

Answer: C

Explanation:

In Prisma SD-WAN, path selection and traffic symmetry are governed by the Path Policy and the available physical/virtual circuits at a site. The scenario describes a situation where return traffic is dropped on the branch ION after arriving via an Internet overlay. To understand why, we must analyze the 'Active' and 'Backup' paths defined in the policy.

The policy specifies Active = MPLS Overlay and Backup = Prisma Access on internet. In a healthy environment, the ION device expects to send and receive traffic based on these defined paths. If the site actually has two internet circuits and no MPLS circuit (Option C), a critical mismatch occurs. Because there is no MPLS circuit available to satisfy the 'Active' path, the device will fall back to the 'Backup' path for initiated traffic.

However, the core issue here relates to how Prisma SD-WAN handles asymmetric routing and session state. If traffic arrives at the branch via an 'Internet Overlay' path that is not explicitly defined or allowed as a valid path for that specific application in the Path Policy, the ION device's flow integrity checks may drop the packets. Specifically, if the ION is configured with only Internet circuits but the policy is looking for an MPLS overlay that doesn't exist, the device may fail to correctly associate the return packets with the session state if the paths are perceived as 'unbound' or 'invalid' per the policy. This behavior is a security feature designed to ensure that traffic only traverses paths that meet the administrator's defined performance and security criteria. Without an MPLS circuit present, the policy cannot be fully realized, leading to potential drops for traffic arriving on paths not intended for that specific application flow.