MyMichigan Telemetry Monitoring and Management Practice Test

What is the purpose of a disaster recovery plan in telemetry management?

To ensure rapid restoration of data, services, and alerts after a disruption, including backups, failover, and tested runbooks.

A disaster recovery plan in telemetry management is all about getting systems back online quickly after an incident. The main goal is to restore data, services, and alerts with minimal downtime, using proven backups, automatic failover, and prepared runbooks that guide the recovery process. A solid plan also sets recovery objectives, like how quickly things need to be up (RTO) and how much data can be lost (RPO), and it includes tested procedures and communication steps so operators know exactly what to do during an outage. In the telemetry context, this means ensuring dashboards, data streams, alert pipelines, and storage can be restored promptly so monitoring and response continue with as little disruption as possible.

This is why the other ideas don’t fit. Maximizing performance during peak load by increasing telemetry granularity is a capacity and optimization goal, not about recovering from failures. Eliminating all latency in a network isn’t realistic, and a disaster recovery plan isn’t about removing latency entirely. Replacing crisis response with automated daily reports would leave you unprepared for immediate action during incidents. The disaster recovery plan specifically supports rapid, reliable recovery after disruptions.

To maximize system performance during peak load by increasing telemetry granularity.

To prevent any data loss by eliminating all latency in the network.

To replace crisis response with automated daily reports.