In configuration management for software projects, which of the following is typically not considered a core configuration management task?

Introduction / Context:
Configuration management (CM) is the discipline of identifying, organizing and controlling changes to the artifacts of a software project. It includes tasks like version control, change management and status reporting. While CM supports quality, not every quality related activity is part of configuration management itself. Distinguishing CM tasks from quality control tasks helps clarify responsibilities in a project.

Given Data / Assumptions:

Configuration items include source code, documents, test scripts, configuration files and sometimes data.
Configuration management plans specify how items are identified, versioned, baselined and changed.
Quality control involves verifying that the product meets specifications, often through testing and review.

Concept / Approach:
Core configuration management tasks usually include version control, change control (or change management) and configuration status accounting. Version control ensures that different versions and variants of artifacts are tracked and recoverable. Change management ensures that changes are proposed, reviewed and approved in a controlled way. Status accounting involves reporting what versions are in use, what changes have been applied and what baselines exist. Quality control, although supported by good CM, belongs to testing and inspection rather than CM itself.

Step-by-Step Solution:
Identify which options describe classic CM activities: version control and change management are immediately recognized as such. Reporting on the current configuration status is a form of configuration status accounting, another key CM function. Quality control and acceptance testing focus on verifying functionality, performance and compliance, which are part of testing and QA, not CM. Therefore, performing quality control is not a core task of configuration management, even though CM indirectly supports it by providing traceable artifacts.

Verification / Alternative check:
CM standards and guides define the scope of configuration management as identification, control, status accounting and verification of configuration items. They do not include functional testing or test result evaluation as CM tasks. Separate quality management and testing processes use CM outputs, which confirms that option c is the correct answer.

Why Other Options Are Wrong:
Option a describes configuration status reporting, such as reports that show which versions are deployed or baselined, which is clearly CM.
Option b describes version control, one of the most recognizable CM functions.
Option d describes change management, which is a central part of CM used to control how and when changes are introduced.

Common Pitfalls:
Some teams blur the line between configuration management and testing, expecting CM staff to verify technical quality of code changes. This can overload CM roles and reduce clarity. A better approach is to keep CM focused on identification and control, while QA and testing teams focus on verifying quality using the artifacts managed by CM.

Final Answer:
The activity that is not a core configuration management task is performing product quality control and acceptance testing.