Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
CompTIA Project+ · CompTIA
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Even if a change seems "easy" or "doesn't affect the date," it still constitutes a change to the Project Scope. Skipping documentation leads to "scope creep," where small, unrecorded changes accumulate and eventually derail a project. Establishing the Audit Trail: You need a formal record of who requested the change and why. Basis for Approval: You cannot present a change to a Change Control Board (CCB) or a Sponsor without a written recommendation that includes your impact analysis. Capturing the "Why": Even if the date doesn't change, the cost or risk profile might. Documenting it ensures these factors are visible.
The correct answer is: B. Review the requested change. Explanation: When a client requests a new feature, the first step for the project manager is to review the change request to understand its impact, feasibility, and requirements before taking any further action.
The question is worded slightly tricky to misdirect a lazy reader. It may appear the PM has already 'reviewed' the change, but the PM has only consulted the calendar. The NEXT step is to analyze the request for aspects like feasibility, impact, and alignment with project goals.