Question 220
An operations group at a manufacturing plant resolved: A site sees duplicate-looking flow logs for retransmissions during an SD-WAN failover, and analysts count them as distinct user sessions. Which ongoing safeguard should become part of its change process?
Explanation
Correct Answer
Use session IDs or supported correlation keys when measuring failover connection counts. This control reduces recurrence of the documented mechanism: Packet retransmissions and new sessions are different events even if addresses match. It creates a repeatable check around the needed response: Correlate session identifiers, protocol state and timestamps before counting unique connections.
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: Packet retransmissions and new sessions are different events even if addresses match.
Retain performance SLA history alongside application experience incidents. That safeguard addresses another potential failure: Voice complaints occur after WAN jitter spikes but the incident review relies on total traffic-byte reports without any performance SLA history. It is not the most targeted recurring control for the described cause: Packet retransmissions and new sessions are different events even if addresses match.
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: Packet retransmissions and new sessions are different events even if addresses match.