PMP Process — Managing Technical Aspects Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Initiate a change request to formally document the new requirement and assess its impact on scope, schedule, and cost

  Why this is correct

  This is the correct project management action. Any new requirement, even if mandatory or regulatory, constitutes a change to the project baseline and must be formally managed through the integrated change control process. Initiating a change request ensures the requirement is documented, its impact on scope, schedule, cost, quality, and resources is thoroughly assessed, and stakeholders can make informed decisions before implementation. This systematic approach prevents uncontrolled scope creep and maintains project control.

• ✗

  Notify stakeholders of the new requirement and proceed with implementation

  Why it's wrong here

  This option is incorrect because proceeding with implementation before a thorough impact assessment is a critical project management misstep. While stakeholder notification is important, it should occur after the change request has been analyzed for its effects on project baselines and approved. Implementing without understanding the full implications can lead to unforeseen cost overruns, schedule delays, and quality issues, undermining project success and stakeholder confidence.

• ✗

  Instruct the team to incorporate the new requirement immediately due to its mandatory nature

  Why it's wrong here

  This action is incorrect as it bypasses the essential integrated change control process, regardless of the requirement's mandatory nature. Directly instructing the team to implement without formal assessment and approval can introduce unmanaged risks, scope creep, and disruptions to the project plan. Every change, even regulatory, requires a structured evaluation to understand its full impact on all project constraints and ensure controlled execution.

• ✗

  Update the risk register to reflect the new regulatory requirement

  Why it's wrong here

  This option is incorrect because a new regulatory requirement, once identified, is a certainty that must be addressed, not an uncertain event that might occur. The risk register is for potential future events that may or may not impact the project objectives. A mandatory new requirement directly alters the project scope or objectives and therefore must be managed as a formal change through the change control process, not as a risk.

Go deeper

Related to this question