PMP domain - 8% of the exam

Business Environment

Business Environment is 8% of the PMP exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

23
Practice questions
3
Objectives
15
Medium
8
Hard

Where people go wrong

  • Acting on an external change before assessing its impact

    When a new regulation or trade restriction lands, the wrong answers jump straight to a response: raising a change request, committing to a substitute, escalating to the sponsor, or waiting and logging it for later. The project manager first analyses how the external change affects scope, cost and schedule, then takes the findings to integrated change control or to the product owner for reprioritisation.

    See it in a sample question
  • Treating delivered output as realised benefit

    The wrong answers read a finished product as a finished benefit: baselines met, acceptance criteria passed, a tool that is live and stable, or every roadmap feature shipped. These are outputs. A benefit is an outcome, such as lower call-centre volume or more monthly active subscribers, and it is judged against the business case metric, which in agile work steers backlog priority.

    See it in a sample question
  • Misplacing who tracks benefits after closure

    The wrong answers put benefits tracking in the wrong hands: keeping the project open to measure operational results, handing over with no owner or measurement approach, or quietly taking accountability back from the owner. Benefits that accrue after closure belong to a named benefits owner in operations, and the project manager makes sure that owner and a measurement method are in place before handover.

    See it in a sample question
  • Collapsing distinct compliance obligations into one

    The wrong answers flatten different obligations: treating internal policy and contract terms as if they were law, merging them into one combined item, or settling a disputed requirement by vote or by assuming the strictest reading. A regulation, an organisational policy and a contract term differ in source and in the consequence of noncompliance, so the project manager classifies each by its source before deciding the response.

    See it in a sample question
  • Forcing or delaying engagement with resistance to change

    Faced with staff resistance, the wrong answers impose the change by mandate, broadcast a compliance notice, escalate to have the resistor corrected, wait until the product is finished, or close the project at go-live. Organisational change management works by understanding the group's culture and objections, involving the people affected, and reinforcing the new behaviours with monitoring, feedback and coaching until they stick.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleBusiness Environmenthard

During a hybrid infrastructure project, newly imposed trade restrictions block the import of a hardware component the current design depends on. The project manager has just been notified of the restriction. What should the project manager do FIRST?

  • ADirect the procurement lead to source any available substitute component at once so the schedule is not disturbed.
  • BRecord the restriction in the issue register and continue with planned work until the next phase-gate review.
  • CEscalate to the sponsor with a request to extend the deadline before any alternatives have been examined.
  • DAnalyse how the restriction affects scope, cost and schedule, then evaluate the options with the team and stakeholders. Correct
Meet a geopolitical or supply disruption by first analysing its impact on scope and constraints, then evaluating options collaboratively. Trade restrictions are an external business-environment change that can invalidate part of the scope. The disciplined first move is to assess the impact across scope, cost and schedule and evaluate alternatives with the team and stakeholders, rather than committing to a substitute, a deferral, or a deadline change before the effect is understood.

Why A is wrong: Speed feels protective of the schedule, but committing to a substitute before understanding the effect on scope and design risks locking in an unsuitable or non-compliant choice.

Why B is wrong: Logging the issue is part of good practice, yet deferring analysis to a later gate lets a change that blocks the design ripple unmanaged through scope and schedule.

Why C is wrong: Asking for time seems responsible, but requesting a deadline change before assessing options presents the sponsor with a solution rather than an analysed impact.

Why D is correct: A geopolitical restriction is an external change, so the project manager first surveys its impact on scope and constraints and works options through with the team and stakeholders before deciding a response.

Free sampleBusiness Environmentmedium

A predictive project has just delivered a new customer-portal that met its scope, schedule, and budget baselines, and the sponsor considers the project a success. The business case promised a 20 percent reduction in call-centre volume, but those savings will only materialise over the year after handover, once customers adopt the portal. The project manager is closing the project. What should the project manager do FIRST to protect the promised benefits?

  • ADeclare the benefits realised because the portal was delivered to its baselines and the sponsor is satisfied with the outcome.
  • BConfirm who will own tracking of call-centre volume after handover and that a measurement baseline exists, then transition that accountability in the closure. Correct
  • CExtend the project schedule for twelve months so the team can keep monitoring adoption until the full call-centre saving appears.
  • DAsk the sponsor to revise the business case downward so the target matches whatever savings have appeared by the closure date.
