Free PMP Full-Length Practice Exam: 180 Questions

This free full-length PMP practice exam includes 180 original PM Mastery questions across the exam domains.

The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.

Count note: this page uses a 180-question full-length practice format for current PMP preparation. Always confirm final exam-day timing, breaks, appointment rules, and candidate instructions directly with PMI before your scheduled exam.

Readiness note: a high score on one practice run is useful, but repeated high scores on varied timed attempts are more meaningful. If you are consistently above your readiness threshold, for example 75% or higher, and you can explain your misses without relying on answer memory, shift toward final review and the real exam rather than trying to memorize a huge bank.

How to run this diagnostic

Set a 230-minute timer and answer the 180 questions before reading explanations. Use a separate answer sheet if possible, then classify misses by People, Process, Business Environment, timing, or misread scenario cues.

How to interpret your result

Use this page as a diagnostic run, not as the only measure of readiness. The most useful result is not just the percentage score; it is the pattern behind the misses.

Score interpretation worksheet

Use this worksheet immediately after the run, before you read too many explanations. The goal is to capture the pattern behind the score while the attempt still feels fresh.

For concept review before or after this set, use the PMP guide on PMExams.com.

What PM Mastery adds after this diagnostic

This static page is useful for one full diagnostic pass. PM Mastery is the better place for repeated practice because it gives you varied attempts and progress history instead of one page you can memorize.

Pacing and review plan

For the cleanest diagnostic result, answer the questions under timed conditions before reading the explanations. If you are using this static page, keep a separate answer sheet or notes file, then review the explanations after each block or after the full run.

Use this pacing guide as a practice budget:

After the run, record four things before starting another mock:

• your overall score and domain-level miss pattern
• the three mistake types that cost the most points
• whether timing, fatigue, or answer recognition affected the result
• the next focused page to drill before another full-length attempt

Do not repeat the same full-length page until you know what you are trying to fix. A diagnostic is most useful when it changes the next study action.

Retake protocol

If you retake this free diagnostic, treat the second attempt as a reasoning check, not as a fresh score. Some stems and answers will be familiar, so the percentage can overstate readiness.

For readiness decisions, give more weight to varied timed attempts in PM Mastery than to repeating one static page. Use this page to diagnose; use the app to build durable speed, coverage, and mixed-scenario judgment.

Exam snapshot

Full-length exam mix

Practice questions

Questions 1-25

Question 1

Topic: Process

A project is deploying a new inventory system across multiple sites. In status meetings, the sponsor and product owner report “no major concerns,” but late in each iteration the operations VP repeatedly escalates issues to the steering committee, saying she was “not consulted” and that the rollout will disrupt peak-season staffing.

The communications plan lists monthly email updates to “Operations leadership” and assumes the operations VP has low interest because she rarely attends project meetings. What is the most likely underlying cause of the situation?

• A. Iteration reviews are uncovering too many defects too late in the cycle.
• B. The stakeholder analysis misclassified a high-power stakeholder, leading to an inadequate engagement approach.
• C. The operations VP is resistant to change because of staffing impacts.
• D. The team is not following the communications plan consistently.

Best answer: B

What this tests: Process

Explanation: The pattern of late escalations from a functional VP indicates a key stakeholder with high power and high impact is not being engaged appropriately. The clue that she was assumed to have low interest because she doesn’t attend meetings points to a faulty assessment, not simply a communication execution problem. The primary issue is inaccurate stakeholder analysis and resulting misalignment in engagement.

Stakeholder analysis focuses on identifying stakeholders and assessing their power/influence, interest, and potential impact so the team can tailor engagement. Here, the operations VP has the authority to escalate to governance and is directly impacted by rollout timing (peak-season staffing), which makes her a high-priority stakeholder regardless of meeting attendance. Treating her as “low interest” and relying on generic updates led to insufficient two-way engagement and late-stage surprises.

A practical diagnosis is:

• Reassess her position on a power/interest (or influence/impact) grid
• Update the stakeholder register and engagement plan with specific touchpoints and decision needs
• Validate assumptions by directly confirming expectations and constraints

The key takeaway is that stakeholder absence from meetings is not evidence of low interest; it often indicates the engagement approach was not tailored to the stakeholder’s influence and operational impact.

A high-power VP showing repeated escalation and operational impact signals she should be treated as high influence/impact and actively engaged, not managed via generic updates.

Question 2

Topic: People

You are leading a hybrid project with a virtual team that includes both senior specialists and new hires. Some team members reported feeling ignored in meetings, so you introduced working agreements, rotating facilitators, and structured round-robin input during planning and reviews. Two sprints later, the sponsor asks how you will validate whether the team’s varied experiences and perceptions are being supported.

Which evidence best validates improved team engagement and inclusion?

• A. Total number of chat messages posted per day in the team channel
• B. Trend results from an anonymous team health/psychological safety pulse survey
• C. Number of team meetings held and average attendance rate
• D. Percent of sprint backlog items completed versus planned

Best answer: B

What this tests: People

Explanation: To support varied experiences and perceptions, you need evidence that reflects how team members feel and whether all voices are being included. An anonymous, repeatable team health/psychological safety pulse provides direct, comparable feedback across the whole team and reduces bias from power dynamics. Trending the results over time validates whether your inclusion practices are working.

Supporting varied experiences and perceptions is validated best by evidence that captures the team’s lived experience, especially for inclusion and voice. Anonymous, lightweight pulse checks (team health/psychological safety, inclusion, ability to speak up, clarity of working agreements) provide direct perception data and are more reliable when power distance or seniority may suppress candid feedback.

Use the results as a trend, not a one-time snapshot:

• Run the same short questions at a regular cadence
• Review trends and themes in comments
• Agree on 1–2 improvement actions and recheck next pulse

Activity counts and delivery throughput can improve while some people still feel excluded; perception-based evidence is needed to validate inclusion outcomes.

An anonymous pulse survey directly measures whether different team members feel safe and included, and trending shows whether perceptions are improving.

Question 3

Topic: Process

A project has many interdependent tasks that share the same specialized engineers. The project manager builds the schedule by first estimating task durations, then leveling resources. Instead of adding safety to each task, the project manager removes most individual padding and adds a project buffer at the end of the longest resource-constrained sequence, plus smaller buffers where noncritical paths feed into it. Buffer consumption is tracked to trigger corrective action early.

Which schedule management principle/concept does this approach best represent?

• A. Fast tracking to overlap sequential activities
• B. Resource smoothing to keep resource use within limits
• C. Critical path method using total float to control slippage
• D. Critical chain method with buffers

Best answer: D

What this tests: Process

Explanation: The described practice is critical chain project management: after considering resource constraints, it protects the critical chain with explicit buffers and monitors buffer consumption to signal emerging schedule risk. This is distinct from managing float on a purely logic-based critical path or compressing the schedule by overlapping work.

This is the critical chain method (CCPM). It identifies the longest chain of dependent work considering both logic dependencies and resource constraints, then manages schedule risk by aggregating safety into explicit buffers (a project buffer at the end of the critical chain and feeding buffers where noncritical paths join it). Tracking buffer consumption provides an early-warning mechanism so the team can take corrective actions before the final milestone is threatened. CPM, in contrast, is centered on the longest path through the network based on dependencies and uses float to manage noncritical work, without the same buffer-management focus.

• Build the network and estimate durations
• Level resources to expose the critical chain
• Place project and feeding buffers
• Monitor buffer burn to manage risk

It manages schedule risk by focusing on the resource-constrained chain and protecting it with project and feeding buffers rather than padding every activity.

Question 4

Topic: Process

A predictive infrastructure project is in Executing. During installation, the operations manager requests adding redundant power units to all racks after a recent outage at another site.

Constraints:

• A formal change control board (CCB) is required for scope/budget changes.
• The project has a fixed go-live date for a contracted customer, and the installation team is waiting for direction.
• No impact analysis has been completed yet, and the sponsor is pressuring the team to “just do it.”

What is the BEST next action for the project manager to move the project forward?

• A. Reject the request because it was not in the approved scope
• B. Log the request, analyze impacts, and submit to the CCB
• C. Direct the team to install redundancy to protect the deadline
• D. Ask procurement to order parts now and formalize later

Best answer: B

What this tests: Process

Explanation: The project needs a decision that complies with its governance while minimizing delay. The fastest compliant path is to document the change request, perform an impact assessment (scope, schedule, cost, risk), and take it to the CCB for disposition. Once approved or rejected, the project can proceed with clear direction and updated plans.

When a new request affects scope, cost, or schedule and a CCB is required, the project manager should use integrated change control to keep work moving without bypassing governance. In this case, the team is blocked and the sponsor is applying pressure, but proceeding without analysis and approval increases rework and contract risk.

Best-next-action sequence:

• Record the change request in the change log
• Perform an impact analysis with the team and key SMEs
• Present the analysis to the CCB for an approve/reject decision
• If approved, update baselines/plans and communicate the decision

Key takeaway: move forward by getting a timely, authorized decision—not by implementing or committing spend outside the control process.

This advances work by following integrated change control: document the change, assess impacts, and obtain the required decision authority before directing implementation.

Question 5

Topic: People

A hybrid product project is in iteration 3. The development lead claims a user story is “done,” but the QA lead rejects it because the acceptance criteria were interpreted differently, creating rework and tension. The sponsor asks why the team “can’t agree on basic definitions.”

What should the project manager do next?

• A. Facilitate a joint review to align interpretations and find the source
• B. Publish a new definition of done and require immediate compliance
• C. Escalate the disagreement to the sponsor for an immediate decision
• D. Update the communications plan and resend reporting expectations

Best answer: A

What this tests: People

Explanation: The best next step is to break down the disagreement by bringing the right people together and comparing their interpretations against the original story, acceptance criteria, and working agreements. This helps pinpoint exactly where meaning diverged (ambiguity, assumptions, missing detail, or missed communication) before taking corrective action. Once the root cause is clear, the team can agree on a durable fix and prevent recurrence.

When a misunderstanding is causing conflict and rework, the project manager should first diagnose it by decomposing the situation: who believed what, based on which artifact or conversation, and where the interpretation split. A short, facilitated session using active listening and focused clarifying questions can trace the issue to a specific root cause (for example, ambiguous acceptance criteria, incomplete refinement, an uncommunicated decision, or inconsistent use of a working agreement). Then the team can update the appropriate artifact (acceptance criteria, definition of done, backlog item notes) and confirm shared understanding.

Key takeaway: align and identify the source of the misunderstanding before enforcing solutions or escalating.

A facilitated alignment discussion with targeted questions isolates where the interpretation diverged so the true cause of the misunderstanding can be addressed.

Question 6

Topic: Process

A predictive project is halfway through execution. The latest cost report shows the project is trending to finish 12% over the approved cost baseline, exceeding the organization’s ±5% variance tolerance. The PMO’s governance requires formal approval for any use of management reserve or changes to baselines.

What should the project manager do next?

• A. Submit a change request with variance analysis and forecast
• B. Rebaseline the cost baseline after reestimating remaining work
• C. Ask the sponsor to approve additional funding in an email
• D. Authorize management reserve use to cover the overrun

Best answer: A

What this tests: Process

Explanation: When budget variance exceeds defined tolerances, the project manager should follow the governance escalation path rather than making unilateral funding or baseline decisions. A formal change request, supported by variance analysis and a revised forecast, enables authorized leaders to approve reserve use, corrective actions, or a rebaseline as appropriate.

The core concept is monitoring cost performance against the cost baseline and using the organization’s governance (integrated change control) to address variances outside tolerance. In the scenario, the forecasted overrun is material (12%) and explicitly exceeds the ±5% threshold, and the PMO requires formal approval to use management reserve or change baselines.

Appropriate next steps are:

• Analyze and document the variance and updated estimate at completion (forecast).
• Recommend response options (corrective actions, reserve use, or rebaseline).
• Submit the change request for review/approval per governance.

Taking action outside the change control process undermines controls and can create unauthorized spending or unapproved baseline changes.

Because the variance exceeds tolerance and governance controls baseline/reserve changes, the PM should escalate through formal change control with supporting cost impacts.

Question 7

Topic: Process

A project manager is integrating subsidiary plans for a hybrid product rollout. The PMO wants weekly data on 30 metrics, but the team says compiling them will reduce delivery capacity. The project manager facilitates a working session with the sponsor, PMO, and product owner to agree on a concise dashboard that includes only the measures needed to make governance decisions and to define who needs what information and how often.

Which principle/governance concept best matches this practice?

• A. Perform integrated change control for all requested reporting changes
• B. Define roles and responsibilities using a RACI matrix
• C. Identify and document stakeholder information requirements
• D. Establish risk escalation thresholds in the risk management plan

Best answer: C

What this tests: Process

Explanation: The described practice is about clarifying and agreeing on the minimum set of information needed for oversight and decision-making. That is the core of determining stakeholder information requirements, which then drives the communications approach (content, cadence, and recipients). It also supports integrated planning by aligning reporting with governance needs without overburdening delivery work.

Determining critical information requirements means identifying, analyzing, and documenting what information key stakeholders need to fulfill their roles (especially governance and decision-making), and then tailoring the reporting content and cadence accordingly. In the scenario, the project manager brings decision-makers together to agree on a concise dashboard and define recipients and frequency, ensuring the communications approach supports oversight while minimizing waste.

A practical way to do this is to:

• Identify decision-makers and their decisions
• Define the minimum metrics/thresholds needed to make those decisions
• Agree on format, frequency, and distribution method

This is different from controlling changes, assigning accountability, or defining risk escalation rules, which may use the information but do not define the information needs themselves.

It focuses on determining who needs what information, in what format, and at what frequency to support decisions.

Question 8

Topic: Process

A hybrid software implementation has completed three iterations. The team keeps repeating the same integration defects and environment setup mistakes, causing rework each sprint. When the project manager reviews project documents, they find the last lessons learned entry was created during project kickoff, and recent sprint retrospectives produced notes that were never added to the lessons learned repository or reflected in updated plans or working agreements.

What is the most likely underlying cause of the repeated problems?

• A. The team lacks technical skills for integration and needs training
• B. Requirements are unclear, so defects are expected until scope is clarified
• C. Lessons learned are not being captured continuously and fed back into planning
• D. The deployment environment is unstable, so rework is unavoidable each sprint

Best answer: C

What this tests: Process

Explanation: The key clue is that the team is generating insights (retrospective notes) but not transferring them into an accessible lessons learned repository or integrating them into updated plans and working agreements. Without that feedback loop, known setup and integration issues recur across iterations. Continuous capture and reuse of lessons learned is the primary continuity mechanism being missed.

The core issue is a broken knowledge-transfer loop: learning is happening, but it is not being institutionalized and reused. In any delivery approach, lessons learned should be captured throughout the project and then integrated into future work so the team changes how it plans and executes.

A practical way to close the loop is:

• Capture agreed actions from retrospectives/phase reviews in a lessons learned register or repository
• Assign owners and due dates for the improvement actions
• Update the relevant artifacts (working agreements, checklists, test/deploy steps, plans)
• Review the updates during planning so the team actually applies them

Skill gaps, unclear requirements, or unstable environments may exist, but the stem’s evidence specifically shows the team is not recording and embedding learning, which directly drives repeated preventable errors.

Because insights from retrospectives are not recorded and used to update plans/agreements, the team repeats the same mistakes.

Question 9

Topic: People

In PMI terminology, what is the artifact used to document and tailor a team’s ground rules (for example, working hours across time zones, meeting etiquette, and collaboration tools) so they align with organizational policies and remote/hybrid constraints?

• A. Stakeholder engagement plan
• B. Team charter
• C. Communications management plan
• D. Resource management plan

Best answer: B

What this tests: People

Explanation: A team charter is the core team-level artifact for establishing and adapting ground rules and expected behaviors. It is where the team explicitly agrees how it will operate (including remote/hybrid norms) while respecting organizational policies and constraints.

The key concept is that ground rules are best established as explicit working agreements the team co-creates and commits to. The artifact that captures these agreements is the team charter, which typically includes items such as team values, decision-making approach, roles, meeting norms, communication channels, and expectations for collaboration across locations and time zones. Because it is an agreement among team members, it is also the right place to tailor how the team will work within organizational policies (for example, required tools, security rules, and core business hours) and to revisit and update those rules as remote/hybrid constraints evolve. Plans like communications, resources, or stakeholder engagement may reference how information flows, staffing, or stakeholder interactions work, but they do not serve as the team’s primary ground-rules agreement.

Key takeaway: ground rules belong in the team charter (team working agreements).

A team charter captures agreed team values, roles, and ground rules tailored to how the team will work within organizational constraints.

Question 10

Topic: People

A hybrid product development project has multiple functional leads (IT, Security, Operations, Compliance) and a product owner. Work is progressing, but key design decisions keep stalling because meetings end without a clear decision owner, and teams later dispute who had final authority. The project manager wants a lightweight way to clarify who drives a decision, who approves it, and who is consulted or informed.

Which tool should the project manager use?

• A. Create a RACI matrix for project work packages
• B. Update the stakeholder register with influence and interest ratings
• C. Facilitate a team charter workshop to agree working norms
• D. Create a DACI decision-rights matrix for major decisions

Best answer: D

What this tests: People

Explanation: This scenario’s main problem is unclear decision authority, not unclear task execution. A DACI matrix is designed to make decision rights explicit by identifying who drives the decision, who approves it, and who contributes or is informed. That directly addresses stalled decisions and later disputes about who had final say.

Use a decision-making framework when the bottleneck is ambiguity over who can make or approve decisions. In this case, multiple leads can influence outcomes, but decisions are stalling and being challenged afterward—classic symptoms of unclear decision rights.

DACI is purpose-built for this by defining:

• Driver (coordinates and moves the decision to closure)
• Approver (has final authority)
• Contributors (provide input)
• Informed (receive the decision)

RACI clarifies responsibility for doing work, but it does not consistently remove ambiguity about who is the final decision maker for a specific decision. The key takeaway is to match the artifact to the governance need: decision rights vs. task responsibilities.

DACI explicitly assigns a decision Driver and single Approver, preventing stalled or disputed decisions.

Question 11

Topic: People

You are taking over a hybrid project with a newly formed cross-functional team spread across three time zones. Productivity is low and work is being duplicated.

Exhibit: Issue log (excerpt)

ID: ISS-07
Summary: Duplicate work and missed handoffs
Details: Dev and QA both built separate test harnesses.
Root cause (reported): Unclear ownership of integration testing.
Impact: 1 sprint of rework; rising frustration.
Stakeholders affected: Product owner, Dev, QA, Ops

What should the project manager do next to accelerate team formation and improve productivity?

• A. Add a detailed procedure for integration testing to the quality management plan
• B. Facilitate a role clarity session and update a RACI/working agreement
• C. Reassign the integration testing work to the most experienced engineer
• D. Escalate the issue to the steering committee for direction

Best answer: B

What this tests: People

Explanation: The issue log points to unclear ownership as the root cause of duplicate work and missed handoffs. A facilitated role clarity discussion, captured in a simple responsibility model and team working agreement, directly addresses onboarding and expectations so the team can coordinate effectively across functions and time zones. This accelerates team formation by making interfaces and decision rights explicit.

This is a team-formation and onboarding problem: duplicated effort is a symptom of unclear responsibilities, handoffs, and decision rights. When the exhibit identifies “unclear ownership” as the root cause, the project manager should quickly align the team on who owns what work, how work transitions between roles, and how the team will collaborate (especially in a hybrid, distributed context).

Practical next steps:

• Facilitate a short role/hand-off workshop with Dev, QA, Ops, and the product owner
• Define responsibilities for integration testing and related interfaces (e.g., build, environments)
• Capture it in a lightweight RACI and/or team working agreement and socialize it

This resolves the root cause and prevents recurrence more directly than governance escalation, added documentation, or individual reassignment.

The exhibit shows ownership confusion causing duplication, so clarifying roles and handoffs is the fastest way to stabilize how the team works.

Question 12

Topic: People

You are leading a hybrid project to deliver a customer portal by a fixed launch date. The team has clear strengths (two members are strong in API integration, one excels in UX, and no one is experienced with performance testing), and work must be planned so the team can deliver quickly while managing the skill gap.

Which tool should you use first to organize the work around the team’s strengths?

• A. Work breakdown structure (WBS)
• B. RACI matrix
• C. Risk register update
• D. Skills (competency) matrix

Best answer: D

What this tests: People

Explanation: A skills (competency) matrix is designed to map required skills to available team capabilities. In this scenario, the key constraint is uneven capability (notably the performance-testing gap), so making strengths and gaps explicit enables assigning work to the best-fit people and planning pairing/training to cover gaps without jeopardizing the launch date.

Organizing around team strengths means intentionally aligning work with demonstrated capabilities while making skill gaps transparent so you can plan support (pairing, mentoring, training, or targeted sourcing). A skills (competency) matrix is the most direct tool for this because it links needed skills to specific team members and highlights gaps that could constrain delivery (such as no performance-testing experience).

Using the matrix, you can sequence and assign work to leverage the API and UX strengths, and plan a concrete response for the performance-testing gap (for example, pair a team member with an expert, schedule coaching, or bring in temporary support). Tools focused on accountability, scope decomposition, or general risk tracking are helpful, but they do not specifically organize execution around strengths.

It makes team strengths and gaps visible so work can be assigned and paired appropriately.

Question 13

Topic: Process

A hybrid software project has failed the last two iteration demos due to high-severity defects that should have been caught earlier. Quality data shows most defects originate in poorly understood acceptance criteria and inconsistent peer review. The project manager recommends adding a clear “definition of done” with testable acceptance criteria and mandatory peer reviews for each story starting next iteration.

What is the most likely near-term impact of this recommendation?

• A. More defects are detected during development, reducing rework in demos
• B. Total project cost decreases due to fewer quality activities
• C. Customer satisfaction improves significantly at product launch
• D. The organization’s quality policy is updated for all projects

Best answer: A

What this tests: Process

Explanation: The quality gaps point to unclear requirements and inconsistent reviews, so the best improvement option is to strengthen in-process quality controls. Adding testable acceptance criteria and mandatory peer reviews prevents and detects defects earlier in the workflow. The immediate effect is fewer severe defects escaping into the next demo and less last-minute rework.

When quality data shows defects are being introduced by unclear acceptance criteria and inconsistent reviews, the improvement option should target prevention and early detection where the defects enter the process. A shared definition of done with testable acceptance criteria reduces ambiguity, and mandatory peer reviews add an in-process check before work is considered complete.

Near-term, these actions typically:

• reduce defect leakage into demos/UAT
• reduce urgent rework late in the iteration
• stabilize delivered increments by improving conformance to acceptance criteria

Broader outcomes like launch satisfaction or organizational policy changes may occur later, but the immediate consequence is improved iteration-level quality and fewer escaped defects.

Strengthening acceptance criteria and peer reviews shifts defect detection earlier, so fewer severe defects reach the demo in the next iteration.

Question 14

Topic: People

A hybrid project is rolling out a new customer support platform to 300 agents. The project manager reports training progress using only course completion rates and attendance. The operations manager asks whether agents can actually perform the new workflows before the upcoming pilot.

What is the most likely near-term impact of relying only on completion/attendance to measure training outcomes?

• A. Skill gaps will surface during the pilot, increasing rework and support
• B. Stakeholder engagement will improve because training feels complete
• C. The project will miss long-term benefits realization targets
• D. Audit findings will occur due to inadequate training documentation

Best answer: A

What this tests: People

Explanation: Training outcomes should be measured by demonstrated competence (for example, assessments, simulations, or on-the-job performance), not just participation. If the team tracks only attendance and completion, readiness is overstated and gaps are discovered only when agents start executing the new processes. That creates immediate performance issues during the pilot and drives rework and extra support load.

Measuring training outcomes means verifying that learners can perform the required tasks to the agreed level, not simply that training was delivered. In this scenario, completion/attendance are activity metrics, so they do not provide evidence that agents can execute the new workflows before the pilot.

Near-term, the first real validation occurs when agents try to use the platform, so capability gaps show up as errors, slower handling, higher support requests, and rework to retrain or adjust procedures.

A better approach is to define success criteria for training (role-based proficiency) and measure it with practical checks such as short skills assessments, supervised simulations, or pilot performance measures tied to the new workflows.

Attendance shows participation, not competence, so performance issues will appear quickly once people use the new workflows.

Question 15

Topic: Process

You are managing a predictive project with a fixed-price vendor contract that uses milestone payments. The contract states payment is released only after the customer formally accepts each milestone deliverable against the acceptance criteria in the statement of work (SOW). A vendor claims Milestone 2 is complete and requests payment.

Which artifact best validates that the project is ready to release the Milestone 2 payment?

• A. Timesheets and invoices showing hours worked to date
• B. Signed milestone acceptance document referencing SOW criteria
• C. Meeting minutes from the Milestone 2 status review
• D. Vendor progress report showing 100% complete for Milestone 2

Best answer: B

What this tests: Process

Explanation: With milestone-based fixed-price contracting, the most defensible validation for payment is objective evidence of deliverable acceptance. A signed acceptance document that ties directly to the SOW acceptance criteria confirms the milestone is completed and accepted per the contract. This provides auditable authorization to proceed with payment.

In a milestone payment structure, “progress” is not measured by effort spent or self-reported completion; it is measured by whether the specified deliverable has been verified and formally accepted per the contract. The best validation is an auditable acceptance record that links the deliverable to the SOW acceptance criteria and shows customer sign-off. This aligns project execution strategy (contracting/finance) with governance: payment is a financial control triggered by acceptance, not by activity outputs. The key takeaway is to use objective, contract-aligned evidence to validate readiness for payment and avoid relying on vanity measures or internal administrative artifacts.

Formal customer acceptance against the SOW criteria is the contractual evidence needed to authorize milestone payment.

Question 16

Topic: People

You are assigned as project manager to a hybrid team delivering an internal analytics solution. The team includes on-site staff and remote members in three time zones, and the sponsor asks you to establish team ground rules for meeting cadence, response-time expectations, and collaboration tools before work begins. The organization mentions “strict HR and information security requirements,” but you have not seen the specifics.

What should you verify or obtain FIRST before finalizing the team’s ground rules?

• A. Approval and budget to procure a new video conferencing platform for the team
• B. The sponsor’s success metrics and acceptance criteria for the solution
• C. The organization’s policies on remote work hours, overtime, and approved collaboration tools
• D. Each team member’s preferred meeting times and communication channels

Best answer: C

What this tests: People

Explanation: Before setting ground rules for a remote/hybrid team, the project manager should confirm the organizational constraints that govern how people can work and what tools can be used. HR policies (work hours, overtime) and information security rules (approved platforms, data handling) define the boundaries for any team agreement. Once those constraints are clear, team preferences can be incorporated safely and realistically.

Team ground rules (often captured in a team charter or working agreement) should enable effective collaboration while complying with organizational policies. In a remote/hybrid setting, constraints like approved communication tools, data classification/handling requirements, core hours, overtime rules, and time zone expectations directly shape what ground rules are feasible and permissible. If you start by collecting preferences or buying tools, you risk creating agreements the team cannot follow or that violate HR/security requirements.

A practical sequence is:

• Obtain applicable HR/remote-work and security/tooling policies.
• Translate constraints into ground rules (availability windows, response times, approved channels).
• Then tailor details with the team based on preferences and operational needs.

The key takeaway is to anchor ground rules in mandatory organizational constraints before optimizing for convenience.

Ground rules must be tailored within HR/security constraints (e.g., core hours, overtime rules, and tool/data restrictions) before team preferences can be applied.

Question 17

Topic: People

A hybrid product implementation has a co-located PM and a virtual delivery team. The same type of conflict has been escalating every iteration.

Exhibit: Issue log (excerpt)

ID: ISS-18  Summary: Dev vs QA dispute on acceptance criteria ownership
Impact: Sprint goal at risk; rework created
Status: Closed; “PM mediated”; root cause not captured
ID: ISS-23  Summary: Repeated argument on who approves “done”
Impact: Handoff delays; team escalation to PM
Status: Open
ID: ISS-27  Summary: Disagreement on priority changes mid-iteration
Impact: WIP exceeded; missed commitments
Status: Open

Based on the exhibit, what should the project manager do next to prevent this conflict from recurring?

• A. Replace the team members who are involved in the disputes
• B. Escalate the unresolved conflicts to the sponsor for direction
• C. Facilitate a working-agreement session to clarify roles, decision rights, and ground rules
• D. Freeze scope changes and route all requests through change control

Best answer: C

What this tests: People

Explanation: The issue log shows recurring disputes about ownership, approval authority, and mid-iteration priority changes—signals that roles and decision rights are not explicit. A facilitated working agreement (and role clarification) addresses the root cause by setting clear expectations for how the team makes decisions and completes handoffs. This is a preventative action aimed at reducing future conflict, not just resolving today’s symptoms.

Preventing recurring conflict requires addressing root causes with clear expectations, not repeatedly mediating individual incidents. The exhibit shows repeated disagreements about who owns acceptance criteria, who approves “done,” and how priority changes are handled mid-iteration—classic indicators of unclear roles/responsibilities and missing team norms.

The project manager should facilitate the team (and relevant leaders like the product owner/QA lead) to define and document:

• Role clarity (e.g., RACI for acceptance criteria, “done,” approvals)
• Working agreements/ground rules (handoffs, conflict resolution path)
• Decision-making rules (how and when priorities can change within an iteration)

Then socialize the agreement and use it as the reference when similar situations arise. Escalation or tighter controls may still be needed later, but they don’t remove the underlying ambiguity causing repeated friction.

The issues repeat due to unclear ownership and decision-making, so establishing clear roles and team ground rules is the preventative action.

Question 18

Topic: People

In a project environment, which term best describes using your professional relationships across the organization to quickly obtain support or resources needed to remove team impediments?

• A. Networking
• B. Communications management plan
• C. Escalation
• D. Stakeholder analysis

Best answer: A

What this tests: People

Explanation: Networking is the practice of building and leveraging relationships across the organization to get help, information, or access to decision-makers. When a team is blocked, effective networking enables the project leader to remove impediments faster by connecting with the right people and securing support. This is distinct from formal documentation or pushing issues up the hierarchy as a first response.

Networking is a leadership and influence skill used to remove impediments by tapping into your professional connections—both formal (roles, governance) and informal (trusted relationships, communities of practice). In practice, you use networking to quickly find the right subject-matter experts, obtain approvals, negotiate for scarce resources, or coordinate with other teams whose work is creating a dependency. It complements formal processes but is often faster for unblocking day-to-day obstacles.

A key test is whether the action relies on relationships and influence to enable progress, rather than producing a document or triggering a formal governance step.

Networking is leveraging formal and informal relationships to gain timely support, information, or resources to resolve blockers.

Question 19

Topic: People

You are managing a hybrid enterprise data-migration project with a cross-functional delivery team and an executive steering committee. To “simplify communications,” you stop sending tailored updates and begin sending one daily, highly detailed task-level status email (including technical logs and backlog item notes) to everyone: team members, functional managers, and executive stakeholders.

What is the most likely near-term impact of this decision?

• A. The project exceeds the cost baseline due to reporting overhead
• B. Stakeholders expand scope because they feel more informed
• C. The organization replaces the project manager at deployment
• D. Executive stakeholders disengage, delaying timely decisions

Best answer: D

What this tests: People

Explanation: This change removes audience-specific communication and leadership, creating information overload for executive stakeholders. In the near term, overwhelmed stakeholders tend to skim or ignore updates, which reduces engagement and slows decision-making and escalations needed to keep work moving.

Effective leadership includes tailoring communication and engagement to different audiences. Executives typically need concise, decision-oriented status (progress against objectives, key risks, decisions needed), while delivery teams need detailed, actionable information. Sending the same highly detailed daily update to everyone increases noise for stakeholders who do not need that level of detail, so they disengage or defer responses. The immediate consequence is slower decisions, weaker sponsorship, and delayed removal of impediments—exactly when the team needs timely guidance and support. The better approach is to keep a tiered communications approach (e.g., executive summary plus separate team-level detail) aligned to stakeholder needs and influence.

Key takeaway: a “single update for all” usually hurts engagement before it affects cost or staffing outcomes.

A one-size-fits-all, overly detailed message overwhelms executives, reducing engagement and slowing needed decisions and support.

Question 20

Topic: People

An agile team has recurring rework because user stories enter development with unclear acceptance criteria. In the sprint retrospective, the team agrees to add a simple Definition of Ready checklist and to assign a rotating peer to review acceptance criteria before refinement ends.

The project manager thanks the team but does not capture the actions, assign owners, or add the changes to any tracking mechanism before moving into the next sprint planning.

What is the most likely near-term impact?

• A. Regulators fail the project audit due to undocumented process controls
• B. Several key team members resign due to unresolved team frustration
• C. The same issues persist and the team disengages from the next retrospective
• D. The sponsor escalates the project for missing quarterly benefits targets

Best answer: C

What this tests: People

Explanation: Retrospectives only improve performance when actions are made visible, owned, and tracked to completion. By not assigning owners or integrating the agreed changes into the team’s work system, the improvement items will likely be dropped. The most immediate consequence is that the same pain points reappear and the team starts viewing the retrospective as ineffective.

The core concept is turning retrospective outcomes into actionable, implemented process changes. In the scenario, the team identified clear experiments (Definition of Ready checklist and peer review) but the project manager failed to create accountability and a feedback loop. In the near term, those actions will not make it into day-to-day work, so the team will continue pulling underprepared stories and experiencing rework, and members will quickly reduce participation because they don’t see results.

Practical facilitation follow-through includes:

• Capture each action as a visible work item
• Assign a single owner and due date
• Integrate it into the team’s backlog/board and review progress
• Verify results in the next retrospective

This is more immediate and directly tied to the inaction than downstream business escalations or staffing outcomes.

Without owners and follow-up, improvement actions are unlikely to be implemented, so the problem recurs and the team quickly loses confidence in retrospectives.

Question 21

Topic: Process

A hybrid project is implementing a customer data platform. The change control board has approved a change to add a new data-retention feature to meet a regulatory requirement, which introduces additional development work and a new vendor-provided component. The project manager is updating project documents to keep plans aligned.

Which action should the project manager NOT take?

• A. Update only the schedule dates and let the team proceed; adjust other baselines later
• B. Update the scope baseline and backlog items to include the new deliverables and acceptance criteria
• C. Analyze schedule and cost impacts and update affected baselines and forecasts through the change control process
• D. Review and update related subsidiary plans (risk, quality, procurement, communications) to reflect the approved change

Best answer: A

What this tests: Process

Explanation: Approved changes must be integrated across the project management plan and baselines so the work, dates, cost, risks, and stakeholder expectations remain consistent. Updating only the schedule while deferring other baseline and plan updates is an integration anti-pattern that leads to conflicting direction and unreliable performance tracking.

The core integration expectation is to assess cross-plan impacts of an approved change and then update all affected components of the project management plan and baselines in a consistent way. In this scenario, adding a regulatory feature and a vendor component can affect scope, schedule, cost, quality approach (e.g., added verification/validation), risks, procurement actions, and stakeholder communications.

A sound approach is to:

• Confirm what plan components/baselines are impacted (scope/WBS or backlog, schedule, cost)
• Update relevant subsidiary plans (risk, quality, procurement, communications, resource)
• Ensure baseline updates follow the organization’s change control and governance

Partially updating just one baseline and proceeding creates disconnects between what is being built, how it is funded, and how performance will be measured.

Updating a single baseline without assessing and updating related plans creates misalignment across scope, cost, risk, procurement, and communications.

Question 22

Topic: Process

A hybrid project has a predictive phase with approved scope, schedule, and cost baselines and an agile delivery phase managed with a product backlog. The change control board approves a change that adds a new regulatory reporting module, affecting deliverables, testing, and an external vendor milestone. The sponsor asks for an updated overall forecast.

What should the project manager use/do to ensure cross-plan impacts are assessed and the plans stay consistent?

• A. Update all affected baselines and subsidiary plans via change control
• B. Update only the schedule model to reflect the new vendor milestone
• C. Add the new work to the product backlog and continue sprinting
• D. Record the change in the risk register and monitor for impacts

Best answer: A

What this tests: Process

Explanation: Because the approved change affects multiple parts of the project (deliverables, testing, vendor milestone), the project manager must apply integrated change control and update the relevant baselines and subsidiary plans together. This keeps scope, schedule, cost, and supporting plans aligned and enables a reliable updated forecast.

