Change Management and Version Control ACCISO Practice Questions (Page 9)

Questions 41–45

1. 41application · medium

   A software development team is working on a critical application. The team has been experiencing issues where developers overwrite each other's changes, and there is no clear record of who changed what or when. The team lead wants to implement a solution that tracks every modification to the source code, allows multiple developers to work concurrently, and provides a complete history of changes. Which approach best addresses these requirements?

   • AImplement a manual change log in a spreadsheet that developers update after each modification.
   • BRequire developers to work on the same file sequentially and lock the file when editing.
   • CAdopt a version control system such as Git, with a branching strategy that supports parallel development and commit history.
   • DUse a shared network folder with file naming conventions that include the developer's name and date.
   Reveal Solution Discussion Select an answer first
2. 42application · medium

   A software development team uses Git for version control. They need to develop a new feature that will take several weeks, while also fixing bugs in the current release. The team wants to keep the feature work isolated from the stable release code. Which branching strategy best supports this requirement?

   • ACreate a branch only for bug fixes and leave the feature work on the main branch.
   • BCommit all changes directly to the main branch to keep the repository simple.
   • CUse a single branch for both feature development and bug fixes to avoid merge conflicts.
   • DCreate a separate feature branch from the main branch and merge it back only when the feature is complete and tested.
   Reveal Solution Discussion Select an answer first
4. 43application · medium

   A company is implementing a major upgrade to its customer relationship management (CRM) system. The change has been approved by the CAB, and the implementation window is scheduled for the upcoming weekend. The change manager wants to ensure that if the upgrade fails, the organization can quickly return to the previous state. What should the change manager include in the change plan?

   • AA detailed rollback plan that specifies the steps to restore the previous version and the criteria for triggering the rollback.
   • BA list of all the new features and benefits of the upgrade to justify the change to stakeholders.
   • CA communication plan that informs all users of the upgrade and provides training on the new system.
   • DA backup of the current system data, but no specific rollback steps because the upgrade is expected to succeed.
   Reveal Solution Discussion Select an answer first
5. 44foundation · easy

   Which outcome is a direct benefit of a well-defined change management process?

   • AIt provides a clear audit trail of what changed, who approved it, and when it was implemented
   • BIt guarantees that no change will ever cause an incident
   • CIt ensures that all changes are implemented without requiring approval
   • DIt eliminates the need for separate security reviews of changes
   Reveal Solution Discussion Select an answer first
6. 45expert · hard

   A development team uses a Git repository with a 'main' branch that is protected. Developers are required to create feature branches and submit pull requests for review. However, a developer accidentally pushed a commit directly to 'main' because they had administrative rights. What is the best way to prevent this from happening again?

   • AAsk developers to be more careful in the future.
   • BRemove administrative rights from all developers and enforce branch protection rules that prevent direct pushes to 'main'.
   • CCreate a new repository and migrate all code to it.
   • DDisable the protected branch feature to simplify the workflow.
   Reveal Solution Discussion Select an answer first