Question 510
At Alpine Public Works, an infrastructure review by the infrastructure assurance team is evaluating mobile inspections and work orders across a multi-region public service network during a secured remote-work pilot (FT-B-01-03). The review finds that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. Any correction must respect this operating requirement: privileged service access remains auditable during outages. Which result is the strongest evidence that the corrective approach succeeded?
Explanation
Correct Answer
This is the most direct validation of the stated failure: In a controlled a multi-region public service network acceptance test, Rule diagnostics show the payment session matches the intended application-specific rule; the outcome is recorded under Alpine Public Works's rollout (FT-B-01-03). It tests the result of the proposed action, reorder and scope the more specific application or destination rule ahead of the generic fallback, rather than a separate feature or an unrelated path metric. The relevant principle is that First-match steering policy design can make generic rules shadow intended exceptions.
Incorrect Answers
The source case reports that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. That observation would support a control associated with: SD-WAN rule strategy determines how eligible path metrics affect selection. It does not prove the specific correction worked. Confirm “Rule diagnostics show the payment session matches the intended application-specific rule; capture the relevant session and policy trace” against: First-match steering policy design can make generic rules shadow intended exceptions.
The source case reports that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. The proposed evidence concerns: FortiGate local-out traffic can have separate selection and routing considerations. The current question instead requires an outcome tied to: First-match steering policy design can make generic rules shadow intended exceptions. The direct observation is “Rule diagnostics show the payment session matches the intended application-specific rule; capture the relevant session and policy trace”.
The source case reports that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. “Loss of either hub restores protected private reachability over the alternate route; confirm it in an approved negative test” tests the distinct technical dependency: Overlay redundancy requires backup control-plane and data-plane continuity. This test could pass while the stated failure remains. The direct verification here is “Rule diagnostics show the payment session matches the intended application-specific rule; capture the relevant session and policy trace” because first-match steering policy design can make generic rules shadow intended exceptions.