The core concept is integrated impact assessment: when a change is approved and it affects more than one aspect of the work, you update the project management plan components consistently, not in isolation. Here, the regulatory module affects scope and quality activities (testing), the schedule (vendor milestone), and likely cost/resources. The project manager should use the change control system to coordinate updates to the scope/schedule/cost baselines (as applicable) and any impacted subsidiary plans (e.g., quality, procurement, communications), then update forecasts and communicate the revised plan. Updating only one artifact (like the backlog or the schedule) creates misalignment between plans and undermines the credibility of reporting and control. The key takeaway is to keep all integrated baselines/plans synchronized after approved changes.

An approved change that impacts multiple components requires integrated change control and coordinated updates to all affected baselines/plans.

Question 23

Topic: Business Environment

A project team is delivering an update to a regulated claims-processing system. To meet a fixed go-live date, the project manager approves deploying to production while the required compliance evidence (test results and approval sign-offs) is still being compiled.

What is the most likely near-term impact of this decision?

• A. Operational costs will increase due to higher post-release maintenance
• B. The organization will likely receive regulatory fines for noncompliance
• C. Customer trust will erode, reducing renewals over the next year
• D. The release will be blocked at the compliance gate until evidence is complete

Best answer: D

What this tests: Business Environment

Explanation: Compliance work often includes mandatory approval checkpoints (gates) that require objective evidence before a release can proceed. Deploying without completed test results and sign-offs most commonly results in an immediate stop or rollback until required artifacts are produced and approved. This is the direct, near-term consequence of bypassing compliance methods.

In compliance-heavy environments, releases typically cannot proceed without specific evidence (for example, completed testing, documented results, and authorized sign-offs). Approving a production deployment before those artifacts are ready creates an immediate governance problem: the release fails the compliance gate, and the organization must halt the deployment (or prevent go-live) until the evidence is completed and approved.

Methods that prevent this include:

• Defining compliance deliverables and approval points in the plan
• Using checklists/traceability to ensure required artifacts are ready
• Scheduling compliance reviews as part of release readiness

Downstream outcomes like fines or reputational damage are possible, but they are less direct and typically occur later or only if regulators or customers are impacted.

Skipping required sign-offs typically triggers an immediate governance hold because the release cannot be approved without mandatory compliance artifacts.

Question 24

Topic: Process

You are taking over as project manager for a hybrid software implementation that has a fixed go-live date set by the steering committee. The previous PM used a single weekly email status report for everyone.

In your first week, you learn that:

• The compliance officer requires traceable, auditable communications for control approvals.
• The vendor team is in a different time zone and misses key decisions made in ad hoc meetings.
• A key operations manager says the weekly report is “too detailed” and stops reading it.

What is the BEST next action?

• A. Send the current weekly report more frequently until stakeholders are satisfied
• B. Standardize a single dashboard and require all stakeholders to use it
• C. Elicit and document stakeholder communication requirements, then update the communications management plan accordingly
• D. Schedule daily cross-functional meetings to ensure no decisions are missed

Best answer: C

What this tests: Process

Explanation: The immediate need is to analyze and align communications to different stakeholder requirements (auditability, time zones, and level of detail) rather than increasing volume or forcing a one-size-fits-all channel. By eliciting and documenting requirements and updating the communications management plan, the project sets appropriate cadence, formats, tools, and decision/approval records for each stakeholder group.

Managing communications starts with analyzing stakeholder communication needs: who needs what information, when they need it, in what format, through which channel, and with what level of formality/traceability. Here, stakeholders have clearly different requirements (auditable approval records for compliance, inclusive decision capture for a remote vendor, and executive-level brevity for operations).

A best-next-action response is to capture these requirements and tailor the communications approach:

• Confirm stakeholder information needs, constraints, and preferences.
• Define cadence, format, and channels by audience.
• Specify decision/approval documentation and storage for traceability.

This creates a fit-for-purpose communications management plan; simply increasing frequency or mandating a single tool does not resolve the differing needs.

This directly analyzes each stakeholder’s information needs, format, timing, and channels so communications can be tailored to the project’s constraints.

Question 25

Topic: Business Environment

A project has released a new customer portal. The business case forecasted a 15% reduction in call volume within 6 months. The sponsor asks for ongoing visibility into whether the expected value is being achieved. The project manager sets up a monthly dashboard that compares planned vs. actual benefit KPIs, shows trends, and forecasts when the target reduction is likely to be reached, and reviews it with the governance board.

Which principle/governance concept best matches this practice?

• A. Earned value performance reporting
• B. Integrated change control
• C. Risk monitoring and control
• D. Benefits realization measurement and reporting

Best answer: D

What this tests: Business Environment

Explanation: The practice described is tracking and communicating whether business outcomes are being achieved after delivery. By comparing planned vs. actual benefit KPIs and forecasting attainment, the project manager is appraising stakeholders on value gain progress, which is central to benefits realization governance.

Appraising stakeholders of value gain progress is about benefits realization measurement and reporting: defining benefit KPIs from the business case, collecting actuals, comparing to targets, and communicating trends and forecasts through the project’s governance channels. In the scenario, the dashboard is explicitly oriented to outcomes (call volume reduction) rather than delivery outputs, and it is reviewed with the governance board to support decisions about realizing expected value. This differs from reporting project execution performance (scope/schedule/cost) or controlling changes and risks, which may affect value but are not, by themselves, value realization reporting.

It focuses on communicating realized and forecast benefits against the business case to key stakeholders.

Questions 26-50

Question 26

Topic: People

A senior developer on a hybrid project has recently missed several sprint commitments and has been slow to respond to critical defect fixes. Stakeholders are starting to complain, but the developer is usually high performing and is well respected by the team. As the project manager, which action should you AVOID when addressing this performance gap?

• A. Offer support such as pairing, training, or workload adjustments based on the root cause
• B. Agree on clear near-term expectations and schedule follow-up check-ins to review progress
• C. Give the developer specific feedback privately and ask what obstacles are contributing
• D. Call out the missed commitments in the team stand-up to create accountability

Best answer: D

What this tests: People

Explanation: Performance gaps are best addressed through timely, private, behavior-based feedback and coaching focused on removing impediments and agreeing on clear expectations. Publicly calling out an individual in a team forum is an anti-pattern because it can shame the person, reduce trust, and make the team less willing to surface problems. Protecting psychological safety supports continuous improvement and sustained performance.

Constructive feedback and coaching aim to improve outcomes while maintaining trust and psychological safety. In this situation, the appropriate approach is to talk privately, describe specific observable impacts (missed commitments, slow defect response), listen for root causes (capacity, unclear priorities, burnout, skill gaps, external dependencies), and then co-create a short improvement plan with measurable expectations and support.

Publicly singling someone out in a stand-up turns a problem-solving conversation into a blame event, which often reduces transparency, increases defensiveness, and harms team cohesion—making performance issues harder to resolve. The key takeaway is to address the issue directly and promptly, but in a respectful setting that enables coaching and continuous improvement.

Publicly criticizing an individual damages psychological safety and is not constructive coaching for performance improvement.

Question 27

Topic: Process

Which term best describes the evaluation performed to determine how a proposed change would affect project scope, schedule, cost, resources, and risks before the change is approved?

• A. Integrated change control
• B. Change impact analysis
• C. Scope validation
• D. Cost-benefit analysis

Best answer: B

What this tests: Process

Explanation: Before approving a change, the project team evaluates the downstream effects across key constraints and risk. That evaluation is called change impact analysis. Its purpose is to inform an approve/reject decision with a clear understanding of consequences and trade-offs.

Change impact analysis is the focused evaluation of a proposed change to determine its effects across the project’s key dimensions (for example scope, schedule, cost, resources, and risks) before a decision is made. It is commonly performed as part of handling a change request so decision makers can compare options, understand trade-offs, and avoid unintended consequences such as rework, new risks, or baseline disruption. Integrated change control is the broader governance process that reviews, approves/rejects, and manages changes; impact analysis is an input to that decision-making, not the overall control mechanism.

It specifically assesses a change request’s cross-domain effects to inform an approval decision.

Question 28

Topic: Process

A hybrid project is delivering a new customer portal and plans to hand it over to the operations team in 10 business days. The product owner has accepted the last increment, but the operations manager says the support runbook is incomplete and the on-call team has not been trained; the sponsor is pushing to “transition now” to start the next phase.

What is the BEST next action for the project manager to validate readiness for transition?

• A. Close the project and archive records to meet the timeline, then begin planning the next phase with operations input.
• B. Obtain sponsor sign-off to transition and document the runbook and training as post-transition action items.
• C. Facilitate an operational readiness review with operations using the transition/acceptance criteria, and address gaps before obtaining formal handover sign-off.
• D. Transition ownership immediately since the product owner accepted the increment, and let operations finalize the runbook after handover.

Best answer: C

What this tests: Process

Explanation: Readiness for transition is validated by confirming the receiving organization can operate and support the product using agreed criteria (documentation, training, support model, and acceptance). An operational readiness review with operations creates a shared, evidence-based go/no-go decision and ensures gaps are resolved before formal handover.

Validating transition readiness means verifying—not assuming—that the receiving team can sustain operations and meet service expectations. Even if the product owner accepted the increment, the transition is not ready if key operational elements (runbook and training) are incomplete. The project manager should use the agreed transition/acceptance criteria to run an operational readiness review with operations, confirm that required transition deliverables are complete, and drive actions to close any gaps before requesting formal handover approval.

A practical sequence is:

• Review transition criteria and required artifacts with operations
• Validate evidence (runbook completeness, training completed, support/escalation path)
• Log and resolve gaps, then obtain formal handover sign-off

Relying only on schedule pressure or a single stakeholder’s approval increases operational risk after transition.

A readiness review against defined handover criteria validates the transition is supportable and drives closure of documentation/training gaps before sign-off.

Question 29

Topic: People

A senior operations manager (key stakeholder) joins a project status call visibly frustrated after a recent production incident and repeatedly interrupts to question the team’s competence. The project is on track, but the stakeholder’s support is critical for upcoming user training. Which response by the project manager should be AVOIDED?

• A. Correct the stakeholder with facts and redirect to the agenda.
• B. Pause the status details to listen and reflect key concerns.
• C. Acknowledge the frustration and ask what outcome they need.
• D. Offer a short follow-up 1:1 to address concerns privately.

Best answer: A

What this tests: People

Explanation: Emotional intelligence starts with recognizing the stakeholder’s emotional state and responding in a way that de-escalates and preserves the relationship. When someone is frustrated and interrupting, the project manager should first acknowledge emotions and create space to be heard. Moving straight to “facts and agenda” can invalidate the person and intensify conflict.

The stakeholder’s interruptions are a behavioral trigger signaling frustration and a threatened sense of control or trust. Applying emotional intelligence, the project manager should adapt communication to reduce emotional intensity before trying to persuade with data. Effective moves include acknowledging feelings, listening actively, and choosing an appropriate setting (such as a private conversation) to restore psychological safety and re-establish collaboration. Redirecting with facts and rigidly enforcing the agenda may be technically accurate, but it ignores the stakeholder’s emotional needs in the moment and often escalates the situation, making it harder to secure support for near-term activities like training.

Key takeaway: regulate the interaction first (emotions), then align on content (status and next steps).

This dismisses the emotional trigger and is likely to escalate defensiveness and reduce stakeholder support.

Question 30

Topic: Process

A hybrid software project is in execution with a committed go-live date in 6 weeks. The integration vendor notifies the team that a required API will be deprecated in 30 days, which will break the planned release unless an alternative integration approach is used. A contract change would require procurement involvement.

As the project manager, what are the TWO best actions to take next to manage this issue and protect project success? (Select TWO)

• A. Replace the vendor to avoid any contract modifications.
• B. Submit a schedule-change request immediately to the CCB.
• C. Move the item to the risk register and monitor.
• D. Log the issue, assign an owner, and set a due date.
• E. Instruct developers to build a custom API without approval.
• F. Engage procurement and vendor to agree on a workaround.

Correct answers: D, F

What this tests: Process

Explanation: This is an active issue impacting the near-term release, so it must be tracked, owned, and worked to closure. The project manager should document and assign the issue for accountability, then rapidly coordinate the appropriate stakeholders (including procurement and the vendor) to identify and agree on a practical workaround within governance constraints.

Managing project issues focuses on timely resolution of current problems that are already affecting (or about to affect) project performance. Here, the vendor’s API deprecation is a present constraint with a short deadline, so the project manager should ensure it is captured in the issue log with clear ownership and a target resolution date, then immediately coordinate the right parties to determine an actionable resolution.

Effective next steps typically include:

• Record the issue and assign an owner for follow-through.
• Engage the stakeholders who can change the solution/contract (vendor and procurement).
• Agree on a workaround and route any required approvals through governance.

The key takeaway is to treat it as an issue to resolve now, not as a future risk to simply monitor.

This ensures the issue is formally owned, tracked, and driven to resolution with clear accountability.

This brings the right decision-makers together to define a feasible resolution given the contract and technical constraints.

Question 31

Topic: People

Midway through a hybrid software implementation, the project manager notices the virtual team has become disengaged: meeting attendance is dropping, cycle time is increasing, and several developers say “there’s no point pushing—no one notices.” The sponsor is asking for an escalation.

What should the project manager do next?

• A. Facilitate a team session to identify motivators and update working agreements, including a visible recognition approach
• B. Escalate to the sponsor to request direction and approval to enforce stricter accountability
• C. Individually counsel underperforming team members and document performance concerns for functional managers
• D. Create a reward program and announce it to the team to quickly improve morale

Best answer: A

What this tests: People

Explanation: The immediate issue is low motivation and a belief that effort is not recognized. The best next step is to engage the team to surface what motivates them and refresh the team’s working agreements/social contract, including how recognition will work. This builds ownership, influences behavior, and improves commitment without premature escalation.

When engagement drops, the project manager should first use leadership and facilitation to influence the team environment before escalating or taking punitive actions. In a virtual, hybrid setting, motivation often improves when the team co-creates clear working agreements (team charter/social contract) and a transparent recognition system tied to outcomes the team values.

A practical next step is to:

• Facilitate a short workshop to discuss what is demotivating and what “good” looks like
• Refresh working agreements (participation, collaboration, decision-making, availability)
• Agree on lightweight, visible recognition (peer recognition, demo shout-outs, milestone celebrations)
• Implement and inspect/adapt in upcoming reviews/retrospectives

Escalation is appropriate if impediments are outside the team’s control, but here the first move is to re-engage and motivate through shared norms and recognition.

This addresses the motivation problem at its source by engaging the team to co-create norms and recognition that reinforce desired behaviors.

Question 32

Topic: Process

A project manager is developing the delivery solution for a hybrid product rollout. The internal team will build the core platform, but a vendor must provide a customer-identity module that must meet strict security requirements and be supportable for 3 years after go-live. The sponsor is pressuring the project manager to “just use the incumbent vendor” to save time.

Which action should the project manager NOT take while planning and managing this procurement as part of the delivery solution?

• A. Perform market research and a make-or-buy analysis
• B. Use weighted selection criteria to evaluate supplier proposals
• C. Issue a purchase order to the incumbent based on prior performance
• D. Define vendor deliverables and acceptance criteria in the SOW

Best answer: C

What this tests: Process

Explanation: Developing a delivery solution that includes outsourced components requires a fit-for-purpose procurement approach and transparent supplier selection. Skipping competitive evaluation and awarding work based only on an existing relationship undermines governance and increases the likelihood of selecting a vendor that cannot meet the security and support needs. The other actions strengthen clarity, comparability, and contractual enforceability.

When developing the delivery solution, procurement planning helps ensure external components can meet requirements (for example, security and multi-year support) and can be integrated and accepted successfully. Good practice is to define what will be procured and how it will be selected and managed, using objective criteria and appropriate governance.

Key actions typically include:

• Define a clear SOW with deliverables, acceptance criteria, and support expectations.
• Research the market and confirm the make-or-buy decision.
• Establish evaluation criteria (often weighted) and conduct a fair supplier selection process.

Awarding work to an incumbent solely to save time is an anti-pattern because it bypasses due diligence and can conflict with organizational procurement policies and risk controls.

It bypasses objective vendor evaluation and procurement governance, increasing compliance and delivery risk.

Question 33

Topic: People

A project sponsor insists that a new security feature be added but says there can be no impact to the approved budget or mandated go-live date. You are preparing for a negotiation meeting.

Exhibit: Change request summary (excerpt)

CR-07: Add multi-factor authentication (MFA)
Estimate impact: +\$90,000 cost; +3 weeks schedule
Current contingency remaining: \$30,000
Go-live date: June 30 (regulatory commitment)
Governance: CCB approval required for baseline changes
Compliance note: Interim manual controls acceptable for 60 days

Based on the exhibit, what should the project manager do NEXT to negotiate effectively?

• A. Commit to delivering MFA within the existing baselines to maintain trust
• B. Escalate the request to the CCB immediately without negotiating options
• C. Reject the request because it violates the approved scope baseline
• D. Define negotiation boundaries and BATNA, then propose trade-off packages

Best answer: D

What this tests: People

Explanation: The exhibit indicates the change cannot fit within remaining contingency and would push past a regulatory go-live date, so the PM must clarify what is negotiable versus non-negotiable. The best move is to enter the discussion with explicit negotiation boundaries (authority limits, schedule constraints) and a BATNA such as using interim manual controls while deferring MFA or seeking a formally approved baseline change.

Effective negotiation starts with preparation: define your negotiation boundaries (what you can and cannot agree to) and your BATNA (best alternative if no agreement is reached). Here, the requested MFA change has an estimated +$90,000 and +3 weeks, while contingency is only $30,000 and the June 30 go-live is a regulatory commitment; baseline changes also require CCB approval. That means you should not promise delivery within existing baselines, and you should not treat the negotiation as only yes/no.

A strong next step is to:

• Set a reservation point aligned to constraints and governance (e.g., no unapproved baseline change).
• Define a BATNA using the compliance-acceptable interim manual controls for 60 days.
• Present packaged options (e.g., interim controls now + MFA next release; or MFA now with approved funding/schedule change).

This keeps the discussion interest-based and anchored to objective constraints and decision rights.

The exhibit shows the request exceeds current authority/constraints, so the PM should set a reservation point and BATNA (e.g., interim controls) and negotiate using viable options.

Question 34

Topic: People

A distributed agile team is building a new customer portal. After two iterations, a key stakeholder says the delivered search feature “isn’t what we agreed to,” while the team insists it met the requirements. The project manager wants to investigate potential misunderstandings and confirm a shared understanding before more work continues.

Which evidence best validates that the stakeholder and team agree on what “done” means for the feature?

• A. Updated user story acceptance criteria approved by the stakeholder in the backlog tool
• B. Team velocity increasing over the last two iterations
• C. Iteration burndown chart showing remaining work trending down
• D. QA report showing the number of test cases executed

Best answer: A

What this tests: People

Explanation: To uncover and resolve misunderstandings, the best validation is evidence that expectations were made explicit and agreed to by both parties. Stakeholder-approved acceptance criteria translate “what we agreed to” into testable conditions and a shared definition of done for the feature. This reduces reliance on interpretations and enables objective acceptance discussions.

Investigating misunderstandings is easiest when expectations are captured as objective, reviewable acceptance conditions that both the stakeholder and team agree to. In agile, the highest-signal evidence of shared understanding for a feature is the user story’s acceptance criteria (or equivalent) that has been reviewed and explicitly approved by the stakeholder/product owner. That artifact creates a single source of truth for what “done” means and what will be accepted.

Practical validation steps include:

• Ensure the acceptance criteria are specific and testable.
• Confirm approval is recorded (tool status, comment, or sign-off).
• Use the criteria to guide demos and acceptance decisions.

Progress metrics and test execution counts can look positive while still delivering the wrong outcome if expectations were misunderstood.

Stakeholder-approved acceptance criteria provide the clearest, testable evidence of shared understanding of expected behavior and completion.

Question 35

Topic: Process

You are the project manager for a hybrid project (predictive procurement and deployment, agile product development). In 10 business days you must submit an integrated project management plan for governance approval. A regulatory go-live date is fixed, and the sponsor has stated there is no tolerance for rework after baselining.

Several teams have provided draft plans, but they conflict on what is in scope and which deliverables are required for regulatory acceptance. To optimize speed and reduce rework, what critical information should you obtain and validate first?

• A. A finalized communications matrix and meeting cadence for all stakeholders
• B. A draft integrated schedule built from current team plans, then adjust later
• C. Approved scope boundaries, acceptance criteria, and mandated constraints
• D. Detailed task-level duration estimates from each functional manager

Best answer: C

What this tests: Process

Explanation: Before integrating subsidiary plans, the project manager must confirm the authoritative definition of what must be delivered and the non-negotiable constraints. Validating scope boundaries and regulatory acceptance criteria enables consistent decomposition, sequencing, and estimating across teams. This prevents baselining conflicting assumptions that would drive rework.

Determining critical information requirements means identifying the minimum high-impact inputs needed to integrate planning outputs into a coherent, approvable baseline. In this scenario, teams disagree on what is in scope and what “done” means for regulatory acceptance, while governance requires a fast plan and minimal rework after baselining. The first critical information to validate is the approved scope boundaries (what is included/excluded), the acceptance criteria for key deliverables (especially regulatory), and any imposed constraints such as fixed dates. With those confirmed, you can consistently align the backlog/WBS, define milestones, reconcile dependencies, and then develop realistic schedule and cost baselines. The most detailed estimating and supporting plans should be built on top of this validated foundation.

These define the required deliverables and fixed limits needed to reconcile team plans into one baseline with minimal rework.

Question 36

Topic: People

In a project environment, what best describes mentoring as a leadership approach?

• A. Providing structured instruction with defined learning objectives and assessments
• B. A long-term development relationship where an experienced person guides another
• C. A short-term, performance-focused partnership to improve specific skills
• D. Leading a group to reach consensus while remaining neutral on content

Best answer: B

What this tests: People

Explanation: Mentoring is primarily a long-term developmental relationship that helps another person grow through guidance, advice, and sharing experience. It is typically broader than a single skill gap and is not limited to immediate performance improvement. This is why it often requires deliberately allocating time across the project to support ongoing development.

Mentoring is a people-focused leadership approach where a more experienced individual supports the long-term professional development of another person (a mentee). It is relationship-based and often covers career growth, broader capabilities, and navigating organizational context—not just completing today’s tasks. Because mentoring is ongoing, project leaders usually need to intentionally allocate time for regular check-ins, feedback, and opportunities for learning through exposure.

Coaching is commonly confused with mentoring, but coaching is typically shorter-term and targeted at improving specific performance or skills for current objectives. Training is structured instruction, and facilitation is about enabling a group process rather than developing an individual over time.

Key takeaway: mentoring is long-term, holistic development guided by experience.

Mentoring focuses on long-term growth through guidance and shared experience rather than immediate task performance.

Question 37

Topic: People

A regulatory compliance project must deliver a security design in 6 weeks. The only qualified cybersecurity architect reports to the operations manager and is currently supporting incident response. Constraints: the regulatory date cannot slip, the project budget cannot increase, and you must maintain a collaborative relationship with operations.

Which negotiation strategy best optimizes meeting the project need while satisfying these constraints?

• A. Ask the sponsor to instruct the operations manager to assign the architect full-time immediately
• B. Reduce the security design scope so the team can proceed without the architect
• C. Offer overtime pay to the architect to complete the project work after hours
• D. Use interest-based negotiation with the operations manager to agree on a time-boxed, partial allocation with clear priorities and escalation, and document it as a resource agreement

Best answer: D

What this tests: People

Explanation: The best approach is collaborative, interest-based negotiation focused on both sides’ underlying needs: regulatory delivery for the project and service continuity for operations. A time-boxed allocation with explicit work priorities and an escalation path creates a workable tradeoff without increasing budget. Documenting the outcome as a resource agreement makes expectations and commitments clear and enforceable.

This situation calls for an integrative (win-win) negotiation strategy because you have constraints (no budget increase, no schedule slip) and an ongoing relationship with operations that you must preserve. Start by clarifying interests and constraints with the operations manager (incident coverage, peak periods, response SLAs) and with your project (which security decisions require the architect and when). Then propose a time-boxed, partial allocation that protects operational coverage through explicit priority rules, agreed handoffs, and an escalation path if incidents spike, and document the commitment (capacity, dates, responsibilities) in a resource agreement so it can be planned and tracked.

The key takeaway is to trade on flexibility and clarity (capacity windows and priority rules), not on authority, budget, or compliance scope.

It collaboratively trades capacity and priority rules to secure needed expertise without added cost while protecting operations and preserving the relationship.

Question 38

Topic: Process

A hybrid CRM implementation project is in execution. The lead integration engineer has resigned and will leave in two weeks. The integration design decisions and troubleshooting steps are mostly in her personal notes, and the shared technical documentation is outdated. The next iteration includes a critical integration that only she has completed before.

As the project manager, what is the best next step to confirm the approach for knowledge transfer and maintain project continuity?

• A. Identify critical knowledge and create a time-boxed transfer plan with recipients
• B. Update the lessons learned register and close the engineer’s work package
• C. Escalate to the sponsor to approve an immediate replacement hire
• D. Schedule a one-time knowledge transfer presentation by the departing engineer

Best answer: A

What this tests: Process

Explanation: The immediate need is to prevent a single-point-of-failure by rapidly planning and organizing knowledge transfer. Start by identifying the critical integration knowledge at risk and the specific team members who must receive it, then time-box sessions and documentation updates before the departure date. This confirms a clear, actionable approach and makes continuity measurable.

Knowledge transfer is most effective when it is planned around the specific continuity risk: what knowledge is critical, who needs it, and how you will confirm it was transferred. With a near-term departure and outdated shared documentation, the next step is to quickly assess the at-risk tacit knowledge and agree on a short, structured transfer approach that includes both documentation and hands-on walkthroughs.

• Identify the critical integration decisions, procedures, and troubleshooting scenarios.
• Select primary/backup recipients and assign documentation ownership.
• Schedule time-boxed walkthroughs/pairing and update the shared repository.
• Validate transfer with a dry-run or independent execution by recipients.

Actions like hiring or a one-time presentation may help later, but they don’t first define and verify what continuity knowledge must be transferred.

You should first define what knowledge must be transferred, to whom, and how/when, then execute and verify the transfer before the engineer departs.

Question 39

Topic: People

Two departments on a hybrid project (Operations and IT Security) have reached an agreement on a shared solution approach and responsibilities after a facilitated workshop. Some team members were not present, and the departments have a history of reversing decisions later.

Which TWO actions should the project manager take to best support the outcome of the parties’ agreement? (Select TWO)

• A. Submit a formal change request to the change control board to “lock in” the agreement
• B. Escalate the agreement to the sponsor for approval to prevent either party from changing it later
• C. Update the relevant project artifacts (plans/backlog/RAID) and communicate the agreed responsibilities to impacted stakeholders
• D. Document the decision and responsibilities, and obtain written confirmation from both parties
• E. Pause related work until both departments revise their departmental procedures to reflect the agreement
• F. Ask each department to provide its own separate summary of the agreement for the project files

Correct answers: C, D

What this tests: People

Explanation: To support an agreement’s outcome, the project manager should make the decision explicit, confirmed, and actionable. Capturing the agreement with written confirmation prevents rework caused by differing recollections. Then integrating it into project artifacts and communicating it to affected stakeholders ensures the agreement is executed and reinforced through normal delivery governance.

Supporting the outcome of an agreement means turning a verbal alignment into an unambiguous, durable commitment that the wider team can follow. In this scenario, the risk is not reaching agreement—it is backsliding and inconsistent execution because key people were absent and the groups have a history of reversing decisions.

The project manager should:

• Record the decision, ownership, and any constraints, and get written confirmation from the parties.
• Operationalize the agreement by updating the relevant delivery artifacts (plan components, backlog items/acceptance criteria, RACI/ownership, RAID entries) and communicating the decision to impacted stakeholders.

Escalation or formal change control is only needed when governance requires it or when scope/baselines must change; it is not the primary way to make an inter-party working agreement stick.

Written confirmation creates a clear, shared record that reduces later reinterpretation or reversal.

Embedding the agreement into the work system and communications helps ensure it is executed and sustained.

Question 40

Topic: Process

You are managing a hybrid CRM rollout. During the first increment review, sales leadership is upset that the team delivered reporting enhancements while a regulatory data-retention feature is still not started. The team says they are building from a 200-item requirements list that was “approved” in a requirements workshop. Meeting notes show many items were captured, but no ranking criteria, decision owner, or trade-off process was agreed; several departments stated their requests were “top priority.”

Which is the most likely underlying cause of the problem?

• A. The project is experiencing scope creep due to uncontrolled changes
• B. Requirements were not prioritized using agreed criteria and decision authority
• C. Stakeholders are resisting the change because they were not trained
• D. The team lacks the technical skills to deliver regulatory features

Best answer: B

What this tests: Process

Explanation: The symptoms point to misaligned delivery priorities, not a delivery capability issue. Although requirements were gathered, there was no agreed method to determine relative priority or a clear decision maker to resolve conflicts. Establishing prioritization criteria and ownership enables selecting the right work first, especially when regulatory requirements exist.

The core issue is failure to determine and prioritize requirements in a way that guides day-to-day work selection. Capturing a long “approved” list is not enough when multiple stakeholders claim top priority; the team needs clear, shared prioritization criteria (e.g., regulatory compliance, business value, risk, dependencies) and a defined decision authority to make trade-offs. In a hybrid setting, this typically results in an ordered backlog (or phased requirements set) that explicitly elevates mandatory items like regulatory needs.

A practical fix is to:

• Confirm who has final prioritization authority
• Agree on prioritization criteria and how conflicts are resolved
• Reorder requirements/backlog and communicate what is in/out for the increment

The key takeaway is that mis-sequenced delivery is usually caused by missing prioritization governance, not by the existence of many requirements.

Without a defined prioritization approach and decision owner, the team cannot reliably focus on the highest-value and mandatory requirements.

Question 41

Topic: Business Environment

A project manager is leading a hybrid rollout of a new enterprise timekeeping system that will change how supervisors approve labor hours. During pilot communications, several frontline supervisors openly discourage their teams from using the new process and claim it will “slow operations.” The sponsor asks the project manager to “get adoption back on track” before the next site goes live.

What should the project manager do next?

• A. Escalate the supervisors’ behavior to the sponsor for enforcement
• B. Start mandatory training for all supervisors immediately
• C. Perform a change readiness assessment and map resistance drivers
• D. Freeze the rollout until all supervisors sign acceptance statements

Best answer: C

What this tests: Business Environment

Explanation: The immediate need is to understand the level of readiness and the specific reasons supervisors are resisting the change. A structured readiness and resistance assessment provides the data to tailor interventions such as targeted messaging, process adjustments, local champions, and role-based training. Acting before diagnosing the resistance is likely to waste effort and increase pushback.

Supporting organizational change requires first diagnosing adoption risk by assessing readiness and resistance, then planning interventions that address the specific drivers. In this scenario, supervisors are actively influencing end users, so the project manager should quickly determine whether the resistance is caused by misunderstanding, workflow impacts, lack of involvement, capacity constraints, or misaligned incentives.

A practical next sequence is:

• Identify affected stakeholder groups and influencers
• Assess readiness and capture resistance themes (interviews/surveys/observations)
• Update the change management and stakeholder engagement approaches with targeted actions
• Validate interventions with site leadership before the next go-live

Escalation or mandates may be needed later, but only after the causes are understood and less coercive interventions have been planned and attempted.

Assessing readiness and the causes of resistance enables targeted engagement, communications, and training interventions before expanding the rollout.

Question 42

Topic: People

Which PMP artifact is used to document stakeholders’ current engagement level versus the desired engagement level to help plan actions that build support and trust?

• A. Stakeholder register
• B. Communications management plan
• C. Power/interest grid
• D. Stakeholder engagement assessment matrix

Best answer: D

What this tests: People

Explanation: The stakeholder engagement assessment matrix shows where each stakeholder is now (for example, resistant, neutral, supportive) and where you need them to be. By highlighting gaps, it guides tailored engagement actions that strengthen relationships, build trust, and increase stakeholder support for project objectives.

The stakeholder engagement assessment matrix is a planning aid used during stakeholder engagement planning and execution to understand and influence stakeholder involvement. It captures each stakeholder’s current engagement level and the desired engagement level, making it easier to identify engagement gaps and choose specific strategies (targeted conversations, involvement in decisions, addressing concerns) that increase buy-in and trust. It is especially useful when you need to shift key stakeholders from resistant or neutral to supportive or leading to accomplish project objectives. A classification model alone is not enough; the matrix explicitly connects the “as-is” and “to-be” engagement states so you can plan concrete actions.

It compares current and desired engagement levels and helps target actions to move stakeholders toward supportive involvement.

Question 43

Topic: People

You are managing a hybrid project that must pass a mandatory security compliance review in 6 weeks. A security architect from the operations department is required for design sign-off and test planning.

Constraints:

• Project budget is fixed; no additional funds are available.
• Organizational policy prohibits overtime.
• The operations manager says the architect can only support 20% due to production incidents.

Objective: Negotiate an agreement that maximizes the likelihood of passing the compliance review on time while maintaining a workable relationship with operations.

What should the project manager do?

• A. Proceed without the architect and defer security activities
• B. Co-create a time-phased allocation with operations and document it
• C. Escalate to the sponsor to force full-time assignment
• D. Hire an external security consultant to cover the gap

Best answer: B

What this tests: People

Explanation: A negotiated project agreement should optimize the stated objective while respecting constraints. A time-phased resource agreement (for example, focused early design sign-off plus scheduled support for test planning) can meet the compliance need without extra budget or overtime. Documenting the commitment clarifies expectations and supports ongoing collaboration with operations.

The core priority is passing the mandatory compliance review on time, and the limiting constraint is scarce specialist availability with no budget or overtime levers. The best negotiation outcome is a realistic, mutually beneficial agreement that protects the critical compliance work by tailoring when and how the architect supports the project, rather than trying to “win” the entire resource.

A strong agreement typically includes:

• Specific time windows (time-phased allocation) for design sign-off and test planning
• Any sequencing adjustments the team will make to align work to those windows
• Clear responsibilities and confirmation in writing (resource/working agreement)

This approach maximizes the likelihood of on-time compliance while preserving the relationship needed for ongoing operational support.

This negotiates a feasible, documented resource commitment that fits budget and no-overtime constraints while protecting the compliance timeline.

Question 44

Topic: People

You are preparing to negotiate a change order with a vendor for a hybrid project. Review the change request summary.

CR-12 Summary: Add audit logging to meet new regulation
Vendor proposal: +\$180,000 and +4 weeks
Business constraint: Compliance deadline fixed; schedule slip limit = 2 weeks
Budget constraint: Max additional funding available = \$140,000
PM approval authority: Up to \$50,000; above requires CCB decision
Alternative: Internal team can deliver in +2 weeks for +\$155,000

Based on the exhibit, what are the bounds you should use for the negotiation?

• A. Accept the vendor proposal now and submit it to the CCB afterward
• B. Negotiate any outcome as long as the compliance deadline is met
• C. Negotiate to no more than $140,000 and 2 weeks, and make any offer above $50,000 contingent on CCB approval
• D. Negotiate up to $155,000 because the internal option sets the reservation point

Best answer: C

What this tests: People

Explanation: Negotiation bounds come from the project’s constraints, decision authority, and credible alternatives. The exhibit sets a hard schedule-slip limit (2 weeks), a maximum available budget ($140,000), and a PM approval cap ($50,000). Therefore, the PM can negotiate within those limits but cannot commit to amounts above their authority without making the agreement contingent on the CCB’s decision.

The bounds of a project negotiation should be anchored in documented constraints and governance: what outcomes are acceptable (cost and schedule limits) and who has authority to commit the organization. Here, the compliance deadline creates a maximum allowable schedule slip of 2 weeks and funding is capped at $140,000, which together define the acceptable deal space. Separately, the PM’s approval authority is only up to $50,000, so any proposed settlement above that must be treated as a recommendation or a conditional offer pending CCB approval. The internal delivery alternative is not a strong fallback because it exceeds the available funding, so it does not expand the negotiable limits beyond the stated budget cap.

The exhibit defines cost/schedule limits and the PM’s authority, so commitments beyond $50,000 must be escalated while staying within $140,000 and 2 weeks.

Question 45

Topic: Process

You are planning a predictive project to upgrade a manufacturing line. Several key activities require the same specialized test lab, and the lab provides fixed booking windows over the next two months. Functional managers can also provide technicians only on specific weeks due to operational peaks.

