- A
Deploy directly to production as soon as the patch compiles successfully.
Why wrong: A successful compile does not prove the change is safe in production. Skipping testing and rollback planning increases outage risk and bypasses normal control points.
- B
Require a documented test in a lower environment and a rollback plan before production approval.
Testing in a lower environment and documenting a rollback plan are core secure change-management practices. They reduce the chance of introducing an outage and make recovery faster if the fix has unexpected side effects. This approach supports controlled release, accountability, and operational resilience while still allowing urgent changes to move forward in a safe way.
- C
Turn off logging during deployment to avoid filling the disk with change records.
Why wrong: Logging should not be disabled during a controlled release. Change records and deployment logs are important for troubleshooting, validation, and auditability.
- D
Allow the release only if the developer verbally confirms the code is safe.
Why wrong: A verbal assurance is not a substitute for documented testing, approval, and rollback planning. It leaves no reliable evidence for review or accountability.
Quick Answer
The correct requirement is to mandate a documented test in a lower environment and a rollback plan before production approval. This directly satisfies the business need for reversibility—if the urgent fix breaks the customer portal, the rollback plan allows the team to undo the change quickly—while also upholding security’s release controls by forcing validation in a non-production setting first. On the Security+ SY0-701 exam, this scenario tests your understanding of change management within the Security Program Management and Oversight domain, specifically how to balance speed with safety. A common trap is choosing an option that allows skipping testing for “emergency” changes, but the exam emphasizes that even urgent fixes must follow a controlled process to prevent security gaps. Remember the mnemonic “Test to Rest”: test in a lower environment first, then rest easy knowing you have a rollback plan to revert if needed.
SY0-701 Security Program Management and Oversight Practice Question
This SY0-701 practice question tests your understanding of security program management and oversight. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A development team needs to release an urgent fix for a customer portal on Friday evening. The business wants the change to be reversible if something breaks, and security does not want the team to skip release controls. Which requirement should be part of the change process?
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
Require a documented test in a lower environment and a rollback plan before production approval.
Option B is correct because it enforces a documented test in a lower environment and a rollback plan, which satisfies both the business requirement for reversibility and the security requirement to maintain release controls. This aligns with the change management process in the SY0-701 domain of Security Program Management and Oversight, ensuring that changes are validated before production deployment and can be undone if issues arise.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy directly to production as soon as the patch compiles successfully.
Why it's wrong here
A successful compile does not prove the change is safe in production. Skipping testing and rollback planning increases outage risk and bypasses normal control points.
- ✓
Require a documented test in a lower environment and a rollback plan before production approval.
Why this is correct
Testing in a lower environment and documenting a rollback plan are core secure change-management practices. They reduce the chance of introducing an outage and make recovery faster if the fix has unexpected side effects. This approach supports controlled release, accountability, and operational resilience while still allowing urgent changes to move forward in a safe way.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Turn off logging during deployment to avoid filling the disk with change records.
Why it's wrong here
Logging should not be disabled during a controlled release. Change records and deployment logs are important for troubleshooting, validation, and auditability.
- ✗
Allow the release only if the developer verbally confirms the code is safe.
Why it's wrong here
A verbal assurance is not a substitute for documented testing, approval, and rollback planning. It leaves no reliable evidence for review or accountability.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think an urgent fix justifies skipping controls (Option A) or that disabling logging is acceptable to avoid disk issues (Option C), but the exam emphasizes that security controls and reversibility must be maintained even for emergency changes.
Detailed technical explanation
How to think about this question
In a structured change management process, a rollback plan typically involves reverting to a previous known-good configuration or version, often using version control systems like Git or deployment tools that support blue-green deployments or canary releases. Documented testing in a lower environment (e.g., staging or QA) validates the fix against security controls and functional requirements, reducing the likelihood of introducing vulnerabilities or breaking changes in production. This approach is consistent with the NIST SP 800-53 change management controls and the ITIL change enablement framework.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Security Program Management and Oversight — study guide chapter
Learn the concepts, then practise the questions
- →
Security Program Management and Oversight practice questions
Targeted practice on this topic area only
- →
All SY0-701 questions
1,152 questions across all exam domains
- →
Security+ SY0-701 study guide
Full concept coverage aligned to exam objectives
- →
SY0-701 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SY0-701 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
General Security Concepts practice questions
Practise SY0-701 questions linked to General Security Concepts.
Threats, Vulnerabilities, and Mitigations practice questions
Practise SY0-701 questions linked to Threats, Vulnerabilities, and Mitigations.
Security Architecture practice questions
Practise SY0-701 questions linked to Security Architecture.
Security Operations practice questions
Practise SY0-701 questions linked to Security Operations.
Security Program Management and Oversight practice questions
Practise SY0-701 questions linked to Security Program Management and Oversight.
Security+ social engineering questions
Practise SY0-701 questions linked to Security+ social engineering questions.
Security+ cryptography practice questions
Practise SY0-701 questions linked to Security+ cryptography.
Security+ IAM questions
Practise SY0-701 questions linked to Security+ IAM questions.
Security+ risk management questions
Practise SY0-701 questions linked to Security+ risk management questions.
Security+ incident response questions
Practise SY0-701 questions linked to Security+ incident response questions.
Security+ malware questions
Practise SY0-701 questions linked to Security+ malware questions.
Security+ vulnerability management questions
Practise SY0-701 questions linked to Security+ vulnerability management questions.
Practice this exam
Start a free SY0-701 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SY0-701 question test?
Security Program Management and Oversight — This question tests Security Program Management and Oversight — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Require a documented test in a lower environment and a rollback plan before production approval. — Option B is correct because it enforces a documented test in a lower environment and a rollback plan, which satisfies both the business requirement for reversibility and the security requirement to maintain release controls. This aligns with the change management process in the SY0-701 domain of Security Program Management and Oversight, ensuring that changes are validated before production deployment and can be undone if issues arise.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.