What is change management in the context of telemetry software updates?

• A. Informal process for occasional updates with limited testing.
• B. Ad hoc deployment without rollback plans.
• C. Formal process for requesting, testing, approving, and deploying updates and patches; includes rollback plans and documentation.
• D. Ignore vendor advisories and deploy only after user complaints.

Answer: (C)

Change management is a formal, structured approach to handling software updates so changes are planned, tested, approved, and deployed in a controlled way. When telemetry software updates are managed this way, there’s a clear process for requesting the change, evaluating risks and impacts on data collection and transmission, testing in a safe environment, obtaining approvals, and coordinating deployment. Importantly, it also requires a rollback plan and thorough documentation so you can revert if something goes wrong and keep an audit trail of what was changed, why, and by whom. This minimizes disruptions to data integrity and system reliability while ensuring compliance and accountability.

That’s why the best answer describes a formal process with testing, approvals, and rollback plans plus documentation. The other options describe unstructured, ad hoc, or unsafe practices—lacking governance, risk assessment, or the ability to recover from issues—which would undermine reliability and control in telemetry updates.