Which tool/artifact should the project manager use to most effectively plan and manage these resource availability constraints in the schedule?

• A. Update the stakeholder engagement plan for the functional managers
• B. Create a resource calendar for technicians and the test lab
• C. Develop a RACI matrix for the project work
• D. Build a resource histogram showing weekly staffing demand

Best answer: B

What this tests: Process

Explanation: Because the deciding factor is fixed, time-bound availability of critical resources (lab windows and technician weeks), the best choice is the artifact that captures and communicates when resources can be used. A resource calendar is specifically used to record availability constraints so activities can be scheduled realistically and commitments can be baselined.

When the main challenge is that people or equipment are only available at certain times, the project manager should use a resource calendar. It records each resource’s working periods, blackout dates, and booking windows, and it becomes a direct input to sequencing and scheduling so planned dates reflect real constraints.

A practical use is:

• Capture availability by role/resource (including shared facilities)
• Apply calendars to schedule activities that require those resources
• Use the resulting dates to confirm commitments and set a feasible baseline

Other artifacts can help clarify responsibilities or visualize demand, but they do not, by themselves, constrain the schedule to specific availability windows.

A resource calendar documents when specific resources are available so schedule activities can be planned within those time windows.

Question 46

Topic: Process

A hybrid project is delivering increments of a customer-facing mobile app that must meet internal security standards. The project manager wants to continually survey deliverable quality so issues are detected early and trends are visible.

Which action should the project manager NOT take?

• A. Make quality metrics visible and discuss them in regular team feedback cycles
• B. Run in-process reviews against agreed acceptance criteria each iteration
• C. Defer most quality checks until final user acceptance to avoid slowing delivery
• D. Use defect and test results trends to spot emerging quality issues

Best answer: C

What this tests: Process

Explanation: Continually surveying quality means performing ongoing quality control and analyzing results throughout delivery, not just at the end. Frequent checks against clear criteria and trend analysis help detect defects early and enable timely corrective actions before rework grows.

Continual deliverable quality surveillance is achieved by integrating quality control into day-to-day execution: inspecting work products as they are produced, measuring results, and analyzing trends so the team can act early. In hybrid/agile delivery, this typically includes iteration-level checks (reviews, testing, acceptance criteria/definition of done) and transparent metrics (defect patterns, test pass rates, escaped defects) that are discussed regularly to drive improvements. Deferring quality checks to final acceptance is an anti-pattern because it delays feedback, hides quality trends, increases rework cost, and risks late discovery of nonconformance—especially problematic when standards like security requirements must be met throughout delivery. The key takeaway is to “build in” frequent inspection and measurement, not “inspect in” quality at the end.

Waiting until the end reduces early detection and prevents timely corrective action, undermining continual quality surveillance.

Question 47

Topic: Process

A project uses a predictive approach. At the end of each phase, the project manager holds a review with the sponsor and end users to compare completed deliverables to the documented acceptance criteria, capture any requested corrections as defects, and obtain formal sign-off before moving to the next phase.

Which PMI concept does this practice best represent?

• A. Manage Quality
• B. Perform Integrated Change Control
• C. Control Scope
• D. Validate Scope

Best answer: D

What this tests: Process

Explanation: The described phase-end review is focused on verifying completed deliverables against acceptance criteria and obtaining formal stakeholder sign-off. That is the core purpose of scope validation—formal acceptance of deliverables—so the work can be accepted and the project can proceed with clarity on what is complete.

Validate Scope is about customer/sponsor acceptance of completed deliverables by reviewing them against agreed acceptance criteria. In the scenario, the project manager brings the sponsor and end users together at phase end, compares deliverables to acceptance criteria, records any needed rework as defects, and obtains formal sign-off—this directly aligns to validating scope.

Control Scope is different: it monitors scope status and manages changes to the scope baseline over time. Integrated change control addresses evaluating and approving changes across baselines, and quality management focuses on processes and quality assurance/control, not acceptance of scope.

It is the process of confirming deliverables meet acceptance criteria and obtaining formal customer/sponsor acceptance.

Question 48

Topic: Process

You are managing a hybrid project to implement a customer portal. Stakeholders include an external development vendor and internal legal and security teams. The team has been sharing requirements and design files by email because the collaboration site access is “taking too long.”

Constraints:

• Customer data elements are included in the artifacts (privacy sensitive).
• Only approved tools may be used for external sharing.
• Organizational policy requires a 7-year retention period for requirements and approvals.

What is the BEST next action?

• A. Set up an approved repository with role-based access and retention controls
• B. Move artifacts to a team member’s personal cloud drive for easier sharing
• C. Grant the vendor full access to the internal collaboration site to speed work
• D. Email the latest files as password-protected attachments to all stakeholders

Best answer: A

What this tests: Process

Explanation: Project artifacts must be accessible to stakeholders while still meeting security, privacy, and retention requirements. The best next action is to use an approved repository and configure access controls so each stakeholder can access only what they need. Applying retention settings ensures requirements and approvals are preserved for the mandated period.

Managing project artifacts includes making them easy to find and use while protecting sensitive information and meeting organizational policies. In this scenario, the artifacts contain privacy-sensitive data, external sharing must use approved tools, and requirements/approvals must be retained for 7 years. The appropriate action is to implement (or expedite) an approved central repository and configure governance controls so access is granted based on need-to-know and retention is automatically enforced.

Practical steps include:

• Enable role-based permissions for internal teams and the vendor
• Apply data classification/handling rules to sensitive artifacts
• Configure retention labels/schedules for requirements and approvals

Workarounds like email or personal drives may improve speed but typically violate tool, privacy, and retention constraints.

This provides timely stakeholder access while enforcing approved-tool use, privacy protections, and required retention.

Question 49

Topic: People

A project manager joins a hybrid product implementation where decisions are frequently delayed because no one is sure who can approve scope and design choices. The project manager facilitates a working session with the sponsor, product owner, and team to define which decisions the team can make independently, which require product owner approval, and which must be escalated to the sponsor. The agreements are documented and shared.

Which governance concept is being applied?

• A. Decision-making authority matrix (delegation framework)
• B. Manage by exception
• C. Change control board (CCB) governance
• D. Servant leadership

Best answer: A

What this tests: People

Explanation: This practice establishes clear decision rights and approval boundaries so the team knows what it can decide versus what must be approved or escalated. That is a delegation and governance mechanism typically captured in a decision-making authority matrix (often aligned with RACI/DACI) and reinforced through team working agreements.

The core concept is deliberately bestowing decision-making authority to the appropriate people to reduce delays while maintaining governance. By defining what the team can decide, what requires product owner approval, and what must be escalated to the sponsor, the project manager is creating a decision-rights framework.

This is commonly implemented as a decision-making authority matrix (sometimes embedded in a RACI/DACI-style decision table) and reinforced in a team charter or working agreements so everyone understands decision thresholds, approvers, and escalation paths. The key is not just documenting roles, but explicitly clarifying who makes which types of decisions.

Other governance mechanisms may still exist, but they do not, by themselves, define day-to-day decision rights at the team level.

It explicitly defines and documents who has decision rights at different levels to enable timely decisions.

Question 50

Topic: Process

A hybrid project is procuring a vendor to build a new customer analytics component. The sponsor expects requirements to evolve after an initial pilot and wants to collaborate with the vendor through iterative demonstrations. Procurement awarded a firm-fixed-price contract with detailed upfront specifications and strict acceptance criteria. Within the first month, the vendor is submitting frequent change orders and threatening to stop work unless the price is renegotiated.

What is the most likely underlying cause of this situation?

• A. The vendor is underperforming due to inadequate technical capability
• B. The contract type is mismatched to high uncertainty, pushing scope risk onto the seller
• C. The project’s change control process is causing the schedule delays
• D. Stakeholders are not engaged enough to clarify requirements during iterations

Best answer: B

What this tests: Process

Explanation: The primary issue is misalignment between the contract type and the project’s uncertainty. When requirements are expected to evolve, a firm-fixed-price contract creates pressure to lock scope early and makes normal iteration appear as “change,” triggering claims and renegotiation. A more flexible procurement approach better allocates risk and supports iterative discovery.

Contract type should be selected based on how well scope can be defined and who should reasonably carry the risk. A firm-fixed-price contract is best when requirements and acceptance criteria are stable and can be specified upfront; otherwise, the seller prices in uncertainty or relies on change orders to protect margin. Here, the sponsor explicitly expects evolving requirements and iterative collaboration, so the procurement approach should allow controlled flexibility (for example, time and materials with a not-to-exceed cap, or a cost-reimbursable/incentive structure with clear governance and review points). The key takeaway is that frequent change orders are a predictable outcome when a fixed-price contract is used in a high-uncertainty environment.

A firm-fixed-price contract assumes stable requirements, so using it with evolving scope predictably drives change orders and disputes.

Questions 51-75

Question 51

Topic: Process

A predictive project has a fixed go-live date. Status reports show “78% complete,” but a key integration activity cannot start until two external interfaces are delivered. The team reports those deliverables are slipping, and the sponsor asks for objective evidence that the schedule is still achievable.

Which evidence best validates whether the project is truly on track, considering dependencies and critical path/near-critical path risk?

• A. Overall percent complete across all work packages
• B. A list of completed deliverables accepted by the sponsor to date
• C. The number of activities started versus planned this month
• D. An updated, logic-linked schedule with recalculated critical path, total float, and forecast go-live date

Best answer: D

What this tests: Process

Explanation: To validate schedule achievability when dependency dates are moving, the project manager needs evidence that reflects schedule logic and the impact on the critical and near-critical paths. A recalculated critical path and total float after updating actuals shows whether the slipping predecessors are consuming float and pushing the forecast go-live date. This directly addresses schedule risk rather than reporting generalized progress.

When schedule risk is driven by dependencies, “progress” must be validated using evidence that models sequencing and recalculates the forecast finish. Updating the project schedule with actuals for completed work and new dates for key predecessors allows the scheduling tool to re-run critical path analysis and show which path now controls the finish date and how much total float remains on near-critical paths.

Practical validation is to confirm the schedule:

• Maintains correct logic ties for the external deliverables and successors
• Recalculates the critical path and identifies near-critical paths
• Shows total float consumption and the resulting forecast go-live date

Percent complete and counts of started tasks can look healthy while critical predecessors slip, so they do not validate achievability under dependency-driven risk.

Re-updating actuals and re-running critical path/float analysis is the most direct evidence of dependency-driven schedule risk and the likely finish date.

Question 52

Topic: People

A hybrid product team has missed two release dates because integrations are taking longer than planned and defects are found late. The project manager reorganizes work so the team’s strongest integration engineer leads integration design early, while testers with automation strengths pair with developers to build automated checks during each iteration. Two iterations later, which evidence best validates that organizing around team strengths is improving delivery readiness?

• A. Trend of reduced integration rework and fewer escaped defects
• B. More backlog items started per iteration
• C. Updated team skills matrix and role descriptions
• D. Higher individual utilization on timesheets

Best answer: A

What this tests: People

Explanation: To validate that organizing around team strengths is working, look for outcome evidence tied to readiness and quality, not just reassignment activity. A downward trend in integration rework and escaped defects shows the team is building the right capabilities into the product earlier and stabilizing the integrated solution. That directly supports release readiness in a hybrid environment.

Organizing around team strengths should show up in measurable delivery outcomes, especially in the area that was constraining the project. In this scenario, the bottleneck is integration and late defect discovery, so the strongest validation is a sustained improvement in integration quality and earlier defect prevention/detection.

Good validation evidence is typically:

• Outcome-based (quality, rework, acceptance)
• Directly linked to the problem area (integration readiness)
• Trended over time (not a one-time snapshot)

If strengths are being applied effectively, integration work should require less rework and fewer defects should escape to later phases or production-like testing, indicating the product is becoming more release-ready each iteration.

A sustained drop in integration rework and escaped defects indicates the right expertise is being applied where it matters for release readiness.

Question 53

Topic: Process

Midway through a hybrid project, multiple impediments are being raised in meetings and chat, but the sponsor reports “nothing is getting resolved.” The issue log exists but many entries have no owner or due date, and two open items are blocking an integration test planned for next week. Several teams are remote and in different time zones.

What is the project manager’s BEST next action?

• A. Move unresolved items to the risk register and perform qualitative risk analysis
• B. Add the blocked integration-test tasks to the schedule baseline and replan the next milestone
• C. Escalate all open issues to the sponsor so governance can assign owners and due dates
• D. Update the issue log with priority, owner, due date, and resolution criteria, then confirm commitment with each owner

Best answer: D

What this tests: Process

Explanation: The immediate problem is not lack of visibility but lack of actionable issue records. The best next action is to make the issue log complete and usable by prioritizing issues and assigning clear owners, due dates, and resolution criteria. This creates accountability and enables rapid unblocking of near-term work across time zones.

Managing project issues requires an issue log that drives action: each issue should be captured, prioritized, assigned to a specific owner, time-bound with a due date, and defined with clear resolution/acceptance criteria. In the scenario, unresolved blockers and missing accountability are causing delays and eroding sponsor confidence, so the project manager should first normalize and strengthen the issue log rather than change baselines or reclassify items.

A practical sequence is:

• Validate the top blocking issues and set priority based on impact/urgency.
• Assign a single accountable owner per issue.
• Set due dates aligned to the integration test and confirm owner commitment.
• Define resolution criteria so “done” is unambiguous and can be verified.

Escalation can follow if owners cannot resolve by the due date, but the best next step is to make the log actionable and prioritized.

This immediately restores a usable issue log by making issues actionable and prioritized, enabling timely resolution of blockers.

Question 54

Topic: Process

A hybrid project is deploying a new time-tracking system across three regions. Frontline supervisors are the most impacted stakeholder group and have raised concerns about overtime reporting and payroll cutover. The project manager has tailored communications to include biweekly supervisor forums, short how-to videos, and a Q&A channel.

Which artifact or evidence best validates that this communications approach is improving supervisor engagement and readiness for go-live?

• A. Calendar invites and attendance records for the forums
• B. Distribution list showing all supervisors received the videos
• C. Trend of supervisor pulse-survey results with participation rate
• D. Count of messages posted in the Q&A channel

Best answer: C

What this tests: Process

Explanation: Validating a tailored communications approach requires evidence of stakeholder understanding, buy-in, and readiness—not just evidence that messages were sent. A pulse survey trend with a clear participation rate provides direct feedback from the impacted group and shows whether engagement and readiness are improving over time. This aligns communications artifacts to the stakeholder outcome being sought: adoption readiness for go-live.

The core concept is choosing communications evidence that validates stakeholder outcomes (engagement and readiness) rather than communications activity. In this scenario, the project needs to know whether frontline supervisors understand the change, feel their concerns are addressed, and are prepared for payroll cutover.

A good validation artifact should:

• Capture stakeholder feedback on understanding/readiness
• Show direction over time (trend)
• Indicate how representative the input is (participation rate)

A pulse survey trend (with response rate) is actionable outcome-based evidence; it helps you adapt channel mix, cadence, and content to close readiness gaps before go-live.

It directly measures whether supervisors are engaged and feel ready, using feedback and response levels rather than just activity counts.

Question 55

Topic: Process

A project is being delivered using a hybrid approach: facility build-out work is managed predictively with a baselined schedule, while the customer portal is developed using Scrum in 2-week iterations. The sponsor wants a single “progress view” in the monthly status report.

Which TWO actions should the project manager take to measure ongoing progress in a way that matches each methodology? (Select TWO)

• A. Use SPI/EV vs. PV from EVM for the predictive work packages
• B. Use iteration burnup/burndown and velocity trends for the Scrum product backlog
• C. Measure progress by the number of approved change requests per month
• D. Use a single percent-complete calculation for the whole project based on subjective estimates
• E. Defer progress measurement until phase-gate acceptance of each major deliverable
• F. Report progress primarily as hours spent versus hours planned across all work

Correct answers: A, B

What this tests: Process

Explanation: Progress measures should align to how the work is planned and controlled. Predictive work uses a baselined plan, so comparing earned value to planned value shows schedule performance objectively. Scrum work plans through iterations and a backlog, so tracking delivered backlog with burnup/burndown and velocity trends provides an accurate view of progress and forecast.

To measure ongoing progress based on methodology, use metrics that reflect how work is decomposed and controlled. For predictive components with a schedule baseline, performance is measured against that baseline; EVM provides objective indicators such as schedule performance index (SPI) by comparing earned value (EV) to planned value (PV). For Scrum components, progress is measured by value delivered from the backlog over time; burnup/burndown and velocity trends support forecasting completion without forcing “percent complete” on evolving backlog items.

The key is to combine reporting at an appropriate level while keeping the underlying measures method-consistent rather than using a single metric that distorts one side of the hybrid approach.

EVM compares earned value to the baselined plan to show schedule performance for predictive scope.

Agile progress is best tracked by delivered backlog over time (flow/velocity), not by baseline percent complete.

Question 56

Topic: Process

You are managing a hybrid product rollout. Over the last three weekly status reports, the following data is consistent: an approved change request (CR-07) added mandatory compliance features and the requirements documentation reflects it, but the integrated master schedule still shows the original milestone dates and the procurement team is still managing the vendor against the original statement of work. The delivery team reports repeated rework due to “different versions of the plan.”

Based on this data, what is the most likely underlying cause?

• A. Approved changes were not integrated across baselines and plans
• B. The team lacks skills to implement the compliance features
• C. Stakeholders are requesting too many changes too frequently
• D. The vendor is underperforming and causing downstream delays

Best answer: A

What this tests: Process

Explanation: The evidence points to a breakdown in integrating planning outputs after an approved change. Requirements were updated, but the schedule and procurement artifacts were not, causing multiple groups to execute against different baselines. This misalignment predictably drives rework and missed iteration goals.

Analyzing the collected status data shows a specific pattern: one planning artifact (requirements) reflects the approved change, while other planning artifacts (integrated master schedule and procurement’s managed scope) remain on the old baseline. That combination indicates the change’s impacts were not integrated across the project management plan and subsidiary plans.

A practical diagnosis is:

• Confirm the approved change exists and where it was recorded.
• Compare scope/requirements, schedule, and procurement baselines for alignment.
• Identify where integrated change control and plan updates broke down.

When approved changes are not propagated to all affected plans and baselines, different teams execute conflicting “versions of the plan,” creating rework and predictable schedule slippage.

The data shows CR-07 was accepted in requirements but not reflected in schedule and procurement, indicating missing plan/baseline integration.

Question 57

Topic: People

You are taking over as project manager for a hybrid project delivering a customer mobile app MVP. Constraints:

• MVP launch date is fixed in 12 weeks.
• Two key developers will roll off in 3 weeks due to another approved project.
• Additional headcount requires a justified request to functional managers; procurement onboarding for contractors typically takes 6 weeks.
• The backlog is high level and the schedule has only major milestones.

What is the BEST next action to deduce the project’s resource requirements?

• A. Authorize overtime for the remaining developers to protect the fixed MVP launch date
• B. Submit an urgent request to HR to backfill the two departing developers immediately
• C. Facilitate near-term backlog refinement and break down work to estimate needed skills, quantities, and timing, then compare to current capacity
• D. Rebaseline the schedule to reflect the expected productivity loss after the developers roll off

Best answer: C

What this tests: People

Explanation: You cannot justify or time resource acquisition until you translate the high-level backlog and milestones into near-term deliverables and estimates. Refining and decomposing the upcoming work, then mapping it to skills and capacity, produces a clear resource requirement (who/what skills, how many, and when). That evidence supports fast decisions within the hiring and contractor lead-time constraints.

Deducing resource requirements means converting scope and near-term work into a time-phased view of the skills and capacity needed. In this scenario, the backlog and schedule are too coarse to support a justified request, and you also have lead-time constraints (developers rolling off soon; contractors take weeks to onboard). The best next step is to collaborate with the product owner and team to refine and decompose the upcoming work and estimate effort, then map those estimates to available capacity to identify gaps.

• Refine the backlog for the next iterations/release and clarify acceptance criteria.
• Decompose into deliverables/activities and estimate effort.
• Build a simple skills-by-time requirement and compare to team capacity.
• Use the resulting gaps to drive an evidence-based resource request or alternative plan.

Actions like hiring, rebaselining, or overtime come after requirements are understood and options can be evaluated against timing and constraints.

Breaking down and estimating upcoming work allows you to quantify skill sets, numbers, and when they are needed before requesting or sourcing resources.

Question 58

Topic: Process

Midway through a predictive project, a regulatory review package and a customer demo both require the same compliance specialist next week. The specialist is already assigned 100% to the review package on the critical path. The project manager approves adding the demo preparation work to the specialist’s assignments without reallocating, leveling, or changing scope.

What is the most likely near-term impact?

• A. Project costs increase next quarter due to additional procurement of external compliance services
• B. Both activities slip as the specialist multitasks, delaying a near-term milestone
• C. Defect rates rise significantly in later releases due to reduced quality assurance coverage
• D. The project finishes within the original schedule because overall team utilization increases

Best answer: B

What this tests: Process

Explanation: Approving additional work for a fully allocated critical-path specialist creates an immediate capacity constraint. In the near term, the specialist will be forced to context-switch or queue work, which typically slows completion of both commitments. The most direct consequence is a slip of upcoming deliverables or milestones tied to that resource.

Resource capacity optimization (allocation, leveling, or throughput management) prevents over-allocation from turning into schedule risk. In the scenario, the compliance specialist is fully booked on critical-path work, so adding another time-bound commitment does not create more capacity—it creates contention.

Near-term, the likely effect is:

• Increased multitasking and wait time for one or both activities
• Reduced throughput for the specialist
• A delay to a scheduled deliverable or milestone unless work is reassigned, leveled, or de-scoped

Cost increases or downstream quality impacts can occur, but they are secondary and not the most immediate, direct impact of ignoring a known resource constraint.

Over-allocation typically reduces effective productivity, causing immediate schedule slippage on time-sensitive work.

Question 59

Topic: Process

A project’s cost baseline was approved last month, and any baseline changes require change control board (CCB) approval. In the latest performance report, EV is $420,000, AC is $500,000, and PV is $450,000. The sponsor asks the project manager to explain the cost variance and provide an updated forecast.

Which action should the project manager NOT take?

• A. Analyze the drivers of the variance and propose corrective or preventive actions
• B. Communicate the variance and forecast impacts using the agreed reporting approach
• C. Calculate an updated EAC using current performance data and assumptions
• D. Rebaseline the cost plan to match actuals so the variance is removed

Best answer: D

What this tests: Process

Explanation: Forecasts (such as EAC) are meant to be updated using current performance information, while the cost baseline remains the approved reference for measuring variance. When performance deviates, the project manager should analyze causes, forecast remaining work, and communicate impacts. The baseline should only be changed through formal integrated change control, not to “make variance go away.”

The cost baseline is the approved time-phased budget used to measure and report cost performance; variances are meaningful only when compared to an unchanged baseline. When AC and EV indicate a cost overrun, the project manager should investigate root causes, evaluate corrective/preventive actions, and update forecasts (for example, EAC/ETC) based on current performance and realistic assumptions.

A baseline change is appropriate only when an approved scope/schedule/cost change is authorized through the CCB; it is not a tool for masking unfavorable performance. Keeping the baseline stable while updating forecasts enables transparent governance decisions and more reliable funding and benefit projections.

Changing the approved cost baseline to eliminate variance without CCB approval bypasses change control and undermines performance measurement.

Question 60

Topic: People

You are managing a hybrid project with a fixed regulatory go-live date. Two functional leads (from different departments) are in an ongoing conflict about solution ownership and are rejecting each other’s work, causing rework and missed iteration goals.

You facilitated a problem-solving session and revisited the team working agreement, but they still cannot agree and one lead has stated they will pull their resources from the project. The organization has a documented escalation path: team –→ project manager → functional managers → sponsor/steering committee.

Which TWO actions should you take next? (Select TWO)

• A. Brief the sponsor/steering committee on impacts and request a decision
• B. Ask HR to formally investigate and mediate the disagreement
• C. Reassign one lead to different work without functional approval
• D. Postpone the decision and schedule another joint workshop next month
• E. Send a broadcast email directing both leads to comply immediately
• F. Escalate the conflict to both functional managers per the escalation path

Correct answers: A, F

What this tests: People

Explanation: You should escalate when the conflict cannot be resolved at the lowest level and is now threatening resourcing and delivery. Using the defined escalation path enables the right authority to make decisions and enforce priorities. Here, functional managers can address resource/role authority, and governance can make cross-department priority decisions to protect the regulatory date.

Escalation is appropriate when (1) attempts to resolve the conflict within the team have failed, (2) the conflict exceeds the project manager’s authority (for example, functional staffing/discipline decisions), or (3) it creates an imminent threat to project objectives that requires governance decisions. In this scenario, the inability to reach agreement persists despite facilitation, and a lead is threatening to withdraw resources, which is a functional authority and governance issue.

Appropriate next steps are to follow the documented escalation path:

• Escalate to functional managers to address role expectations, resource commitments, and authority boundaries.
• Escalate to the sponsor/steering committee to set priorities and make/endorse a binding decision given the fixed regulatory deadline.

Avoid actions that bypass authority, inflame the conflict, or delay decisions when schedule risk is already material.

The conflict now involves resource authority and cannot be resolved at the team level, so it should move to the functional managers.

With a fixed regulatory date and cross-department impact, sponsor-level governance is needed to set priorities and enforce a decision.

Question 61

Topic: Process

You are managing an agile software project using 2-week sprints. A key external API needed for several high-priority stories will be delivered later than planned.

Exhibit: Issue log (excerpt)

Method: Agile (Scrum), Sprint length: 2 weeks
Release target: June 30 (fixed market commitment)
ISS-17: External API sandbox access delayed 3 weeks
Impacted work: 8 stories planned for Sprints 6–7
Constraint: Team cannot start integration without API

What should the project manager do next to modify the schedule appropriately for this methodology?

• A. Update the WBS and network diagram to reflect the new dependency, then reissue the baseline schedule
• B. Submit a change request to rebaseline the schedule before replanning
• C. Facilitate release replanning with the product owner to re-sequence and re-estimate work, then update and communicate the release plan
• D. Direct the team to crash the schedule by adding overtime until the original plan is met

Best answer: C

What this tests: Process

Explanation: Because the project is using Scrum and the release date is fixed, the appropriate way to modify the schedule is to replan the upcoming iterations and release forecast with the product owner and team. The delay prevents integration work from starting, so the plan must be updated by re-sequencing and re-estimating work and then communicating the revised release plan.

In agile methods, the detailed near-term schedule is managed through iteration planning and release forecasting, not by reissuing a predictive baseline. The exhibit shows a 3-week external dependency delay that blocks integration stories planned for upcoming sprints, while the release target date is a fixed commitment. The project manager should enable a replanning conversation with the product owner and team to adjust the release plan (for example, move blocked stories later, pull forward independent work, and re-forecast based on updated information), then communicate impacts and options to stakeholders. This aligns schedule modification to the agile approach by updating plans and expectations through iterative replanning rather than formal baseline change mechanics.

In agile, schedule adjustments are made by replanning iterations/releases with the product owner and team using updated forecasts, then communicating the new plan.

Question 62

Topic: Process

Which term describes a schedule method that accounts for resource constraints and protects the finish date by placing buffers on the longest resource-constrained chain of activities?

• A. Free float
• B. Resource leveling
• C. Critical path method
• D. Critical chain method

Best answer: D

What this tests: Process

Explanation: Critical chain method (CCM) extends network schedule analysis by explicitly considering resource constraints and then adding buffers to reduce schedule risk. Instead of managing only the longest logical path, it manages the longest resource-constrained chain and protects delivery with project and feeding buffers.

Critical chain method is used to manage schedule risk when resource availability affects the true sequence and duration of work. It identifies the longest chain of dependent activities considering both logic and resource constraints (the critical chain), then adds buffers to protect key dates:

• A project buffer at the end of the critical chain protects the final completion date.
• Feeding buffers protect the critical chain from delays on non-critical-chain paths.

This differs from critical path method, which identifies the longest path based on logical dependencies and uses float analysis but does not inherently add buffer management focused on resource constraints. Key takeaway: CCM = resource-constrained chain plus buffer-based protection.

It focuses on the longest resource-constrained chain and uses project/feeding buffers to manage schedule risk.

Question 63

Topic: Process

A project manager is leading a hybrid project to deliver an update to a medical device companion app. The organization mandates strict requirements traceability and formal validation evidence. The project manager applies the company’s “standard Scrum” playbook with minimal documentation. After two iterations, the compliance team rejects the increment, rework increases, and stakeholders complain they cannot see when regulatory deliverables will be ready. The delivery team is new to agile.

What is the most likely underlying cause of these problems?

• A. Poor team performance causing low-quality increments
• B. Stakeholders are changing requirements too frequently
• C. Failure to tailor practices to regulation and team maturity
• D. Too many defects discovered late in testing

Best answer: C

What this tests: Process

Explanation: The primary issue is improper tailoring of methods and practices to the project context. The regulatory environment requires traceability and validation artifacts, and the team’s low agile maturity calls for additional guidance and enabling documentation. Using a one-size-fits-all Scrum playbook predictably led to compliance rejection, rework, and misaligned stakeholder expectations.

Tailoring means selecting and adapting practices to fit constraints such as regulation, uncertainty, stakeholder needs, and team capability. Here, the strongest clues are mandated traceability/validation evidence, stakeholder need for visibility into regulatory deliverables, and a team new to agile. Applying “standard Scrum” with minimal documentation is misaligned with compliance requirements and increases the risk of increments being rejected, driving rework and eroding trust.

Appropriate tailoring in this context typically includes:

• Defining required regulatory deliverables and acceptance criteria up front
• Building traceability into the workflow (e.g., linking backlog items to requirements and tests)
• Adding governance checkpoints/quality practices without losing iteration cadence
• Coaching and lightweight process scaffolding for a new agile team

The key takeaway is that the symptoms (rework, rejection, low visibility) are consequences of an approach not tailored to the project’s regulatory constraints and team maturity.

The approach wasn’t adapted to required traceability/validation and a novice agile team, causing predictable compliance rejections and confusion.

Question 64

Topic: Process

You are managing a hybrid project to implement a new customer portal. A functional manager suggests outsourcing the portal’s development to “speed things up,” and the sponsor asks you to propose a procurement strategy by the end of the week.

The details of what should be outsourced and how the work will be accepted are not yet clear. What should you verify or obtain first before deciding the procurement strategy?

• A. Have Legal draft a fixed-price contract template with schedule penalties
• B. Ask Procurement to issue an RFP to the three most well-known vendors
• C. Request Finance to increase contingency reserves for potential vendor delays
• D. Clarify the specific deliverables to be procured and the high-level acceptance criteria/requirements stability

Best answer: D

What this tests: Process

Explanation: Procurement strategy decisions depend on what work is being procured and how clearly it can be defined and accepted. By first clarifying the outsourced deliverables and acceptance criteria (and how stable the requirements are), the project manager can appropriately tailor the sourcing method and contract type. Acting without this information risks selecting a misaligned procurement approach.

Planning a procurement strategy starts by defining the procurement need: what portion of the project will be acquired externally and what “done” means for those deliverables. In the scenario, the project is still unclear on what will be outsourced and how deliverables will be accepted, which directly drives choices such as contract type (e.g., fixed price vs. time and materials), the level of detail needed in the SOW, evaluation criteria, and the overall solicitation approach.

A practical first step is to obtain enough information to describe:

• The deliverables/work packages to outsource
• High-level requirements and acceptance criteria
• The expected level of requirements stability/uncertainty

Once that foundation exists, you can select an appropriate procurement path and prepare the right procurement documents and evaluations. Jumping to solicitation, contract drafting, or reserves is premature without a clear procurement scope and acceptance basis.

You need a clear definition of what will be bought and how it will be accepted to choose an appropriate sourcing approach and contract type.

Question 65

Topic: Process

You have been assigned as the new project manager on a hybrid product rollout with internal operations, an external vendor, and executive sponsors in multiple time zones. Stakeholders are complaining that they either receive too much detail or learn about issues too late, and there is no current communications management plan.

Before you decide the communication methods, channels, frequency, and level of detail, what should you verify/obtain FIRST?

• A. A weekly status email template to send to all stakeholders
• B. A governance decision on who is responsible for the communication problems
• C. Stakeholder communication requirements and preferences for information type, format, and cadence
• D. The sponsor’s approval to mandate a single collaboration tool for everyone

Best answer: C

What this tests: Process

Explanation: The first step is to understand what each stakeholder needs and expects, including preferred channels, frequency, and level of detail, along with any constraints (e.g., confidentiality, time zones). With that information, you can tailor communications appropriately and document it in a communications management plan.

Selecting methods, channels, frequency, and detail is a tailoring decision that should be driven by stakeholder needs and constraints, not by a one-size-fits-all approach. In this scenario, complaints indicate misalignment, but the root cause is unknown because communication requirements were not clearly established or updated.

Start by confirming communication requirements (often by reviewing the stakeholder register and engaging key stakeholders) to determine:

• Who needs what information (detail level and content)
• When they need it (cadence and triggers)
• How they want to receive it (channels/formats)
• Any constraints (access, confidentiality, language, time zones)

Only after this analysis should you standardize templates/tools and finalize the communications management plan; otherwise, you risk reinforcing the current mismatch.

You must first perform communications requirements analysis so channels, frequency, and detail are tailored to each stakeholder’s needs and constraints.

Question 66

Topic: Process

You are planning procurement for a custom reporting platform that must integrate with several legacy systems. The risk register notes high requirements volatility and unknown integration effort until a short discovery is completed, but the finance director is pushing for a firm-fixed-price contract to “lock in costs.”

What is the best immediate action to address this procurement risk?

• A. Open an issue and require the vendor to start integration now
• B. Plan a phased contract: capped T&M for discovery, then fixed-price
• C. Proceed with firm-fixed-price and add strict penalties
• D. Ask the sponsor to choose the contract type before continuing

Best answer: B

What this tests: Process

Explanation: The key is aligning contract type to uncertainty and risk allocation. When scope and effort are unclear, using time-and-materials with a not-to-exceed cap limits buyer exposure while enabling discovery. Once requirements and integration approach are better defined, a fixed-price contract can then provide the cost certainty stakeholders want.

Procurement risk can often be reduced by tailoring the contract type to the level of uncertainty. With high requirements volatility and unknown integration effort, a firm-fixed-price contract is likely to drive heavy contingencies, disputes, or change requests because the seller is being asked to price unknowns. A better immediate response is to structure the procurement so learning happens first under a contract that shares risk, then lock in price after scope is clearer.

• Update the procurement approach to a two-phase strategy
• Use capped T&M (not-to-exceed) for time-boxed discovery/prototyping
• Define exit/acceptance criteria for moving to phase 2
• Use fixed-price for the build once requirements are baselined

This directly mitigates cost-overrun and change-dispute risk while still addressing the need for cost predictability later.

A capped T&M phase limits cost exposure while uncertainty is high, and a later fixed-price phase appropriately shifts risk once scope is defined.

Question 67

Topic: Process

Which artifact documents stakeholder engagement strategies and how engagement will be monitored and adjusted over time?

• A. Stakeholder register
• B. Communications management plan
• C. Issue log
• D. Stakeholder engagement plan

Best answer: D

What this tests: Process

Explanation: The stakeholder engagement plan is the artifact used to plan stakeholder engagement approaches and to track whether engagement levels are moving toward the desired state. It is updated as stakeholders’ needs, influence, or attitudes change and as engagement effectiveness is measured through project interactions and feedback.

The stakeholder engagement plan is the core plan for how the project team will engage each stakeholder (or stakeholder group) to increase support and minimize resistance. It typically links current and desired engagement levels (for example, unaware/neutral/supportive) and defines actions, owners, and timing to move stakeholders toward the desired level. Because engagement changes throughout the project, this plan is reviewed and updated based on performance information such as participation, feedback, sentiment, escalations, and outcomes of engagement activities. In contrast, other documents may list stakeholders or describe communications, but they do not focus on tailoring engagement strategies and measuring engagement effectiveness over time.

It defines tailored engagement approaches and includes how to monitor current vs. desired engagement and update actions over time.

Question 68

Topic: People

You are managing a hybrid product implementation with an aggressive go-live date. Several key team members are new to the organization’s delivery practices, and the sponsor has asked you to mentor them to reduce rework. Your calendar is already heavily booked with governance meetings and issue resolution.

Which action should you NOT take to allocate time for mentoring?

