What Step Follows Identifying Design Issues in a Released System?
During an annual review of the system design, an engineer identified a few issues with the currently released design. Which of the following should be performed next according to best practices?
Community Votes
60% 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 whether you recognize that identifying flaws in a production environment immediately triggers formal change management protocols rather than additional analytical reviews.
This question evaluates knowledge of post-deployment system maintenance procedures. While many candidates favor re-evaluating the design, CompTIA’s official guidance prioritizes the change control process to ensure any modifications to a released system are formally tracked and approved.
Candidates frequently select the design review process, assuming they must re-analyze the identified flaws before taking action; however, this overlooks the fact that the annual review already completed the assessment phase, making change control the procedurally correct next step.
Community Discussion (17 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Correct Answer: Change Control Process
According to CompTIA Security+ best practices, when an engineer identifies flaws in a currently released design, the immediate next step is initiating the change control process. Once a system moves from development to production, any modifications must be formally documented, evaluated, approved, and tracked to prevent unauthorized or destabilizing updates. As noted by multiple candidates, the annual review has already concluded its identification phase, so the workflow naturally progresses to structured change management rather than restarting analysis.Why Other Options Fall Short
- Risk management process: While evaluating impact is important, risk management is typically a broader, ongoing activity or occurs earlier in the lifecycle. It does not directly handle the execution of design fixes.
- Product design process: This applies to initial creation or major redesigns, not incremental corrections to an operational system.
- Design review process: Many test-takers incorrectly select this option, arguing that you must re-evaluate the issues first. However, as highlighted in community feedback, the annual review already served as the evaluation phase. Repeating it delays action, whereas change control ensures the identified issues are addressed systematically without bypassing governance.
Community Consensus & Exam Logic
The vote split reflects a common SY0-701 trap: confusing iterative analysis with procedural compliance. CompTIA emphasizes that "released" systems require strict adherence to change management frameworks (like ITIL). Even if further discussion seems logical in real life, certification exams prioritize standardized workflows. Choosing change control demonstrates awareness that production environments cannot be altered outside established approval chains.Official Reference
Exam Strategy
When a scenario mentions a 'released' or 'production' system and highlights identified flaws, immediately prioritize formal change management processes over starting new analysis phases. Scan for keywords like 'annual review,' 'identified issues,' and 'next step' to trigger your change control workflow memory, and remember that certification exams favor standardized governance over ad-hoc troubleshooting.
Related Analysis
Practice All SY0-701 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SY0-701 Practice Test →