Question 220
At Northpoint Health, an infrastructure review by the clinical edge networking group is evaluating clinic and telehealth connectivity across a regional clinic network after the last approved policy installation (FT-A-18-02). The review finds that staff dispute whether a failover occurred because they only inspect a current member status screen. Any correction must respect this operating requirement: patient-service networks remain isolated from visitor access. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Retain timestamped SLA and member-state events for incident review; make it a repeatable part of Northpoint Health's change assurance (FT-A-18-02). It sustains the corrective action, compare historical performance-SLA state changes with FortiAnalyzer SD-WAN events, and must preserve the requirement that patient-service networks remain isolated from visitor access.
Incorrect Answers
The source case reports that staff dispute whether a failover occurred because they only inspect a current member status screen. That ongoing review concerns: Test latency jitter and loss jointly during scheduled network drills; schedule a recorded review after topology changes. The governing risk here is: Retain timestamped SLA and member-state events for incident review; confirm this in the next branch rollout checklist. Maintain “Retain timestamped SLA and member-state events for incident review; confirm this in the next branch rollout checklist” as the case-specific check.
The source case reports that staff dispute whether a failover occurred because they only inspect a current member status screen. The alternative is a useful recurring check for: Trend healthy baselines and review thresholds quarterly; schedule a recorded review after topology changes. The present failure instead depends on: Retain timestamped SLA and member-state events for incident review; confirm this in the next branch rollout checklist. The targeted safeguard is “Retain timestamped SLA and member-state events for incident review; confirm this in the next branch rollout checklist”.
The source case reports that staff dispute whether a failover occurred because they only inspect a current member status screen. That ongoing review concerns: Correlate member alarms with session path changes after outages; retain the evidence under approved change control. The governing risk here is: Retain timestamped SLA and member-state events for incident review; confirm this in the next branch rollout checklist. Maintain “Retain timestamped SLA and member-state events for incident review; confirm this in the next branch rollout checklist” as the case-specific check.