• A. Create a lightweight mentoring plan and enlist senior SMEs as co-mentors
• B. Use pairing and working sessions to mentor during real work
• C. Block a recurring mentoring timebox on the team calendar
• D. Defer mentoring until after the next major milestone to protect delivery time

Best answer: D

What this tests: People

Explanation: Effective mentoring requires intentionally allocating time, not treating it as optional work. Timeboxing mentoring and integrating it into daily delivery helps close capability gaps early and prevents rework. Deferring mentoring until “things slow down” is an anti-pattern because the project is most vulnerable while the team is still ramping up.

Allocating time to mentoring is a proactive leadership activity: you make it visible, intentional, and sustainable within delivery constraints. In a high-pressure timeline, the best approach is to timebox mentoring and embed it into normal work (pairing, reviews, working sessions) so learning happens where it is immediately applied. You can also scale mentoring by involving experienced team members while staying accountable for overall development and alignment. Deferring mentoring until after a milestone is risky because skill gaps will likely show up as defects, rework, and delays—creating more schedule pressure rather than less. The key takeaway is to protect small, regular mentoring investments early to reduce downstream disruption.

Postponing mentoring increases the chance of continued skill gaps, rework, and avoidable escalations during the critical period.

Question 69

Topic: People

You are leading a hybrid product rollout with a virtual, cross-functional team. Rework is increasing because people are unsure who can make decisions on requirements changes.

Exhibit: Team working agreement (draft excerpt)

Project goal: Release MVP by July 31 with required compliance.
Team hours: Core overlap 10:00–14:00 UTC.
Meetings: Daily standup (15 min); weekly planning (60 min).
Roles: PM, Product Owner, Dev Lead, QA Lead (responsibilities TBD).
Decision rule: "Team decides quickly" (no further detail).
Conflicts: "Escalate to PM" and "PO owns product decisions".

Based on the exhibit, what should the project manager do NEXT?

• A. Escalate the decision-authority conflict to the sponsor for a final ruling
• B. Assign the project manager as the final approver for all requirement changes to reduce rework
• C. Facilitate a workshop to define roles/responsibilities and explicit decision rules, then update and re-confirm the working agreement
• D. Proceed with current practices and address decision issues as they arise in retrospectives

Best answer: C

What this tests: People

Explanation: A working agreement (team charter) is effective only when it clearly states who does what and how decisions are made. The excerpt contains “responsibilities TBD,” a vague decision rule, and conflicting authority statements between the PM and product owner. The most appropriate next action is to facilitate alignment and update the agreement with explicit roles and decision rules that the team commits to follow.

The core problem in the exhibit is not meeting cadence or availability; it is ambiguity: roles are undefined and decision authority is contradictory. To create and maintain a team charter/working agreement, the project manager should facilitate a short, structured working session with the team (and key roles like the product owner) to agree on:

• Clear role/accountability boundaries (e.g., lightweight RACI for key decisions)
• Decision rules (who decides what, decision method, and escalation path)
• How changes will be evaluated and approved within the agreed authority

Once agreed, update the working agreement and obtain explicit team commitment so it becomes a shared reference point for day-to-day decisions and reduces rework.

The exhibit shows unclear roles and conflicting decision authority, so the next step is to align and document roles and decision rules with team buy-in.

Question 70

Topic: People

Which term describes a facilitated workshop technique that creates a visual model of the user journey to help stakeholders reach consensus on scope and delivery sequencing?

• A. Work breakdown structure (WBS)
• B. Process flowchart
• C. User story mapping
• D. Product backlog

Best answer: C

What this tests: People

Explanation: User story mapping is a collaborative facilitation technique that uses a visual model of the end-to-end user journey. By arranging stories under user activities and discussing gaps and priorities, the team and stakeholders can quickly align on what to build and in what order.

User story mapping is used to build shared understanding by facilitating a workshop where the team and stakeholders lay out the user’s workflow (activities/steps) and map user stories beneath it. This makes the product scope visible, surfaces missing requirements and dependencies, and supports consensus on prioritization and release/iteration slicing.

A key characteristic is that it is organized around the user journey (what users do and in what sequence), not around a deliverable decomposition or a simple list. The output often informs backlog refinement and release planning, but it is distinct from the backlog itself. The takeaway is that story mapping is a consensus-building visual model centered on user value flow.

It visually organizes user activities and related stories to build shared understanding and agree on priorities and releases.

Question 71

Topic: People

You are a project manager on a hybrid product rollout with a cross-functional team working in two-week iterations. A functional manager has started assigning tasks daily and requiring approval before any design decision. The team reports slower cycle time and low ownership. At the same time, there are non-negotiable compliance criteria and a fixed release date.

What is the BEST next action to enable self-organization while keeping necessary boundaries?

• A. Escalate to the sponsor to direct the functional manager to stop interacting with the team immediately
• B. Create a detailed task-level plan and assign owners with instructions for how to execute each task
• C. Implement a daily mandatory status report and require the functional manager to approve all work in progress
• D. Facilitate a session to agree on iteration outcomes, decision rights, and working agreements, including compliance guardrails

Best answer: D

What this tests: People

Explanation: To enable self-organization, the team needs clear outcomes and explicit guardrails, not task-by-task control. Facilitating agreement on goals, decision boundaries, and compliance criteria creates shared expectations and allows the team to choose how to deliver within constraints. This addresses micromanagement while still protecting the fixed release date and regulatory needs.

Self-organization is supported by shifting from controlling tasks to clarifying “what” must be achieved and the limits within which the team can decide “how.” In this scenario, compliance requirements and a fixed release date are real constraints, so the right move is to establish clear outcomes and decision boundaries rather than removing oversight entirely.

A practical next step is to facilitate alignment on:

• Iteration/release outcomes (e.g., sprint goals and deliverables)
• Decision rights (what the team can decide vs. when escalation/approval is needed)
• Working agreements and lightweight reporting cadence
• Compliance guardrails (e.g., required reviews, Definition of Done criteria)

This reduces micromanagement, restores ownership, and keeps necessary governance without slowing delivery with unnecessary approvals.

This sets clear goals and boundaries (including compliance) while removing day-to-day control so the team can self-organize.

Question 72

Topic: People

A hybrid project is digitizing an insurance claims intake process across three departments. During a requirements workshop, stakeholders disagree on what “claim submitted” means and keep debating edge cases. Constraints:

• The workshop is limited to 90 minutes, and two departments are joining remotely
• The new solution must comply with an existing audit trail requirement
• The team needs a shared definition today to proceed with prioritizing the backlog

What is the project manager’s BEST next action to reach consensus?

• A. Ask each department to submit detailed requirements after the meeting
• B. Move on to other items and let the product owner decide later
• C. Escalate the disagreement to the steering committee for a decision
• D. Facilitate a process-mapping session and define acceptance criteria

Best answer: D

What this tests: People

Explanation: The fastest way to build shared understanding in a time-boxed workshop is to co-create a simple visual model of the current and desired process and agree on what “done” means. A process map makes handoffs and audit-trail touchpoints explicit, and acceptance criteria turn the agreed definition into testable statements. This enables immediate backlog prioritization with a common baseline.

This situation calls for facilitated consensus-building, not deferral or escalation. When stakeholders interpret key terms differently, a shared visual model (such as a process map with swimlanes) helps the group converge by making steps, handoffs, inputs/outputs, and compliance touchpoints visible—especially with remote attendees. Then, translating the agreed definition into lightweight, testable acceptance criteria (or user story acceptance criteria) locks in the shared meaning so the team can prioritize and plan consistently.

A practical approach in the remaining time is:

• Timebox a high-level process map for “claim submitted” (start/end, key handoffs)
• Identify where the audit trail is created/updated
• Capture acceptance criteria for the agreed state and edge cases

The key takeaway is to use facilitation and visual models to reach alignment now, rather than collecting documents, escalating, or postponing a decision needed for the backlog.

A shared visual process map plus agreed acceptance criteria aligns interpretations quickly and captures compliance needs so backlog prioritization can proceed.

Question 73

Topic: People

You introduced a new workflow tool for a hybrid project and scheduled training for all team members. Two weeks later, you review the following learning outcomes report.

Training: Workflow Tool v2 (Week 6)
Participants: 24
Knowledge check avg: 88%
Adoption (users active weekly): 58% (target 85%)
Avg cycle time: 6.2 days (baseline 4.0)
Rework due to workflow errors: 19% (baseline 8%)
Top observation: Steps for approvals frequently skipped

What should the project manager do next?

• A. Tailor follow-up training with coaching and job aids focused on the approval steps, then re-measure adoption and rework
• B. Escalate to the sponsor to enforce tool usage through formal performance management
• C. Declare the training effective because the knowledge check average exceeds 80%
• D. Pause tool adoption until the next phase to avoid further productivity impacts

Best answer: A

What this tests: People

Explanation: The exhibit shows that knowledge retention is high, but on-the-job performance outcomes are worse than baseline and below target. Training effectiveness should be evaluated primarily through measurable performance results (adoption, cycle time, rework) and observed gaps. The best action is to adjust the training plan with targeted support on the specific failure point and then re-measure the same outcomes.

Training effectiveness is demonstrated by improved work performance, not only by test scores. Here, the team scored well on the knowledge check, yet adoption is far below target and key delivery outcomes (cycle time and rework) have deteriorated, with a clear pattern of errors around skipped approvals. That indicates the training approach needs to be adjusted to close an application/behavior gap.

A practical next step is to:

• Focus reinforcement on the observed weak area (approval steps)
• Add on-the-job supports (coaching, job aids, office hours)
• Reconfirm expectations in working agreements/process guidance
• Re-measure adoption, cycle time, and rework after the intervention

Escalation or pausing adoption may be needed later if results do not improve, but the exhibit supports first refining the training and support plan based on measurable outcomes.

The outcomes show a performance gap (low adoption, higher cycle time and rework) that requires targeted reinforcement and a revised measurement check.

Question 74

Topic: People

You are leading a hybrid project with an internal team and a contracted vendor. A vendor lead has started messaging developers directly to ask for small “no paperwork” feature tweaks.

Exhibit: Project working agreement (excerpt)

1) We follow the organization's values: integrity, transparency, respect.
2) All external requests route through the product owner and PM.
3) No side agreements; changes use the agreed change/backlog process.
4) Issues are raised early; escalation path is PM -> sponsor.

Based on the exhibit, what is the best next action?

• A. Allow the direct messages for minor requests to maintain responsiveness, and document them later.
• B. Reinforce the working agreement with the vendor and team, and re-route requests through the product owner/PM using the agreed change process.
• C. Update the backlog based on the developers’ messages and inform the product owner afterward.
• D. Escalate the vendor’s behavior to the sponsor immediately to enforce compliance.

Best answer: B

What this tests: People

Explanation: The exhibit defines organizational principles (integrity and transparency) and specific ground rules for interacting with external parties. The vendor’s direct requests violate the agreed routing and “no side agreements” rules. The best action is to communicate and enforce these principles with both the team and the vendor and re-establish the agreed request and change/backlog path.

Team ground rules are only effective when the project manager actively reinforces them with both the team and external stakeholders. Here, the working agreement explicitly ties behavior to organizational principles (integrity and transparency) and defines how external requests and changes must flow. Because the vendor is bypassing the agreed channel and proposing “no paperwork” changes, the project manager should intervene promptly to realign expectations and protect transparent decision-making.

A practical next step is to:

• Remind the vendor and team of the working agreement and organizational values
• Reconfirm the single request path (vendor -3 product owner/PM)
• Direct any requested tweaks through the agreed change/backlog process

Escalation is available if the behavior continues, but the exhibit supports first enforcing the established ground rules and communication approach.

This directly applies the stated organizational values and communication ground rules to stop side agreements and restore transparent, approved request routing.

Question 75

Topic: People

A hybrid project is implementing a new customer portal. Several business unit leaders were previously resistant, delaying decisions and challenging the project’s direction. Over the last month, the project manager held targeted working sessions and incorporated their feedback. The sponsor asks for evidence that the key leaders are now engaged and aligned so the project can proceed confidently.

Which metric/evidence best validates improved stakeholder engagement and alignment?

• A. Number of working sessions held with business unit leaders
• B. Distribution log showing weekly status reports sent on time
• C. Meeting minutes documenting discussion topics and questions raised
• D. Co-reviewed stakeholder engagement assessment showing desired engagement achieved

Best answer: D

What this tests: People

Explanation: The strongest validation of stakeholder engagement is evidence that stakeholders’ current engagement level matches the desired level and that they agree with that assessment. A co-reviewed stakeholder engagement assessment matrix makes engagement visible, enables candid conversation, and provides a credible basis to proceed. Counts of meetings, emails, or minutes show activity, not alignment.

Building trust and influence requires demonstrating that stakeholders are not only being communicated with, but are actually supportive, participating appropriately, and making timely decisions. The most defensible evidence is an updated stakeholder engagement assessment (current vs desired) that is reviewed and confirmed with the key leaders and sponsor, because it validates engagement outcomes rather than communication volume.

A practical validation approach is:

• Reassess current engagement for each key stakeholder (e.g., resistant -4 neutral -4 supportive)
• Compare to the desired level needed to meet objectives
• Review the assessment with stakeholders and agree on actions to close gaps

Activity artifacts can support the story, but they do not, by themselves, confirm alignment or commitment.

A stakeholder-validated current-vs-desired engagement assessment provides direct evidence of alignment and commitment, not just activity.

Questions 76-100

Question 76

Topic: Process

You are managing a hybrid project with a distributed team. After sending an update about a planned scope change, you review the communications log excerpt below.

Exhibit: Communications log (excerpt)

Comms ID: CL-22
Message: "Phase 1 go-live moved to May 15; UAT scope reduced to critical flows only."
Audience: Business ops leads (3 regions)
Channel: Email + Teams post
Requested: Acknowledge + confirm regional impact by Friday
Status: 2 replies received; 1 region no response
Reply from Region B: "We will stop all UAT and focus on training." (not intended)

What should the project manager do next?

• A. Send a longer follow-up email with additional details and assumptions
• B. Hold a quick clarification session and ask each region to restate impacts and confirm understanding
• C. Proceed with the reduced UAT scope since most regions replied
• D. Escalate the lack of response to the sponsor as a communications compliance issue

Best answer: B

What this tests: Process

Explanation: The exhibit shows missing acknowledgment and an incorrect interpretation of the message, which creates a high risk of misaligned work. The best action is to immediately close the feedback loop using interactive communication and a confirmation technique (such as having recipients paraphrase expected actions/impacts). This ensures the message is understood consistently across regions.

Confirming communication is understood requires more than sending additional information; it requires receiving and validating feedback. Here, one region did not respond and another misinterpreted “reduced to critical flows only” as “stop all UAT,” indicating the message was not understood as intended.

The project manager should use an interactive channel to verify shared understanding and capture explicit confirmation:

• Bring the regional ops leads together briefly (Teams call)
• Ask each region to state planned actions and impacts (read-back/paraphrase)
• Resolve misunderstandings immediately and document the agreed impacts/next steps

This closes the loop, prevents divergent execution, and produces clear, auditable confirmation versus relying on one-way messaging or assumptions.

A two-way clarification and confirmation (e.g., read-back) directly verifies understanding and captures feedback to correct misinterpretations.

Question 77

Topic: People

A hybrid project team agreed on ground rules, including “challenge ideas, not people” and “no interruptions.” During a planning meeting, a senior engineer repeatedly interrupts others and dismisses a tester’s concern. After the meeting, the project manager gives the engineer private, behavior-specific feedback and at the next meeting briefly reinforces the ground rules and invites the tester to restate the concern.

What is the most likely near-term impact of this action?

• A. More team members will share concerns in the next meetings
• B. The senior engineer will be removed from the project by HR
• C. Team conflict will be eliminated for the remainder of the project
• D. Schedule performance will immediately improve due to faster meetings

Best answer: A

What this tests: People

Explanation: By addressing the behavior privately and reinforcing the agreed ground rules publicly, the project manager corrects the violation without shaming anyone. This maintains psychological safety while managing conflict, so the team is more likely to participate and raise risks and quality concerns right away. The immediate effect is improved willingness to speak up, not instant performance or organizational consequences.

Enforcing team ground rules is most effective when it combines timely feedback with conflict management that protects psychological safety. In this scenario, the project manager uses a respectful approach: coaching the individual privately to stop the interrupting/dismissing behavior, then reinforcing expectations with the whole team without singling anyone out. The near-term result is typically a safer team climate where people feel permitted to surface concerns and disagree constructively in upcoming meetings. Larger outcomes like sustained performance gains or formal personnel actions are possible but are indirect and depend on patterns, escalation paths, and time.

Key takeaway: address the behavior quickly and consistently while preserving dignity to increase speak-up behaviors.

Timely, specific feedback plus reinforcing ground rules increases psychological safety, making people more willing to speak up quickly.

Question 78

Topic: People

A distributed agile team is in the last week of an iteration, with a production release committed in 2 weeks. The release requires a full regression test and formal QA sign-off.

The team raises these impediments:

• A new developer is still ramping up and needs frequent help.
• The product owner is traveling but answers questions within 24 hours.
• Testers cannot access the shared test environment because an IT access request has been pending for 6 days; without access, regression testing cannot start.

What is the project manager’s BEST next action?

• A. Ask the team to continue development and defer regression testing to the next iteration
• B. Use the established escalation path to expedite test-environment access
• C. Reassign testers to write additional test cases until access is granted
• D. Record all impediments in the issue log and wait for IT to process the request

Best answer: B

What this tests: People

Explanation: The most critical impediment is the one that prevents the team from completing a mandatory release criterion within the fixed time window. Lack of access to the test environment blocks regression testing and therefore QA sign-off. The best next action is to actively remove the blocker by engaging IT and escalating through the agreed path.

Determining critical impediments means identifying which obstacle most threatens the iteration goal or near-term delivery commitments, especially mandatory acceptance criteria (for example, compliance, testing, or approvals). Here, the team can still progress despite ramp-up needs and slower product owner feedback, but they cannot start regression testing at all without the test environment. With a fixed release date and required QA sign-off, this dependency becomes the highest-impact blocker.

A practical sequence is:

• Confirm the specific impact (what testing is blocked and by when).
• Engage the responsible group (IT access owner) with urgency and clear dates.
• Escalate using the predefined path if normal processing will miss the needed start date.

The key takeaway is to focus first on removing the blocker that stops required work on the critical delivery path.

This is the only item directly blocking required regression testing and QA sign-off for the fixed release window.

Question 79

Topic: Process

A project team previously identified the risk that the external vendor might not provision the test environment by March 15, which would delay integration testing. The risk response plan includes a preapproved contingency to use a temporary sandbox environment for up to two iterations if the March 15 trigger date is missed.

On March 16, the vendor confirms provisioning will take an additional four weeks. As the project manager, what should you do next? (Select TWO)

• A. Wait until integration testing is actually delayed before acting
• B. Submit a change request before taking any action
• C. Perform qualitative risk analysis again to re-rank the risk
• D. Enter this as an issue in the issue log and assign an owner
• E. Activate the planned contingency to use the temporary sandbox
• F. Keep it in the risk register since it was already identified

Correct answers: D, E

What this tests: Process

Explanation: A risk becomes an issue when the uncertain event occurs (or is confirmed to be occurring) and requires immediate management. Here, the vendor’s confirmation after the trigger date means the risk event has materialized. The appropriate next steps are to manage it through issue management and execute the preplanned contingency response.

A risk is an uncertain event that may affect objectives; an issue is a current problem (or confirmed event) that is happening now and needs action. In this scenario, the trigger date has passed and the vendor has confirmed a four-week delay, so there is no longer uncertainty—the risk has materialized and must be treated as an issue.

Appropriate immediate actions are:

• Log the situation as an issue, assign an owner, and track resolution.
• Execute the preapproved contingency tied to the trigger to minimize impact.

Updating the risk register can still occur (e.g., marking the risk as occurred/closed), but the key recognition is switching from monitoring a risk to actively managing an issue and implementing the planned response.

The uncertainty is resolved and the impact is now occurring, so it must be managed as an issue with ownership.

The defined trigger was met, so executing the preapproved contingency is appropriate to reduce immediate schedule impact.

Question 80

Topic: People

You are negotiating an agreement with a vendor to deliver a customer portal. Review the exhibit.

Artifact: Vendor agreement open items (excerpt)
1) Pricing: Vendor proposes T&M; buyer requested fixed price
2) Scope maturity: Requirements 40% complete; backlog evolving
3) Schedule: Target go-live Nov 1; vendor requests +4 weeks
4) Service levels: 99.9% uptime; vendor offers 99.5% with credits
5) Risk: Integration with legacy API unknown; no access until contract signed

What is the best next action to move the negotiation toward an agreement that fits the project’s current situation?

• A. Insist on a fixed-price contract and escalate if the vendor resists
• B. Accept the vendor’s schedule extension and reduced uptime to get the contract signed quickly
• C. Negotiate a phased agreement with procurement: fixed-price discovery, then T&M with a ceiling for delivery
• D. Suspend negotiations until the vendor is given legacy API access before discussing any terms

Best answer: C

What this tests: People

Explanation: The exhibit shows high uncertainty (40% requirements complete and unknown integration), making a pure fixed-price agreement risky for both parties. A phased agreement lets the team reduce uncertainty through a short discovery effort, then negotiate delivery terms with clearer scope while still setting guardrails like a not-to-exceed ceiling. This approach supports a realistic, negotiable path to a mutually acceptable contract.

Effective agreement negotiation aligns contract structure to the current level of scope clarity and risk. Here, the vendor’s concerns are supported by the exhibit: the backlog is still evolving and integration access is unknown, so insisting on a single fixed-price delivery contract increases the chance of disputes, change orders, and adversarial behavior.

A practical negotiation move is to propose a structure that shares risk appropriately:

• Set a short, fixed-price discovery/prototype phase to complete requirements and validate integration.
• Use outputs from discovery (refined backlog/requirements, integration findings) to negotiate delivery pricing.
• For delivery, consider T&M with a ceiling and clear acceptance criteria/service-credit terms to bound cost and performance.

This keeps negotiations moving while matching the agreement to uncertainty and protecting both buyer and seller interests.

With requirements only 40% complete and key integration unknowns, a phased approach balances uncertainty while still creating cost and risk boundaries.

Question 81

Topic: People

You are managing a hybrid project with a fully virtual delivery team across the U.S., India, and Germany. Over the last two iterations, defects increased and several team members stopped speaking up in daily standups. Two developers privately mention that meetings occur outside their normal working hours and that their video conferencing tool is unreliable due to local bandwidth limits.

What is the best next step?

• A. Hold short 1:1 check-ins to understand each member’s time-zone, environment, and tool constraints
• B. Escalate to the sponsors to approve funding for new collaboration tools
• C. Ask functional managers to replace team members who are not participating
• D. Require all team members to attend a fixed daily standup time going forward

Best answer: A

What this tests: People

Explanation: The immediate issue suggests misalignment with time zones and working conditions, which commonly affects engagement and quality on virtual teams. The project manager’s next step is to examine individual needs and constraints (geography, schedules, environment, and tools) before changing policies or escalating. This enables targeted adjustments to team working agreements and communications.

With virtual teams, performance and engagement problems are often symptoms of unmet needs (time-zone overlap, home/office environment, connectivity, cultural norms around speaking up, and tool access). Before imposing new rules or escalating, the project manager should gather facts directly from team members.

A practical next step is to:

• Conduct brief 1:1 check-ins (or a quick anonymous survey)
• Document constraints and patterns (hours, bandwidth, tool access)
• Use the findings to update working agreements and the communications approach

Escalation or staffing changes can be appropriate later, but only after validating the root constraints and attempting tailored support.

You should first assess virtual team member needs and constraints so you can tailor communication and working agreements effectively.

Question 82

Topic: People

You are leading a hybrid project to implement a new CRM. During sprint execution, Sales requests a change to the lead-scoring rules that affects integration logic. The Product Owner says the change is needed for business value, but the integration lead says it will increase rework unless approved by the enterprise architecture group. Decision rights are unclear, and delays will impact a fixed go-live date.

What is the BEST next action to clarify authority and accountability for this decision and similar future decisions?

• A. Submit a change request to the CCB for immediate approval
• B. Ask the Product Owner to decide to protect sprint flow
• C. Create a DACI/RACI for key decisions and confirm it with governance
• D. Escalate the disagreement to the project sponsor to decide

Best answer: C

What this tests: People

Explanation: Because multiple groups claim approval authority, the immediate need is to define decision rights rather than debate the technical solution. Using a DACI or RACI tailored to key decisions (like architecture-impacting changes) assigns accountability and approval authority and aligns those roles with existing governance, reducing future delays while protecting the fixed go-live date.

When decision-making authority is unclear, the project manager should establish and socialize a decision-rights framework so decisions are made by the right people at the right time. In this scenario, the Product Owner can prioritize value, but architecture-impacting changes may require an explicit approver; the integration lead is raising a governance dependency, not just an implementation preference.

Best next action is to create (or refine) a DACI/RACI for key decision types and validate it with the relevant governance bodies (e.g., enterprise architecture, product, sponsor) so:

• accountability for the decision is explicit
• approval authority is agreed in advance
• contributors and informed parties are clear

This prevents repeated escalation and reduces cycle time for similar cross-functional decisions. The key takeaway is to clarify decision rights first, then execute the agreed decision path.

A decision-rights framework clarifies who drives, approves, contributes, and is informed, enabling timely, accountable decisions aligned with governance.

Question 83

Topic: Process

A hybrid project is preparing for a regulatory readiness review before deploying a new customer onboarding system. Several requirements and test artifacts have been updated over the last month by a distributed team, and the reviewer specifically asks for proof that the artifacts are current, approved, and traceable to authorized changes.

Which evidence best validates this?

• A. An email thread with the latest document attachments
• B. A count of artifacts updated during the last month
• C. Configuration status accounting/audit report from the version control system
• D. A burndown chart showing the team’s velocity trend

Best answer: C

What this tests: Process

Explanation: A configuration status accounting or configuration audit report is the strongest evidence that artifacts are controlled through versioning, baselined, and linked to authorized change decisions. It validates not just that work happened, but that the current versions are the approved ones and can be traced back to specific change records. This directly addresses “current and traceable” for a readiness review.

Configuration management and version control provide objective proof that artifacts are current, approved, and traceable. For a readiness or audit review, the best validation is evidence that shows (1) which versions are baselined/approved, (2) what the current controlled versions are, and (3) the linkage from each change to an authorized record (e.g., change request/decision).

A configuration status accounting report (often produced from the version control system and change control records) or a configuration audit report provides that end-to-end traceability and confirms that what the team plans to deploy matches the approved baselines. Activity outputs or volume metrics may indicate effort, but they do not validate artifact integrity or authorization.

It shows the approved baselines, current versions, and traceability to authorized change records.

Question 84

Topic: People

You are managing a hybrid project to implement a new cloud-based billing system. After the first integration increment, several defects were traced to configuration errors, and the sponsor asks you to “schedule training for the team right away.” You want to determine the most appropriate training option.

What should you verify or obtain FIRST before selecting a training approach?

• A. A vendor quote for an off-the-shelf system configuration course
• B. The total training budget and approval limits from HR
• C. A role-based skills gap assessment against required competencies
• D. A revised delivery date that accounts for time spent in training

Best answer: C

What this tests: People

Explanation: Before choosing training options, the project manager should confirm the training need by identifying the required competencies and the current proficiency of the people doing the work. A role-based gap assessment ensures training is targeted (who, what, and depth) and avoids spending time and money on unnecessary or misaligned training.

Selecting a training option is a decision about the best way to close a specific performance or knowledge gap. In the scenario, defects may be caused by insufficient skills, unclear requirements, poor peer review practices, or tooling/environment issues, so the first step is to verify the actual training need. A role-based skills gap assessment compares required competencies for upcoming work (e.g., configuration standards, integration patterns, security rules) to current capability levels and identifies which individuals or roles need training.

Once the gap is known, you can tailor the option appropriately (e.g., targeted coaching, focused workshop, pairing, or vendor-led training) and then confirm cost/schedule impacts.

You need to confirm who lacks which specific skills before choosing the right training method and audience.

Question 85

Topic: Process

A hybrid project has completed development of a new customer onboarding portal and is preparing to hand it over to the operations team. The sponsor asks the project manager to confirm whether the solution is ready for transition this week. Some stakeholders report that “all critical work is done,” but no single readiness indicator has been agreed upon.

What should the project manager verify first to validate readiness for transition?

• A. Whether the team can improve performance by adding more resources
• B. Whether the sponsor wants to expand scope for additional features
• C. Formal acceptance criteria and sign-off for transition deliverables
• D. Whether procurement can close remaining invoices with the vendor

Best answer: C

What this tests: Process

Explanation: To validate readiness for transition, the project manager should first anchor the decision to objective, agreed acceptance criteria and documented acceptance of transition deliverables. Without this, “ready” is subjective and risks handing over an incomplete or unsupported solution. Confirming sign-off provides the basis for any go/no-go transition decision.

Readiness for transition should be confirmed using predefined, measurable acceptance criteria for both the product and the transition package (for example, operational documentation, training, support model, and cutover requirements) and then validated through documented acceptance. In this scenario, stakeholders are offering informal assurances, but no single indicator has been agreed, so the first step is to verify what “ready” means and whether it has been formally met.

A practical sequence is:

• Confirm transition deliverables and their acceptance criteria.
• Verify completion evidence (tests, docs, training, support readiness).
• Obtain formal acceptance/sign-off for handover.

Other activities may be important, but they should follow after acceptance criteria and acceptance status are clear.

Transition readiness should be validated against defined acceptance criteria and documented acceptance, not informal opinions.

Question 86

Topic: People

You are taking over as project manager for a hybrid product team with members in three time zones. The sponsor complains that “sprints keep slipping” because completed stories often return for rework after the review. Team members disagree on whether work is truly finished.

Before proposing new team ground rules, what should you clarify first?

• A. What is the current Definition of Done and who agreed to it?
• B. What additional budget is available to add testers immediately?
• C. What is each developer’s utilization and velocity trend?
• D. What penalties does the sponsor want for missed sprint commitments?

Best answer: A

What this tests: People

Explanation: The most direct way to restore predictable delivery is to confirm whether the team has a shared, documented Definition of Done and who has agreed to it. If “done” means different things to different people, work will repeatedly fail acceptance or quality expectations and cycle back as rework. Clarifying the current Definition of Done is the right first step before changing norms or decision rules.

Working agreements create predictability by making expectations explicit (for example, meeting norms, decision rules, and a Definition of Done). In the scenario, the recurring problem is that work thought to be complete returns for rework after reviews, which strongly suggests misalignment on completion/acceptance and quality criteria.

The first clarification should establish the current baseline:

• Whether a Definition of Done exists
• Where it is documented and used (planning, reviews, acceptance)
• Who agreed to it (team, product owner, key stakeholders)

Once the current Definition of Done is understood, the team can update it (and related norms/decision rules) to reduce rework and improve delivery predictability. Resource or accountability discussions come after clarifying the shared standard for “done.”

Rework from “done” items indicates a shared, explicit Definition of Done may be missing or not aligned across the team and stakeholders.

Question 87

Topic: People

A hybrid project is delivering a customer self-service portal. During the sprint review, the sponsor says the “Account History” feature is incomplete because it does not include export to CSV. The team insists the story is done and is asking to start new work.

To break down the situation and identify the root cause of the misunderstanding, which evidence should the project manager review first to validate what was actually agreed for acceptance?

• A. The number of stakeholder comments captured during the sprint review
• B. The user story’s documented acceptance criteria and approval history
• C. The sprint burndown chart for the iteration
• D. The team’s timesheets showing hours spent on the feature

Best answer: B

What this tests: People

Explanation: The fastest way to pinpoint a misunderstanding about completeness is to compare the delivered outcome to the agreed acceptance criteria for the specific work item. Reviewing the acceptance criteria and when/who approved them validates the definition of “done” and clarifies whether CSV export was included, omitted, or later changed.

When stakeholders disagree about whether something is complete, the root cause is usually an unclear or inconsistently understood definition of acceptance, not a lack of effort or activity. The most valid evidence is the artifact that explicitly states the expected outcomes and quality conditions for acceptance and shows stakeholder agreement.

In this case, reviewing the user story’s acceptance criteria and approval/change history helps the project manager:

• Verify whether CSV export was part of the original scope for that story
• Determine whether expectations changed without a corresponding update
• Separate a requirements gap from a communication/expectations gap

Progress charts, hours, and participation counts can be useful for monitoring work, but they do not validate what the sponsor agreed to accept.

Acceptance criteria with approval history best validates the shared definition of “done” and reveals whether the gap is missing scope or missing understanding.

Question 88

Topic: Business Environment

A hybrid project delivered a new customer self-service portal and was accepted by operations. Three months later, the sponsor asks for an update on expected benefits (reduced call volume and higher digital adoption). The project manager finds there is no agreed set of benefit KPIs, no baseline for current call volume, and no assigned owner or cadence to collect and report the data.

Which underlying issue most likely explains the problem?

• A. No benefits measurement system was established and transitioned to operations
• B. Operations is resisting adoption of the new portal
• C. Project status reporting during execution was ineffective
• D. The sponsor failed to approve the project charter

Best answer: A

What this tests: Business Environment

Explanation: The symptoms point to an inability to measure outcomes after handoff, not a delivery or reporting problem. A benefits measurement system requires defined metrics, baselines, data sources, owners, and a reporting cadence so realized benefits can be tracked and communicated post-implementation.

The core issue is missing benefits measurement and realization planning. When benefits are stated (e.g., reduce call volume, increase digital adoption) but there are no agreed KPIs, no baseline, and no owner/cadence to collect data, the organization cannot verify whether the project is delivering value after transition to operations.

A practical measurement system typically includes:

• Benefit KPIs with clear definitions and targets
• Baselines and data sources/collection method
• Assigned benefits owner(s) in the business/operations area
• Review cadence and reporting mechanism (e.g., dashboard) after go-live

Adoption challenges may exist, but the stem’s primary clue is the absence of measurement components needed to track benefits at all.

Without defined KPIs, baselines, owners, and reporting cadence, benefits cannot be objectively tracked after delivery.

Question 89

Topic: Process

A hybrid project to implement an enterprise HR platform is repeatedly delayed because priorities and scope decisions keep changing. The team receives conflicting direction from functional managers, and change requests sit unapproved for weeks; some stakeholders bypass the project manager and ask the CIO directly.

The organization already uses a PMO-led steering committee and a defined escalation path for cross-functional decisions, and the project has been sending weekly status reports and holding regular sprint reviews.

What is the most likely underlying cause of these problems?

• A. The project lacks a risk management approach for decision delays
• B. The team is not controlling scope because too many changes occur
• C. Project governance and decision authority were not formally established
• D. Stakeholders are not receiving enough project communications

Best answer: C

What this tests: Process

Explanation: The symptoms point to unclear decision rights and escalation, not a lack of reporting or team activity. Since the organization already has an established PMO/steering-committee model, the project should replicate and tailor that governance so approvals, change authority, and escalation paths are explicit and consistently used.

Project governance defines how decisions are made, who has authority, and how issues are escalated. In the scenario, stakeholders bypass the project manager, functional leaders provide conflicting direction, and changes wait for approval even though regular status reporting and reviews are occurring. Those are classic signs that governance was not established or not aligned to the organization’s existing PMO/steering committee model.

Effective governance for this situation would clarify, at minimum:

• Decision rights (who approves scope/priority changes)
• Escalation path (when and how to raise cross-functional conflicts)
• Forums/cadence (e.g., steering committee or CCB meetings)
• Thresholds for approvals (what can be decided within the team vs. escalated)

The key takeaway is that transparency (communications) does not replace decision authority; governance makes decisions timely and consistent.

Without a defined governance structure aligned to the organization, decision rights and escalation routes remain unclear and stakeholders make ad hoc decisions.

Question 90

Topic: Process

You are closing a predictive IT infrastructure upgrade project. The customer has started using the solution. Review the closeout log excerpt:

Closeout log (excerpt)
- Deliverable acceptance: Signed Feb 10
- Transition to operations: Completed Feb 12
- Lessons learned: Draft complete; workshop scheduled Feb 20
- Contract V-12 (network vendor): Final invoice received; vendor eval pending; status OPEN
- Project financials: Final cost report pending until final invoice processed
- Resources: Team released; PM + procurement analyst remain

What should the project manager do next to support project closure?

