Question 140
An operations group at a service-provider edge resolved: An analyst confuses implicit SD-WAN rule hits with explicit application-specific rule selection during a monthly performance review. Which ongoing safeguard should become part of its change process?
Explanation
Correct Answer
Label and report implicit rule traffic separately from named application steering. This control reduces recurrence of the documented mechanism: Implicit fallback can appear similar to a normal rule if logs are read without service context. It creates a repeatable check around the needed response: Inspect matched service-rule identifiers and distinguish explicit versus implicit policy matches.
Incorrect Answers
Monitor NTP drift and preserve timezone metadata in security log analysis. That safeguard addresses another potential failure: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. It is not the most targeted recurring control for the described cause: Implicit fallback can appear similar to a normal rule if logs are read without service context.
Record data freshness and reporting time boundaries on WAN health dashboards. That safeguard addresses another potential failure: A service report claims a WAN path is healthy based on an old dashboard snapshot even though the SLA failed later in the review interval. It is not the most targeted recurring control for the described cause: Implicit fallback can appear similar to a normal rule if logs are read without service context.
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: Implicit fallback can appear similar to a normal rule if logs are read without service context.