Question 710
At Harbor Civic, an infrastructure review by the government network operations team is evaluating citizen service reachability across a county-service branch network during a secured remote-work pilot (FT-B-04-02). 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: case data must remain within approved agency boundaries. 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 citizen service reachability 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 alternative states a real but different technical principle: SD-WAN rule strategy determines how eligible path metrics affect selection; separate observed path selection from configuration intent. The facts in this question are explained by: Implicit behavior applies when no higher-priority user-defined rule matches; separate observed path selection from configuration intent.
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: Application-aware and internet-service matching can be more stable than static cloud IP lists; avoid assuming a healthy session proves all services work. It is not the causal distinction established here: Implicit behavior applies when no higher-priority user-defined rule matches; separate observed path selection from configuration intent.
The source case reports that an unmatched flow uses a default path that differs from the intended high-priority custom rule. The alternative states a real but different technical principle: ADVPN can create on-demand shortcuts inside a governed hub-and-spoke overlay; avoid assuming a healthy session proves all services work. The facts in this question are explained by: Implicit behavior applies when no higher-priority user-defined rule matches; separate observed path selection from configuration intent.