An administrator notices that Prisma Access users experience intermittent connection drops. What should be the first step in troubleshooting?

Question

Options

• AReconfigure mobile user VPN settings
• BRestart all security nodes
• CDisable security policies temporarily
• DCheck the Prisma Access real-time monitoring tools

• A
  9% (3)
• B
  3% (1)
• C
  3% (1)
• D
  84% (27)

Explanation

Checking real-time monitoring tools (D) is the correct first step because troubleshooting always begins with observation and data gathering - you need to understand what is happening before taking any corrective action, and Prisma Access provides dashboards and logs specifically designed to surface connection issues, latency, and node health in real time.

Why the distractors are wrong:

• (A) Reconfigure VPN settings - this is a corrective action, not a diagnostic one; you'd only do this after identifying a misconfiguration as the root cause.
• (B) Restart all security nodes - a drastic, disruptive action that could worsen the outage and should never be a first step without evidence that nodes are the problem.
• (C) Disable security policies - this creates a security gap and is never appropriate as a first troubleshooting step; it also wouldn't reveal the cause of connection drops.

Memory tip: Remember the rule "Diagnose before you act." In any network or cloud troubleshooting scenario, monitoring/logging tools are always the first step - they're your evidence before you touch anything.

No community discussion yet for this question.