Question 420
At Orchard Biotech, an infrastructure review by the laboratory network group is evaluating remote researcher access across a laboratory hybrid network before an expanded branch rollout (FT-B-05-01). The review finds that device-originated DNS and management traffic uses an undesirable WAN despite correct client data-plane rules. Any correction must respect this operating requirement: sensitive lab assets remain inaccessible to untrusted endpoints. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that device-originated DNS and management traffic uses an undesirable WAN despite correct client data-plane rules. Review local-out routing and applicable SD-WAN steering separately from transit traffic rules as part of Orchard Biotech's remote researcher access update (FT-B-05-01), while enforcing the constraint that sensitive lab assets remain inaccessible to untrusted endpoints. A successful implementation must be checked rather than assumed: In a controlled a laboratory hybrid network acceptance test, A device-originated connectivity test uses the intended healthy member without altering user sessions; the outcome is recorded under Orchard Biotech's rollout (FT-B-05-01). The technical reason is that FortiGate local-out traffic can have separate selection and routing considerations.
Incorrect Answers
The source case reports that device-originated DNS and management traffic uses an undesirable WAN despite correct client data-plane rules. This option would change the control governed by: Matching and quality-based member choice are separate stages of SD-WAN processing. That does not resolve the present failure, where fortiGate local-out traffic can have separate selection and routing considerations. The applicable response is “Review local-out routing and applicable SD-WAN steering separately from transit traffic rules; confirm the dependent routing state”.
The source case reports that device-originated DNS and management traffic uses an undesirable WAN despite correct client data-plane rules. “Reorder and scope the more specific application or destination rule ahead of the generic fallback; confirm the dependent routing state” addresses the technical dependency: First-match steering policy design can make generic rules shadow intended exceptions. The reported problem instead follows: FortiGate local-out traffic can have separate selection and routing considerations. The more direct correction is “Review local-out routing and applicable SD-WAN steering separately from transit traffic rules; confirm the dependent routing state”.
The source case reports that device-originated DNS and management traffic uses an undesirable WAN despite correct client data-plane rules. This option would change the control governed by: A route tied to one interface can constrain otherwise available SD-WAN failover. That does not resolve the present failure, where fortiGate local-out traffic can have separate selection and routing considerations. The applicable response is “Review local-out routing and applicable SD-WAN steering separately from transit traffic rules; confirm the dependent routing state”.