Amending an incorrect version of source code typically points to a failure in change management controls, particularly in areas such as:
Version control: Ensuring that only the correct, most recent version of the code is modified.
Approval and tracking: Properly authorizing, documenting, and managing changes to the codebase.
Configuration management: Identifying and maintaining the integrity of the versions throughout the software lifecycle.
Why not the others?
B. Project management: Focuses on timelines, resources, and deliverables—not detailed code control or versioning.
C. Incident management: Deals with identifying and resolving operational disruptions, not source code errors or version control.
D. Quality assurance (QA): While QA checks for correctness and quality, it's not primarily responsible for managing source code versions.
If the wrong version was amended, it suggests that there was a lack of proper oversight, version control, or testing during the change process, which are key components of effective change management.
it most likely points to a weakness in the quality assurance (QA) processes. QA ensures that the code is rigorously tested, reviewed, and validated before it is deployed to production. A weak QA process increases the likelihood of bugs and errors going unnoticed
This section is not available anymore. Please use the main Exam Page.CISA Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Greens
1 month, 3 weeks agoRukiISAdtr
4 months, 2 weeks ago1Naa
7 months, 3 weeks agoChangwha
1 year ago