In a Prisma SD-WAN environment experiencing voice quality degradation, which initial action is recommended?

The most appropriate initial action for troubleshooting voice quality degradation is to investigate and diagnose the root cause. Prisma SD-WAN provides extensive real-time analytics for path performance, including critical metrics for voice traffic such as latency, jitter, and packet loss. By reviewing these analytics, an administrator can identify which specific network path is underperforming and causing the issue. This data-driven approach is fundamental to effective troubleshooting, allowing for a precise understanding of the problem before taking any corrective action. Making configuration changes or assuming hardware failure without first analyzing performance data is contrary to best practices.

A. Modifying path quality thresholds without first diagnosing the problem is a reactive change that may mask the underlying issue or cause other unpredictable network behavior.
C. Switching all traffic is a temporary fix, not a diagnostic step. The primary path's issue remains unaddressed, and the backup path may not be optimal.
D. Requesting a Return Merchandise Authorization (RMA) is a drastic measure. It assumes hardware failure without any evidence, which should only be considered after exhausting all other troubleshooting steps.

1. Palo Alto Networks Prisma SD-WAN Administrator’s Guide 6.2: The guide emphasizes using the monitoring features for troubleshooting. The "Monitor" section details how to view network health. Specifically, the "Monitor > Sites > Health" page allows administrators to "view the health of the circuits at a site" and analyze "Link Quality metrics such as Latency, Jitter, and Packet Loss," which are essential for diagnosing VoIP issues. (Reference: Chapter "Monitor", Section "Monitor Sites").

2. Palo Alto Networks Prisma SD-WAN Administrator’s Guide 6.2: The "Monitor > Applications" page provides visibility into application performance. For VoIP, this includes the Mean Opinion Score (MOS). The guide states, "You can view application performance metrics to troubleshoot network issues." This directly supports reviewing analytics as the initial step. (Reference: Chapter "Monitor", Section "Monitor Applications").

3. Palo Alto Networks TechDocs - Troubleshoot Poor Application Performance: In the context of troubleshooting, the official documentation consistently prioritizes investigation through monitoring tools. The first step is always to "Use the Prisma SD-WAN web interface to investigate the issue," which involves checking application performance scores and path statistics before making any changes. (Reference: Prisma SD-WAN Docs > Troubleshoot > Troubleshoot Poor Application Performance).