Question 210
At Juniper Manufacturing, an infrastructure review by the plant network engineers is evaluating plant-to-datacenter traffic across an industrial site WAN during a secured remote-work pilot (FT-B-08-02). The review finds that a dual-uplink branch has a static route bound to one failed member rather than a resilient SD-WAN zone. Any correction must respect this operating requirement: operational technology subnets keep their approved segmentation. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a dual-uplink branch has a static route bound to one failed member rather than a resilient SD-WAN zone. Select route attachment appropriate to the intended member or zone failover behavior as part of Juniper Manufacturing's plant-to-datacenter traffic update (FT-B-08-02), while enforcing the constraint that operational technology subnets keep their approved segmentation. A successful implementation must be checked rather than assumed: In a controlled an industrial site WAN acceptance test, When the preferred transport fails the destination remains reachable through the approved alternate member; the outcome is recorded under Juniper Manufacturing's rollout (FT-B-08-02). The technical reason is that A route tied to one interface can constrain otherwise available SD-WAN failover.
Incorrect Answers
The source case reports that a dual-uplink branch has a static route bound to one failed member rather than a resilient SD-WAN zone. This option would change the control governed by: Transport reachability alone may not reveal the usable quality of an overlay. That does not resolve the present failure, where a route tied to one interface can constrain otherwise available SD-WAN failover. The applicable response is “Select route attachment appropriate to the intended member or zone failover behavior; stage the change with an explicit backout plan”.
The source case reports that a dual-uplink branch has a static route bound to one failed member rather than a resilient SD-WAN zone. The offered alternative is useful for: Policy route decisions can affect forwarding independently of the main static route preference. In this case the decisive mechanism is: A route tied to one interface can constrain otherwise available SD-WAN failover. The specific action is “Select route attachment appropriate to the intended member or zone failover behavior; stage the change with an explicit backout plan”.
The source case reports that a dual-uplink branch has a static route bound to one failed member rather than a resilient SD-WAN zone. This option would change the control governed by: FortiGate local-out traffic can have separate selection and routing considerations. That does not resolve the present failure, where a route tied to one interface can constrain otherwise available SD-WAN failover. The applicable response is “Select route attachment appropriate to the intended member or zone failover behavior; stage the change with an explicit backout plan”.