First Step Before Patching a High-Availability Production VM
The Chief Information Security Officer (CISO) asks a security analyst to install an OS update to a production VM that has a 99% uptime SLA. The CISO tells the analyst the installation must be done as quickly as possible. Which of the following courses of action should the security analyst take first?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests change management procedures for high-availability environments, where candidates often overlook the immediate need for a rapid rollback mechanism in favor of direct patching.
When applying OS updates to a critical production VM with a strict uptime SLA, creating a point-in-time recovery option is essential to minimize downtime. This page establishes that taking a VM snapshot is the mandatory first step before initiating any patches or configuration changes.
Candidates frequently select Install the patch immediately due to the pressure to complete the task quickly, ignoring that a failed update would violate the 99% uptime SLA and require significantly longer recovery time.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Taking a snapshot captures the exact current state of the virtual machine, providing an instant rollback point if the OS update introduces instability or breaks critical services. For a system bound by a 99% uptime SLA, reverting from a snapshot takes minutes rather than hours required for full restoration, ensuring compliance with strict availability targets. CompTIA Security+ explicitly prioritizes pre-change validation and recovery planning in all infrastructure modification scenarios.Why the Other Options Are Wrong
Performing a health check does not protect against failure during the update itself. Installing the patch immediately bypasses change control safeguards and risks prolonged downtime if the update fails. Confirming the backup service is running verifies tool readiness but does not actually create a recoverable point-in-time image needed for rapid reversion.Community Comment Notes
Learners consistently emphasize that snapshots serve as the fastest fallback mechanism for active databases without requiring services to be stopped. As user shady23 noted, "Taking a snapshot of the VM would be the first course of action" because it ensures a quick revert path. Multiple commenters agree that traditional copy-based backups cannot reliably capture open files, making the snapshot the only viable first step under tight time pressure.Exam Strategy
Always identify the constraint driving the scenario; here, the 99% uptime SLA dictates that speed of recovery matters more than traditional backup methods. Memorize the change management sequence: request approval, verify dependencies, create recovery point, implement change, validate, and document.
Frequently Asked Questions
Why isn't confirming the backup service the first step?
Verifying a backup service only checks tool status, whereas a snapshot creates an actual point-in-time image required for rapid reversion under SLA pressure.
Can I skip the snapshot if the update is low risk?
No. CompTIA exam doctrine mandates a verified recovery point before any production change, regardless of perceived risk, to prevent SLA violations.