Question 380
An emergency change is proposed for: An analyst sees an unexpected new SD-WAN policy match after migrating an application from TCP to QUIC. Which caution is most important for this specific change?
Explanation
Correct Answer
The most relevant caution is that assuming an application always retains its former port and protocol across software updates is unreliable. The case concerns an analyst sees an unexpected new SD-WAN policy match after migrating an application from TCP to QUIC. The safer path is to compare application identification, service/protocol logs, and matched SD-WAN rule criteria and then, after verification, to update supported steering match rules based on the validated protocol and app identity. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Misaligned clocks can make a healthy failover sequence appear to precede the triggering outage. The check concerns misaligned clocks can make a healthy failover sequence appear to precede the triggering outage, not confirming that assuming an application always retains its former port and protocol across software updates is unreliable.
Historical hits should not be interpreted as evidence that a rule remains enabled today. This assesses historical hits should not be interpreted as evidence that a rule remains enabled today; it does not determine the reported condition—an analyst sees an unexpected new SD-WAN policy match after migrating an application from TCP to QUIC.
A snapshot green status may hide a short-lived quality failure during a user call. The case-specific requirement is confirming that assuming an application always retains its former port and protocol across software updates is unreliable, which that option does not establish.