• A. Work with procurement to complete contract closure and process final payment
• B. Release remaining project funds back to the organization and close the project charter
• C. Hold the lessons learned workshop immediately and archive all project documents
• D. Request a final acceptance sign-off from the customer sponsor

Best answer: A

What this tests: Process

Explanation: The exhibit indicates product acceptance and transition are complete, but an external contract remains open and the final cost report is waiting on the vendor’s final invoice. Completing procurement closure (including vendor evaluation and final payment processing) removes the remaining dependency for financial closure. This is a core closure activity needed before final administrative closeout.

In project/phase closure, the project manager ensures all work is formally accepted, contracts are closed, financials are finalized, resources are released, and records are archived. Here, acceptance and transition are already completed, and the lessons learned activity is planned, but the exhibit shows a vendor contract is still OPEN and the final cost report cannot be completed until the final invoice is processed. The next action should therefore focus on procurement closure in coordination with the procurement function—confirm all contract deliverables are complete, complete the vendor performance evaluation, resolve any remaining claims, and authorize final payment—so the project can finalize financials and complete administrative closure. Scheduling the lessons learned is important, but it is not the current blocker for closure in the exhibit.

The exhibit shows an open vendor contract and pending final invoice that is preventing financial closeout, so procurement closure is the next blocking closeout action.

Question 91

Topic: People

You are leading an agile software team on a hybrid project with a fixed regulatory submission date in 8 weeks. The team is distributed across three time zones, and the same blockers (test environment outages and delayed security approvals) have been raised in daily standups for the past two weeks with no sustained improvement. Several blockers are outside the team’s control and require support from operations and the security office.

What is the BEST next action?

• A. Wait for the next iteration retrospective to address the recurring blockers
• B. Document the blockers in the risk register and continue development around them
• C. Make blockers visible, assign owners, and review/escalate them daily until resolved
• D. Add overtime and reassign work so the team is not impacted by external dependencies

Best answer: C

What this tests: People

Explanation: The situation shows persistent, repeating blockers that are not being removed and that threaten a fixed deadline. The best next action is to implement a disciplined, ongoing impediment management approach: make blockers transparent, assign accountable owners, and inspect and adapt daily with escalation paths for items outside the team’s authority.

Continually re-assessing impediments means treating blockers as first-class work: visible, owned, timeboxed, and actively followed up—not just discussed. Here, blockers are recurring, cross-functional, and outside the team’s control, so the project leader should establish an explicit impediment management loop and use escalation paths to get decisions and capacity from operations/security.

• Create/update an impediment list (single source of truth) with severity and due dates
• Assign an owner for each blocker (team or external) and define the escalation path
• Review daily in the standup (or async equivalent across time zones) and immediately escalate stalled items

The key takeaway is to inspect impediments frequently and drive resolution, rather than deferring action or merely documenting them.

A visible impediment list with daily ownership, follow-up, and escalation enables continual reassessment and timely removal of blockers beyond the team’s control.

Question 92

Topic: Process

A company is developing a fintech mobile app using two-week agile sprints. The delivery team is new to agile and often skips acceptance criteria and test evidence. A regulator announces an audit in six weeks, and the compliance officer (key stakeholder) requires full requirements-to-test traceability and documented approvals for anything entering UAT.

The project manager decides to add a requirements traceability matrix, mandatory test evidence capture, and a weekly stage-gate review before promoting any increment to UAT.

What is the most likely near-term impact of this decision?

• A. Sprint throughput drops due to added compliance documentation and gates.
• B. The upcoming regulatory audit will have no findings.
• C. Production support effort decreases in future releases.
• D. Project budget increases immediately due to regulatory penalties.

Best answer: A

What this tests: Process

Explanation: Because regulatory constraints and stakeholder expectations have increased, the team must adopt more formal controls and evidence generation. The most immediate consequence is reduced capacity for building features as the team spends time on documentation, traceability, and approvals. This is a direct, near-term effect of tailoring the process to meet compliance needs and low team maturity.

Tailoring means adjusting practices to fit uncertainty, regulatory demands, stakeholder needs, and team capability. Here, a near-term audit and a compliance stakeholder requirement for traceability force the project to add more predictive-style controls (e.g., documented requirements, test evidence, approvals). With a team that is still maturing, these controls create immediate extra work (learning, producing artifacts, facilitating reviews), so delivery flow slows in the next iterations. Over time, the added rigor may reduce rework and improve audit outcomes, but the first-order, near-term impact is decreased sprint throughput due to added process overhead. The key takeaway is that tighter constraints often trade speed for compliance and visibility.

Adding regulatory traceability and approvals increases overhead immediately, reducing delivery capacity in the next few sprints.

Question 93

Topic: Process

A project manager is leading a hybrid project to implement a regulated customer portal. The integration work is managed predictively with approved schedule and cost baselines, and the vendor contract requires formal approval for scope changes. Mid-project, a senior stakeholder requests adding multi-factor authentication to the portal to address emerging security concerns.

Which action should the project manager AVOID when handling this change request?

• A. Submit a formal change request for review and decision through the defined change control process
• B. Begin development immediately and seek approval in parallel to protect the target go-live date
• C. Once a decision is made, communicate it and update the relevant plans, baselines, and backlog items
• D. Document the request and perform impact analysis on scope, schedule, cost, and risk

Best answer: B

What this tests: Process

Explanation: In a regulated environment with established baselines and contractual change requirements, work should not proceed until the requested change is formally evaluated and approved. Proper change strategy is to document the request, analyze impacts, route it through governance, and then update plans based on the decision. Implementing first creates unauthorized scope and weakens change control.

The core strategy for handling change is to follow the defined change control approach and governance, especially when regulatory obligations and contract terms require formal approval. Here, adding multi-factor authentication may be valuable, but it must be treated as a controlled change: capture the request, assess impacts to scope/schedule/cost/risk and compliance, obtain the appropriate decision (including any contract modification), and then incorporate the approved change into the plan and delivery backlog. Starting work before approval is an anti-pattern because it effectively authorizes scope without agreement, can trigger unplanned cost/schedule impacts, and can create procurement and compliance exposure. The key takeaway is to protect governance and baselines by approving changes before executing them.

Starting work before formal change approval bypasses governance and can create unauthorized scope, cost, and contractual impacts.

Question 94

Topic: Process

Which PMI term describes raw observations and measurements gathered during project execution that are later analyzed to support project decision-making?

• A. Work performance data
• B. Work performance reports
• C. Work performance information
• D. Project management plan

Best answer: A

What this tests: Process

Explanation: Work performance data is the raw, unvalidated and unanalyzed measurements collected while the work is performed. It becomes useful for decisions after it is analyzed and placed in context, producing work performance information and then summarized into reports for stakeholders.

The core concept is the progression from collecting measurements to analyzing them for decisions. Work performance data is the starting point: the direct observations and measurements captured during project work (for example, actual start/finish dates, hours used, number of defects, tests passed). The project team analyzes that data (often against the plan and baselines) to create work performance information, which explains meaning and variances. That information is then packaged into work performance reports (such as a status report or dashboard) tailored to stakeholder needs. The key takeaway is that “data” is raw; analysis turns it into “information,” and communication packaging turns it into “reports.”

It is the unprocessed, raw measurements (for example, percent complete, costs, defect counts) collected for later analysis.

Question 95

Topic: Process

A project manager collects the scope, schedule, cost, quality, resource, communications, risk, and procurement plans created by different leads. She reconciles interdependencies and assumptions, aligns the baselines, and produces one approved plan to guide how the project will be executed, monitored, and controlled across phases.

Which project management governance concept does this best represent?

• A. Progressive elaboration (rolling wave planning)
• B. Developing and integrating the project management plan
• C. Performing integrated change control
• D. Stakeholder engagement planning

Best answer: B

What this tests: Process

Explanation: The described work is about assembling and reconciling all subsidiary plans and baselines into one integrated, approved project management plan. This consolidation ensures the project is managed as a coherent whole with consistent assumptions, dependencies, and control approaches across phases.

Consolidating project or phase plans is the integration activity of building a single, approved project management plan from the various subsidiary plans and baselines (scope, schedule, cost, etc.). The key is not just collecting documents, but reconciling conflicts, aligning assumptions and dependencies, and establishing a unified basis for execution and for monitoring and controlling work. Once consolidated and approved, this integrated plan becomes the primary reference for how work will be performed and how changes will be evaluated.

A different governance concept would apply if the focus were deciding on proposed changes to approved baselines rather than creating the consolidated plan.

It consolidates subsidiary plans and baselines into a single, approved, integrated project management plan.

Question 96

Topic: Business Environment

A manufacturing company recently implemented a new inventory management system. The project is in the benefits realization period, and the change is active.

Two months after go-live, the sponsor reports that on-time fulfillment has not improved as expected and warehouse staff are using workarounds. The project manager has access to system usage analytics and operational KPIs, but no formal post-change measurement has been performed yet.

What should the project manager do next?

• A. Conduct additional end-user training immediately to eliminate workarounds
• B. Escalate the lack of benefits to the change control board for a decision
• C. Collect adoption and outcome measures, compare to targets, and define corrective actions
• D. Declare the change unsuccessful and recommend rolling back the system

Best answer: C

What this tests: Business Environment

Explanation: Before taking action, the project manager should measure both adoption (usage, process compliance) and outcomes (KPIs tied to intended benefits) and compare results to the targets. That evidence identifies the real gaps (e.g., low usage vs. process issues) and enables focused corrective actions to realize benefits. Acting without measurement risks addressing symptoms instead of causes.

In the post-change period, benefits are realized only if the solution is adopted and produces the intended outcomes. When benefits lag and workarounds appear, the next step is to establish a fact base by measuring adoption (e.g., feature use, process adherence, exception rates) and outcomes (e.g., on-time fulfillment KPI) and comparing them to the benefits targets. Use the results to identify root causes (training, process design, data quality, performance, stakeholder resistance) and then plan and implement corrective actions with accountable owners and follow-up measurement. This sequence ensures actions are tied to measurable gaps and supports benefits realization rather than relying on assumptions. Escalation, training, or rollback may be appropriate later, but only after measurement confirms the nature and magnitude of the problem.

Measuring adoption and outcomes against intended benefits is the next prerequisite step before selecting and implementing corrective actions.

Question 97

Topic: People

In an agile project, the project manager stops assigning tasks and instead clarifies the sprint goal and Definition of Done, establishes working agreements, and focuses on removing impediments so the team can decide how to do the work. Which leadership approach does this describe?

• A. Autocratic leadership
• B. Laissez-faire leadership
• C. Management by exception
• D. Servant leadership

Best answer: D

What this tests: People

Explanation: Servant leadership emphasizes enabling the team’s self-organization by focusing on outcomes and boundaries while providing support. The leader serves the team by removing impediments and facilitating decision-making instead of directing tasks and methods.

This scenario describes servant leadership, a core agile leadership approach where the leader prioritizes the team’s ability to deliver value. Rather than micromanaging tasks, the leader clarifies the “what” (goals, expected outcomes) and establishes guardrails (e.g., working agreements, Definition of Done), then helps the team succeed by removing impediments and fostering collaboration. This balance of autonomy plus clear boundaries is what enables true self-organization and accountability.

The key takeaway is that empowerment is not “hands-off”; it is active support with clear expectations and constraints.

It empowers a self-organizing team by setting clear outcomes/guardrails and supporting delivery by removing obstacles rather than micromanaging.

Question 98

Topic: Process

A project manager is assigned to a hybrid project to upgrade a bank’s customer onboarding platform. The organization’s PMO already mandates a governance model for all customer-facing regulatory-impacting initiatives, including stage-gate approvals, a Change Control Board (CCB) for scope/budget changes, and defined escalation paths to the portfolio steering committee.

What is the MOST appropriate project governance approach for this project?

• A. Adopt the existing PMO stage-gate governance and required boards
• B. Use Scrum events only and let the product owner decide changes
• C. Create a tailored governance model specific to this project
• D. Use a RACI and weekly status meetings as the main governance

Best answer: A

What this tests: Process

Explanation: When an organization has an established, mandated governance framework for a class of projects, the project manager should replicate and integrate with it rather than invent a parallel model. This ensures decision authority, approvals, and escalation paths match enterprise oversight needs. It also provides consistency, auditability, and alignment with portfolio controls.

Project governance defines how decisions are made, who approves changes, and how the project escalates issues. In the scenario, the PMO already mandates governance for regulatory-impacting, customer-facing initiatives, including stage gates, a CCB, and portfolio steering escalation. The project manager should therefore adopt that existing structure and integrate project-specific details (cadence, membership, thresholds, decision rights) within the mandated framework.

A practical approach is to:

• Confirm required governance forums (stage gates, CCB, steering committee)
• Define decision rights and escalation paths consistent with PMO policy
• Align project artifacts (plans/backlog, change requests, reporting) to those forums

Creating a parallel governance model or relying only on team-level ceremonies risks bypassing required oversight and weakening control over scope, budget, and compliance-impacting decisions.

Because an enterprise-mandated governance model exists for this type of work, the project should align to it, including decision bodies and escalation paths.

Question 99

Topic: Process

A hybrid project is testing a new data migration tool. During the last integration test, the tool failed and data could not be migrated.

Exhibit: Risk register and issue log (excerpt)

Risk ID: R-07 | Event: Migration tool incompatible
Trigger: Integration test fails
Response: Mitigate (vendor patch before UAT)
Contingency: Use manual script; +3 days schedule

Issue ID: ISS-12 | Summary: Migration tool failed in test
Impact: Testing blocked; go-live at risk
Status: New | Owner: Unassigned

Based on the exhibit, what should the project manager do next?

• A. Close the risk since it has already occurred
• B. Treat it as an issue, implement contingency, and update the risk register
• C. Wait for the vendor patch decision before updating any logs
• D. Keep monitoring it as a risk until the next test cycle

Best answer: B

What this tests: Process

Explanation: The integration test failure shows the risk has materialized, so it is no longer a future uncertainty. The project manager should manage it through the issue process (assign ownership and act) and also update the risk register to reflect response execution and any new or residual risks created by the contingency.

A risk is an uncertain event that may occur; an issue is a current condition that has already occurred and needs immediate management. Here, the documented trigger (“integration test fails”) has happened and an issue has been recorded, so the focus shifts to issue resolution.

The project manager should:

• Assign an owner and take action to unblock work (execute the planned contingency/workaround).
• Update the risk register to show the risk response was executed and to capture any residual or secondary risks (for example, defects introduced by manual scripts).

Continuing to “monitor the risk” delays needed action, and closing the risk without updating responses/lessons misses the required risk management follow-through.

The risk trigger has occurred, so it must be managed as an issue while updating risk responses (including residual/secondary risks) in the risk register.

Question 100

Topic: Business Environment

Halfway through execution of a predictive infrastructure project, the organization announces a restructuring: the data governance group is moving under a new VP, and a new policy requires all customer data to be hosted in the company’s approved cloud platform. Your approved design uses an on-premises database, and stakeholders are already asking whether the project will be canceled.

What should the project manager do next?

• A. Escalate to the PMO to decide the project’s future
• B. Assess impacts and confirm continued alignment with sponsor/governance
• C. Submit a change request to rebaseline scope, schedule, and cost
• D. Stop project work until the new organization is fully staffed

Best answer: B

What this tests: Business Environment

Explanation: An organizational change can alter assumptions, constraints, and benefits, so the project manager should first perform an impact assessment and validate continued alignment and decision rights with the sponsor/governance. With that clarity and data, the PM can then route any required updates through the appropriate change control or termination process.

The core concept is to evaluate how the organizational change affects the project’s continued business alignment before taking irreversible actions. A new data-hosting policy and leadership restructure may change requirements, constraints, funding, and stakeholders, so the project manager’s next step is to assess the impacts and confirm direction with the sponsor/governance body.

Practical sequence:

• Identify what changes (policy, decision makers, priorities).
• Analyze impacts to scope/requirements, schedule, cost, risks, and benefits.
• Confirm who now has authority and whether the project remains viable.
• Then raise the appropriate change request(s) or proceed to controlled closure.

Rebaselining or escalating without a fact-based impact assessment is premature and can create rework or unnecessary disruption.

First determine the restructuring’s impact on scope, benefits, and constraints and validate direction with the sponsor before initiating formal changes.

Questions 101-125

Question 101

Topic: Business Environment

A project is implementing a new customer onboarding platform for a financial services company. During UAT, the team discovers the vendor solution cannot retain required AML/KYC audit logs for 7 years, which is a regulatory requirement. Go-live is in 3 weeks, and the sponsor is pushing to launch and “address logging later” to avoid contractual delay penalties.

Which TWO actions should the project manager take? (Select TWO)

• A. Have operations keep manual logs after go-live
• B. Submit a change request to defer go-live until compliant
• C. Remove the audit-log requirement from the project scope
• D. Authorize overtime to build a workaround without approvals
• E. Escalate the noncompliance via the defined governance path
• F. Proceed and fix the logging in the next release
• G. Negotiate a temporary exemption directly with the regulator

Correct answers: B, E

What this tests: Business Environment

Explanation: Releasing a solution that is known to be noncompliant exposes the organization to regulatory, legal, and reputational consequences that typically outweigh schedule or contract penalties. The project manager should immediately escalate through governance and use formal change control to adjust the plan so compliance is achieved before go-live.

The core concept is that regulatory requirements are not optional scope; knowingly deploying a noncompliant product can trigger audits, fines, forced remediation, loss of license/ability to operate, and reputational damage. When noncompliance is discovered late, the project manager’s role is to ensure the right decision makers are engaged and that changes are handled transparently.

Practical response:

• Log and escalate the issue through the established governance/compliance/legal channels.
• Use integrated change control to rebaseline (for example, defer go-live or fund a compliant solution path).

Trying to “ship now and fix later” treats compliance as a defect backlog item and can create immediate business-environment impacts that the team cannot simply absorb with overtime or workarounds.

Known regulatory noncompliance must be raised immediately to compliance/legal decision makers per governance.

Deferring release through change control addresses the noncompliance before exposing the organization to regulatory consequences.

Question 102

Topic: Process

A hybrid project team is preparing for user acceptance testing (UAT) of an increment. The project manager reviews the following artifact and is concerned validation will be subjective.

Backlog Item BI-27: Export audit report to PDF
Acceptance criteria: "Report is user friendly"; "Performance acceptable"
Quality measures: Not specified
Definition of Done: Code merged; Unit tests passed
Planned validation: UAT sign-off by Compliance

What is the best next action?

• A. Request immediate sponsor approval of the increment to avoid delaying the release
• B. Proceed with UAT and let Compliance determine whether the report is acceptable
• C. Perform a quality audit of the development process to confirm standards were followed
• D. Facilitate refinement to define measurable acceptance criteria and add quality measures to the Definition of Done

Best answer: D

What this tests: Process

Explanation: The acceptance criteria in the exhibit are subjective and the quality measures are missing, so UAT outcomes would be based on opinions rather than evidence. The best action is to collaborate with the product owner, compliance, and the team to define clear, testable acceptance criteria and measurable quality thresholds and incorporate them into the Definition of Done to support objective validation.

Acceptance criteria and quality measures enable objective validation by defining what “acceptable” means and how it will be verified. In the exhibit, phrases like “user friendly” and “performance acceptable” are not testable, and the Definition of Done focuses on development completion rather than product quality and validation readiness.

A practical next step is to refine BI-27 with stakeholders and the team to:

• Convert criteria into testable statements (e.g., required fields, layout rules, error handling)
• Define measurable quality thresholds (e.g., PDF generation time, defect severity limits)
• Update the DoD to include the necessary verification evidence (e.g., performance test passed, compliance checklist met)

This makes UAT sign-off based on defined evidence rather than subjective judgment.

The exhibit shows vague criteria and missing measures, so the team must agree on testable acceptance criteria and DoD quality measures to enable objective validation in UAT.

Question 103

Topic: People

You are leading a hybrid product rollout. A newly assigned business representative is acting as product owner but is unfamiliar with agile practices. During refinement, they hesitate to make priority decisions and ask you to “just decide what the team should build first.” The team is stalled waiting for direction.

Which TWO actions should you take to recognize and act on this mentoring opportunity? (Select TWO)

• A. Arrange shadowing or pairing with an experienced product owner and set recurring check-ins to reinforce learning
• B. Escalate to the sponsor to replace the product owner with someone who has agile experience
• C. Assume responsibility for backlog prioritization to keep delivery moving, then brief the product owner afterward
• D. Pause refinement and require the product owner to complete formal agile training before participating further
• E. Hold a short coaching session to clarify product owner decision rights and practice prioritizing the next iteration items together
• F. Convert the backlog into detailed requirements documentation yourself to reduce the product owner’s workload

Correct answers: A, E

What this tests: People

Explanation: The situation signals a capability gap in a key stakeholder role that is blocking progress. Mentoring means helping the stakeholder learn how to fulfill their responsibilities through targeted coaching and practical, supported practice. Actions that transfer ownership away from the stakeholder or delay decisions do not build long-term capability.

Mentoring opportunities often appear when a stakeholder’s lack of role clarity, confidence, or skills creates hesitation, rework, or delays. Here, the product owner is explicitly asking you to take over prioritization, which would undermine accountability and keep the team dependent on the project manager.

Effective mentoring focuses on building the stakeholder’s capability while keeping ownership where it belongs:

• Clarify expectations, decision rights, and working agreements for the role.
• Coach using real work (e.g., prioritize the next iteration) so learning is immediately applied.
• Provide ongoing support through pairing/shadowing and short, regular check-ins.

The key takeaway is to enable the stakeholder to make decisions independently rather than substituting for them or forcing a disruptive reset.

This directly mentors the stakeholder in their role and builds capability to make timely priority decisions.

This provides ongoing, practical mentoring support while helping the stakeholder develop confidence and competence.

Question 104

Topic: People

You are managing a fully remote, cross-time-zone project team. You want to continually evaluate whether engagement is improving after recent adjustments to meeting times and team working agreements.

Exhibit: Engagement health check (last 3 sprints)

Metric                      S1   S2   S3
Daily attendance rate        92%  81%  79%
Sprint retro attendance      100% 80%  60%
PR review median cycle time  18h  27h  31h
Slack “blocked” msgs/week    3    7    9

Based on the exhibit, what should the project manager do next?

• A. Increase the number of mandatory status meetings to reinforce accountability
• B. Escalate to functional managers to replace low-participation team members
• C. Freeze the current meeting schedule to avoid further disruption to the team
• D. Facilitate a focused conversation to identify engagement barriers and update working agreements and support needs

Best answer: D

What this tests: People

Explanation: Multiple engagement signals are deteriorating over time (attendance, retro participation, collaboration speed, and more “blocked” messages). The appropriate next action is to inspect what is driving disengagement in the virtual environment and collaboratively adapt the team’s working approach and supports. This directly evaluates engagement effectiveness and enables timely corrective action.

Continually evaluating virtual team engagement means using objective signals (participation, collaboration flow, and impediment frequency) to detect trends and then taking a lightweight, team-centered action to understand causes and adjust. Here, every metric moves in an unfavorable direction across three sprints, indicating the recent changes are not producing the desired engagement outcomes.

A practical next step is to facilitate a short, focused discussion (e.g., in a retro or dedicated session) to:

• Validate what is driving lower participation (time-zone burden, meeting overload, psychological safety, unclear expectations)
• Identify needed support (tooling, pairing windows, clearer handoffs)
• Update working agreements and communication norms, then monitor the same metrics

Escalation or adding mandatory meetings treats symptoms and often reduces engagement further; the goal is to remove barriers and iteratively measure improvement.

The trends show worsening participation and slower collaboration, so the next step is to inspect causes with the team and adjust how the virtual team works and is supported.

Question 105

Topic: Process

A project has a documented risk management plan that defines risk categories and a probability/impact matrix. However, the team’s risk register contains only risk descriptions, and the “Category,” “P/I rating,” and “Owner” fields are blank. Several risks have occurred, and no one is sure who should implement the planned responses.

What is the most likely underlying cause of this situation?

• A. The risk register is not being maintained with categories, P/I ratings, and assigned owners
• B. The budget baseline did not include contingency reserves for risk events
• C. Risk responses were not communicated after risks started occurring
• D. The team is identifying too many risks, causing analysis paralysis

Best answer: A

What this tests: Process

Explanation: The key clue is that the risk register exists but critical fields are blank. A risk register must be maintained with categories, probability/impact assessments, and named risk owners so risks can be prioritized and responses executed with clear accountability. Without these elements, risks can materialize with no one empowered to act.

The core issue is not the absence of risk management guidance—the plan and scoring method already exist—but the failure to maintain a usable risk register. A complete risk register enables consistent prioritization (via probability/impact), analysis by category, and accountability (via assigned risk owners) to monitor triggers and implement agreed responses.

In this scenario, the blank category, P/I rating, and owner fields directly explain why:

• Risks are not prioritized, so attention is misallocated.
• No risk owner is accountable to monitor and act.
• Planned responses are unlikely to be executed on time.

The takeaway is to keep the risk register current and actionable, not just a list of risk statements.

Without categorization, prioritization, and risk ownership, the team cannot assign accountability or act on responses in time.

Question 106

Topic: People

A product team uses Kanban and recently implemented a WIP limit after a retrospective to address long and unpredictable cycle times. Two months later, the project sponsor asks the project manager to verify whether the change improved team performance using objective evidence, not opinions.

Which method or artifact should the project manager use?

• A. Cycle time control chart comparing before-and-after data
• B. Updated team charter reflecting the new WIP policy
• C. Individual performance appraisals for the last two months
• D. Stakeholder satisfaction survey results from the last review

Best answer: A

What this tests: People

Explanation: To verify a performance improvement, the project manager should use measurable, repeatable indicators and compare results to a baseline. In a Kanban context, cycle time is a primary flow metric, and a control chart/trend view shows whether the process became faster and more stable after the WIP limit was introduced.

Verifying performance improvements means demonstrating that the team’s outcomes changed in the desired direction using objective measures, ideally compared against pre-change performance. Because the change targeted flow efficiency and predictability in a Kanban system, cycle time is the most relevant metric. A cycle time control chart (or before/after trend analysis) uses actual work-item data to show whether cycle times decreased and whether variation reduced, providing evidence that the improvement is real and sustained. This is stronger than subjective feedback or documentation updates, which may indicate adoption but do not prove results.

A control chart (or equivalent trend of cycle times) provides objective, time-based evidence of whether flow performance improved after the WIP limit.

Question 107

Topic: Business Environment

A project manager is joining a company that is starting an enterprise-wide digital transformation. In this organization, work is guided by detailed procedures, multiple approval levels are required for most decisions, success is measured by compliance with standards, and experimentation is discouraged to avoid disrupting operations.

Which organizational culture best matches this situation?

• A. Adhocracy culture (entrepreneurial and innovation-oriented)
• B. Market culture (competitive and results-oriented)
• C. Clan culture (collaborative and people-oriented)
• D. Hierarchy culture (control- and process-oriented)

Best answer: D

What this tests: Business Environment

Explanation: The described environment prioritizes stability, control, and adherence to defined processes. Those are core indicators of a hierarchy culture, where governance relies on policies, standards, and approval chains to manage risk and maintain operational consistency.

Assessing organizational culture means identifying the norms that drive how decisions get made and how work gets rewarded or constrained. In the scenario, the strongest signals are centralized decision authority (multiple approval layers), reliance on formal procedures, and success defined by compliance—along with low tolerance for experimentation. These characteristics align with a hierarchy culture, which typically values predictability, standardization, and control. When supporting organizational change in this environment, the project manager should expect heavier governance, more formal communications, and a need to build buy-in through risk-managed pilots and clear control impacts. A key takeaway is to read culture through observable behaviors (decision rights, risk tolerance, measures of success), not through stated values.

The emphasis on formal procedures, approvals, compliance, and stability indicates a hierarchy culture.

Question 108

Topic: Process

A hybrid software project is reporting monthly using EVM against approved scope, schedule, and cost baselines. The change control board approves a change to add a security module, and the project manager updates the scope statement and schedule baseline to include the additional work. The team begins work immediately, but the cost baseline and funding requirements have not yet been updated.

What is the most likely near-term impact?

• A. The delivered product will likely fail to achieve its planned business benefits at project closure
• B. The vendor supporting the security module will likely submit a contract claim during procurement closeout
• C. Team morale will likely decline, causing key specialists to leave the project
• D. Cost performance reports will show misleading negative variances against an outdated baseline

Best answer: D

What this tests: Process

Explanation: Because the cost baseline was not updated to match the approved change, spending for the new work will be compared to an outdated baseline. In the near term, that makes EVM-based cost variances and forecasts unreliable and can trigger incorrect decisions or escalations. Integrated baselines must be updated consistently across affected plans after approved changes.

Integrated change control requires updating all impacted baselines and subsidiary plans so performance measurement remains consistent. In this scenario, the project has an approved scope/schedule change and has started executing it, but the cost baseline (and related funding needs) still reflect the pre-change plan. As soon as time and money are booked for the security module, EVM comparisons (AC and forecasts against the cost baseline) will indicate unfavorable variances that are artifacts of misaligned baselines rather than true underperformance.

A practical sequence is:

• Ensure the change is approved and documented.
• Update all impacted baselines/plans (scope, schedule, cost, funding, reporting).
• Communicate the updated integrated plan and resume performance measurement.

Approved change work will increase actual costs while the cost baseline still reflects the pre-change plan, distorting near-term variance reporting.

Question 109

Topic: Process

You are managing a hybrid project to deliver a software update for a regulated healthcare product. Defects found during the last release’s late testing caused rework and stakeholder concern. As you plan the next release, you want to prevent recurrence by strengthening how quality will be achieved.

Which TWO actions are part of quality planning for the next release? (Select TWO)

• A. Perform a process audit to verify teams follow the agreed workflows
• B. Integrate reviews and test activities into the release plan and backlog
• C. Define measurable quality metrics and acceptance criteria for key requirements
• D. Coach the team to improve adherence to engineering practices during delivery
• E. Execute system tests and record defects found against requirements
• F. Inspect completed features against the Definition of Done at iteration end

Correct answers: B, C

What this tests: Process

Explanation: Quality planning defines what “quality” means for the deliverables and how the project will build quality into the work. In this scenario, the planning focus is on establishing measurable criteria and proactively embedding review/testing activities into the plan and backlog so quality is designed in rather than discovered late.

Quality planning is the proactive work of defining quality requirements/standards, translating them into measurable criteria, and deciding the methods and activities that will be used to meet them. For a hybrid release, that commonly means clarifying acceptance criteria/metrics for regulated requirements and planning when and how reviews and testing will occur within both the predictive plan and the agile backlog.

Quality assurance is process-focused and evaluates whether the chosen processes are appropriate and being followed (e.g., audits, process reviews, coaching). Quality control is product-focused and checks actual results for conformance (e.g., inspections, testing, defect identification). The key takeaway is that planning sets the targets and the approach; assurance checks the process; control checks the outputs.

Quality planning includes defining the standards, metrics, and acceptance criteria that will be used to judge conformance.

Quality planning determines the activities and approach (who/when/how) to build in quality rather than relying on late detection.

Question 110

Topic: People

On a hybrid project, a key business sponsor has recently become noticeably quiet in steering meetings, asks for detailed data in follow-up emails, and reacts strongly to surprises. You need to communicate a newly identified high-impact risk that may affect the release date.

Which action SHOULD AVOID to best apply emotional intelligence to this stakeholder?

• A. Acknowledge the sponsor’s concerns and present response options with trade-offs
• B. Ask the sponsor how they prefer to receive sensitive updates
• C. Announce the risk for the first time in the full steering meeting to “push urgency”
• D. Share a structured risk brief in advance and offer a 1:1 discussion

Best answer: C

What this tests: People

Explanation: The sponsor’s behavior indicates anxiety about uncertainty and a need for time to process information. Applying emotional intelligence means adapting your approach to reduce surprise, provide structure, and create a safe setting for questions. Introducing the risk publicly for the first time is most likely to trigger a negative emotional response and damage the relationship.

Emotional intelligence includes noticing personality and emotional cues (e.g., withdrawal, strong reactions to surprises, requests for detail) and adapting communication to meet the stakeholder’s needs. In this scenario, the sponsor signals a preference for predictability, data, and private processing time. Effective actions include confirming communication preferences, providing a structured risk summary ahead of time, and acknowledging concerns while discussing options and trade-offs. The behavior to avoid is creating an avoidable “surprise moment,” especially in a public forum, because it can increase threat response, reduce openness to problem-solving, and undermine trust and influence when you need alignment on next steps.

It ignores the sponsor’s cues about needing preparation and psychological safety, increasing defensiveness and eroding trust.

Question 111

Topic: Process

A company is outsourcing development of a new customer-facing mobile app. The sponsor wants work to start immediately, but the product vision is clear only at a high level and requirements are expected to change significantly after user feedback. Management also requires a hard spending limit for the vendor work.

Which contracting strategy should the project manager recommend to best support execution given these conditions?

• A. Time and materials with a not-to-exceed ceiling
• B. Fixed-price with economic price adjustment
• C. Cost-plus-incentive-fee contract
• D. Firm-fixed-price for the full solution

Best answer: A

What this tests: Process

Explanation: When requirements are expected to change significantly, the execution strategy should maximize flexibility and enable rapid reprioritization. A time-and-materials contract supports iterative discovery and frequent adjustments without constant renegotiation of a fixed scope. Adding a not-to-exceed ceiling meets the organization’s need for a hard spending limit.

The deciding factor is high requirements uncertainty combined with the need to start quickly. In that context, fixed-price approaches create friction because each major requirement change tends to trigger contract change requests, negotiation delays, and disputes about what is “in scope.” A time-and-materials contract better fits iterative delivery because the buyer pays for actual effort while work is refined through feedback.

To meet the additional constraint of cost control, the contract should include guardrails such as:

• A not-to-exceed ceiling (spending cap)
• Short review cycles with acceptance of incremental deliverables
• Clear reporting and approval for continued funding within the cap

The key takeaway is to align contract type to uncertainty (flexible pricing) while adding terms that control exposure (a ceiling).

It provides flexibility for evolving scope while enforcing a firm spending cap.

Question 112

Topic: Process

A hybrid project must launch a customer portal in 6 weeks. A hiring freeze and budget cap prevent adding staff, and the organization prohibits overtime. Development produces about 15 stories/week, but two certified testers can validate only 8 stories/week, creating a growing queue and threatening the launch. The product owner is willing to defer low-value features as long as the compliant minimum feature set ships.

What should the project manager do to best optimize resource capacity to meet the date and maximize delivered value?

• A. Outsource testing to a contract lab to increase throughput immediately
• B. Authorize weekend overtime for testers until the queue is eliminated
• C. Implement WIP limits aligned to test capacity and re-sequence work to deliver the minimum compliant set first
• D. Keep all developers coding at full speed to maximize completed work before testing

Best answer: C

What this tests: Process

Explanation: Testing is the capacity constraint, so optimizing the system means aligning upstream work to the testers’ throughput. Using WIP limits and resequencing to the minimum compliant feature set reduces queueing and rework, stabilizes flow, and protects the fixed launch date while maximizing value delivered by the deadline.

Resource capacity optimization starts by managing the bottleneck that drives end-to-end throughput. Here, certified testing is the constraint and you cannot add resources or overtime, so pushing more development only increases inventory and delays validation. The best approach is to level demand to test capacity and prioritize the highest-value, compliance-critical work so the team finishes what can be tested and released by the launch date.

• Reprioritize to the minimum compliant feature set first
• Set WIP limits (or a pull policy) so dev work entering test matches test capacity
• Resequence and focus the team on finishing and validating work, deferring low-value items

This improves schedule predictability and value delivered without breaking cost, staffing, or overtime constraints.

This levels flow to the testing bottleneck without violating constraints and preserves value by prioritizing the compliant minimum set for launch.

Question 113

Topic: Process

You are leading a hybrid project to deliver a new customer-facing claims portal for an insurance company. The next release will be built iteratively, but it must meet regulatory and internal audit requirements for requirements traceability. Key users (claims adjusters) and the compliance lead are in different time zones, and you have two weeks to baseline scope for the release so the team can start iteration planning.

Which action best optimizes fast, shared understanding while still meeting the traceability constraint?

• A. Produce a comprehensive business requirements document and obtain formal sign-off from all stakeholders before planning iterations
• B. Distribute a detailed survey to all stakeholders and compile the responses into a single requirements list
• C. Begin development with high-level epics only and capture detailed requirements informally during daily standups
• D. Facilitate a virtual requirements workshop using story mapping, then document outcomes as a prioritized backlog with acceptance criteria and trace links to compliance needs

