How can a network administrator diagnose intermittent connectivity issues in an SD-WAN deployment aimed at Google Cloud? (Choose Two)

Question

Options

• AAnalyzing real-time logs
• BChecking the SD-WAN event history
• CUpdating device firmware
• DVerifying physical cable integrity

• A
  95% (35)
• C
  3% (1)
• D
  3% (1)

Explanation

Diagnosing intermittent connectivity issues requires real-time visibility and historical pattern analysis, which is exactly what options A and B provide. Analyzing real-time logs (A) lets the administrator observe live traffic anomalies, latency spikes, or path failures as they occur. Checking the SD-WAN event history (B) surfaces patterns over time - intermittent issues often only reveal themselves when you correlate timestamps across multiple events.

C (Updating firmware) is a remediation action, not a diagnostic one - it might fix a known bug, but it doesn't help you identify the root cause of an intermittent issue. D (Verifying physical cable integrity) is a Layer 1 troubleshooting step relevant to on-premises hardware failures, but SD-WAN targeting Google Cloud uses internet/overlay tunnels, making physical cable checks irrelevant to the problem space.

Memory tip: Think "See it happening, See what happened" - real-time logs = see it now, event history = see what happened before. Both are observational tools, which is what diagnosis demands.

No community discussion yet for this question.