Which practice helps minimize risk when performing troubleshooting in a busy environment?

• A. Randomly trying fixes
• B. Ignore change control
• C. Document and obtain approval before changes
• D. Reboot until it works

Answer: (C)

Structured change management during troubleshooting is about planning, documenting, and getting approval before you make any changes, especially in a busy environment. This approach minimizes risk by ensuring every action is reviewed for potential impact, coordinated with the right teams, and scheduled in a window that reduces service disruption. The documentation provides a clear record of what was changed, why, and how to revert if needed, which helps with accountability and future troubleshooting. An approved change also means there’s a rollback plan in place, so you’re prepared if the fix doesn’t behave as expected.

Why the other approaches don’t fit: randomly trying fixes can introduce new problems and conflicts with other systems; bypassing change control opens the door to uncoordinated changes that destabilize services; rebooting until it works often causes unnecessary downtime and doesn’t address the underlying issue, potentially leading to data loss or longer outages.