Best answer: D

What this tests: Process

Explanation: For a hybrid, iterative release, the best elicitation technique is a facilitated, time-boxed workshop that creates shared understanding quickly despite distributed stakeholders. Capturing the results as user stories with clear acceptance criteria in a prioritized backlog supports iterative planning. Adding explicit trace links to compliance needs provides the audit trail the project requires.

The core decision is selecting an elicitation and documentation approach that fits iterative delivery while honoring a hard constraint: requirements traceability for compliance/audit. A facilitated virtual workshop (often run like a JAD session) accelerates alignment by resolving ambiguities in real time and works well for distributed stakeholders when time-boxed. Story mapping helps structure the end-to-end workflow and identify slices for the release.

To satisfy traceability, document the output in the team’s requirements repository (typically the product backlog) with:

• User stories (or equivalent) and testable acceptance criteria
• A way to trace each story to compliance needs (tags/links/IDs)
• Prioritization for iteration planning

This achieves speed and shared understanding without sacrificing auditable documentation; relying on surveys, heavy upfront documents, or informal capture either slows delivery or fails the traceability requirement.

A facilitated workshop plus story mapping fits iterative delivery for rapid alignment, and documenting user stories with acceptance criteria and trace links satisfies auditability.

Question 114

Topic: People

Which stakeholder analysis tool classifies stakeholders based on their level of authority (power) and their level of concern about the project (interest) to help determine their influence and the appropriate engagement approach?

• A. RACI chart
• B. Power/interest grid
• C. Salience model
• D. Stakeholder engagement assessment matrix

Best answer: B

What this tests: People

Explanation: The power/interest grid is a stakeholder analysis technique used to categorize stakeholders by how much authority they have and how interested they are in the project. This classification helps a project manager assess influence and decide how to manage communications and engagement for each stakeholder group.

Analyzing influence starts with categorizing stakeholders in a way that indicates how strongly they can affect project decisions and outcomes. The power/interest grid does this by mapping stakeholders on two dimensions: their power (authority/influence over resources or decisions) and their interest (level of concern about the project). The resulting categories help the project manager prioritize attention and tailor engagement (for example, closely manage high-power/high-interest stakeholders and keep satisfied those with high power but low interest). This tool is specifically about assessing influence-related priority using power and interest, rather than measuring engagement levels, assigning responsibilities, or applying a different influence model.

It maps stakeholders by power and interest to prioritize influence and tailor engagement strategies.

Question 115

Topic: Process

You are leading a hybrid software project for a medical device company. Requirements for analytics features are highly uncertain, the product must meet strict regulatory documentation needs, several stakeholders expect formal approvals at key milestones, and the delivery team is new to agile. You decide to use timeboxed iterations for discovery work, keep stage-gate reviews for compliance and stakeholder approvals, and add extra coaching and lightweight templates until the team matures.

Which project management principle or governance concept best matches this practice?

• A. Management by exception using tolerances and escalation paths
• B. Tailoring the approach to fit the project context
• C. Progressive elaboration of scope and plans
• D. Integrated change control through a change control board

Best answer: B

What this tests: Process

Explanation: This situation is primarily about selecting and adjusting the delivery approach, governance checkpoints, and documentation to match the project’s context. The decisions are explicitly driven by uncertainty, regulatory constraints, stakeholder approval needs, and team maturity. That is the essence of tailoring a fit-for-purpose approach rather than applying a one-size-fits-all method.

Tailoring means intentionally adapting the project’s life cycle, practices, governance controls, and artifacts to the reality of the work. In this scenario, high uncertainty drives iterative discovery, regulatory constraints drive stronger documentation and formal reviews, stakeholder expectations drive stage-gate approvals, and low team maturity drives added coaching and initially simpler, more guided ways of working.

A tailored approach balances agility where learning is needed with predictive controls where compliance and governance require them. The key takeaway is that the project manager adjusts process and oversight to optimize value delivery while still meeting required constraints.

It deliberately adjusts methods, controls, and artifacts based on uncertainty, compliance needs, stakeholder expectations, and team capability.

Question 116

Topic: People

You are leading a hybrid project with a partially remote delivery team. Over the last two iterations, one experienced engineer has repeatedly submitted work that does not meet the agreed definition of done, creating rework and tension with testers. The next customer demo is in two weeks, and you want to correct the behavior quickly while maintaining trust and team morale.

What feedback approach should you use?

• A. Escalate immediately to the functional manager and request they handle the performance problem
• B. Hold a private 1:1 soon, describe specific observed gaps and impacts, ask for their perspective, and agree on clear next steps and support
• C. Wait until the next formal performance review so you have more data and can avoid overreacting
• D. Address the issue in the next team meeting to reinforce standards and avoid singling anyone out privately

Best answer: B

What this tests: People

Explanation: The best option optimizes speed of improvement and team health by giving timely, specific, behavior-based feedback in a private setting. A two-way conversation surfaces causes (workload, clarity, skill gaps) and enables coaching and commitments without publicly undermining the person. This approach preserves trust while directly addressing delivery risk before the upcoming demo.

Effective feedback to support team performance is timely, specific, and focused on observable behavior and impact, delivered in a way that protects psychological safety. In this situation, the fastest way to reduce rework before the demo while maintaining morale is a private 1:1 conversation that uses facts (what was missing vs. the definition of done), explains the impact (rework, tester tension, risk to demo), and invites the team member’s perspective so you can identify root causes and offer support.

A practical approach is:

• Share specific examples tied to the definition of done
• Describe impact on the team and outcomes
• Ask what is getting in the way and listen
• Agree on concrete actions, check-ins, and needed support

Public callouts, delaying feedback, or immediate escalation tend to reduce trust or slow correction, which conflicts with the stated objective and time constraint.

It is timely, specific, and two-way, correcting performance while protecting psychological safety and enabling immediate improvement.

Question 117

Topic: People

You are leading a hybrid project to roll out a new customer billing platform. In recent meetings, the project sponsor (CFO) becomes impatient with long discussions and repeatedly asks for “the numbers and the decision.” The operations director becomes visibly tense when impacts on frontline staff are mentioned and keeps returning to “how people will cope with the change.”

The CFO and operations director are the two most influential stakeholders for approval of the next release. What should the project manager do? (Select TWO.)

• A. Hold brief 1:1s to confirm each stakeholder’s preferences and concerns
• B. Tailor the message format and delivery for each stakeholder’s style
• C. Request immediate approval to keep the release on schedule
• D. Escalate the tension to the steering committee for direction
• E. Send one standardized weekly status report to all stakeholders
• F. Rely on email updates to avoid emotionally charged discussions

Correct answers: A, B

What this tests: People

Explanation: Emotional intelligence starts with accurately reading stakeholder cues, then validating them and adapting your engagement approach. Here, the CFO is signaling a task/decision-and-data preference, while the operations director is signaling change anxiety and a people-impact focus. The best actions are to confirm needs directly and tailor communications to reduce resistance and increase support.

This situation calls for applying emotional intelligence to influential stakeholders: observe behavioral cues, validate them, and then tailor your approach to what each person needs to feel heard and make decisions. The CFO’s impatience with discussion and repeated requests for numbers suggests a preference for concise, data-driven decision inputs. The operations director’s visible tension and focus on coping indicates heightened change-related emotions and a need for reassurance, involvement, and clear people-impact plans.

Practical steps:

• Meet 1:1 to confirm preferences, triggers, and success criteria.
• Adjust content, level of detail, and channel (e.g., decision briefs vs. change-impact discussions).
• Use active listening and acknowledge concerns before proposing next steps.

Escalation or forcing approvals may increase defensiveness; tailoring builds trust and commitment.

Direct conversations validate observed personality indicators and surface emotional needs to tailor engagement appropriately.

Adapting content and approach (data/decisions vs. people/transition support) addresses each stakeholder’s emotional needs and improves buy-in.

Question 118

Topic: Process

A project is in planning for a customer-facing web portal using a hybrid approach. The team has gathered over 120 requirements from multiple departments, but the sponsor confirms the approved budget and target launch date cannot accommodate all of them. Stakeholders are now debating which features are “must have,” and the scope statement has not been finalized.

What should the project manager do next?

• A. Facilitate a requirements prioritization workshop using agreed criteria
• B. Create the WBS using the full list of collected requirements
• C. Submit a change request to increase budget and extend the schedule
• D. Escalate the disagreement to the steering committee for a decision

Best answer: A

What this tests: Process

Explanation: After collecting requirements and confirming constraints, the correct next step is to prioritize requirements with stakeholders using clear, agreed criteria (for example, business value, risk, compliance). This produces an ordered set of requirements that can be used to finalize the scope statement and plan deliveries within the approved budget and date.

The core need is to determine and prioritize requirements so the project can commit to a feasible scope. Since the constraints are confirmed and stakeholders are debating importance, the project manager should facilitate a structured prioritization with the right decision-makers (sponsor, product owner/business owner, key stakeholders) and make the criteria explicit. The outcome is a ranked set of requirements (and typically documented decisions/assumptions) that informs the scope statement, WBS/backlog ordering, and release/iteration planning.

A practical sequence is:

• Confirm prioritization criteria (value, urgency, risk, compliance)
• Facilitate ranking and resolve conflicts
• Capture the prioritized requirements and obtain approval
• Use the result to finalize scope and plan delivery

Building the WBS before prioritization locks in an unrealistic scope, and escalating or requesting more funding is premature until prioritization shows what can be delivered within constraints.

With constraints confirmed and requirements collected, the next step is to establish and apply prioritization criteria with key stakeholders to rank requirements before finalizing scope.

Question 119

Topic: Process

You are leading a hybrid product rollout with a distributed team. The sponsor escalates that decisions are being made using outdated documents, while the team complains about duplicative artifacts across email, a shared drive, and an agile tool. A regulator will audit requirements-to-test traceability in 6 weeks, and the project cannot absorb a major tool migration. What should the project manager do to continually assess and improve the effectiveness of managing project artifacts?

• A. Require weekly full updates of every project document and get sponsor approval
• B. Establish an artifact “health check” cadence with owners, quality criteria, and a single source of truth
• C. Freeze artifact access to a small admin group to prevent further inconsistencies
• D. Migrate all artifacts into a new enterprise repository before the audit

Best answer: B

What this tests: Process

Explanation: The best optimization is to put in place a lightweight, continuous mechanism to verify artifacts are current, consistent, and usable while meeting the traceability constraint. Assigning ownership, defining quality criteria, consolidating to a single source of truth, and reviewing on a short cadence improves artifact effectiveness without the risk and disruption of a major migration.

Continually assessing artifact management means regularly checking whether artifacts are accurate, easy to find, actively used for decisions, and fit for required governance (such as traceability for audits). In this scenario, the constraints are a near-term audit and no capacity for a disruptive tool change, so the best approach is lightweight, embedded inspection and control.

A practical way to do this is to:

• Identify the minimum set of “critical” artifacts (e.g., requirements, traceability, test evidence).
• Assign a clear owner and quality criteria (currency, versioning, linkage).
• Designate one system as the authoritative source and retire duplicates.
• Review on a short cadence (e.g., per iteration) and act on findings.

This improves decision quality and audit readiness without overburdening the team.

This creates lightweight, ongoing inspection and control of artifact accuracy, accessibility, and traceability without disrupting delivery.

Question 120

Topic: Process

A project is entering the next phase in a predictive environment. The project manager has collected updated inputs from the leads (scope, schedule, cost, resource, communications, risk, and procurement) and tailored them for the phase. The steering committee asks for evidence that the phase plans have been consolidated into one coherent, aligned plan before authorizing execution.

Which artifact best validates that the phase plans are consolidated and ready for approval?

• A. A resource histogram showing planned staffing by month
• B. A detailed risk register with updated response owners
• C. A WBS and WBS dictionary for the phase deliverables
• D. An integrated project management plan with approved phase baselines

Best answer: D

What this tests: Process

Explanation: The strongest validation that planning is consolidated is a single integrated project management plan that reconciles and aligns the subsidiary plans and establishes the phase baselines for scope, schedule, and cost. Governance can review one coherent package for internal consistency, feasibility, and approval. Individual planning outputs do not demonstrate integration across all knowledge areas.

Consolidating project/phase plans means integrating the subsidiary plans (scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement) into one coherent project management plan, resolving conflicts (e.g., schedule vs. resource limits), and establishing the approved baselines needed to execute and control work. For a phase gate, the best evidence of readiness is an integrated, internally consistent plan package that governance can approve as the basis for directing work and measuring performance. A single planning component (like risk, resources, or scope detail) can be high quality but still fail to show that the overall plan is aligned and feasible across constraints.

Key takeaway: approval-ready readiness is demonstrated by the integrated plan and baselines, not by isolated planning outputs.

A single integrated plan (with aligned subsidiary plans and baselines) is the primary evidence that planning has been consolidated and is ready for governance approval.

Question 121

Topic: Process

A hybrid project is delivering a customer-facing mobile app. Recent increments are being rejected during validation because different stakeholders interpret “done” differently. The project manager wants to define clear acceptance criteria and quality measures to support validation.

Which action should the project manager NOT take?

• A. Add compliance tests and defect thresholds as quality measures
• B. Let each team member define done for their work
• C. Define measurable acceptance criteria before starting each item
• D. Co-create a Definition of Done with the team and PO

Best answer: B

What this tests: Process

Explanation: To support validation, acceptance criteria and quality measures must be shared, explicit, and objectively testable. A common Definition of Done and measurable criteria create a consistent basis for verifying results and obtaining acceptance. Allowing each person to decide what “done” means creates variability and makes acceptance subjective.

Acceptance criteria and quality measures are the agreed, objective conditions used to validate that a deliverable or backlog item is acceptable. In agile/hybrid delivery, a team-level Definition of Done complements item-level acceptance criteria by setting a consistent minimum quality bar (e.g., required testing, documentation, and compliance checks).

Practical approach:

• Define acceptance criteria that are specific and testable for each item.
• Establish a shared Definition of Done with the product owner and team.
• Include relevant quality measures (such as defect thresholds and compliance tests) in the quality planning artifacts so validation is repeatable.

The key is consistency and measurability; personal or ad hoc definitions of “done” undermine reliable validation and acceptance.

Individual, inconsistent definitions of “done” prevent objective validation and predictable acceptance.

Question 122

Topic: Process

A hybrid project is delivering a customer-facing mobile app update in monthly releases. The sponsor asks the project manager to continually survey deliverable quality so the team can detect degradation early and confirm each release candidate is ready for acceptance testing. Which metric or evidence best validates deliverable quality progress in this context?

• A. Percentage of user stories moved to “Done” each iteration
• B. Count of code reviews completed per week
• C. Sprint velocity trend for the last four iterations
• D. A release quality dashboard showing test pass rate and defect leakage trend

Best answer: D

What this tests: Process

Explanation: The strongest way to continually survey deliverable quality is to use objective quality control results tied to acceptance criteria and tracked as trends over time. A dashboard combining test outcomes (pass rate) and defect leakage provides actionable evidence of conformance and readiness, and it flags quality deterioration early enough to respond before release acceptance activities.

Continually surveying deliverable quality relies on objective, product-focused evidence from quality control (inspection and testing) that demonstrates conformance to defined requirements and acceptance criteria. Trend-based measures such as test pass rate and defect leakage/escape rate validate whether the product increment is stabilizing, improving, or degrading over time, and they support release readiness decisions.

Useful evidence typically:

• Is derived from inspection/testing of the deliverable
• Is traceable to acceptance criteria/quality standards
• Shows trends (not just a one-time snapshot)

Activity or throughput measures can indicate productivity, but they do not validate the quality of what was produced.

It directly measures conformance to acceptance criteria over time and provides early warning of quality deterioration.

Question 123

Topic: People

You are managing a fully virtual, hybrid project with team members across five time zones. Work is being duplicated because requirements clarifications are happening in ad hoc chats, decisions are not captured, and people in other time zones cannot see outcomes until days later. The sponsor asks you to “fix collaboration quickly” without adding significant meeting time.

What is the best next step?

• A. Add daily cross-time-zone status meetings to ensure everyone hears the latest decisions
• B. Standardize on a single chat tool immediately and instruct the team to stop using other channels
• C. Escalate the collaboration breakdown to the sponsor and request a directive for mandatory tool compliance
• D. Facilitate a team working-session to agree on communication norms and select tools for async decisions and a single source of truth

Best answer: D

What this tests: People

Explanation: The issue is less about tool availability and more about inconsistent collaboration practices across time zones. The most effective next step is to align the team on working agreements (what goes where, response expectations, and decision capture) and then choose tools that support asynchronous visibility and traceability. This addresses root causes while minimizing additional synchronous meeting load.

In virtual, multi-time-zone teams, effective collaboration depends on clear norms and tools that support asynchronous transparency (captured decisions, searchable context, and a single source of truth). When people rely on ad hoc chats, information becomes fragmented and time-zone gaps amplify delays and rework.

The best sequence is:

• Align on team working agreements (channels, decision logging, response times, meeting purpose).
• Select and configure a small set of tools to match those agreements (e.g., decision log/wiki + backlog/board + chat + video).
• Communicate and reinforce usage, then inspect and adapt.

Mandating a tool or escalating to the sponsor is premature until the team has agreed on how it will collaborate and what outcomes the tools must enable.

This establishes shared working agreements and purpose-fit synchronous/asynchronous tools before enforcing usage, reducing rework without adding meetings.

Question 124

Topic: Process

Which PMP artifact is the formally approved, integrated document that consolidates subsidiary plans and baselines and is used to guide project execution and control within the organization’s governance and constraints?

• A. Business case
• B. Benefits management plan
• C. Project management plan
• D. Project charter

Best answer: C

What this tests: Process

Explanation: The project management plan is the approved, integrated plan that pulls together subsidiary plans and baselines and defines how the project will be executed, monitored, and controlled. Because it is baselined and managed through change control, it helps keep delivery aligned with organizational constraints and governance expectations.

The core term is the project management plan: the integrated, approved document that consolidates all subsidiary plans (for example, scope, schedule, cost, quality, resources, communications, risk, procurement, stakeholder engagement) along with the project baselines. It is the primary reference for directing work and for monitoring and controlling performance through governance mechanisms such as change control.

In practice, it keeps integrated planning aligned because it:

• defines how work will be performed and measured against baselines
• specifies how changes will be evaluated, approved, and incorporated
• provides a single, consistent source for decisions and reporting within governance constraints

Artifacts like the charter and business case justify and authorize the project, but they do not serve as the integrated execution-and-control plan.

It integrates the baselines and subsidiary plans and becomes the primary approved reference for directing and controlling the project under governance.

Question 125

Topic: Process

A predictive project is in execution with approved scope, schedule, and cost baselines. A new regulation is announced and a compliance stakeholder requests adding an encryption feature. The sponsor says, “Just build it—there’s no time for paperwork.” The change would likely affect schedule and budget.

What should the project manager do next?

• A. Document the request and perform an impact analysis for formal change review
• B. Direct the team to start the encryption work immediately
• C. Escalate to the sponsor’s manager to get a decision
• D. Update the baselines to include the encryption feature

Best answer: A

What this tests: Process

Explanation: To embrace needed change without losing control of the baselines, the project manager should first capture the change request and assess its impacts. An impact analysis provides the information required for the formal decision body to approve, defer, or reject the change. This follows change management practices while still responding to the regulatory need.

The core concept is integrated change control: even when change is necessary (for example, regulatory compliance), work should not proceed outside the approved baselines. The project manager’s next step is to formally document the change request and analyze impacts (scope, schedule, cost, risk, and quality) so decision-makers can evaluate options and trade-offs.

Typical sequence:

• Record the request (change log/change request)
• Analyze impacts with the team and relevant experts
• Submit for the defined approval path (e.g., CCB/sponsor per governance)
• After approval, update baselines and communicate/implement

Starting work or updating baselines before approval undermines governance and creates uncontrolled scope growth.

Changes should be captured and assessed for impacts before seeking approval through the defined change control process.

Questions 126-150

Question 126

Topic: Process

A project is in execution on a fixed delivery date with limited contingency reserve. The risk register includes a risk that a critical component supplier may miss a shipment, with the trigger defined as “supplier confirms lead time -> 6 weeks.” In today’s vendor call, the supplier confirms an 8-week lead time, and the team has not held a formal risk review in over a month.

As the project manager, what is the BEST next action?

• A. Implement the planned contingency response immediately and inform stakeholders later
• B. Submit a change request to extend the schedule baseline due to the supplier delay
• C. Hold an immediate risk review to reassess exposure, update responses and priorities, and assign owners
• D. Escalate to the sponsor to request additional contingency reserve

Best answer: C

What this tests: Process

Explanation: A defined risk trigger has been met, and regular reviews have lapsed, so the priority is to perform a timely risk review. This confirms current probability/impact, validates assumptions, and updates response actions, owners, and risk priorities based on the latest information. Acting or escalating first can waste limited reserves or bypass needed re-prioritization.

Monitoring risk triggers and conducting regular risk reviews help ensure responses stay aligned to current conditions. Here, the trigger condition is met (8-week lead time exceeds the 6-week threshold), so the team should immediately review the risk: confirm updated probability/impact, check for secondary risks, and decide whether to execute the planned response or select an alternative.

A practical next step is to:

• Update the risk register (status, exposure, trigger met)
• Re-prioritize risks and confirm response strategy (avoid/mitigate/transfer/accept)
• Assign/confirm owners and near-term actions, then communicate outcomes

Escalation, contingency execution, or baseline changes may follow, but they should be based on an updated risk review so the response and priorities reflect the latest exposure and constraints (limited reserve and fixed date).

The trigger has occurred, so the team should promptly review and update the risk register, response plans, and priorities before taking further action.

Question 127

Topic: People

Which term best describes a team-created and team-maintained set of explicit rules for how the team will work together, such as meeting norms, decision rules, and a shared Definition of Done, to improve predictable delivery?

• A. Project charter
• B. Team working agreement
• C. Product backlog
• D. Communications management plan

Best answer: B

What this tests: People

Explanation: A team working agreement captures how the team will operate day to day, including norms for meetings, how decisions are made, and shared quality expectations such as a Definition of Done. Because it is created and owned by the team, it can be revisited and adjusted to sustain predictable delivery as conditions change.

The core concept is establishing team ground rules to enable consistent collaboration and execution. A team working agreement is a lightweight, team-owned artifact that makes expectations explicit (for example: meeting etiquette and cadence, decision-making method, escalation/conflict norms, and shared completion criteria such as a Definition of Done). Because delivery environments evolve, the agreement is also maintained over time—reviewed and updated when friction appears or when the team’s context changes—so the team keeps a stable way of working that supports predictability. Other plans or documents may mention communications or governance, but they are not the team’s day-to-day working rules owned and adjusted by the team.

It is a collaboratively defined set of ground rules (norms, decision rules, DoD) that the team uses and updates to guide day-to-day collaboration.

Question 128

Topic: Process

You are managing a hybrid project to implement a patient scheduling system. Several project artifacts (requirements, defect logs, test evidence) contain patient identifiers, and external vendor staff need access to some—but not all—documents. Your organization requires least-privilege access, auditability, and a 7-year retention period for regulated records. What is the best way to make project artifacts accessible to stakeholders?

• A. Store artifacts on an open team wiki for easy access
• B. Email artifacts to stakeholder distribution lists as needed
• C. Keep artifacts in the project manager’s personal cloud folder
• D. Use an enterprise document repository with RBAC and retention policies

Best answer: D

What this tests: Process

Explanation: A centralized, organization-approved document repository with role-based access control and retention rules best balances accessibility with security, privacy, and records retention requirements. In regulated environments, artifact storage must support least-privilege access, audit trails, and controlled retention/defensibility. This enables the right stakeholders (including vendors) to access only what they are authorized to see while meeting compliance obligations.

The core requirement is to make artifacts accessible while meeting security, privacy, and retention controls. When artifacts include regulated or sensitive data (such as patient identifiers), the project should use an approved system of record that supports role-based access control (so vendors and internal roles see only what they need), audit logs (so access and changes are traceable), and retention/disposition controls (so required records are preserved for the mandated period). This approach also reduces version confusion by keeping one authoritative source and avoids uncontrolled duplication. Convenience-focused sharing methods are insufficient if they cannot enforce least-privilege access and retention consistently.

It provides controlled, auditable access while enforcing privacy and required retention for regulated artifacts.

Question 129

Topic: Process

On a hybrid project with a distributed team, the project manager sends a detailed message announcing a revised integration cutover date and new responsibilities for several component owners. In the next few days, different teams ask conflicting questions, suggesting the message was not interpreted consistently.

Which TWO actions should the project manager take to confirm the communication is understood and that feedback is received? (Select TWO)

• A. Send a brief follow-up requesting each impacted stakeholder to reply with impacts, questions, and confirmation of their updated dates
• B. Wait until the next status report cycle to see whether the teams implemented the change correctly
• C. Upload the message to the document repository so everyone can reference it later
• D. Ask each impacted owner to restate their understanding of the change and their next steps during the next coordination meeting
• E. Add more senior leaders in cc to increase compliance with the message
• F. Request email read receipts and treat opened messages as confirmation

Correct answers: A, D

What this tests: Process

Explanation: Use closed-loop communication techniques that require recipients to demonstrate understanding and provide responses. Having owners restate the change verifies interpretation in real time, while a structured follow-up response captures impacts and questions from those who could not attend or need time to assess. Together, these actions validate comprehension and ensure feedback is received and addressed before execution diverges.

To confirm communication is understood, the project manager should use closed-loop communication, where the sender verifies how the receiver interpreted the message and invites a response. In this scenario, the confusion indicates the message was received but not consistently understood.

Effective ways to close the loop include:

• Use a “teach-back” in a meeting: ask each impacted owner to summarize what changed, their actions, and any risks.
• Require an explicit response (reply, form, or confirmation message) that captures impacts, questions, and updated commitments.

Passive approaches (posting information, adding cc’s, or waiting for outcomes) do not verify comprehension and delay discovery of misalignment.

A structured “teach-back” confirms shared understanding and exposes gaps immediately.

A required response creates a feedback loop and validates that recipients understood and can act on the message.

Question 130

Topic: Process

You are leading a hybrid project to enhance a hospital’s medication-dispensing system. The dosing logic changes are subject to strict regulatory documentation and formal sign-offs, while the user interface has high uncertainty and will evolve based on pharmacist feedback. The delivery team is newly formed and has limited agile experience, and hospital compliance stakeholders expect predictable checkpoints.

Which action SHOULD AVOID when tailoring the project approach?

• A. Add compliance-focused acceptance criteria and scheduled sign-off checkpoints into the plan
• B. Provide agile coaching and define working agreements before starting iterative UI work
• C. Use a hybrid approach: predictive governance for regulated logic and iterative development for the UI
• D. Run all work as pure agile with minimal documentation and no formal stage-gates

Best answer: D

What this tests: Process

Explanation: Tailoring should balance uncertainty with constraints like regulation, stakeholder governance needs, and team maturity. In this scenario, regulated components require documentation and formal approvals, while the UI benefits from iterative learning. The approach to avoid is the one that discards necessary controls and assumes high agile maturity that the team does not have.

Tailoring the methodology means selecting practices that fit the work and the environment. Here, regulatory constraints and compliance stakeholder expectations require defined documentation, traceability, and formal decision points—especially for safety-critical dosing logic. At the same time, the UI has high uncertainty, so iterative discovery with frequent pharmacist feedback is appropriate. Because the team is new and has limited agile experience, adding coaching and clear working agreements reduces execution risk and supports a sustainable pace. The anti-pattern is adopting a one-size-fits-all approach that removes governance and documentation needed for regulated deliverables.

Key takeaway: match higher-uncertainty work to iterative practices, but keep predictive controls where regulation and stakeholder governance demand them.

This ignores regulatory constraints and stakeholder expectations for formal documentation and approvals, and it is high risk for an immature team.

Question 131

Topic: People

A Scrum team has missed its last two sprint goals because the same environment access problem keeps resurfacing. In daily standups, team members mention “still waiting on IT,” but no one can say who is responsible for following up, what was already tried, or when it should be escalated. The scrum master is new and tracks blockers only in personal notes.

What is the most likely underlying cause of the repeated impediment?

• A. The team is taking on too much work each sprint
• B. The team lacks the technical skills to configure environments
• C. No shared impediment log and unclear escalation/ownership rules
• D. IT support is understaffed and cannot meet demand

Best answer: C

What this tests: People

Explanation: The symptoms point to an impediment management breakdown rather than a purely technical or capacity issue. A transparent impediment log with named owners and clear escalation rules is needed so blockers are prioritized, tracked to closure, and escalated promptly when external teams are involved.

In agile delivery, impediments that require action outside the team (for example, IT access) must be explicitly owned, tracked, and escalated. The key clues are that nobody can state the owner, actions taken, or escalation timing, and the scrum master is tracking blockers only in personal notes. That indicates there is no shared mechanism to prioritize and drive impediments to closure.

A practical approach is:

• Capture each blocker in an impediment log visible to the team and stakeholders.
• Assign a single owner and due date, and define escalation triggers (time/impact).
• Review impediments frequently and escalate per the agreed path.

If those governance basics are missing, the same issue will recur even if the team is performing well in other areas.

Without a visible impediment log and explicit ownership/escalation rules, blockers are not tracked, prioritized, or driven to resolution across boundaries.

Question 132

Topic: People

You are leading an experienced, cross-functional agile team delivering a customer-facing mobile app. The product owner is available daily, and the team has a strong track record of self-organizing. A new integration approach is needed, and several developers disagree on the best option.

Which leadership approach SHOULD AVOID in this situation?

• A. Encourage constructive conflict and reinforce working agreements for debate
• B. Make the technical decision yourself and assign tasks to enforce it
• C. Coach the team to reach a decision and document the rationale for alignment
• D. Facilitate a time-boxed workshop to evaluate options and agree on criteria

Best answer: B

What this tests: People

Explanation: With an experienced, self-organizing team and a product owner available, the project manager should use a collaborative or coaching style to help the team evaluate alternatives and build shared commitment. A directive, top-down decision is an anti-pattern here because it bypasses team ownership and can reduce engagement and quality of the decision.

Leadership style should be tailored to the team’s capability and the nature of the problem. In this scenario, the team is experienced and accustomed to self-organization, and the challenge is selecting an integration approach where multiple valid viewpoints exist. A collaborative or coaching stance is most appropriate: facilitate a structured discussion, help the team define decision criteria, surface risks and assumptions, and support alignment on a solution and rationale. Using an overly directive style (making the decision unilaterally and assigning tasks to enforce it) may create compliance without commitment, suppress useful dissent, and weaken team accountability. The key takeaway is to reserve directive leadership for situations like safety, compliance, or low-skill/low-clarity execution—not for enabling capable teams to solve complex problems.

A directive, decision-by-authority approach undermines a capable self-organizing team when collaboration is needed to evaluate options and gain commitment.

Question 133

Topic: Process

You are leading a hybrid project to enhance software used in a regulated medical laboratory. Requirements are still evolving, but the quality manager and external auditor require objective evidence that each critical requirement is verified and traceable before any release can be deployed.

At the end of an iteration, which metric/evidence/artifact best validates that the increment is ready for release in this context?

• A. Requirements traceability matrix with approved verification results
• B. Percentage of user stories moved to Done this iteration
• C. Team velocity increasing over the last three iterations
• D. Sprint burndown chart reaching zero remaining work

Best answer: A

What this tests: Process

Explanation: In regulated work, readiness is validated by objective compliance evidence, not by delivery activity or throughput. A traceability matrix tied to documented verification results demonstrates that critical requirements were built and tested as required and can be audited. This best fits stakeholder expectations and the regulatory constraint while still supporting iterative delivery under uncertainty.

Tailoring for a regulated, high-uncertainty project means you can iterate to learn, but you must validate progress with artifacts that satisfy governance and audit needs. For release readiness, stakeholders typically need evidence that (1) agreed critical requirements are complete, (2) verification/validation was executed with results recorded, and (3) each requirement is traceable to design, tests, and outcomes. A requirements traceability matrix linked to approved verification results provides this objective, auditable proof and also helps a less-mature team be consistent by making compliance part of the definition of done. Activity and flow metrics can support forecasting and team improvement, but they do not demonstrate compliance or acceptance readiness.

In a regulated environment, traceability plus documented verification provides objective release-readiness evidence.

Question 134

Topic: Process

A hybrid project is in execution with a fixed go-live date mandated by a customer contract. A critical supplier issue was just resolved, but a new cybersecurity vulnerability affecting the product was discovered and an external audit is scheduled in 6 weeks. The risk register has not been reviewed since the last quarterly governance meeting.

What is the project manager’s BEST next action?

• A. Escalate the vulnerability to the steering committee and wait for direction before updating any risk information
• B. Facilitate a timeboxed risk reassessment with the team and SMEs, then update and reprioritize the risk register and response actions
• C. Implement the existing contingency plans for all previously high-ranked risks to protect the go-live date
• D. Submit a change request to extend the schedule due to the newly discovered cybersecurity vulnerability

Best answer: B

What this tests: Process

Explanation: Conditions have materially changed (a new vulnerability and an imminent audit), so the priority is to reassess risks with the right stakeholders and refresh prioritization. Updating the risk register and response actions ensures the team focuses on the most significant current risks and integrates responses into near-term plans without relying on outdated rankings.

Iteratively assessing and prioritizing risks means regularly revisiting the risk landscape as new information emerges and then re-ranking risks so responses target what matters now. In this scenario, a resolved supplier issue and a newly discovered cybersecurity vulnerability (with an audit in 6 weeks) change both the probability/impact profile and urgency of multiple risks.

A strong next step is to:

• Convene a focused risk review with the delivery team and relevant SMEs
• Identify new risks and retire/adjust outdated ones
• Reassess probability, impact, and urgency; then reprioritize
• Update owners and integrate response actions into the hybrid plan/backlog

This keeps risk management current and action-oriented, rather than acting on stale priorities or delaying analysis until governance meets.

This enables iterative risk identification, analysis, and reprioritization based on changed conditions and near-term constraints (audit and fixed go-live).

Question 135

Topic: Process

You are taking over a hybrid project with a distributed team and a regulatory audit scheduled in two months. Several key artifacts (requirements/backlog, design decisions, change log, and test evidence) exist in different tools and locations. To improve traceability, you are defining artifact ownership and the artifact lifecycle (create, review, approve, store, retire).

Which approach should you NOT use?

• A. Assign each artifact an accountable role and define archival/retirement rules
• B. Let individuals keep “working copies” in email and personal drives
• C. Create an artifact register with owners, approvers, and repositories
• D. Define review/approval steps and versioning in the project management plan

Best answer: B

What this tests: Process

Explanation: Artifact governance requires clear ownership plus a controlled lifecycle so teams can prove what was created, who approved it, where the current version lives, and what was archived. Allowing uncontrolled “working copies” in personal locations creates multiple sources of truth and undermines review, approval, and retention. That directly increases audit and delivery risk in a distributed environment.

Managing project artifacts means deliberately defining who is accountable for each artifact and how it moves through create, review, approve, store, and retire. In a distributed, audit-exposed project, the key need is a single source of truth with version control and an explicit approval path so traceability is preserved.

A practical setup is to:

• Identify the key artifacts that require control (e.g., baseline items, compliance evidence)
• Assign an owner and an approval authority for each artifact
• Specify where the authoritative version is stored (controlled repository) and how versions/changes are handled
• Define retention, archival, and retirement rules

Uncontrolled personal storage is the opposite of an artifact lifecycle: it weakens configuration management, makes approvals non-verifiable, and increases the chance the team uses outdated information.

Decentralized, informal storage breaks version control, approval traceability, and retention/archival discipline needed for audits.

Question 136

Topic: Process

Midway through a hybrid software project, the quality management plan includes scheduled process audits and peer reviews to verify the team is following agreed development standards. To recover two weeks of schedule slip, the project manager decides to cancel the audits and peer reviews for the next month and rely only on end-of-sprint testing to detect defects.

What is the most likely near-term impact of this decision?

• A. More defects escape to testing, increasing near-term rework
• B. The project will capture more lessons learned for future work
• C. The customer will reject the final product at acceptance
• D. The quality management plan must be reapproved by governance

Best answer: A

What this tests: Process

