CSM Software Configuration & Change Management Flashcards
6 cards from real CSM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 CSM Software Configuration & Change Management flashcards as text
What is the primary purpose of a Configuration Management Database (CMDB) in software management?
Answer: To track and manage all configuration items and their relationships
A CMDB serves as a centralized repository that tracks all configuration items (CIs) and their interdependencies to support IT service management.
Which IEEE standard is most closely associated with software configuration management practices?
Answer: IEEE 828
IEEE 828 defines the requirements for Software Configuration Management Plans, covering identification, control, status accounting, and auditing.
In change management, what does a Change Advisory Board (CAB) primarily do?
Answer: Reviews and approves or rejects proposed changes
The CAB reviews proposed changes, assesses their risk and impact, and makes authorization decisions before changes are implemented.
What is a baseline in the context of software configuration management?
Answer: A formally reviewed and agreed-upon specification or product used as a reference point
A baseline is a formally approved version of a configuration item that serves as a reference for future development and can only be changed through formal change control procedures.
Which of the following BEST describes a version control branching strategy that uses short-lived feature branches merged frequently into the main branch?
Answer: Trunk-based development
Trunk-based development uses short-lived branches that are frequently integrated into the main (trunk) branch to reduce merge conflicts and support continuous integration.
What is the key difference between a 'normal change' and an 'emergency change' in IT change management?
Answer: Emergency changes bypass standard approval processes due to urgency
Emergency changes are expedited through a streamlined or abbreviated approval process to address critical issues quickly, though they are still documented and reviewed post-implementation.