The NOC hopes telemetry will automatically remediate BGP failures by itself. What separation should the candidate apply?
Select an answer to reveal the explanation.
Short Explanation
Telemetry is the dashboard camera; remediation is the mechanic with a wrench—or a carefully written automation playbook. Watching BGP break is not the same as fixing it unless you built that closed loop on purpose. Hoping the camera turns the bolts for you is wishful ops.
Full Explanation
Telemetry primarily provides visibility; automatic remediation of BGP failures requires a separate automation or orchestration design if the NOC wants closed-loop action. Telemetry does not always include a built-in closed loop that resets every BGP peer without design. Telemetry and remediation are not the same inseparable Junos daemon topic. BGP can fail in leaf-spine fabrics; visibility and optional remediation both remain relevant. Exam caveat: Authorize and test any auto-remediation; untested loops can worsen municipal outages. Operational check: Document whether BGP down alerts are observe-only or trigger a specific approved automation playbook. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.