Reducing Change Impact with Staging and Rollback
A hardening script is pushed to a production web server and, within minutes, the application stops accepting secure connections. The team discovers the script disabled a required TLS setting that the legacy application still needs. What should have been in place to reduce the impact of this change?
Quick Answer
The correct choice is a documented change window with testing in a staging environment and a rollback plan. This combination directly addresses the scenario because a staging environment mirrors production, allowing you to validate that a hardening script won’t disable critical settings like a legacy TLS version before it hits the live server. The rollback plan then provides a clear, pre-defined procedure to revert the change quickly if something breaks, minimizing downtime and impact. On the Security+ SY0-701 exam, this question tests your understanding of change management principles, specifically the need for controlled deployment and contingency planning. A common trap is to focus only on the technical fix—like re-enabling TLS—rather than the process that prevents the issue. Remember the mnemonic “SCR” for Staging, Change window, Rollback to keep the three essential components straight.
⚠ Common exam trap
The trap here is that candidates might think the issue is about authentication (Option B) or hardware (Option D), but the core problem is a configuration change that broke TLS compatibility, which requires proper change management and testing, not hardware or password policies.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A documented change window with testing in a staging environment and a rollback plan.
A documented change window with testing in a staging environment and a rollback plan ensures that changes are validated before production deployment. In this scenario, the hardening script disabled a required TLS setting (e.g., TLS 1.0 or a specific cipher suite) that the legacy application depended on. Testing in staging would have caught the incompatibility, and a rollback plan would allow reverting the change quickly, minimizing downtime.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A documented change window with testing in a staging environment and a rollback plan.
Why this is correct
A documented change window with staging validation and a rollback plan directly satisfies the stem's impact-reduction constraint: staging testing would have exposed the legacy application's TLS dependency before production, and the rollback plan would have restored the disabled TLS setting immediately, cutting outage duration. Change windows alone do not prevent misconfiguration; the rollback capability is what limits blast radius.
- ✗
A longer password policy for administrators so they can log in after the outage.
Why it's wrong here
Password length governs administrator authentication, not the impact of a faulty configuration change; the script would still have disabled the TLS setting. It is tempting because credential policy is a hardening control, but the scenario needs a tested rollback or staged deployment so the legacy TLS requirement is caught before production.
- ✗
Disabling all logging during the change so the application can restart faster.
Why it's wrong here
Disabling logging removes the audit trail needed to diagnose why secure connections failed, and does not restore the TLS setting. It is tempting because logging overhead can slow restarts, but the outage is caused by configuration, not performance; rollback capability and change approval would have contained the impact.
- ✗
Replacing the web server hardware to ensure the TLS settings are applied correctly.
Why it's wrong here
Hardware replacement does not prevent a script from disabling a required TLS setting; the same configuration would be applied to new servers. It is tempting because hardware refresh is a legitimate lifecycle activity, but the failure is configuration drift, addressed by change control with rollback and pre-production validation.
Go deeper
Related to this question
Learn chapter
Red Team vs Blue Team Operations
Key term
Transport Layer Security
Transport Layer Security (TLS) is a cryptographic protocol that provides secure, encrypted communication between two devices over a network, such as between a web browser and a server.
Key term
Hardening
Hardening is the process of securing a computer system or network by reducing its attack surface, disabling unnecessary services, and applying security configurations.
About these practice questions
One of 1,030 original SY0-701 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on SY0-701
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A critical patch must be applied to a production server next week. What is the best way to reduce the risk of downtime if the patch causes a problem?
easy- A.Apply the patch during business hours so users can report issues quickly
- ✓ B.Create a rollback plan before installing the patch
- C.Skip testing because critical patches are always safe
- D.Disable logging during the patch to improve performance
Why B: Creating a rollback plan before installing a patch ensures that if the patch causes unexpected issues, the system can be restored to its previous stable state quickly, minimizing downtime. A rollback plan typically includes steps to revert the patch, restore from a backup, or switch to a failover system, which is a fundamental change management practice in security operations.
Variation 2. A critical patch must be applied to a retail point-of-sale server. What is the best way to reduce business disruption?
easy- A.Apply the patch during the busiest business hours to make the change sooner.
- ✓ B.Schedule the patch during an approved maintenance window.
- C.Skip the patch and rely on hope that the issue will not be exploited.
- D.Turn off all backups so the patch process runs faster.
Why B: Scheduling the patch during an approved maintenance window is the best practice to minimize business disruption because it allows the organization to plan for downtime during low-activity periods, coordinate with stakeholders, and ensure rollback procedures are in place. For a retail point-of-sale (POS) server, applying a critical patch outside of business hours prevents transaction interruptions and potential revenue loss, aligning with change management policies that prioritize availability and security.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.