A configuration management system is a standardized, effective, and efficient way to manage changes to project documentation. A configuration management system is a set of tools and processes that help to track, control, and update the configuration items (CIs) of a project, such as documents, requirements, designs, code, tests, etc. A configuration management system helps to ensure that the project documentation is consistent, accurate, and up-to-date throughout the project life cycle. It also helps to maintain the traceability and auditability of the changes made to the project documentation. A configuration management system typically includes the following components:
* A configuration management plan that defines the scope, roles, responsibilities, policies, procedures, and standards for configuration management.
* A configuration management database (CMDB) that stores the information about the CIs, their attributes, relationships, versions, baselines, and changes.
* A configuration identification process that assigns unique identifiers and names to the CIs and their versions.
* A configuration control process that evaluates, approves, and implements changes to the CIs and their versions.
* A configuration status accounting process that records and reports the status and history of the CIs and their versions.
* A configuration verification and audit process that verifies and validates the CIs and their versions against the requirements and specifications.
References: = PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 13.

The main output is the scope baseline, which consists of three documents; the scope statement (including both project and product requirements), the WBS(s), and the WBS dictionary. These are reviewed and upon approval, the scope baseline is created. Once that baseline has been approved, changes can only be made through a change control procedure. The scope baseline will be used to continually compare the actual results and work being done on the project to the original, approved scope.

Explanation
The business analyst will need to use the product scope as an input to the business case. The product scope is the description of the features, functions, and characteristics of the product, service, or result that the project will deliver. The product scope helps to define the business problem or opportunity, the desired outcomes, and the benefits of the solution. The product scope also helps to identify the assumptions, constraints, risks, and dependencies that may affect the project feasibility and viability. References: PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline1, page 9; Business Analysis for Practitioners: A Practice Guide2, page 36.

Nonfunctional requirements are the characteristics or qualities of a solution that describe how well it performs or operates. They include aspects such as usability, reliability, availability, scalability, security, performance, etc. The website crashing frequently indicates that the nonfunctional requirements related to availability and performance were not identified and tested properly. Quality attributes are another term for nonfunctional requirements, so option A is equivalent to option C. Critical business requirements and essential product requirements are both functional requirements, which describe what a solution does or provides, not how well it does it. Therefore, options B and D are incorrect. References: PMI Professional in Business Analysis (PMI- PBA) Examination Content Outline, page 18; Business Analysis for Practitioners: A Practice Guide, page
114-115.