Question 370
At Yardley Foods, an infrastructure review by the security architecture group is evaluating cold-chain site communications across a food distribution SD-WAN after an audit of cloud access (FT-B-04-01). The review finds that an unmatched flow uses a default path that differs from the intended high-priority custom rule. Any correction must respect this operating requirement: warehouse telemetry stays on explicitly approved secure paths. Which architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Implicit behavior applies when no higher-priority user-defined rule matches. In this cold-chain site communications decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that an unmatched flow uses a default path that differs from the intended high-priority custom rule; the intended approach is to create an appropriate explicit match if required and review implicit rule behavior. The distinguishing confirmation is that A previously unmatched test flow now follows its approved explicit steering policy.
Incorrect Answers
The source case reports that an unmatched flow uses a default path that differs from the intended high-priority custom rule. The proposed explanation concerns: First-match steering policy design can make generic rules shadow intended exceptions; do not infer authorization solely from connectivity. The reported symptom instead follows: Implicit behavior applies when no higher-priority user-defined rule matches.
The source case reports that an unmatched flow uses a default path that differs from the intended high-priority custom rule. That principle controls the offered alternative: FortiGate local-out traffic can have separate selection and routing considerations; do not infer authorization solely from connectivity. It is not the causal distinction established here: Implicit behavior applies when no higher-priority user-defined rule matches.
The source case reports that an unmatched flow uses a default path that differs from the intended high-priority custom rule. The proposed explanation concerns: Parameterized overlay deployment reduces duplicated manual configuration in large fabrics; do not infer authorization solely from connectivity. The reported symptom instead follows: Implicit behavior applies when no higher-priority user-defined rule matches.