Next Step After Identifying Design Issues in Annual Review
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 core trap is confusing the initial identification of issues with the formal process required to modify an already-released asset, which mandates Change Control rather than further review or risk assessment.
This question tests the proper sequence of IT governance processes when flaws are found in a released system design. The correct procedure is to initiate a change control process to formally address and document necessary modifications.
Many learners select 'Design review process' because they assume more analysis is needed first; however, since the design is already released, any modification must go through Change Control.
Community Discussion (17 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is D — Change control process. When an engineer identifies issues with a currently released design, the organization cannot simply alter it informally. Best practices dictate that any modification to an approved, released asset must go through the Change Control Process. This ensures that the proposed changes are evaluated, approved, tested, and documented to maintain system integrity and minimize disruption. Since the design is already released, the act of fixing it constitutes a change request.Why the Other Options Are Wrong
Option A (Risk management) is ongoing but not the immediate procedural step for implementing fixes. Option B (Product design) applies to new development, not modifying existing released systems. Option C (Design review) is typically performed before release to validate the design; while one might argue for another review, the question asks for the next step in addressing the issues in a released product, which triggers the change management workflow. As noted by commenter Ty13, "You only need Change Control when you're actually making changes," implying the identification leads directly to the mechanism for those changes.Community Comment Notes
The community is split between C and D, with many voting for D based on the keyword "released." User RoRoRoYourBoat correctly points out that "change control... ensures that any modifications... are systematically evaluated." However, users like TmNvrWts admit confusion, noting that "GPT mislead me" towards other options, highlighting the difficulty in distinguishing between iterative review and formal change management in exam scenarios.Exam Strategy
Always look for keywords indicating the status of the asset. If it is 'released' or 'in production,' any modification requires Change Control. If it were still in development, a Design Review would be appropriate.
Frequently Asked Questions
Why isn't Design Review the answer if we just found issues?
Design Review is typically a pre-release validation step. Once the design is released, any fix becomes a change request governed by Change Control.
Does identifying an issue automatically mean I should start Risk Management?
No. While risk is assessed during change control, the primary procedural requirement for altering a released asset is the Change Control Process itself.
Related Analysis
Practice All SY0-701 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SY0-701 Practice Test →