9 PMP Mock Exams and Review
A practical guide to PMP exam structure, situational decision-making across the People, Process, and Business Environment domains, and using mock-exam results to target further practice.
Exam structure and timed practice
The PMP examination outline effective from July 2026 assigns of the exam to People, to Process, and to Business Environment. Predictive, adaptive, and hybrid approaches are integrated across all three domains. Approximately of items use predictive approaches and use adaptive or hybrid approaches.
The exam has questions and minutes, with two -minute breaks. A short -question practice set is a diagnostic, not a full simulation or a prediction of an exam result. Its approximate domain mix is four People questions, five Process questions, and three Business Environment questions. Allow minutes, or about seconds per question, and choose the best answer before checking the key. The practice questions described here are original, not official PMI exam questions.
People: collaboration and communication
People-domain scenarios often call for understanding the situation, working with the people involved, and choosing a response that supports collaboration and project goals.
Conflict: When two team members disagree about meeting a milestone and collaboration is suffering, first understand the conflict and facilitate their agreement on a solution. Do not begin by asking the sponsor to choose, reassigning someone, or imposing the option that appears fastest.
Knowledge transfer: If a specialist with essential knowledge will leave before a critical activity is complete, arrange knowledge-sharing sessions and capture critical information so the team can continue. Waiting to see whether the departure causes a problem does not transfer the knowledge; neither is it necessary to start by demanding that all remaining work be completed or asking the sponsor to extend the assignment without assessing alternatives.
Communication: A sponsor who wants concise monthly outcome updates and technical stakeholders who need frequent integration detail have different information needs. Tailor the communication and establish a feedback loop rather than sending everyone the same detailed report or communicating only on request.
Team performance: When a capable team member misses commitments and the cause is unclear, speak privately with the person first. Understand possible barriers and identify appropriate support or corrective actions before removing the person, lowering expectations, or escalating to the sponsor.
Process: changes, delivery, and control
Process-domain decisions should fit the project context. Assess impacts and use the relevant process rather than acting solely on authority, habit, or an unexamined preference.
Requested change: In a predictive project, a senior stakeholder requests a feature that may improve customer satisfaction but could delay the approved release. Assess the impacts and process the request through established . Do not add it just because the stakeholder is senior, reject it simply to protect the baseline, or leave the decision to whether the team can avoid overtime.
Backlog priorities: When customer feedback indicates that a planned feature is more valuable than items near the top of an agile backlog, work with the product owner and relevant stakeholders to reassess priorities using value and feedback. Developers should not decide without the product owner, and the iteration is not automatically stopped and replaced in full.
Possible supplier delay: If a supplier warns that a component may arrive late and the delay could affect a milestone, analyze its probability and impact, consider response options, and update information and communications as appropriate. Do not treat the potential delay as an already-occurring issue or tell the customer the milestone will slip before assessment. Do not wait passively for confirmation or replace the supplier without evaluating contractual and schedule effects. If the possible delay occurs, it becomes an issue requiring action.
Cost performance: Cost performance index is earned value divided by actual cost. With earned value of and actual cost of , . This means the project is earning cents of value per dollar spent. A CPI below indicates less earned value per dollar spent than planned; CPI by itself does not indicate schedule performance.
Repeated defects: If testing finds the same type of defect in several components, work with the team to identify the underlying cause and determine corrective or process-improvement actions. Repairing defects without further analysis may leave a systemic cause in place. Blame and deferring all testing until the end do not address the recurrence.
Choosing an approach: Stable, contract-defined infrastructure work alongside user-facing features that need frequent feedback may warrant considering a . Fit the approach to the different work characteristics and plan and manage interfaces and dependencies. A single predictive or should not be selected automatically for every component, nor should the approach simply be copied from a previous project without assessing current needs.
Business Environment: external change and benefits
Business Environment scenarios require attention to external conditions, potential benefits, and risks. Before acting on a change or promising a benefit, assess its implications with appropriate stakeholders and use the relevant .
New regulation: If a regulation issued during a project may affect the planned product design, assess the impact with appropriate subject-matter experts and stakeholders. Then determine required actions through . Do not continue the design without assessment until a scheduled review, leave interpretation and implementation to the team alone, or remove features from scope immediately.
AI feature: A pilot recommendation feature may improve efficiency while users report biased recommendations and the feature may use sensitive data. Assess value alongside bias, data-use requirements, potential impacts, and relevant legal or policy obligations with appropriate stakeholders and before deciding whether and how to proceed. Do not expand deployment on efficiency evidence alone, ask users simply to ignore recommendations they consider biased, or remove all AI work without evaluating its value and alternatives.
Review results and target practice
Review every item after answering, not only incorrect answers. A correct guess may still indicate a knowledge gap, while a wrong answer may result from rushed reading rather than misunderstanding a concept.
Record results by domain: People out of four, Process out of five, and Business Environment out of three for this mini-exam. These are small samples, so one response can shift a domain percentage substantially; treat the results as diagnostic.
Classify each miss. Possible causes include a knowledge gap, misreading, weak approach selection, overlooking stakeholder or business value, calculation error, or time pressure.
Write the reasoning for each missed or uncertain item: why the best answer fits and why the most tempting alternative does not.
Look for patterns. Repeated errors in a task or approach may point to an area for targeted review. Check whether you defaulted too often to escalation, immediate implementation, or one delivery method.
Practice deliberately: review the relevant concept, answer fresh questions on that skill, and retest later under timed conditions to check whether accuracy and reasoning improve.
For a fuller timing check, complete a mixed set of questions in minutes and follow the current exam instructions for breaks. Track pacing, unanswered questions, confidence, and performance by domain. Do not treat one percentage on a short practice set as a guaranteed pass or fail; use it to identify what to practice next.
A useful review log records: question, domain or task, your answer, best answer, why you missed it, concept to review, and follow-up result. Effective practice combines realistic timing, mixed-domain scenarios, and careful review. Use the current exam outline to guide coverage, choose responses that fit the project context and value, and use recurring reasoning gaps to direct further practice.