Change Control & Configuration Flashcards
7 cards from real CAPM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Change Control & Configuration flashcards as text
A sponsor requests an urgent feature addition without going through the change control process. What should the project manager do?
Answer: Explain that all changes must follow the formal change control process
Even sponsor-initiated changes must be processed through formal change control to assess impact and maintain baseline integrity.
Which of the following is an example of a preventive action in the context of change control?
Answer: Adjusting the project schedule to avoid a future delay
A preventive action is taken proactively to reduce the probability of negative consequences before they occur.
What distinguishes a defect repair from a corrective action?
Answer: Defect repair addresses a non-conforming product; corrective action re-aligns future work with the plan
Defect repair fixes a specific non-conforming component, while a corrective action aligns future project performance with the project management plan.
During a configuration audit, the team discovers that a delivered software module does not match its approved design specification. This finding is called a:
Answer: Configuration discrepancy
A configuration discrepancy (also called a configuration audit finding) is any difference between the configuration item and its documented requirements.
Which input is MOST important when evaluating the impact of a proposed change?
Answer: Project management plan
The project management plan contains all baselines and subsidiary plans needed to assess how a proposed change will affect scope, schedule, cost, and quality.
A project team is using a version control system to manage project documents. This practice is BEST associated with:
Answer: Configuration management
Version control is a core configuration management practice that tracks changes to documents and ensures teams work from current, approved versions.
When should a change request be formally documented?
Answer: Whenever any change to any project document is proposed
All proposed changes—regardless of size or impact—should be formally documented as change requests so they can be tracked and controlled.