Question 820
A risk review at a financial services branch focuses on preventing this issue again: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. Which recurring control is most suitable?
Explanation
Correct Answer
Include representative distant probes, not just carrier state, for critical services. This control reduces recurrence of the documented mechanism: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures. It creates a repeatable check around the needed response: Use a performance SLA that probes an appropriate end-to-end service path beyond the local link.
Incorrect Answers
Review SLA values using measured voice quality and contractual objectives. That safeguard addresses another potential failure: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It is not the most targeted recurring control for the described cause: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.
Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover. That safeguard addresses another potential failure: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. It is not the most targeted recurring control for the described cause: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.
Validate health-detection delay against payment transaction recovery objectives. That safeguard addresses another potential failure: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. It is not the most targeted recurring control for the described cause: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.