Configuration Management

Correct Answer: Implement version tracking and merge control processes to manage concurrent modifications

Version tracking and merge control processes represent the most effective strategy for handling parallel changes in configuration items because: - It enables multiple team members to work simultaneously on configurations - Provides automated conflict detection and resolution capabilities - Maintains a complete history of all changes - Allows for easy rollback if needed - Follows industry best practices for configuration management The other options are less effective because: Documentation alone doesn't solve the concurrent modification problem - it only records what happened. Sequential review cycles create unnecessary delays and bottlenecks in the development process, reducing team efficiency. Locking the configuration item is too restrictive and creates workflow bottlenecks, preventing team members from working efficiently in parallel.

Correct Answer: To verify that the configuration items match their documentation and baseline requirements

The primary objective of conducting periodic CMS reviews is to verify that configuration items match their documentation and baseline requirements. This is crucial because: 1. It ensures the integrity of the configuration management system 2. It validates that actual configuration items align with their documented specifications 3. It helps identify any unauthorized changes or deviations from approved baselines The other options are incorrect because: Labeling and storing items in a database is a basic administrative task, not the primary objective of periodic reviews. Maintaining an audit trail is a byproduct of configuration management but not the main purpose of periodic reviews. Establishing new baselines is a separate process that occurs when changes are approved, not during routine CMS reviews. Reviews focus on verifying compliance with existing baselines rather than creating new ones.

Correct Answer: Number of failed changes divided by total changes multiplied by severity factor

The Configuration Management Risk Index (CMRI) formula: Number of failed changes divided by total changes multiplied by severity factor is the correct calculation for assessing potential risks in configuration changes. This formula effectively captures three essential elements: 1. Failure rate (failed changes/total changes) - measures the historical performance of changes 2. Severity factor - accounts for the impact level of potential failures 3. Proportional representation - provides a normalized value between 0 and 1 when multiplied by severity This calculation helps organizations: - Quantify the risk associated with configuration changes - Track performance trends over time - Make data-driven decisions about change management processes - Prioritize risk mitigation efforts The other formulas incorporate irrelevant factors like implementation costs, frequency of changes, or complexity indices, which don't directly relate to risk assessment in configuration management. The correct formula focuses on the core elements that determine risk: failure rate and severity.