While troubleshooting an unstable database server you discover that a mis-tuned memory parameter is responsible for repeated crashes, and you have already confirmed the fix in a staging environment. According to the CompTIA troubleshooting methodology, which action should you take next as part of establishing a plan of action before touching the production server?
Complete the root-cause analysis report and close the incident ticket.
Collect additional system and application logs to broaden the evidence base.
Apply the corrected memory setting on the production server to restore stability as quickly as possible.
Inform the affected stakeholders of the scheduled maintenance window and expected service impact.
Once the theory has been tested and the root cause verified, the methodology calls for establishing a plan of action. A key element of that plan is to notify the users or business owners who will be affected by the forthcoming change so they can prepare for any downtime or performance impact. Only after communication (and any required approvals) should the administrator implement the change. Installing the fix immediately skips the planning step, gathering more logs belongs to the initial problem-identification phase, and performing root-cause analysis is done after full functionality is restored.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the purpose of notifying stakeholders before implementing a fix?
Open an interactive chat with Bash
Why does applying the fix immediately skip the planning step?
Open an interactive chat with Bash
What phase does collecting more logs belong to, and why is it incorrect here?