PMP Certification — Practice Q&A
Q: Why did PMBOK 8 consolidate the 12 principles from PMBOK 7 down to 6?
A: The 12 principles were largely regrouped, not discarded — overlapping ones were merged into broader themes (stewardship and leadership behaviors became "Be an Accountable Leader"; systems thinking and navigating complexity became "Adopt a Holistic View"). Two didn't merge into another principle at all: tailoring moved into its own section of the Guide, and risk moved into the Risk performance domain. The one genuinely new principle, not a merge of anything from PMBOK 7, is "Integrate Sustainability Within All Project Areas."
Q: What does "tailoring" mean in PMP terms, and why isn't it listed as one of the 6 principles anymore?
A: Tailoring means adapting the project management approach — planning depth, documentation formality, process rigor — to fit a specific project's size, complexity, and risk profile, rather than applying a fixed methodology uniformly regardless of context. PMBOK 8 moved it out of the principles list into its own dedicated section, but the underlying skill is tested just as heavily — most PMP scenario questions still ultimately test tailoring judgment in some form, whether or not the question labels it that way.
Q: Why might a hybrid approach combine predictive planning for high-level milestones with agile delivery for solution development?
A: This applies tailoring deliberately rather than forcing one uniform methodology across a project with genuinely varied needs — high-level scope, budget, and regulatory milestones often benefit from predictive structure's stability and formal sign-off, while the detailed solution-development work often benefits from agile's iterative refinement as understanding evolves. Combining both isn't an inconsistent approach; it's matching each part of the project to what genuinely fits its own characteristics.
Q: As of the July 2026 exam update, which domain carries the largest share of PMP exam content — and which domain's weight changed the most?
A: Process carries the largest share (41%), followed by People (33%) and Business Environment (26%). The domain whose weight changed the most is Business Environment, which more than tripled from 8% to 26% — reflecting new exam emphasis on value creation, sustainability, systems thinking, and AI-enabled work environments, not just a reshuffling of the same content.
Q: A team member raises a conflict on a project. What response does PMI's framework generally favor?
A: Direct, collaborative conflict resolution addressing the underlying issue at the team level, consistent with PMI's servant-leadership framing of the project manager's role — rather than escalating to higher authority or avoiding the issue, unless the situation genuinely exceeds what direct team-level resolution can address. This reflects the "Build an Empowered Culture" and "Be an Accountable Leader" principles' emphasis on fostering collaborative team effectiveness, expressed through the Resources domain's "Lead the Team" process, rather than defaulting to directive authority.
Q: Why can a technically successful, on-time, on-budget project still represent a poor outcome under PMBOK 8's framework?
A: The Business Environment exam domain and the "Focus on Value" principle connect project work back to organizational strategy and value delivery — if business conditions changed during the project such that the original scope no longer serves the organization's actual need, delivering that scope successfully doesn't mean the project delivered genuine value. PMBOK 8's "Integrate Sustainability Within All Project Areas" principle adds a further dimension: a project can also underdeliver on value if its approach ignored environmental, social, or economic sustainability considerations. A project manager's responsibility includes surfacing these value-relevance and sustainability concerns to stakeholders, not simply executing the originally defined scope regardless of whether it remains the right thing to deliver.