Explanation: Process audits and peer reviews are quality assurance activities focused on preventing defects by verifying the process is being followed. Canceling them shifts detection to quality control testing, which finds problems after they are introduced. In the near term, the team is more likely to discover more defects during testing and spend time on rework within upcoming iterations.

Quality planning defines the standards, metrics, methods, and acceptance criteria in artifacts like the quality management plan. Quality assurance focuses on process-focused, preventive activities (for example, audits and peer reviews) to confirm the team’s work approach is capable of producing conforming results. Quality control is product-focused and detective (for example, testing and inspections) to verify deliverables meet acceptance criteria.

In this scenario, canceling audits and peer reviews removes key assurance feedback loops. The most immediate consequence is that process nonconformities persist unnoticed, so more defects are introduced and then discovered later during end-of-sprint testing, driving rework and churn. Longer-term outcomes like customer rejection may occur, but the near-term impact is increased defects found in QC.

Removing quality assurance activities reduces defect prevention, so issues are found later during quality control and require rework.

Question 137

Topic: Business Environment

You are managing a hybrid project delivering a customer data portal. A new regulation was announced that affects the product scope. Your organization requires governance approval for any change that impacts the release date or budget.

Exhibit: Change request summary (CR-17)

Change: Add audit logging + 7-year data retention
Driver: New regulation (effective in 12 weeks)
Current release: 10 weeks; budget cap: \$800,000
Effort impact: +2 sprints with current team
Option to keep date: add 2 contractors (+\$45,000 total)
Management reserve available: \$60,000
Constraint: Compliance work cannot be deferred

Based on the exhibit, what should the project manager recommend next?

• A. Submit CR-17 with trade-off options for governance approval
• B. Reject CR-17 because the budget is capped
• C. Reprioritize the backlog and start the work immediately
• D. Defer compliance items to a post-release patch

Best answer: A

What this tests: Business Environment

Explanation: This is an externally driven, non-deferrable compliance change that will impact either schedule (add sprints) or cost (add contractors). Because the organization requires governance approval for changes affecting date or budget, the project manager should package the alternatives and submit the change for decision. After approval, the PM updates the baseline plans and backlog accordingly.

When an external business environment change creates a mandatory requirement (for example, regulation), the project manager’s role is to assess impacts and recommend response options that balance constraints. The exhibit already quantifies two viable paths: extend the schedule by two sprints with the current team, or maintain the date by using management reserve to fund contractors. Because either path changes approved commitments (date and/or budget), the PM should not implement unilaterally; the appropriate action is to submit the change with these trade-offs to the governance body for approval, then update the release plan/backlog and communicate the approved decision. The key takeaway is to convert the external change into an approved scope/backlog change with explicit cost/schedule impacts.

The exhibit shows a mandatory external change with defined cost/schedule options, so the next step is formal approval of the selected option before updating plans/backlog.

Question 138

Topic: People

A project manager brings two team members into a meeting to openly discuss the root cause of their disagreement, explore alternatives, and reach a solution that satisfies both parties’ key needs. Which conflict resolution technique is being used?

• A. Smooth/accommodate
• B. Force/direct
• C. Collaborate/problem solve
• D. Compromise/reconcile

Best answer: C

What this tests: People

Explanation: The described approach seeks a win-win outcome by jointly exploring the root cause and generating options that meet both parties’ needs. That is the hallmark of collaborating/problem solving, which is typically the most effective technique when time allows and preserving relationships is important.

Collaborating (also called problem solving) is a conflict resolution technique where the parties work together to understand the real source of the conflict and develop a solution that fully addresses key interests on both sides. It is characterized by open discussion, analysis of root causes, and generating alternatives to reach a mutually beneficial (win-win) agreement.

In the scenario, the project manager explicitly facilitates:

• Open discussion between the parties
• Root-cause exploration
• Option generation to satisfy both parties’ needs

That combination aligns with collaborating, not with faster but less durable approaches like compromising, smoothing, or forcing.

It focuses on addressing underlying causes to achieve a win-win solution that satisfies both parties.

Question 139

Topic: Process

A hybrid CRM implementation project is tracking progress with a weekly dashboard, plus ad hoc communications for major risks. During testing, the team identifies a critical integration defect and believes the go-live date may slip by about two weeks, but the impact and workaround options are not yet confirmed. A sales vice president has heard rumors and asks the project manager for an update today.

What is the best next step?

• A. Escalate to the steering committee to determine what to communicate
• B. Confirm impact with leads, then send a targeted ad hoc update
• C. Wait for the next weekly dashboard to avoid sharing unconfirmed information
• D. Send an immediate email to all stakeholders about the potential delay

Best answer: B

What this tests: Process

Explanation: The project manager should provide timely, accurate information using the agreed communications approach. Since the schedule impact is not yet confirmed, the next step is to quickly validate the key facts with the responsible leads and then issue an ad hoc update to the impacted stakeholders. This maintains transparency while avoiding the spread of unvetted or misleading information.

Effective communication balances speed with accuracy and follows the communications management approach already agreed for the project. Here, a potentially major risk is generating rumors and a senior stakeholder is requesting an update, so waiting for the regular dashboard is too slow. At the same time, broadcasting an unconfirmed delay to everyone can create unnecessary alarm and rework.

Best next step:

• Rapidly validate the current impact, confidence level, and near-term plan with the responsible leads
• Communicate a concise, targeted ad hoc update to the appropriate stakeholders (what happened, current assessment, when the next update will be)

The key is to control the message with verified information and predictable follow-up rather than escalating prematurely or over-communicating speculation.

It verifies the facts first, then communicates promptly using the agreed ad hoc channel for major risks.

Question 140

Topic: People

Midway through a hybrid product implementation, a recurring issue is slowing delivery: the development team waits days for approvals because different functional managers give conflicting directions on priorities and who can make decisions. The project sponsor asks the project manager to “fix the confusion” without adding new governance layers.

What is the best next step?

• A. Escalate the conflict to the sponsor for an immediate decision on priorities
• B. Facilitate a working session to update the team charter with roles, decision rights, and escalation rules
• C. Submit a change request to add a formal approval board to the governance structure
• D. Publish a RACI based on the org chart and direct managers to follow it

Best answer: B

What this tests: People

Explanation: The problem is ongoing confusion about roles and decision authority, which is exactly what a team charter/working agreement is meant to address. The best next step is to convene the team and key stakeholders to explicitly agree on decision rules, ownership, and escalation paths, then document and socialize them. This creates shared expectations and speeds decisions without adding unnecessary bureaucracy.

A team charter (or working agreement) aligns how the team will work by making goals, roles, and decision rules explicit and agreed. In this scenario, delivery is slowed because decision authority and priority-setting are unclear and inconsistent across functional managers. The project manager should first bring the right people together to re-establish a shared operating model rather than immediately escalating or adding governance.

A practical sequence is:

• Facilitate a session with the team and relevant functional representatives
• Agree and document decision rights (who decides priorities/acceptance)
• Define escalation paths and timeboxes for decisions
• Confirm buy-in and communicate the updated agreement

Escalation and governance changes are options later if the agreed working agreement is not respected or proves insufficient.

A refreshed, team-owned working agreement clarifies who decides what and how conflicts are resolved, reducing delays without premature escalation.

Question 141

Topic: People

A vendor supporting a critical project component requests a contract adjustment due to a new technical requirement. The procurement manager reminds you that only the sponsor can approve any agreement that changes total contract value by more than $25,000 or shifts a regulatory milestone. You have a negotiation meeting with the vendor tomorrow.

Which should you use to establish the bounds of what you can agree to in the negotiation?

• A. Log the request as an issue and ask the team to choose concessions
• B. Submit the vendor request to the CCB before discussing it
• C. Obtain a sponsor-approved negotiation mandate with clear limits
• D. Develop your BATNA based on current market pricing

Best answer: C

What this tests: People

Explanation: When negotiating agreements, the most important boundary is what you are authorized to commit to on behalf of the organization. Since governance restricts changes over $25,000 and any regulatory milestone impacts, you need a clear, sponsor-approved negotiation mandate (limits and escalation path) before the vendor meeting.

Negotiation bounds are the acceptable ranges and non-negotiables you can commit to, based on objectives, constraints, and—critically—your delegated authority. In this scenario, procurement governance explicitly limits what you can approve (cost and regulatory milestone impacts). Before negotiating, you should confirm the sponsor’s position and document a negotiation mandate (e.g., targets, minimum/maximum acceptable outcomes, and what must be escalated). This lets you negotiate efficiently while avoiding unauthorized commitments that could violate governance or create an unapproved change.

A strong BATNA is useful, but it does not override formal authority limits or regulatory constraints.

Because your negotiation boundaries are constrained by delegated authority and governance thresholds, you must confirm and document what you can commit to before negotiating.

Question 142

Topic: People

You are negotiating a change order with a software vendor on a hybrid project. The vendor says the additional integration work will cost $120,000 and will push go-live by 3 weeks, or they can keep the date if the team removes a required security control. Your sponsor set a hard go-live date due to a regulatory filing and capped total additional funding at $80,000. Your delegation of authority allows you to approve up to $50,000; higher amounts require steering committee approval.

What should you do to best optimize reaching an agreement while staying within the negotiation bounds?

• A. Accept removing the security control to keep the go-live date
• B. Commit to $80,000 and sign the change order now to meet the date
• C. Counteroffer within the cap and your authority, state non-negotiables, and prepare to escalate if no overlap
• D. Agree to the $120,000 increase to protect the relationship

Best answer: C

What this tests: People

Explanation: The negotiation bounds are set by non-negotiable constraints (regulatory go-live date and required security control) plus cost and approval limits. The best move is to make a counteroffer that fits within the $80,000 cap and your $50,000 authority, while explicitly reserving escalation for amounts requiring approval. This maximizes the chance of a timely agreement without overcommitting.

Effective negotiation starts by identifying what is fixed versus variable, then negotiating only within that space. In this scenario, the go-live date and security control are hard constraints, and your negotiating authority and the sponsor’s funding cap define financial limits. The best approach is to make a counteroffer that stays within your approval limit (or is explicitly contingent on governance approval), while exploring trades that could create overlap with the vendor’s position.

A practical way to apply the bounds is:

• State the non-negotiables (date and security control) and your approval limits.
• Offer a package within the cap and authority (e.g., reprioritized scope, phased delivery, or shared tasks to reduce vendor effort).
• If there is no ZOPA, escalate per governance rather than committing beyond authority.

The key takeaway is to negotiate value within constraints and decision rights, not around them.

This keeps the negotiation inside the limits (date and security fixed, cost and authority capped) while seeking a ZOPA and using escalation only if needed.

Question 143

Topic: People

In a hybrid product development project, three consecutive iterations have missed the sprint goal because the test environment becomes unavailable during peak hours. The team has been using temporary workarounds, but the outages keep recurring and different people describe different triggers (access changes, configuration drift, and vendor maintenance windows).

Which technique should the project manager use to identify and remove the systemic impediment?

• A. Facilitate a cause-and-effect (fishbone) analysis workshop
• B. Ask the team to apply the 5 Whys to the most recent outage
• C. Document each outage in the issue log and assign owners
• D. Add schedule buffers to protect sprint goals from future outages

Best answer: A

What this tests: People

Explanation: Because the outages are recurring and appear to have multiple contributing factors, the best next step is a structured root cause analysis technique that supports broad cause exploration. A cause-and-effect (fishbone) analysis helps the team categorize and validate potential sources (people, process, tools/vendor, environment) and focus corrective actions on systemic fixes rather than repeated workarounds.

The core concept is removing impediments by addressing root causes, not just documenting or compensating for symptoms. When a blocker repeats across iterations and the triggers are inconsistent, treat it as a systemic problem with potentially multiple contributing causes.

A cause-and-effect (fishbone) analysis is well-suited here because it:

• Structures brainstorming across common cause categories
• Helps surface contributing factors beyond the last incident
• Enables the team to identify root causes and define preventative actions

Techniques like logging issues or adding buffers may manage visibility or impact, but they don’t eliminate the underlying conditions creating the repeated outages.

A fishbone diagram helps the team explore multiple contributing causes and converge on root causes to eliminate the recurring environment outage.

Question 144

Topic: People

A project manager is leading a hybrid project with a virtual, cross-functional team. Two key contributors regularly clash in planning meetings: one pushes for rapid decisions and high-level direction, while the other insists on detailed analysis and risks. The conflict is starting to affect iteration commitments.

The organization supports using validated personality indicators for team development, and the team has not used one on this project.

What should the project manager do next?

• A. Assign the two contributors to separate workstreams to reduce friction
• B. Escalate the conflict to functional managers for resolution
• C. Revise the communications plan based on observed meeting issues
• D. Have the team complete a personality indicator and debrief together

Best answer: D

What this tests: People

Explanation: Personality indicators help the project manager assess behavioral preferences that are driving recurring conflict (for example, pace of decision-making versus need for detail). Facilitating a voluntary assessment and structured debrief builds self-awareness and shared language so the team can tailor communication and decision-making. This is an appropriate next step before escalation or structural changes.

Applying emotional intelligence includes building awareness of how different people prefer to communicate, decide, and process information. In this situation, repeated conflict suggests a pattern rooted in differing behavioral preferences, not a one-time misunderstanding. A practical next step is to use an agreed, validated personality indicator to assess those preferences and then facilitate a debrief so the team can translate insights into specific collaboration adjustments.

A useful sequence is:

• Explain purpose, confidentiality, and obtain voluntary participation
• Run the assessment and share results in a facilitated session
• Convert insights into updated working agreements (meeting norms, decision rules)

Escalation or reassigning work may be needed later if behavior remains harmful, but assessing preferences first enables a targeted, team-owned solution.

Using a personality indicator to assess behavioral preferences enables a targeted agreement on how the team will communicate and decide.

Question 145

Topic: Process

A project is entering transition to operations, and a new support team will take over the solution. The sponsor asks you to “set expectations for the working environment” so knowledge transfer sessions can start next week, but you have not met the receiving team yet.

What should you ask/verify FIRST before deciding how to run knowledge transfer?

• A. Which lessons learned should be added to the organizational repository?
• B. Can the project team publish a detailed transition schedule today?
• C. Can the sponsor approve overtime to accelerate the transition?
• D. What tools, access, hours, and locations will the receiving team use?

Best answer: D

What this tests: Process

Explanation: Setting expectations for the working environment during knowledge transfer requires clarifying the receiving team’s practical constraints first. Understanding their tools, access needs, work hours, and location/time-zone realities lets you tailor sessions, materials, and handoff mechanisms so operations can sustain the solution. Without this information, any plan risks being unusable or ignored.

The core concept is to clarify the target operating environment before committing to a knowledge transfer plan. In a continuity handoff, “working environment expectations” are about how the receiving team will actually work day-to-day (availability, tools, access, collaboration channels, and constraints), because those factors determine the format, timing, and artifacts needed for an effective transfer.

A practical sequence is:

• Identify the receiving team and their operating model (on-call, shifts, time zones).
• Confirm required access, tools, and repositories for training and documentation.
• Then plan sessions, assign owners, and publish the transition schedule.

Requests about overtime, repositories, or publishing a detailed schedule can be valid later, but they assume key environment details that are not yet known.

You must first understand the receiving team’s working conditions and constraints so the knowledge transfer approach and expectations are realistic and usable.

Question 146

Topic: Business Environment

A hybrid project is deploying a customer portal for a financial services company. A key requirement in the charter is compliance with the organization’s security standard and applicable data-privacy regulations. Development is nearly complete, and leadership asks for evidence that the solution is ready for release from a compliance standpoint.

Which artifact best validates compliance readiness for go-live?

• A. A signed security and privacy compliance attestation with audit test results
• B. Minutes from the weekly compliance working group meetings
• C. A penetration test was scheduled and resources were assigned
• D. A report showing 95% of security user stories are completed

Best answer: A

What this tests: Business Environment

Explanation: Compliance readiness is best validated by objective evidence that required controls were tested and met, plus documented approval to release. A signed compliance attestation backed by audit/security test results provides verifiable proof that the product satisfies the security and privacy requirements defined for go-live.

To confirm project compliance requirements, the strongest evidence is objective, test-based validation tied to the compliance criteria and accompanied by formal acceptance/authorization to proceed. For security and data privacy, that typically means documented results from required assessments (e.g., control testing, audit procedures, security validation) and a sign-off/attestation from the authorized compliance function.

Completion percentages, meeting notes, and planned activities can indicate effort or coordination, but they do not prove the solution meets regulatory and organizational compliance requirements. The key is traceable evidence that required controls were tested with acceptable outcomes and that an authorized party has approved release based on those outcomes.

A formal attestation supported by audit evidence demonstrates the solution meets stated compliance requirements for release.

Question 147

Topic: People

A distributed Scrum team has missed the last three sprint goals. Most stories are completed through development but sit in “Ready for Test” for several days. The product owner attends refinement and acceptance criteria are clear. Developers report they are frequently blocked waiting for access to a shared test environment; only the operations group can provision or restart it, and their turnaround averages 4–5 business days.

What is the most likely primary underlying impediment?

• A. Delayed operations support for provisioning and maintaining the test environment
• B. Poorly defined requirements causing rework late in the sprint
• C. Low developer productivity resulting in unfinished development work
• D. Too many stories started at once, creating excess work in progress

Best answer: A

What this tests: People

Explanation: The dominant constraint is the team’s dependency on operations to access a shared test environment with multi-day turnaround. That external bottleneck prevents work from flowing to “done,” even when requirements are clear and development is largely complete. Removing or mitigating this dependency is the key impediment to address.

An impediment is the most constraining factor that repeatedly prevents the team from completing work. Here, the pattern is consistent: work accumulates after development, and progress stops at testing because the environment is controlled by another group with long lead times. That points to an external dependency and inadequate operational enablement (e.g., no timely provisioning, no self-service access, no agreed support model) as the primary blocker.

A good diagnosis focuses on where flow stops and what the team cannot change on its own. Since refinement is happening and stories are largely built, the root issue is not requirements or effort; it’s the environment/access constraint that must be addressed through coordination, escalation, or a new support agreement.

The consistent waiting on an external group for a critical environment is the blocker driving the repeated carryover.

Question 148

Topic: People

You are taking over a hybrid product implementation with a cross-functional team and several external stakeholders. Decisions have been delayed because different people are influencing priorities outside the formal governance meetings. You plan to analyze team members’ and stakeholders’ influence to improve decision-making and engagement.

Which action should you NOT take when analyzing influence?

• A. Rely primarily on job titles and the org chart to determine influence
• B. Validate the influence assessment with the sponsor and update engagement and communications approaches
• C. Create an influence-focused stakeholder map (for example, power/interest plus informal networks)
• D. Interview key team members and stakeholders to understand who influences decisions

Best answer: A

What this tests: People

Explanation: Influence analysis must account for both formal authority and informal influence patterns. Relying mainly on titles and org charts can overlook informal leaders, gatekeepers, and relationship networks that are driving delays in the scenario. Using direct inputs and validating findings enables a more accurate engagement strategy and faster decisions.

Analyzing influence is about understanding who can shape outcomes and decisions in practice, not just who appears powerful on paper. In a cross-functional, hybrid environment, informal networks (trusted experts, long-tenured staff, gatekeepers, and coalition builders) often affect priorities as much as formal governance roles. Effective influence analysis uses multiple inputs (interviews, observations, prior decisions, escalation paths) and then translates the findings into tailored engagement and communications actions so the right people are involved at the right time. The main pitfall is treating the organization chart as the primary indicator of real influence, which can cause you to miss the true decision shapers and continue the cycle of delays.

Formal authority does not reliably show who actually influences decisions, so this approach can miss informal influencers and block effective engagement.

Question 149

Topic: People

A hybrid project team is experiencing escalating conflict between the solution architect and the QA lead. In planning sessions, the architect pushes for rapid decisions and speaks in short, direct statements; the QA lead repeatedly asks for detailed data and risks before agreeing. After meetings, both complain that the other is “slowing us down” or “being reckless,” yet their individual deliverables meet quality expectations.

The project manager reviews the team’s recent personality indicator results: the architect scored highest in “Dominance/Decisiveness,” and the QA lead scored highest in “Conscientiousness/Analytical.”

What is the most likely underlying cause of the conflict?

• A. The QA lead lacks the technical skills to assess risk quickly
• B. Misinterpreting different work styles as resistance or incompetence
• C. Unclear requirements are forcing repeated rework and debate
• D. The architect is not meeting quality standards, driving scrutiny

Best answer: B

What this tests: People

Explanation: The behavior and personality indicator clues suggest a style mismatch: one person optimizes for speed and decisions, while the other optimizes for accuracy and risk reduction. Without tailoring communication and agreeing on decision norms, each interprets the other’s natural style as a personal problem. Since output quality is acceptable, the primary issue is perception and interaction patterns, not capability or quality.

Personality indicators help a PM diagnose behavior patterns (how people prefer to communicate, decide, and manage risk) so conflicts can be addressed at the root. Here, a high decisiveness profile tends to push for quick alignment and action, while a high analytical profile tends to seek data, precision, and risk clarity before committing. When these preferences are not acknowledged and managed, team members often make attribution errors—labeling the other as “blocking” or “reckless”—even when performance and quality are strong.

A PM applying emotional intelligence would use the indicator insights to:

• Reframe the conflict as preference differences, not intent
• Set working agreements for decision readiness (what “enough data” means)
• Tailor communication (summaries and options for one; details and risks for the other)

The key takeaway is that the indicators point to a style-based interaction issue rather than a requirements, skills, or quality failure.

The indicator results point to a fast, decisive style clashing with an analytical, detail-oriented style, creating attribution errors rather than performance issues.

Question 150

Topic: Process

You are leading a hybrid project to implement a customer portal for a regulated financial services firm. Multiple departments submitted conflicting requirements, and the first release must fit a fixed date and budget. You are preparing to determine and prioritize requirements for the release.

Which action should the project manager NOT take?

• A. Identify regulatory and technical dependencies and factor them into the prioritization
• B. Facilitate a cross-functional workshop to agree on prioritization criteria and rank requirements
• C. Use the designated business owner to make final trade-offs after collecting stakeholder input
• D. Prioritize requirements primarily by stakeholder seniority and immediately baseline them as final

Best answer: D

What this tests: Process

Explanation: Requirements should be prioritized using transparent, agreed criteria (value, risk, compliance, dependencies) and validated with the appropriate decision authority. Ranking mainly by stakeholder seniority bypasses objective prioritization and increases the likelihood of rework when conflicts and constraints surface. In a fixed-date release, this anti-pattern typically results in missed compliance needs, unmanaged dependencies, and uncontrolled change.

Determining and prioritizing requirements means eliciting inputs, resolving conflicts, and ranking needs using explicit criteria that align to constraints and value (for example, compliance obligations, business value, risk reduction, and technical dependencies). In a hybrid setting, stakeholders provide input, but a defined decision authority (such as a business owner/product owner or sponsor per governance) makes trade-offs using an agreed approach. Prioritizing based mainly on organizational power is an anti-pattern because it is not transparent, is hard to defend, and tends to ignore constraints and dependencies, which destabilizes scope and increases change and rework. The key takeaway is to prioritize collaboratively and objectively, then baseline/commit only after validation and alignment to release constraints.

Prioritizing by power and baselining without an agreed method and validation leads to biased, unstable requirements and scope churn.

Questions 151-175

Question 151

Topic: Process

A hybrid project is implementing a new CRM and has a fixed go-live in three weeks. The PM reviews the transition readiness log below.

Transition readiness log (excerpt)
- Operations runbook: Draft (60%); owner Ops Lead; due 5 days before go-live
- Service desk training: Not scheduled; owner Service Desk Mgr; due 10 days before
- Support model (RACI + escalation): In review; owner PM; due 7 days before
- Knowledge base articles: Not started; owner Vendor; due 5 days before
- Cutover checklist: Approved; owner Tech Lead; due 2 days before

Based on the exhibit, what should the project manager do next to support an effective handover to operations?

• A. Ask the sponsor to accept the risks and waive the remaining transition deliverables to protect the go-live date
• B. Transfer the system to operations immediately and address missing documentation and training during post–go-live support
• C. Proceed with administrative closure because the cutover checklist is approved
• D. Hold a transition readiness review with operations to confirm required documentation, training, and support coverage, assign actions to close gaps, and update the plan through change control if dates are at risk

Best answer: D

What this tests: Process

Explanation: The transition readiness log indicates critical handover components are incomplete or unscheduled, especially operations documentation, service desk training, and the support model. The best next step is to convene operations and other owners to validate readiness criteria, close gaps with clear accountability and dates, and formally adjust the plan if the go-live is threatened.

Transition/handover planning focuses on operational readiness: the receiving organization must be able to run, support, and maintain the product on day one. The exhibit shows that while technical cutover is under control, key continuity items (runbook, service desk training, support model, knowledge articles) are not complete and some are not even scheduled.

The project manager should:

• Review readiness criteria with operations and support stakeholders
• Assign owners and due dates for missing documentation/training/support tasks
• Integrate these tasks into the project schedule and manage impacts via change control when needed

The key takeaway is that “ready to deploy” is not the same as “ready to operate,” so gaps must be addressed before formal handover.

The log shows multiple readiness gaps (training, support model, knowledge articles) that require coordinated ownership, dates, and plan updates to enable a controlled handover.

Question 152

Topic: Business Environment

A hybrid project is delivering a new customer portal for a financial services firm. The organization has a mandatory compliance gate before any pilot release, including sign-off that regulatory requirements for audit logging and strong customer authentication are met.

To avoid schedule slippage, the project manager decides not to confirm the detailed security/compliance requirements with the compliance officer and proceeds with development based on assumptions. At the end of the next iteration, the team demonstrates working features but has not implemented audit logging.

What is the most likely near-term impact of this decision?

• A. The firm is fined by regulators for noncompliance
• B. The pilot release is blocked until compliance gaps are addressed
• C. The project’s business case is withdrawn due to reputational damage
• D. Team velocity drops because of increased defect density

Best answer: B

What this tests: Business Environment

Explanation: Because the organization requires compliance sign-off before any pilot release, failing to confirm and implement required controls creates an immediate release blocker. The most immediate consequence is failing the compliance gate and needing rework and re-verification before proceeding.

Confirming compliance requirements early (and when changes/assumptions arise) prevents building features that cannot legally or policy-wise be released. In this scenario, the organization has an explicit compliance gate with required controls; not validating requirements with the compliance officer led to a deliverable that is demonstrably incomplete from a compliance standpoint (missing audit logging). The near-term impact is operational and procedural: the release cannot pass the gate.

Practical response pattern:

• Validate applicable regulations and internal policies with the compliance authority
• Translate them into backlog/requirements and acceptance criteria
• Verify evidence (e.g., logs, test results) before the release gate

Longer-term outcomes like fines or reputational harm are possible but depend on an actual noncompliant release or an incident, which is not yet described.

A missed compliance requirement will be detected at the mandatory gate and immediately stop release until required controls are implemented and verified.

Question 153

Topic: Process

You are managing a hybrid project to deploy new point-of-sale devices across 300 retail stores. A key vendor warns of a potential component shortage next quarter that could delay shipments, and stakeholders are pushing you to “do something now.” The risk is newly identified and has not yet been analyzed.

What should you verify or obtain FIRST before deciding on the appropriate risk response option?

• A. Updated lessons learned from similar projects
• B. Vendor’s commitment to penalties for late shipment
• C. Sponsor approval for additional contingency budget
• D. Likelihood, impact, and trigger details for the shortage risk

Best answer: D

What this tests: Process

Explanation: Before selecting a risk response, the project manager should first analyze the risk to understand its exposure. Obtaining the likelihood, potential impact to objectives, and when/how the risk could materialize enables an informed choice among response options and right-sized actions.

Choosing among risk response options (avoid, mitigate, transfer, accept, or escalate) depends on the risk’s exposure and urgency. In this scenario, the risk is only identified; without understanding how likely the shortage is, how severe the schedule/cost impact could be, and what triggers or time window apply, any response would be guesswork or could waste time and money.

A practical first information request is:

• Probability/likelihood of the shortage affecting your orders
• Estimated impact (e.g., weeks delayed, added cost, quality implications)
• Timing, triggers, and early warning indicators

With that analysis, you can compare response options (e.g., mitigation via alternate sourcing vs. transfer via contract terms) and align actions to thresholds and decision authority.

You need probability, impact, and timing/trigger information to choose an appropriate response (avoid/mitigate/transfer/accept) proportional to the risk exposure.

Question 154

Topic: People

You are leading a hybrid product rollout with a cross-functional team working across three time zones. After two missed iteration goals, team members are blaming other functions and participation in ceremonies is dropping; the sponsor is concerned about morale and commitment. What should you do to inspire, motivate, and influence the team? (Select TWO)

• A. Announce mandatory overtime until iteration goals are met
• B. Implement a visible recognition system for contributions and teamwork
• C. Escalate the conflict to functional managers to reset priorities
• D. Facilitate a session to refresh the team working agreements
• E. Replace low performers immediately to signal urgency
• F. Require daily status reports and enforce stricter compliance checks

Correct answers: B, D

What this tests: People

Explanation: Rebuilding motivation in a strained team is best achieved by strengthening shared norms and reinforcing positive behaviors. Refreshing working agreements re-establishes how the team collaborates and resolves conflict. Pairing that with consistent recognition increases engagement and encourages the teamwork needed to reliably meet iteration goals across time zones.

When morale drops and blame increases, the project manager’s most effective levers are influence-based: re-align the team around shared expectations and reinforce the behaviors that lead to results. A facilitated working-agreements (team charter/social contract) session creates psychological safety, clarifies decision-making and handoffs, and gives the team a jointly-owned way to handle conflict.

A lightweight recognition system (peer kudos, celebrating iteration outcomes, calling out collaborative behaviors) provides timely reinforcement and helps re-focus the team on outcomes and cooperation. Coercive actions or punitive controls may increase compliance short term, but typically worsen trust and disengagement in already-fragile team dynamics.

Co-creating and recommitting to a team social contract rebuilds trust, clarifies expectations, and improves collaboration.

Timely, meaningful recognition reinforces desired behaviors and increases engagement without relying on authority.

Question 155

Topic: Process

Midway through a hybrid project, the change control board approves adding an analytics dashboard requested by a regulator. The product backlog and scope statement are updated, and the team starts building it immediately. Two weeks later, the monthly status report shows an unexplained cost overrun, the schedule forecast still reflects the original baseline dates, and the test team says no new quality criteria were added for the dashboard. Stakeholders complain that they were not told about impacts.

What is the most likely underlying cause?

• A. Stakeholders are unhappy because communications were inadequate
• B. Impacts were not assessed across plans and baselines were not updated
• C. The team is resisting the new work and delaying delivery
• D. The sponsor did not provide enough funding for the change

Best answer: B

What this tests: Process

Explanation: The symptoms point to a change being executed without integrating it into the overall project management plan. Updating scope/backlog alone is insufficient; the schedule and cost baselines and relevant subsidiary plans (such as quality) must be updated consistently based on impact analysis. The disconnect creates “unexplained” variances and surprises in reporting.

The core issue is weak integration when a change occurs: the work began after approval, but the project was not replanned end-to-end. In integrated change control, once a change is approved, the project manager ensures the change’s impacts are assessed across affected components and then updates the relevant baselines and subsidiary plans so performance measurement and expectations stay aligned.

In this scenario, clues show partial updating (scope/backlog) but missing integration (schedule forecast still on the old baseline, cost impacts not reflected, and quality criteria not updated). That pattern indicates the primary problem is failure to assess cross-plan impacts and consistently update integrated baselines/plans, not a funding decision, team behavior, or communications alone.

Communication issues are real here, but they stem from the underlying lack of integrated replanning and baseline updates.

The change was implemented in scope/backlog but not integrated into schedule, cost, and quality plans/baselines.

Question 156

Topic: People

A project manager is negotiating a contract amendment with a vendor for additional cybersecurity testing on a regulated product. Procurement previously told the project manager that any amendment must stay within a total contract value of $250,000 and that changes above that amount require sponsor approval.

During negotiations, the project manager offers $275,000 to “close the deal.” The vendor accepts, but procurement rejects the amendment and the vendor now refuses to continue testing unless the $275,000 offer is honored. The schedule is slipping due to rework in negotiations.

What is the most likely underlying cause of this situation?

• A. The project manager negotiated outside the authorized limits
• B. The testing requirements were unclear and kept changing
• C. Procurement failed to communicate the process for amendments
• D. The vendor is using hardball tactics to increase profit

Best answer: A

What this tests: People

Explanation: The key clue is that a $250,000 ceiling and an approval threshold were explicitly provided before negotiations. By offering $275,000 anyway, the project manager acted outside the approved negotiation range and authority, creating an agreement that could not be ratified. This predictably triggers rejection, loss of trust, and repeated renegotiation.

Negotiation bounds are the explicit limits within which the project manager is authorized to make commitments (for example, cost ceilings, approval thresholds, and non-negotiable terms). In this scenario, procurement clearly set a maximum total contract value and stated that exceeding it requires sponsor approval. The project manager’s offer exceeded that limit, so the “agreement” was not enforceable internally and could not be finalized.

To prevent this outcome, the project manager should ensure the negotiation mandate is confirmed before bargaining and follow it during discussions:

• Document the authorized range (target, ceiling, and walk-away point).
• Clarify who must approve exceptions and how to obtain timely approval.
• Pause negotiations and escalate when the other party’s position is outside the authorized range.

The takeaway is that failing to negotiate within approved limits is a primary cause; other factors may exist, but they don’t explain why the accepted deal was rejected.

The project manager exceeded the stated spending cap without obtaining required approval, violating the negotiation mandate.

Question 157

Topic: Process

A project will implement a new customer portal while also upgrading an existing billing platform. The billing changes are subject to strict regulatory audits with fixed documentation and sign-offs, but the portal requirements are expected to evolve through frequent user feedback. Governance requires a quarterly steering committee review, and a change control board (CCB) is mandated only for changes to regulated billing deliverables.

Which planning and governance approach should the project manager NOT use?

• A. Baseline billing scope, and plan portal work in rolling waves
• B. Use stage gates for billing and sprint reviews for the portal
• C. Send every portal backlog change through the CCB for approval
• D. Let the product owner reorder portal backlog within release goals

Best answer: C

What this tests: Process

Explanation: The situation calls for a hybrid lifecycle: predictive planning and formal control for regulated billing work, and adaptive planning for the evolving portal. Governance should be tailored so compliance items follow required approvals while portal scope is managed through product ownership and iterative reviews. Routing every portal backlog adjustment through the CCB conflicts with that tailoring and creates unnecessary friction.

When parts of the solution have high certainty and mandatory compliance (regulated billing) while other parts have high uncertainty and need frequent feedback (customer portal), a hybrid approach is appropriate. Planning and governance should be fit-for-purpose: use predictive baselines, documentation, and formal approvals where required, and use iterative planning, demos, and product ownership where learning and reprioritization are expected.

A practical hybrid setup is:

• Define a baseline and change control for regulated deliverables.
• Manage portal scope through a prioritized backlog and timeboxed iterations.
• Use steering committee/stage gates for major funding, risk, and compliance decisions, while using sprint reviews to govern incremental portal value.

The key is separating what must be formally controlled from what should remain adaptable.

It applies predictive change control to adaptive work, undermining the hybrid approach and slowing value delivery.

Question 158

Topic: Process

A project uses a predictive lifecycle with a formal change control board (CCB). The CCB approves a change request to add a new compliance report to the product. The project manager logs the approval but does not communicate the change to the team or update the scope statement, WBS, or schedule baseline before work begins next week.

What is the most likely near-term impact?

• A. The existing vendor contract is automatically voided by the approved change.
• B. The delivered product fails the compliance audit at project closure.
• C. The sponsor terminates the project due to lack of change governance.
• D. The team continues work to the old baseline, causing rework and missed tasks.

Best answer: D

What this tests: Process

Explanation: Once a change is approved, the project manager must communicate it and update relevant plans, baselines, and artifacts so execution aligns with the new decision. If this is not done, the team will keep working from the previous scope and schedule assumptions. The immediate result is confusion, wrong work sequencing, and rework when the new requirements surface in execution.

Approved changes are only actionable when they are incorporated into the project’s controlled documents and communicated to the people doing the work. In a predictive environment, that typically means updating the project management plan and relevant baselines (such as scope and schedule), along with supporting artifacts (requirements documentation/traceability, WBS/WBS dictionary, schedule, and the change log), and then informing the team and stakeholders per the communications approach.

