Question 240
After a corrective change at a national SOC, the team documents: A branch link becomes congested yet a report labels all sessions as normal because the dashboard tracks bytes and not interface drops or SLA degradation. Which repeatable control BEST prevents a recurrence?
Explanation
Correct Answer
Review link saturation metrics and health-check measurements in combined WAN performance reports. This control reduces recurrence of the documented mechanism: High byte counts alone cannot establish whether a path met application quality needs. It creates a repeatable check around the needed response: Add appropriate interface utilization, drop and SLA metrics to the operational analysis alongside session volume.
Incorrect Answers
Use per-session SD-WAN rule and egress fields during steering incident triage. That safeguard addresses another potential failure: A branch's CRM sessions use wan2 instead of preferred wan1 but an engineer looks only at interface uptime rather than the matching SD-WAN service logs. It is not the most targeted recurring control for the described cause: High byte counts alone cannot establish whether a path met application quality needs.
Maintain per-member utilization dashboards with cost thresholds. That safeguard addresses another potential failure: An operations dashboard shows an unexpected surge on cellular backup but a report aggregates all WAN members, obscuring the affected interface. It is not the most targeted recurring control for the described cause: High byte counts alone cannot establish whether a path met application quality needs.
Check rule hit and session keys before tuning SLA thresholds. That safeguard addresses another potential failure: An engineer states SD-WAN ignored a rule because the interface was healthy, but rule diagnostics show no source-address match for the problem client. It is not the most targeted recurring control for the described cause: High byte counts alone cannot establish whether a path met application quality needs.