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

Business Environment: Governance and Compliance

Defining and establishing project governance frameworks, managing compliance requirements including sustainability regulations, and upholding professional ethics.

5 minutes 5 Questions

Business Environment: Governance and Compliance is a critical knowledge area in PMP that focuses on how projects operate within organizational and regulatory frameworks to ensure accountability, transparency, and adherence to laws, standards, and policies. **Governance** refers to the structured f…

Concepts covered
Defining Project Governance FrameworksGovernance Structures, Roles, and Decision AuthorityOrganizational Process Assets and Enterprise FactorsEscalation Paths and Decision-Making AuthorityEthics and Professional Responsibility in PMSuccess Metrics and KPI Definition for GovernanceProject Compliance ManagementRegulatory and Legal RequirementsSustainability as a Compliance RequirementESG Integration in Project GovernanceAudit and Inspection RequirementsPMI Code of Ethics and Professional Conduct
Test mode:
Start practice test

PMP - Business Environment: Governance and Compliance Example Questions

Test your knowledge of Business Environment: Governance and Compliance

Question 1

A new team member reviews the project's compliance documentation and asks what the difference is between a standard the project chose to follow voluntarily and a rule imposed by a government body. How should the project manager explain this distinction?

Correct Answer: Voluntary standards reflect adopted best practices, while government rules carry legal enforcement and penalties for breaches

The correct answer is right because a standard is a voluntary set of guidelines representing best practices, while a regulation is a mandatory requirement imposed by a government or authority that carries legal consequences if not met.

The timing-based option is wrong because both standards and regulations can apply across any phase, not restricted to particular ones. The register-tracking option is wrong because compliance items are managed together, not artificially split into separate risk tracking. The approval option is wrong because the difference lies in enforceability, not in who signs off.

Key concept tested: distinction between voluntary standards and mandatory regulations in compliance management.

Question 2

A project manager overseeing a software update discovers a new regulatory compliance requirement that will increase the total project budget by 15%, exceeding the manager's individual approval authority. The manager has documented the business case showing that non-compliance poses significant legal and operational risk. Following standard project governance structures, who should the project manager approach first to authorize this budget increase?

Correct Answer: The project steering committee or governance board, because they review and authorize budget modifications that exceed the project manager's financial authority and affect project scope, schedule, or resources.

In standard project management governance structures (PMI/PMBOK), budget increases that exceed a project manager's approved financial tolerance require escalation to the appropriate governance authority. The project sponsor may be a member of or report to this committee, but the steering committee or governance board is the proper authorizing body for budget variances and change requests. This committee has the delegated authority to review the business case for the compliance requirement, assess risk implications, and authorize funding adjustments. The steering committee ensures that budget changes are evaluated against organizational priorities, compliance obligations, and strategic goals. While the project sponsor is involved in major decisions, the formal authorization mechanism for budget increases typically flows through the established change control and governance process, which is managed by the steering committee. This structure prevents individual stakeholders from unilaterally committing additional funds and ensures proper oversight of project finances.

Question 3

A project manager is preparing to initiate a new product development project. The team has identified and gathered the organization's centralized repository of past project schedules, budgets, cost performance indices, and documented lessons learned from similar completed projects. How should this item be classified in project management inputs?

Correct Answer: An Organizational Process Asset because it represents documented knowledge and lessons learned from previous similar projects that can be reused to inform the current project

Historical project archives containing past schedules, budgets, and performance data are classic examples of Organizational Process Assets (OPAs). OPAs are tangible or intangible assets created by the organization through the execution of previous projects. They include processes, procedures, policies, lessons learned databases, templates, and historical information that become part of the organization's institutional knowledge. These assets exist to support current and future projects by providing evidence-based guidance and reducing rework. Enterprise Environmental Factors (EEFs), by contrast, are external conditions or the organization's internal environment that the project must adapt to (such as market conditions, regulatory requirements, organizational culture, or infrastructure), rather than internal knowledge repositories meant for reuse. The distinguishing factor is that OPAs are intentionally accumulated and documented for organizational learning and project improvement, making historical project data a textbook OPA.

More Business Environment: Governance and Compliance questions
1428 questions (total)
Practice 100 questions
One session at a time, always new questions