If the approval is logged but the baselines and artifacts are not updated and shared, near-term execution will proceed using the old plan. The team may start the wrong work, omit the new compliance-report tasks, and generate immediate rework and coordination churn once the discrepancy is discovered. The key takeaway is to promptly update controlled documents and communicate the approved change before work is performed.

Without communicating and updating plans/baselines, the team will execute against outdated scope and schedule, creating immediate misalignment and rework.

Question 159

Topic: People

You are serving as the scrum master for a software team. The sprint ends tomorrow, and the team’s definition of done requires code to be merged and a CI build to pass.

Several impediments are raised within the same hour:

• The CI pipeline is down, blocking all merges and integrated testing.
• The product owner is unavailable today to clarify two stories’ acceptance criteria.
• One team member requests a new monitor due to eye strain.

As you prioritize impediments, which action SHOULD AVOID?

• A. Ask the team to continue coding and postpone integration and build validation until after the sprint ends.
• B. Replan the next day’s work to pull forward items not requiring merges while the CI outage is being resolved.
• C. Escalate the CI outage immediately using the agreed escalation path and track it as the top impediment until service is restored.
• D. Facilitate a quick triage with the team and rank impediments by impact on the sprint goal and definition of done, then tackle the CI outage first.

Best answer: A

What this tests: People

Explanation: Prioritizing impediments means addressing what most threatens the sprint goal and the team’s ability to meet the definition of done. A CI outage blocks merges and integrated testing for everyone, making it the highest-impact blocker to remove or escalate immediately. Planning workarounds is fine only if the critical blocker remains the top focus and is actively being removed.

Impediment prioritization is impact-based: remove or escalate what most constrains the team’s ability to deliver against the sprint goal and definition of done, especially items that block multiple people or sit on the critical path to “done.” Here, a down CI pipeline prevents merges and integrated testing, so it is the dominant blocker and should be treated as the top priority while other issues are managed in parallel.

Good prioritization behaviors include:

• Rapidly triage with the team using impact/urgency criteria (blast radius, time sensitivity, DoD risk).
• Actively remove or escalate the highest-impact blocker via the agreed path.
• Adjust near-term work to keep flow without compromising “done.”

The key takeaway is to avoid “work now, integrate later” when integration is required for completion.

Delaying integration ignores the most critical blocker to meeting the definition of done and increases delivery risk.

Question 160

Topic: Process

A hybrid product implementation is in execution. A vendor submits a change request that adds an integration component and increases cost by $35,000. The project sponsor tells the project manager to “get it approved,” but the steering committee chair says all scope changes must be decided by the committee, which meets monthly. No decision thresholds or escalation paths were defined.

What is the most likely near-term impact?

• A. The project’s benefits are reduced because the integration is omitted.
• B. The vendor initiates a contract claim that stops all project work.
• C. The change decision is delayed, putting the next milestone at risk.
• D. Key stakeholders lose confidence and withdraw funding for the project.

Best answer: C

What this tests: Process

Explanation: When decision rights and escalation paths between the sponsor and steering committee are unclear, change approvals commonly stall. With a committee that meets monthly and no defined thresholds, the most immediate consequence is waiting for a governance decision. That delay quickly threatens near-term milestones and creates idle time or re-planning.

Project governance clarifies who can decide what (decision rights), who performs which roles, and how to escalate when decision-makers disagree or are unavailable. In this scenario, the sponsor and steering committee provide conflicting direction on who approves scope/cost changes, and there are no thresholds (for example, “sponsor can approve up to X”) or an escalation path to resolve conflicts quickly. The most likely immediate outcome is an approval bottleneck: the team cannot confidently proceed with the vendor change, so work is paused, replanned, or sequenced around the uncertainty, putting the next milestone at risk. Longer-term outcomes like reduced benefits or loss of funding may occur, but the near-term impact is the decision delay caused by unclear governance interfaces.

Without defined decision rights and an escalation path, approvals stall while sponsor and steering committee roles are clarified.

Question 161

Topic: Process

Which term describes the document or approach that defines how procurement will be managed, including contract types, selection criteria, and roles/responsibilities?

• A. Change control plan
• B. Procurement management plan
• C. Bidder conference
• D. Procurement statement of work (SOW)

Best answer: B

What this tests: Process

Explanation: The procurement management plan is the artifact that documents the project’s procurement strategy and how procurements will be planned, executed, controlled, and closed. It commonly includes the contracting approach (such as contract types), seller selection criteria, and who will perform procurement activities.

The procurement management plan is a component of the project management plan that explains how the team will acquire products, services, or results from outside the organization. It translates project needs into a procurement approach by describing decisions such as the contract type(s) to use, how sellers will be solicited and evaluated, and how procurement work will be coordinated and governed (for example, roles, responsibilities, and interfaces with legal/procurement).

A procurement statement of work (SOW) describes what is being procured, not how procurement will be managed. A bidder conference is an event to clarify solicitation details with potential sellers. A change control plan governs how changes are evaluated and approved across the project, not specifically the procurement strategy.

It defines how the project will conduct procurements, including contracting approach, evaluation/selection methods, and procurement roles.

Question 162

Topic: Process

A hybrid project is integrating inputs from scope, schedule, and risk planning workshops. The project manager has collected over 200 unstructured stakeholder comments describing desired features, constraints, and concerns, and needs to turn them into a small set of clearly defined themes to support the integrated project management plan.

Which technique should the project manager use to analyze the data collected?

• A. Monte Carlo simulation to model combined schedule and cost uncertainty
• B. Scatter diagramming to test correlation between two variables
• C. Pareto charting to focus on the “vital few” categories
• D. Affinity diagramming to group similar inputs into themes

Best answer: D

What this tests: Process

Explanation: Because the data is high-volume and unstructured, the key need is to organize qualitative inputs into meaningful categories. Affinity diagramming helps the team cluster related statements and reveal common themes that can be translated into requirements, backlog items, and planning assumptions for integration.

Analyzing collected data during planning is about converting raw inputs into usable information for decisions and plan integration. When the team has many qualitative statements (comments, ideas, concerns) from multiple workshops, the most effective approach is to group and synthesize them into themes before refining into requirements, risks, or work items.

A practical way to do this is:

• Capture each input as a separate item
• Collaboratively sort items by natural similarity
• Label each cluster as a theme and validate with stakeholders
• Use the themes to drive prioritization and decomposition

Other techniques are better when the data is numeric (simulation), frequency-based (Pareto), or focused on relationship between two variables (scatter).

It is designed to synthesize large volumes of qualitative, unstructured input into logical groupings for planning.

Question 163

Topic: Process

A hybrid project is building a mobile app for field technicians. The sponsor wants a pilot in 4 weeks to validate business value. The security team states that any pilot using real customer data must include an audit trail for ticket changes.

Exhibit: Product backlog excerpt

ID    Item                         Value  Effort  Dependency  Compliance
PBI-2 Create service ticket         High   13      —           No
PBI-4 Audit trail for ticket edits  High   5       PBI-2       Yes
PBI-5 ERP integration               High   21      PBI-2       No
PBI-3 Offline mode                  Med    20      PBI-2       No
PBI-1 SSO login                     High   8       —           No
PBI-6 UI theme customization        Low    3       —           No

Based on the exhibit, what should the project manager facilitate next to define the MVP/iteration goal and prioritize for early value?

• A. Prioritize UI theme customization and SSO because they are quicker to deliver
• B. Prioritize offline mode before ticket creation to improve technician adoption
• C. Prioritize ticket creation and the required audit trail ahead of integration and offline work
• D. Prioritize ERP integration first because it has high business value

Best answer: C

What this tests: Process

Explanation: For an MVP/pilot, prioritize the smallest set of backlog items that delivers usable value soon while meeting mandatory constraints. The exhibit shows the audit trail is a compliance requirement and depends on ticket creation. Focusing the iteration goal on creating and editing tickets with an audit trail enables the pilot and defers larger dependent work.

Value-based prioritization for an MVP/iteration starts with the minimum end-to-end capability that produces measurable value early, while honoring mandatory requirements and item dependencies. Here, the pilot must use real customer data, so the audit trail is not optional; it also cannot be delivered until ticket creation exists. A good facilitation outcome is an iteration goal centered on a pilot-ready workflow (create/edit tickets with an audit trail) and a backlog order that supports that goal.

• Confirm the iteration goal: pilot-ready ticket workflow with compliance
• Order the backlog to satisfy dependencies: deliver ticket creation before audit trail
• Defer larger, nonessential items (integration, offline) until after the pilot learns

Prioritizing work that is high value but not needed for the pilot (or that increases scope significantly) delays early validation.

This selects the highest-value, pilot-enabling capability while respecting the compliance need and the dependency on ticket creation.

Question 164

Topic: People

A project manager is planning a hybrid rollout of a new claims workflow system. To save time, the project manager invites only IT and the sponsor to requirements workshops and keeps sending a standard monthly update to all other stakeholders. Two weeks later, the operations director (who will be most affected by the new workflow and controls day-to-day staffing) asks why the team is “changing how we work” without their input.

What is the most likely near-term impact of the project manager’s approach?

• A. A contract dispute occurs with the implementation vendor
• B. Realized benefits drop after go-live due to low adoption
• C. Requirements approval is delayed due to late objections and rework
• D. Team productivity increases because fewer stakeholders are involved

Best answer: C

What this tests: People

Explanation: Stakeholder analysis should identify who has high influence and/or high impact and tailor engagement accordingly. Excluding the operations director from requirements discovery creates misalignment that is surfaced quickly when the affected leader becomes aware. The near-term consequence is resistance that delays approval and drives rework to incorporate operational needs.

The core issue is an incomplete stakeholder analysis: the project manager did not map stakeholder impact and engagement needs, and instead used a one-size-fits-all communication approach. A stakeholder who is highly impacted (and often influential over operational readiness and acceptance) needs early, frequent engagement in requirements and workflow decisions. When such a stakeholder is not identified and actively engaged, the most immediate outcome is pushback when they discover changes, leading to delayed sign-off and rework to address missing requirements and constraints. The key takeaway is that influence and impact both drive engagement strategy; omitting a high-impact stakeholder commonly disrupts near-term alignment and approvals.

Failing to analyze and engage a high-impact stakeholder typically triggers near-term pushback that delays agreement and forces requirements changes.

Question 165

Topic: Process

You are leading a hybrid product rollout with multiple business units. The sponsor reports that key users are missing sprint reviews and their feedback is arriving late, increasing rework. You already have a stakeholder engagement plan, but it has not been updated since planning.

You need to optimize for restoring timely stakeholder input while creating a way to measure whether engagement is improving over the next two months. What should you do next?

• A. Schedule weekly all-hands meetings and require every stakeholder to attend until rework decreases
• B. Update the stakeholder engagement plan using a refreshed engagement assessment, tailor strategies per stakeholder group, and define measurable indicators with a review cadence
• C. Send a project-wide status email twice per week and track email open rates as the primary engagement measure
• D. Escalate missed sprint reviews to the sponsor and proceed with delivery to avoid further delays

Best answer: B

What this tests: Process

Explanation: When engagement drops, the project manager should refresh the stakeholder analysis and update the stakeholder engagement plan with targeted actions for the stakeholders who matter most to timely decisions. To measure effectiveness over time, define a few practical indicators (for example attendance, response time, decision turnaround, feedback cycle time) and review them on a set cadence to adapt as needed.

The core need is to update the stakeholder engagement plan and verify whether the change is working. Start by reassessing current vs. desired engagement for key users (for example with an engagement assessment matrix), then tailor engagement approaches to remove the specific bottlenecks causing late feedback (who needs what information, when, and through which forum). To measure effectiveness over time, select leading indicators tied to the problem (attendance at reviews, response time to questions, decision/approval turnaround time, backlog item churn/rework due to late input) and review them at a defined cadence (for example each iteration and monthly with governance). This creates a feedback loop: measure, adjust strategies, and re-measure. Tactics like more meetings or more emails may increase noise and do not ensure targeted engagement or meaningful measurement.

It updates the plan based on current engagement gaps and establishes simple metrics and regular checkpoints to measure improvement over time.

Question 166

Topic: Process

You are asked to recommend an approach for a customer self-service portal that integrates with a legacy billing system. The go-live date is fixed and the integration and regulatory reporting requirements are well understood, but the user experience features are expected to evolve based on early user feedback.

Which recommendation should you NOT make?

• A. Agile with built-in compliance criteria and frequent stakeholder reviews
• B. Agile while freezing all requirements and changes after kickoff
• C. Predictive with rolling-wave planning for uncertain features
• D. Hybrid: predictive for integration, agile iterations for UX enhancements

Best answer: B

What this tests: Process

Explanation: The project has both high-certainty, compliance-heavy integration work and high-uncertainty user experience work. Appropriate recommendations support tailoring to manage certainty and uncertainty while still meeting governance needs. An approach that claims to be agile but locks scope and blocks change undermines the purpose of choosing agile practices.

Methodology selection is a tailoring decision: use more predictive practices where requirements are stable and governance/compliance is heavy, and more adaptive practices where requirements are expected to change through feedback. In this scenario, integration and regulatory reporting can be planned with predictive controls, while UX features benefit from iterative development and frequent review.

Good recommendations generally:

• Align planning rigor to requirement stability and risk.
• Build compliance needs into working agreements, acceptance criteria, and reviews.
• Preserve the ability to incorporate feedback where uncertainty is high.

A recommendation that labels the work “agile” but freezes requirements and prevents change removes the main advantage of agile and creates unnecessary friction when UX evolves.

Freezing requirements and changes conflicts with agile’s adaptive planning and is a common tailoring anti-pattern.

Question 167

Topic: People

On a hybrid product implementation project, the team created ground rules (working agreement) that include “one speaker at a time,” “assume positive intent,” and “raise concerns respectfully.” During recurring planning meetings, a senior developer repeatedly interrupts others and dismisses their input. Several team members have complained that the meetings feel unsafe and unproductive.

As the project manager, what should you do to manage and rectify this ground rule violation? (Select TWO)

• A. Update the ground rules yourself and email the new version
• B. Remove the developer from meetings until attitudes improve
• C. Facilitate a team review and recommitment to ground rules
• D. Meet privately with the developer to address behavior
• E. Ignore it to avoid creating conflict in the team
• F. Escalate immediately to the sponsor for intervention

Correct answers: C, D

What this tests: People

Explanation: Ground rules are team-owned and exist to protect collaboration and psychological safety. The project manager should address the specific violation directly with the individual and also reinforce the shared working agreement with the whole team so expectations and accountability are clear going forward.

Managing ground rule violations requires prompt, respectful intervention and reinforcement of the team’s agreed ways of working. In this situation, the repeated interrupting and dismissive behavior is harming psychological safety and meeting effectiveness, so it should be addressed directly with the person involved to create awareness of impact and gain commitment to change. In parallel, the team should revisit the working agreement in a facilitated discussion to reaffirm norms (and adjust them only if the team agrees) so expectations apply to everyone consistently.

Key actions that fit the situation:

• Address the behavior privately using the ground rules and observed impacts.
• Facilitate a team check-in to recommit to the working agreement and how it will be upheld.

Escalation or punitive removal is typically reserved for continued noncompliance after coaching and team reinforcement, or for severe policy violations.

A timely private conversation referencing the agreed ground rules helps correct behavior while preserving respect and psychological safety.

Revisiting and recommitting to the working agreement resets shared expectations and reinforces accountability across the team.

Question 168

Topic: Business Environment

A hybrid project is building a customer onboarding platform. Midway through delivery, a new government regulation is announced with a firm effective date in 4 months that adds mandatory identity-verification steps; noncompliance will prevent go-live. The sponsor asks how you will evaluate the external change and prioritize scope so the project still delivers expected benefits.

Which metric/evidence/artifact best validates that the project has appropriately assessed the change and reprioritized the scope/backlog?

• A. A working demo of the current onboarding flow presented at the iteration review
• B. Meeting minutes from a workshop where the regulation was reviewed with the team
• C. A sprint burndown chart showing increased velocity over the last two sprints
• D. A re-prioritized backlog/release plan showing compliance items first, with documented impact analysis and Product Owner/compliance approval

Best answer: D

What this tests: Business Environment

Explanation: The strongest validation is evidence that scope/backlog ordering changed because of the external regulation and that the change was evaluated and agreed by the right decision-makers. An updated backlog and release plan, coupled with documented impact analysis and approval, shows prioritization decisions that protect compliance and benefits within the new constraint.

When an external business environment change creates a hard constraint (like a regulation with an effective date), the project must explicitly assess impact and then adjust scope/backlog priorities so mandatory work is delivered in time. The best validation is an artifact that shows the new ordering of work and the decision basis (value, risk, compliance urgency, and schedule impact) along with acceptance by accountable stakeholders (for example, Product Owner, sponsor, compliance).

This kind of evidence demonstrates:

• The change was analyzed for scope/benefits impact
• The backlog/scope was re-ordered to address the external driver
• The decision has governance/stakeholder validation

Activity records or delivery progress visuals may be useful, but they do not prove the prioritization decision aligns to the external change and its business impact.

It directly demonstrates scope/backlog reprioritization based on external change, supported by impact rationale and stakeholder validation.

Question 169

Topic: People

A hybrid product team is delivering a regulated customer portal. A senior developer who owns the build-and-release pipeline (mostly tacit knowledge) will leave the company in two weeks. The team is distributed across four time zones, and the organization has had repeated delays in onboarding replacements.

Which approach best maintains team continuity through effective knowledge transfer given this situation?

• A. Update the RACI matrix to clarify release responsibilities
• B. Hold a lessons learned workshop at project close
• C. Escalate to the sponsor to retain the developer longer
• D. Run a structured handover with shadowing and a shared runbook

Best answer: D

What this tests: People

Explanation: The key discriminator is the imminent loss of critical tacit knowledge in a distributed team. A structured knowledge-transfer handover (shadowing) converts tacit knowledge into shared, reusable assets and builds redundancy. This maintains continuity for both current delivery and near-term onboarding.

Maintaining team and knowledge transfer is most at risk when a single person holds specialized, tacit knowledge and is about to exit. In that case, the best response is to rapidly transfer know-how to others and capture it in an accessible form so the team is not dependent on one individual.

A practical approach is:

• Time-box knowledge-transfer sessions focused on critical workflows (e.g., release pipeline)
• Use shadowing/pairing to transfer tacit steps and troubleshooting heuristics
• Capture outcomes in a shared runbook (steps, checks, contacts, rollback)
• Confirm transfer with a short “new owner” dry run

This both builds redundancy (team resilience) and creates durable onboarding material; governance artifacts alone don’t transfer the missing know-how.

With an imminent departure and largely tacit know-how, structured shadowing plus a maintained runbook transfers knowledge quickly and makes it reusable for future onboarding.

Question 170

Topic: People

A project manager leading a fully remote, cross-time-zone team notices declining participation and misunderstandings in chats and meetings. She facilitates a session where the team agrees on core overlap hours, expected response times, meeting etiquette, tool/channel usage, and how decisions will be made, then commits to revisiting these agreements monthly.

Which project management concept does this practice best represent?

• A. Responsibility assignment matrix (RACI)
• B. Communications management plan
• C. Stakeholder engagement assessment matrix
• D. Team charter with working agreements

Best answer: D

What this tests: People

Explanation: Co-creating and periodically revisiting norms like overlap hours, response-time expectations, and decision-making is a direct way to engage and support a virtual team. This is the purpose of a team charter (working agreements): clarifying how the team will work together to reduce friction and increase participation. Regular review reinforces accountability and continuous improvement.

Virtual teams often struggle with delays, misinterpretations, and disengagement because many “how we work” assumptions are invisible across time zones and communication tools. A team charter with working agreements makes those expectations explicit and team-owned, improving engagement by creating clarity and psychological safety around participation.

In practice, working agreements commonly cover:

• Meeting norms (time zones, etiquette, facilitation)
• Communication channels and response-time expectations
• Decision-making and escalation paths within the team
• Cadences to inspect and adapt (e.g., monthly refresh)

Plans and matrices that focus on roles, stakeholders, or broad communication needs can support the effort, but they do not specifically create and maintain the team’s shared operating norms.

It establishes shared team norms and operating rules to improve engagement and collaboration in a virtual environment.

Question 171

Topic: Process

You are managing a software product using Scrum with 2-week sprints. Work is estimated in story points, and the team avoids task-hour estimating. The sponsor wants a reliable view of schedule progress toward a fixed release date, and the PMO expects a simple forecast that can be updated each sprint. What is the BEST next action to measure and report ongoing progress?

• A. Implement EVM with PV/EV calculations to report SPI monthly
• B. Baseline a detailed WBS schedule and track percent complete weekly
• C. Use team velocity and a release burnup to forecast completion
• D. Track progress by comparing actual hours to the original effort estimate

Best answer: C

What this tests: Process

Explanation: In Scrum, progress is best measured using agile information radiators and empirical forecasting based on completed work. Using velocity with a release burnup (or burndown) uses the team’s story point estimates and provides a transparent, sprint-by-sprint projection toward the release date. This meets the sponsor’s need for a schedule forecast without forcing hour-based tracking.

Progress measures should fit the delivery method and the way work is estimated. Because this project is using Scrum and estimates work in story points (not hours), the most appropriate way to assess schedule progress is to measure delivered scope per sprint and use empirical data to forecast the remaining work.

A practical approach is:

• Capture completed story points each sprint (velocity).
• Maintain a release burnup showing scope completed vs. total scope.
• Use recent velocity to forecast the number of sprints needed to finish.

This produces an easy-to-update forecast at each sprint review and avoids introducing predictive, hour-based tracking that conflicts with how the team plans and delivers.

Velocity-based forecasting with a release burnup aligns with Scrum estimates and provides an updateable projection each sprint.

Question 172

Topic: Process

A hybrid software project has repeated quality gaps: in the last two iterations, 22% of completed stories failed user acceptance testing due to missed edge cases, and a quality audit noted inconsistent peer reviews across teams. The release date cannot move.

As the project manager, what TWO options should you recommend to improve quality going forward? (Select TWO.)

• A. Replace underperforming developers to eliminate the source of defects
• B. Request additional budget to hire more testers for the remaining work
• C. Submit a change request to relax acceptance criteria to reduce rework
• D. Update the team’s Definition of Done or quality checklist to require peer review and acceptance-criteria verification
• E. Facilitate a root cause analysis on the defect patterns and agree on targeted process improvements
• F. Add a final, dedicated inspection step for all stories before release

Correct answers: D, E

What this tests: Process

Explanation: Quality gaps call for preventive, process-focused improvements that reduce defect introduction and variation. Analyzing the defect trends to identify root causes enables selecting high-impact changes. Standardizing expected quality practices (for example, through a Definition of Done or checklist) helps the team apply those improvements consistently without relying on end-of-line detection.

When quality gaps repeat, the best improvement options are those that prevent defects and reduce process variation, not those that simply detect defects later. Here, the data (UAT failures due to missed edge cases) plus the audit finding (inconsistent peer reviews) indicate both a likely upstream cause and inconsistent execution across teams.

Recommended improvement actions are to:

• Analyze defect patterns with the team (for example, Pareto/cause-and-effect) to identify the biggest drivers and select targeted changes.
• Make the desired quality practices explicit and consistent (such as peer review and acceptance-criteria checks) via working agreements like the Definition of Done and then monitor results.

In contrast, adding more inspection or staffing can increase cost and cycle time and may still allow the same defects to be created.

Root cause analysis focuses improvement on the highest-contributing sources of the quality gaps rather than treating symptoms.

Making key quality practices explicit in working agreements reduces variation and prevents recurrence of the gaps.

Question 173

Topic: Business Environment

A project manager is assigned to a new internal automation project. The project charter authorizes funding, but it only lists deliverables and does not define expected business benefits or how they will be measured. The sponsor asks the team to begin execution immediately to “show progress.” What should the project manager do NEXT?

• A. Begin executing on the highest-priority deliverables and define benefits after the first milestone
• B. Facilitate a session with the sponsor and key stakeholders to identify and document expected benefits and measures
• C. Escalate to the steering committee to decide whether the project should proceed without defined benefits
• D. Create the detailed schedule and cost baseline first, then confirm benefits during planning sign-off

Best answer: B

What this tests: Business Environment

Explanation: Before moving into execution, the project needs clearly identified and measurable benefits so the team can align decisions to value and verify success. The next step is to work with the sponsor and key stakeholders to define the intended outcomes, how they will be measured, and when they are expected, then document them in the appropriate benefits artifacts.

In benefits/value management, authorization to spend money is not enough; the project must have clearly defined intended benefits and success measures to guide prioritization, trade-offs, and eventual value realization. When benefits are missing or vague, the project manager should collaborate with the sponsor and key stakeholders to identify the expected outcomes (the “why”), define measurable indicators and target values, and confirm when the benefits should be realized. Those details are then documented (for example, in a benefits management plan and/or by updating the charter and related governance artifacts) before significant execution begins. Starting execution or baselining plans without clear benefits increases the risk of delivering outputs that do not translate into business value.

Benefits must be explicitly identified and measurable before proceeding so the project can be aligned to value and success criteria.

Question 174

Topic: People

A hybrid project team introduced WIP limits and daily standups to improve delivery speed. Two sprints later, team members say performance has improved, but the sponsor says release dates and throughput look unchanged. The team’s dashboard shows velocity, cycle time, and defect trends, but the measures were started after the changes and different teams are using different definitions.

What is the most likely underlying cause of the inability to verify performance improvements?

• A. The team is relying on dashboard data rather than stakeholder feedback
• B. The sponsor is focused on dates instead of team productivity
• C. No agreed baseline and consistent metrics were established before the change
• D. WIP limits and daily standups are not suitable for hybrid projects

Best answer: C

What this tests: People

Explanation: To verify performance improvements, the project needs a consistent way to measure change over time. Because the metrics started only after the process change and are defined inconsistently across teams, there is no reliable baseline for comparison. The result is conflicting perceptions and an inability to demonstrate whether performance truly improved.

Verifying performance improvements requires objective evidence, typically by comparing current results to an agreed baseline using consistent definitions. In this scenario, measurements began only after the team changed its ways of working, and different teams interpret the metrics differently. That makes any trend ambiguous because you cannot tell whether differences are due to real improvement or simply measurement inconsistency.

A practical approach is to:

• Agree on a small set of KPIs (e.g., cycle time, throughput, escaped defects) and definitions
• Establish or reconstruct a pre-change baseline period
• Compare results over comparable time windows and contexts

Stakeholder concerns about dates may be valid, but the primary diagnostic issue is the lack of a credible before/after measurement baseline.

Without a pre-change baseline and shared definitions, the team cannot make a credible before/after comparison to confirm improvement.

Question 175

Topic: People

A hybrid project is implementing a new CRM. Sales insists on adding three revenue features before launch, while Compliance insists on completing audit controls first. Tension is rising and stakeholders are starting to bypass the project team.

The project manager decides to hold short 1:1 conversations with each leader using their preferred level of detail, then facilitates a joint prioritization session focused on shared goals and agreed decision criteria.

What is the most likely near-term impact of this decision?

• A. Stakeholders begin to align on tradeoffs and re-engage through agreed channels
• B. User adoption increases significantly immediately after go-live
• C. Change requests stop because all stakeholders feel fully satisfied with the plan
• D. The number of post-release defects drops because fewer features are delivered

Best answer: A

What this tests: People

Explanation: Meeting stakeholders in a way that fits their needs and then facilitating a shared prioritization discussion reduces defensiveness and rebuilds trust. By making interests and decision criteria explicit, the project manager increases the likelihood of near-term agreement on tradeoffs and restores constructive engagement through the project’s governance and communication paths.

The core concept is using tailored communication and influence to rebuild trust and resolve competing priorities. In the scenario, stakeholders are bypassing the team, which signals low trust and ineffective engagement. Targeted 1:1 discussions help the project manager understand each leader’s underlying interests and communicate in the format that resonates with them, reducing resistance. A facilitated joint prioritization session then shifts the conversation from positions (“my items first”) to transparent tradeoffs based on shared goals and agreed criteria.

Near term, this approach most directly improves alignment and re-engagement because it creates psychological safety, clarifies what matters to each party, and provides a fair mechanism for making priority decisions.

Outcomes like adoption, defect reduction, or eliminating change requests are indirect and not the immediate effect of stakeholder alignment.

Tailored 1:1 communication builds trust and the facilitated session creates a shared basis to resolve competing priorities quickly.

Questions 176-180

Question 176

Topic: Business Environment

You are managing a hybrid project to launch an online customer portal in 8 weeks. The portal will store EU customer personal data, and your organization has a documented policy requiring EU data to remain in EU-hosted environments. During an iteration review, the vendor’s architect states that their standard cloud setup will replicate databases to a non-EU region for resilience, and procurement says changing vendors now would likely delay the launch.

What is the project manager’s best next action to determine potential threats to compliance?

• A. Proceed after asking the team to add database encryption
• B. Submit a change request to replace the vendor immediately
• C. Hold a compliance review and document risks and gaps
• D. Accept the vendor setup to protect the go-live date

Best answer: C

What this tests: Business Environment

Explanation: A potential breach of data-residency policy is a compliance threat that should be assessed before deciding on technical or procurement changes. The best next step is to engage the appropriate compliance authorities (e.g., legal/privacy) to confirm requirements, identify the specific gap introduced by the vendor’s approach, and document the threat and exposure so it can be managed through the project’s governance.

Compliance threats are identified by comparing what the project plans to do (solution design, vendor approach, locations, processes) against binding requirements (laws, regulations, internal policies, and contract terms). Here, cross-region replication to a non-EU region conflicts with an explicit organizational data-residency policy for EU personal data, creating a clear potential compliance gap. The project manager should promptly facilitate a compliance/legal/privacy review to validate the requirement interpretation, assess the impact (what data, which regions, what controls), and document the resulting compliance risks/issues for decision-making via the established governance.

Key actions in this step:

• Confirm applicable requirements and constraints with compliance/legal
• Identify and document the gap and exposure (risk register/issue log)
• Define escalation path and decision owner for disposition

Implementing controls or changing vendors may be solutions, but they come after the compliance threat is clearly identified, documented, and routed for an informed decision.

Engaging compliance/legal to assess the data-residency gap and recording it as a compliance risk is the fastest way to identify and document compliance threats.

Question 177

Topic: Process

A project team is about to store requirements, design documents, and test results in a new cloud repository so internal teams, a vendor, and the customer can access them. Some artifacts may contain customer personal data, but the sponsor wants “easy access for everyone” to avoid delays. Before selecting the repository settings and sharing method, what should the project manager ask or verify FIRST?

• A. What collaboration tool does the vendor prefer to use?
• B. Can the sponsor approve immediate read access for all parties?
• C. How often should the team email artifact updates to stakeholders?
• D. What is each artifact’s classification and required retention?

Best answer: D

What this tests: Process

Explanation: Artifact accessibility must be balanced with security, privacy, and retention obligations. The first step is to determine information classification and records requirements so the project can configure appropriate permissions, storage location, and retention/disposition rules for each stakeholder group.

Managing project artifacts means making them available to the right stakeholders while applying appropriate security, privacy, and retention controls. In this scenario, the repository configuration cannot be responsibly decided until the team knows what types of information are in scope (for example, customer personal data) and what rules apply to storing, sharing, and retaining it.

Start by clarifying information governance needs such as:

• Data classification (sensitivity and handling rules)
• Who needs access and at what level (least privilege)
• Retention and disposition requirements (records management)

Once those constraints are known, the project can choose the repository settings and sharing approach that meet stakeholder access needs without violating policy or contractual obligations.

Security, privacy, access, and retention controls must be set based on data classification and records requirements before granting access.

Question 178

Topic: Process

A hybrid project has stakeholders in three time zones and a vendor providing detailed requirements. Team members have been emailing documents back and forth, and two groups recently built from different versions of the requirements specification, causing rework. Several stakeholders say they “can’t tell what the latest version is” and don’t have access to some project files.

What should the project manager do next?

• A. Submit a change request to rebaseline requirements immediately
• B. Escalate to the sponsor to direct everyone to stop using email
• C. Implement a single shared repository with version control and role-based access
• D. Pause requirements work until the steering committee approves a process

Best answer: C

What this tests: Process

Explanation: The immediate problem is uncontrolled artifact versions and uneven access, which is creating errors and rework. The best next step is to establish a single, controlled location for project information with version control and appropriate permissions so stakeholders can reliably find and use the most current artifacts.

Managing project artifacts includes keeping information current and ensuring it is accessible to the right stakeholders. When documents are shared through email, teams quickly lose version control, leading to conflicting work products and rework.

The next step is to create a single source of truth (typically in a PMIS/shared repository) and enforce basic configuration management:

• Store the current approved versions in one location
• Enable version history/check-in controls
• Set role-based access so stakeholders can retrieve what they need
• Communicate where the authoritative artifacts are maintained

Escalation, rebaselining, or pausing work may be appropriate later, but they do not first fix the underlying artifact control and accessibility problem.

A controlled, accessible single source of truth prevents outdated versions from being used and ensures stakeholders can retrieve current artifacts.

Question 179

Topic: People

A hybrid product implementation is facing repeated late changes from the operations director, who has high influence and has been resistant to the new workflow. After several targeted actions (one-on-one meetings, involving operations in backlog refinement, and agreeing on decision rights), the project sponsor asks how you will validate that stakeholder engagement has improved and is likely to stay improved.

Which evidence or artifact best validates improved engagement of this high-influence stakeholder?

• A. Updated stakeholder engagement assessment matrix showing current vs desired engagement improving for operations
• B. A log of emails and messages sent to operations stakeholders
• C. An increase in the operations director’s meeting attendance rate
• D. A revised communications management plan with more frequent status updates

Best answer: A

What this tests: People

Explanation: To validate engagement improvement, use evidence that reflects a stakeholder’s influence and their current commitment level versus what the project needs. A stakeholder engagement assessment matrix provides a structured, repeatable way to evaluate whether the high-influence operations director is moving from a resistant/neutral state toward a supportive/leading state needed for decisions and adoption.

The key concept is validating stakeholder engagement by measuring the quality and level of commitment of influential stakeholders, not just the volume of communications or participation. In this scenario, the operations director has high influence and has been driving disruptive changes, so the project needs evidence that their engagement level is shifting to the desired state (e.g., supportive of decisions and adoption). The stakeholder engagement assessment matrix (often paired with stakeholder analysis) captures current and desired engagement levels and can be updated over time to show a trend.

Practical validation steps include:

• Update current vs desired engagement for the operations director.
• Confirm the observed shift with direct feedback and decision behaviors (e.g., timely approvals, fewer late changes).
• Use the matrix trend to inform further engagement actions.

Attendance, message counts, and plan updates are activities or vanity indicators; they don’t reliably demonstrate commitment or influence-aligned engagement.

It directly compares current and desired engagement for a specific influential stakeholder and shows whether engagement is moving to the required state.

Question 180

Topic: People

A hybrid construction project has a safety incident at a site with strict regulatory oversight. The team includes several new subcontractors, and work must resume within hours to avoid a major penalty. The project manager must give clear, immediate direction to ensure compliance and prevent recurrence.

Which leadership style is most appropriate right now?

• A. Collaborative (facilitative) leadership
• B. Delegating (laissez-faire) leadership
• C. Coaching leadership
• D. Directive leadership

Best answer: D

What this tests: People

Explanation: A safety incident under strict regulatory oversight is a high-risk, time-critical situation where the priority is rapid stabilization and compliance. In that context, the project manager should use a directive style to set expectations, give unambiguous instructions, and ensure controls are followed before work continues. Once the situation is stabilized, the style can be adjusted as appropriate.

Leadership style should be tailored to the situation, and the strongest discriminator here is urgent safety/compliance risk with inexperienced parties. When immediate corrective action is needed and the team cannot safely self-organize (new subcontractors, regulatory scrutiny, hours to resume), a directive approach provides the clarity and control required to stop unsafe work, assign responsibilities, and enforce required procedures.

Typical directive actions in this moment include:

• Issue a stop-work/hold point and communicate non-negotiable safety requirements
• Assign owners for incident response and compliance verification
• Confirm corrective actions and approvals before restarting work

More collaborative styles are better after stabilization, when the team can contribute to root-cause learning and longer-term prevention.

A time-critical, compliance-driven safety situation requires clear instructions and tight control to quickly stabilize work.

Continue with full practice

Use the PMP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Focused topic pages

• PMP: People
• PMP: Process
• PMP: Business Environment

Free review resource

Read the PMP guide on PMExams.com for concept review, then return here for PM Mastery practice.