What is the intent of Configuration Management (CM)?

What is the intent of Configuration Management (CM)?

• A. Identify causes of selected outcomes and take action to prevent recurrence of undesirable outcomes or ensure recurrence of positive outcomes.
• B. Manage the integrity of work products using configuration identification, version control, change control, and audits.
• C. Make and record decisions using a recorded process that analyzes alternatives.
• D. Estimate the size, effort, duration, and cost of the work and resources needed to develop, acquire, or deliver the solution.

Answer: (B)

Configuration Management aims to preserve the integrity of the project’s work products by controlling changes and keeping clear records of what exists at any point in the lifecycle. It does this through four key activities: - Configuration identification: clearly defining and labeling the items to be controlled (the configuration items) and their baselines. - Version control: tracking revisions of each item so you know which version is in use or deployed. - Change control: a formal process for reviewing, approving, and implementing changes to configuration items. - Audits: periodic checks to verify that the records and baselines match the actual configuration and that dependencies are complete. Together, these activities establish stable baselines, enable traceability across the development lifecycle, and ensure consistent, reproducible configurations even as the product evolves. This is why the described option is the best fit for the intent of Configuration Management. Other choices describe activities outside CM’s purpose: identifying causes and preventing recurrence relates more to problem solving or corrective action; making and recording decisions using a process that analyzes alternatives points to decision management; and estimating size, effort, duration, and cost pertains to project estimation.

Configuration Management aims to preserve the integrity of the project’s work products by controlling changes and keeping clear records of what exists at any point in the lifecycle. It does this through four key activities:

• Configuration identification: clearly defining and labeling the items to be controlled (the configuration items) and their baselines.

• Version control: tracking revisions of each item so you know which version is in use or deployed.

• Change control: a formal process for reviewing, approving, and implementing changes to configuration items.

• Audits: periodic checks to verify that the records and baselines match the actual configuration and that dependencies are complete.

Together, these activities establish stable baselines, enable traceability across the development lifecycle, and ensure consistent, reproducible configurations even as the product evolves. This is why the described option is the best fit for the intent of Configuration Management.

Other choices describe activities outside CM’s purpose: identifying causes and preventing recurrence relates more to problem solving or corrective action; making and recording decisions using a process that analyzes alternatives points to decision management; and estimating size, effort, duration, and cost pertains to project estimation.