Benefits that accrue after handover require a named owner and a measurement system transitioned into operations at closure. A project delivers outputs, but many benefits are realised only during operations after the project closes. Protecting them means assigning ongoing benefits ownership and verifying a measurement baseline exists so realisation can be tracked, rather than assuming delivery equals value.

Why A is wrong: Delivering an output on baseline is not the same as realising the outcome. Call-centre volume falls only as customers adopt the portal over the following year, so the benefit is not yet realised at handover.

Why B is correct: Benefits realised after the project ends need a named owner and a working measurement system carried into operations; securing both during closure is what keeps the promised savings from going unmeasured and unowned.

Why C is wrong: Keeping a delivered project open to babysit an operational outcome is wasteful and blurs the project-to-operations handover; benefits tracking belongs with an accountable owner in operations, not an extended project.

Why D is wrong: Rewriting the target to match early results hides the gap rather than managing it, and the savings were always expected to accrue over a year, so judging them at closure is premature.

Free sampleBusiness Environmentmedium

Midway through planning a hybrid project, the team disagrees about a single requirement: some members treat a particular reporting rule as a binding legal obligation, while others believe it is only an internal organisational preference. What should the project manager do NEXT?

  • AAdopt the stricter interpretation and treat the reporting rule as a binding legal obligation to remove any doubt for the team.
  • BAsk the team to vote on how the reporting rule should be treated so that work can continue without any further delay.
  • CRecord the reporting rule as optional in the backlog so the product owner can decide its priority during the next review.
  • DDetermine whether the requirement is externally mandated by regulation or internally driven by organisational policy, and classify it accordingly. Correct
Classify a compliance requirement by its source to determine whether it is mandatory or discretionary before planning the work. Compliance categories separate externally mandated regulation from internal policy. Knowing the category tells the project manager how binding the requirement is and how much rigour and evidence its fulfilment demands.

Why A is wrong: Defaulting to the strictest reading seems safe, but committing to legal-grade effort without confirming the source can gold-plate the work and waste capacity on an internal preference.

Why B is wrong: A vote resolves the dispute quickly, but the status of a compliance requirement is a matter of fact about its source, not a team preference that a majority can settle.

Why C is wrong: Deferring to backlog prioritisation fits an agile cadence, but labelling a possibly mandatory requirement as optional before classifying it risks dropping a legal obligation.

Why D is correct: Classifying a compliance item by its source clarifies whether it is mandatory or discretionary, which drives how much effort, evidence, and priority the requirement receives across the plan.

Free sampleBusiness Environmenthard

A predictive project will replace the claims-handling system used daily by a large operations team. The solution is technically ready, but the project manager has heard that a previous rollout in the same department was abandoned because staff refused to adopt it. Before planning any communication or training, what should the project manager do FIRST to support adoption?

  • ADraft a detailed training schedule and communication plan so the team receives consistent messaging from the launch date.
  • BAssess the operations team's current culture, attitudes, and sources of resistance so the change approach can be tailored to them. Correct
  • CEscalate to the sponsor and request a directive that makes use of the new system mandatory once it goes live.
  • DProceed straight to deployment because control quality has confirmed the system meets every documented requirement.
Supporting organisational change begins with assessing the affected group's culture and resistance before designing communication or training. Adoption failures usually stem from people and culture, not technical defects, so the change effort must start by diagnosing the target group's readiness and sources of resistance; that diagnosis is what makes later communication, training, and reinforcement effective.

Why A is wrong: Tempting because communication and training are core adoption levers, but building them before understanding the team's culture and resistance risks repeating the previous rollout that staff rejected.

Why B is correct: Correct. Organisational change management starts by understanding the readiness and culture of the affected group; that assessment shapes the communication, training, and reinforcement that follow, and directly addresses the earlier failure.

Why C is wrong: A mandate is a command-and-control shortcut that treats symptoms rather than causes; forcing adoption without understanding resistance tends to harden it, and escalation here is premature.

Why D is wrong: Technical readiness is not the same as adoption readiness; a system that meets its requirements can still fail if the people who must use it are not prepared, which is exactly what happened before.

Other domains in this exam

See also the PMP cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.