Question 850
The deployment team is preparing a sign-off for: A branch uses static routes for each member rather than the intended SD-WAN zone and route selection remains pinned to one link. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that manually pinning a static route to one physical link can undermine SD-WAN steering design. The case concerns a branch uses static routes for each member rather than the intended SD-WAN zone and route selection remains pinned to one link. The safer path is to compare per-interface static routes, zone-route design, and administrative preference for the public destination and then, after verification, to replace conflicting per-member routes with validated supported zone routing where appropriate. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
SD-WAN rules do not remove the need for a usable destination route. The check concerns sD-WAN rules do not remove the need for a usable destination route, not confirming that manually pinning a static route to one physical link can undermine SD-WAN steering design.
Removing one member must not automatically erase unrelated essential routing dependencies. This assesses removing one member must not automatically erase unrelated essential routing dependencies; it does not determine the reported condition—a branch uses static routes for each member rather than the intended SD-WAN zone and route selection remains pinned to one link.
Selecting a healthy outbound WAN alone does not prove the return path is symmetric. The case-specific requirement is confirming that manually pinning a static route to one physical link can undermine SD-WAN steering design, which that option does not establish.