New to the July 2026 exam? Read what changed in the 2026 PMP exam.

Business Environment: Risk, Change, and Issue Management

Planning and managing risks, controlling changes through integrated change control, removing impediments, and resolving project issues effectively.

5 minutes 5 Questions

Business Environment: Risk, Change, and Issue Management is a critical knowledge area in PMP that addresses how project managers navigate uncertainty, adapt to evolving conditions, and resolve problems within the broader business context. **Risk Management** involves systematically identifying, an…

Concepts covered
Impediment Removal StrategiesRisk Management PlanningRisk Identification and CategorizationQualitative Risk AnalysisQuantitative Risk AnalysisRisk Response Strategies for ThreatsRisk Response Strategies for OpportunitiesImplementing and Monitoring Risk ResponsesIntegrated Change Control ProcessChange Request Evaluation and ManagementIssue Identification and ResolutionConfiguration ManagementReserve Analysis: Contingency and Management Reserves
Test mode:
Start practice test

PMP - Business Environment: Risk, Change, and Issue Management Example Questions

Test your knowledge of Business Environment: Risk, Change, and Issue Management

Question 1

During a cloud migration project, the team identifies a significant risk of data corruption when transferring a legacy database to the cloud environment. The project manager decides to migrate data incrementally in small batches while maintaining the legacy system fully operational in parallel. Additionally, detailed rollback procedures are documented and tested before each batch transfer. Which risk response strategy is the project manager primarily using, and what is the rationale?

Correct Answer: Mitigate, because the approach reduces the probability and impact of data corruption by using incremental transfers and rollback capabilities

The project manager is applying a mitigation strategy, which is a risk response approach that reduces either the probability of a risk occurring or the impact if it does occur. By implementing parallel systems (keeping the legacy database operational as a safety net), performing incremental data transfers in small batches (reducing the scope of potential corruption), and establishing rollback procedures at each step (enabling recovery if corruption is detected), the team actively reduces both the likelihood of widespread data corruption and the severity of its consequences. This is distinctly different from avoidance (which would involve not migrating at all), transfer (which shifts the responsibility to another party), or acceptance (which acknowledges the risk without proactive reduction measures). The combination of preventive measures (small batches, parallel systems) with contingency controls (rollback procedures) defines mitigation as the primary strategy.

Question 2

During a software development project, a project manager submits a scope modification request to the Change Control Board. After a thorough review, the board formally approves the request. To ensure the team can begin executing the new scope appropriately, what action should the project manager take next?

Correct Answer: Update the change log with the approved status and notify the assigned project team and relevant stakeholders.

Once a change request is approved by the Change Control Board, the project manager must first update the change log and communicate the decision to the relevant stakeholders and team so they can implement it.
Rewriting the project charter is incorrect because charters are high-level documents rarely updated for standard scope changes. Modifying the business case is outside the project manager's core responsibilities and is managed by the sponsor. Instructing the team to immediately halt all current activities is inappropriate because the new scope must first be integrated into the existing schedule and project baselines.
Key concept: Perform Integrated Change Control process and change communication.

Question 3

A quality manager reviews the configuration management plan before project kickoff. She wants to confirm the plan specifies who has authority to approve modifications to baselined items and which items fall under formal control. Which element of the plan should she examine to find this information?

Correct Answer: The roles, responsibilities, and the defined scope of items placed under governance

The manager needs to know who can authorize changes and which items are formally controlled, and the roles, responsibilities, and defined scope of items under governance section captures exactly this authority and coverage information.

The status accounting schedule only records the current state of items, not approval authority. The audit calendar lists verification and reconciliation dates, not change approvers. The version numbering convention and branching strategy address technical versioning mechanics, not authority or item scope.

Key concept: configuration management plan components, specifically defining change approval authority and configuration item scope.

More Business Environment: Risk, Change, and Issue Management questions
1501 questions (total)
Practice 100 questions
One session at a time, always new questions