Question 870
The deployment team is preparing a sign-off for: A WAN member is reachable but a probe server responds through the wrong ISP and makes measured latency look unusually low. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that a health check that leaves through the wrong interface can produce misleading selection data. The case concerns a WAN member is reachable but a probe server responds through the wrong ISP and makes measured latency look unusually low. The safer path is to inspect probe source path, member binding, route table, and reported per-member performance and then, after verification, to correct the member-specific probe routing so each path measures its own transport. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Unmeasured links should not be assumed to satisfy SLA requirements automatically. The check concerns unmeasured links should not be assumed to satisfy SLA requirements automatically, not confirming that a health check that leaves through the wrong interface can produce misleading selection data.
A single overall green status can hide why one application's more demanding SLA is not met. This assesses a single overall green status can hide why one application's more demanding SLA is not met; it does not determine the reported condition—a WAN member is reachable but a probe server responds through the wrong ISP and makes measured latency look unusually low.
A member's old numerical ID may no longer identify the intended physical link after a reconfiguration. The case-specific requirement is confirming that a health check that leaves through the wrong interface can produce misleading selection data, which that option does not establish.