Free PMI-SP Full-Length Practice Exam: 170 Questions

This free full-length PMI-SP practice exam includes 170 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 170-question full-length practice format for PMI-SP preparation. Always confirm final exam-day timing, appointment rules, and candidate instructions directly with PMI before your scheduled exam.

How to run this diagnostic

Set a 210-minute timer and answer the 170 questions before reading explanations. Track misses by schedule strategy, planning/development, monitoring/control, closeout, or stakeholder communication.

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.

For concept review before or after this set, use the PMI-SP 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.

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 schedule-judgment practice.

Exam snapshot

Full-length exam mix

Practice questions

Questions 1-25

Question 1

Topic: Schedule Monitoring and Controlling

As of July 31, you are auditing a mechanical subcontractor’s monthly update before linking it to the integrated master schedule. The file shows 18 interface activities with no predecessors or successors to prime-contractor milestones, 11 activities using Finish On constraints, and 14 in-progress activities still showing their original remaining durations even though field reports say they are 80%-90% complete. The subcontractor also reports SPI = 0.98. Which audit focus should take priority to determine whether the data can be reliably integrated?

• A. Audit interface logic, constraint usage, and remaining-duration status
• B. Run Monte Carlo on the current integrated forecast
• C. Trend SPI over additional monthly reporting periods
• D. Perform total float analysis on the subcontractor path network

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The immediate issue is whether the subcontractor update is a credible schedule model, not whether its performance looks acceptable. Missing interface logic, hard constraints, and stale remaining-duration data can distort the integrated forecast and make later analysis outputs unreliable.

The priority is a schedule-model integrity audit. If interface activities are not tied to prime-contractor milestones, the subcontractor work may not drive or be driven correctly in the integrated master schedule. Finish On constraints can mask the true forecast by forcing dates, and very high reported percent complete with unchanged remaining duration is a warning that status data may be cosmetic rather than predictive.

Before using the file for deeper analysis, the scheduler should:

• verify predecessor and successor ties at each interface point
• challenge inappropriate hard constraints
• reconcile actual progress with remaining duration as of the data date

Only after those inputs are credible will float analysis, SPI trends, or schedule risk analysis produce decision-quality results.

Integration reliability depends first on model integrity, and missing logic, forced dates, and stale remaining durations make later analyses unreliable.

Question 2

Topic: Stakeholder Communications Management

A hybrid implementation has an approved schedule baseline and a customer-committed go-live milestone of September 30. On the August 15 data date, a vendor test-environment delivery is 8 working days late on the driving path to go-live. A related scope change request is still pending, and the schedule management plan says baseline dates can change only after approval. The sponsor needs clear visibility for tomorrow’s steering committee. What is the BEST action?

• A. Report overall percent complete and SPI for a simpler executive view.
• B. Replace baseline dates with the current forecast before the steering meeting.
• C. Send a milestone report with baseline, actual, forecast, driving-path impact, and pending change separate.
• D. Exclude the vendor dependency until the vendor confirms a recovery date.

Best answer: C

What this tests: Stakeholder Communications Management

Explanation: Useful schedule visibility means showing current status and forecast against the approved baseline for the committed milestone. Because the change request is still pending, the baseline must stay unchanged, and stakeholders need to see the vendor delay’s driving-path effect on September 30.

In schedule communications, the goal is to make commitments visible and decision-ready, not just to summarize progress. Here, the sponsor needs a steering-committee view of an approved baseline, a current driving-path delay, and the likely effect on a customer commitment. The best communication is a milestone-focused status report that clearly separates the approved baseline from current status and forecast.

• Show the committed milestone’s baseline date.
• Show actual/status information as of August 15.
• Show the forecast impact from the vendor delay.
• Keep the pending scope change separate until approval.

This preserves schedule-control integrity and gives stakeholders useful visibility of progress, forecast, and commitments. A simpler summary may look cleaner, but it would not show whether the promised go-live date is still credible.

This keeps baseline, status, and forecast distinct while showing the driving-path effect on the committed milestone.

Question 3

Topic: Stakeholder Communications Management

The status date is August 4. A vendor server delivery on the critical path is now forecast 10 working days late, moving the regulatory testing milestone from August 22 to September 5. The communication plan requires escalation to the sponsor when any committed milestone slips more than 3 days and says the escalation must state the issue, schedule impact, options, and decision needed. What is the best escalation content?

• A. Instruct the team to overlap installation and testing now, then report results next week.
• B. Tell the sponsor a vendor issue exists and send impact details after further analysis.
• C. State the vendor delay, quantify the 10-day milestone slip, compare realistic recovery options, and request sponsor approval of the chosen response.
• D. Replace the baseline milestone with September 5 and inform the sponsor of the updated plan.

Best answer: C

What this tests: Stakeholder Communications Management

Explanation: When a committed milestone exceeds the escalation threshold, the sponsor needs a decision-ready message, not just a status note. The best content identifies the issue, shows the 10-day schedule impact, outlines response options, and asks for the needed approval or direction.

For schedule issue escalation, the goal is to enable timely decision-making. A strong escalation does four things: states the issue, quantifies the impact to the schedule, presents realistic response options, and clearly asks for the decision or approval needed. Here, the vendor delay is on the critical path and moves a committed regulatory milestone by 10 working days, so the escalation should explicitly show that slip and frame viable recovery or change paths for sponsor action. Replacing the baseline with the forecast would hide variance, and directing fast tracking immediately would bypass proper analysis and approval. A complete escalation preserves schedule transparency and gives the sponsor enough information to act.

This escalation is decision-ready because it states the issue, quantifies schedule impact, presents options, and asks for the sponsor decision required.

Question 4

Topic: Schedule Planning and Development

During schedule development for a substation project, the contractual Ready for energization milestone is due October 15. Management wants to know whether that date is credible before approving any mitigation.

Both activities are on the driving path. Which analysis is most appropriate next?

• A. Use SPI trend to assess confidence
• B. Rely on total float alone
• C. Run a Monte Carlo schedule risk analysis
• D. Escalate the milestone as already late

Best answer: C

What this tests: Schedule Planning and Development

Explanation: The contract milestone is not yet forecast late, but it has only 2 workdays of float against activities with much wider duration uncertainty. A Monte Carlo schedule risk analysis is the best way to test the probability of meeting October 15 before deciding on escalation or schedule adjustment.

When a contractual milestone shows only a small amount of deterministic float, a single CPM finish date is not enough if the driving activities have wide duration ranges. In this case, the 2-day buffer is smaller than the uncertainty on both driving-path activities, so the next best step is a schedule risk analysis, typically using Monte Carlo, to estimate confidence in meeting October 15.

That result supports a fact-based decision on whether to escalate the date risk or approve mitigation. Relying only on float ignores uncertainty, SPI is not appropriate here because the project is still in schedule development and there is no execution performance trend yet, and treating the milestone as already late is premature because the deterministic forecast still meets the contract date.

The milestone still has positive deterministic float, but the uncertainty on its driving activities exceeds that buffer, so Monte Carlo best quantifies contractual-date risk.

Question 5

Topic: Schedule Planning and Development

Before baselining a 7-month facilities schedule, the scheduler runs float analysis. One driving-path activity, Install interior finishes, is 40 days long; 92 of 180 activities are 1-day tasks for routine crew work; and 15 activities show more than 60 days of total float because they are linked only to the project finish milestone. What is the best interpretation?

• A. The schedule is ready because the extra float protects delivery.
• B. The activity definitions are inconsistent and need refinement before baselining.
• C. SPI should be calculated next to confirm schedule realism.
• D. Monte Carlo should be run before revising the activity list.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: These float-analysis results indicate schedule-definition quality problems, not healthy flexibility. A 40-day driving-path activity is too broad for good control, many routine 1-day tasks are over-detailed, and very high total float caused by finish-only links signals weak network logic.

Float analysis can reveal more than schedule flexibility; it can also expose poor activity definition and weak logic in a draft schedule. Here, the 40-day driving-path activity is likely too broad to status and manage effectively, while the large number of routine 1-day tasks suggests unnecessary detail that can make maintenance harder without improving control. The activities with more than 60 days of total float are not showing healthy schedule margin if that float comes from being tied only to the project finish milestone; that usually indicates artificial or incomplete sequencing.

Before baselining, the scheduler should refine activity decomposition and add meaningful predecessor-successor logic so the schedule model supports credible analysis and reporting. High float from weak logic is not protection, and metrics such as SPI or Monte Carlo are less useful until the underlying schedule structure is sound.

The mix of a very long driving activity, many routine 1-day tasks, and artificially high float shows poor activity sizing and weak logic.

Question 6

Topic: Schedule Monitoring and Controlling

A scheduler is reviewing a draft weekly control report before it is sent to the sponsor and client.

Exhibit: Draft control report excerpt

Data date: April 30
Contract milestone: Factory Acceptance Test complete
Baseline date: June 20
Forecast date: July 2
Forecast variance: +8 workdays
Overall SPI: 1.01
Driving path total float: -8 workdays
Reason SPI is favorable: two non-driving fabrication packages finished early
Draft summary: "Schedule remains generally on track. Continue routine monitoring."

Which message is most important to add before issuing the report?

• A. The contract milestone is forecast 8 workdays late on the driving path, so recovery analysis and escalation are needed.
• B. Milestone dates should be removed and only SPI should be reported.
• C. The favorable SPI shows early work offsets the negative float on the driving path.
• D. The baseline should be reset to July 2 so the report reflects current dates.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The missing message is the actual schedule implication: the contractual milestone is forecast late on the driving path. A favorable overall SPI does not override negative float or a slipped milestone forecast, especially when the index is improved by non-driving work.

Control reporting should communicate what the schedule data means for commitments, not just repeat a favorable metric. Here, milestone analysis and driving-path analysis show a real problem: the contract milestone is forecast 8 workdays late and the path driving that date has negative float. The overall SPI of 1.01 is misleading because it was improved by early completion of non-driving fabrication work.

• Compare the committed milestone baseline with the forecast.
• Check whether the slippage is on the driving path.
• Explain why the aggregate SPI does not represent milestone protection.
• State the need for recovery analysis and stakeholder escalation.

Rebaselining or reporting SPI alone would hide variance instead of supporting schedule control.

Stakeholders need the driving-path milestone slippage called out because the favorable SPI is being masked by early non-driving work.

Question 7

Topic: Schedule Strategy

A construction project’s forecast now shows the handover milestone 12 workdays late. The owner asks for an audit-ready explanation of the delay, but the scheduler finds that monthly updates overwrote the same file, two logic changes were never logged, and approved versions are scattered across email. What is the best control action?

• A. Replace the baseline with the delayed forecast.
• B. Freeze edits, recover approved versions and logs, then reforecast under control.
• C. Use the newest file as the official record and fill gaps later.
• D. Crash a non-driving path with float to gain time.

Best answer: B

What this tests: Schedule Strategy

Explanation: The main problem is weak schedule configuration control, not just the delay itself. The scheduler should first preserve evidence, reconstruct the approved baseline and version history, and restore change-log discipline before issuing a controlled forecast or any change request.

For audit or forensic use, a schedule must have traceable lineage: an approved baseline, dated status versions, logged logic changes, and controlled records. In this scenario, overwritten files and missing log entries mean the current late forecast is not yet a defensible schedule record. The best corrective action is to stop further uncontrolled edits, preserve all existing files, reconstruct the approved model versions and change history from available records, and then produce a controlled forecast or formal change package.

• Preserve current evidence before it is altered again.
• Re-establish the approved baseline and version sequence.
• Reconcile missing change-log entries.
• Submit any reforecast or rebaseline through formal control.

Changing dates first may look faster, but it weakens auditability and schedule integrity.

Audit or forensic use requires preserved schedule evidence, traceable versions, and logged changes before issuing a new forecast or rebaseline.

Question 8

Topic: Stakeholder Communications Management

A scheduler is preparing a one-page monthly report for the steering committee. The committee wants early warning on externally committed dates, not detailed activity lists. In the latest update, overall SPI = 1.00 and the project finish date is unchanged, but the committed milestones show this pattern:

Which analysis/reporting technique would best support stakeholder awareness?

• A. Issue a milestone trend report for the committed dates
• B. Issue the detailed critical-path activity list
• C. Issue a rebaselined schedule with zero variance
• D. Issue only an overall SPI trend report

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: A milestone trend report is the best fit because the audience cares about specific externally committed dates. It shows that Site ready and Customer go-live are slipping from report to report even though overall SPI and the total finish date still look stable.

For stakeholder awareness, the most useful schedule report highlights the dates the audience actually cares about. Here, the steering committee wants visibility into externally committed milestones, not a detailed view of activity logic. Milestone trend analysis compares baseline dates with successive forecast dates, so it clearly shows that two commitments are drifting later each reporting period.

An overall SPI of 1.00 can mask localized slippage, and an unchanged final finish date does not mean every contractual or stakeholder-facing milestone is safe. A good schedule report preserves the difference between baseline and forecast so stakeholders can see emerging commitment risk early and decide whether escalation or recovery is needed. The key is to communicate milestone movement directly, not to bury it in aggregate metrics or excessive detail.

It makes drift in stakeholder-facing commitments visible over time without hiding variance behind aggregate metrics or a reset baseline.

Question 9

Topic: Schedule Monitoring and Controlling

A scheduler is reviewing a critical-path activity. Baseline duration is 10 working days with a planned crew of 2 technicians at 8 hours per day. At the status date after 5 working days, the task is 50% physically complete, has 5 working days remaining, and shows 120 actual labor-hours versus 80 planned labor-hours. Which interpretation is best?

• A. The task is ahead of schedule because it used extra labor-hours.
• B. The task is on plan for resource usage because 5 days remain.
• C. The task is behind schedule because actual hours exceed planned hours.
• D. The task is on schedule by progress, but labor usage is above plan.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: Schedule progress evidence comes from status data such as physical percent complete and remaining duration against the baseline. Here, 50% complete after 5 of 10 days with 5 days remaining is on-plan progress, while 120 actual labor-hours versus 80 planned shows higher-than-planned resource usage.

This item tests the difference between schedule progress evidence and resource utilization evidence. Progress is assessed from elapsed time, actual status, physical percent complete, and remaining duration versus the baseline. Resource utilization is assessed from crew loading or labor-hours consumed versus the planned usage. In this scenario, a 10-day activity is halfway through its duration and reports 50% physical complete with 5 days remaining, so its progress still aligns with the baseline. However, the team has used 120 labor-hours when only 80 were planned by the status date, which shows the task is consuming more resource effort than planned. That may signal inefficiency, over-allocation, or lower productivity, but it does not by itself prove schedule slippage. The common mistake is treating hours spent as direct evidence of schedule progress.

Physical progress and remaining duration match the 10-day baseline, while 120 actual hours versus 80 planned shows higher-than-planned resource utilization.

Question 10

Topic: Schedule Monitoring and Controlling

On a plant upgrade project, the data date is August 10. A field lead says a critical-path activity is 90% complete, but access problems mean 5 working days remain; the scheduler updates only percent complete and leaves 1 day remaining duration in the schedule. After recalculation, the turnover milestone still shows on time and the former driving path gains float. Which explanation best fits this result?

• A. This is a baseline problem; float is unreliable until the schedule is rebaselined.
• B. This is a cost problem; earned value must confirm the delay first.
• C. This is a risk problem; the 5-day impact should stay outside the update.
• D. This is a status-quality problem; unrealistic remaining duration distorted critical path, float, and forecast.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The distorted result comes from poor activity status quality, not from the baseline or cost system. If percent complete is updated but remaining duration stays unrealistically low, the schedule recalculates from bad status data and can show false float and an inaccurate finish forecast.

Critical path, float, and forecast dates depend on the quality of current activity status. In this scenario, the team knows 5 working days remain, but the schedule still carries only 1 day remaining duration. That mismatch makes the network think less work is left than reality, so recalculation can wrongly move the driving path, create artificial float, and keep downstream milestones looking on time. Percent complete by itself is not enough for reliable forecasting; remaining duration must reflect the current expected effort and timing. Rebaselining would only replace the measurement reference, and cost data would not correct a schedule model built on inaccurate status inputs.

Good schedule control starts with credible actual status before trusting the forecast.

Critical path and float are recalculated from current status, so a stale remaining duration can produce a false on-time forecast.

Question 11

Topic: Schedule Monitoring and Controlling

As of the data date, HVAC riser installation is 5 workdays late because of rework. It is on the driving path to a contractual turnover milestone, and the forecast milestone is now 3 workdays later than the approved baseline. A second qualified crew is available tomorrow and would reduce the remaining installation work by 4 workdays; a separate late procurement activity still has 8 workdays total float. No scope change has been approved. What is the best recovery response?

• A. Expedite the late procurement activity with remaining float
• B. Rebaseline the turnover milestone to the current forecast
• C. Report the variance and wait for the next update cycle
• D. Crash the remaining riser installation with the available crew

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The delay is already affecting a driving-path activity, so this is a schedule issue that needs recovery action now. Because adding a qualified crew can shorten the remaining critical work, crashing that activity is the best way to protect the contractual milestone while keeping the approved baseline intact.

Use recovery action on the work that actually drives the threatened commitment. Here, the delayed HVAC riser installation is on the driving path, and the stem explicitly says an added qualified crew can reduce its remaining duration by 4 workdays, enough to address the 3-workday forecast slip to the contractual milestone.

The approved baseline remains the control reference because no scope change has been approved. Replacing baseline dates with forecast dates is not recovery; it only hides variance. Likewise, expediting another late activity that still has 8 workdays of total float does not improve the milestone because that activity is not currently driving it. Reporting the delay is necessary, but reporting alone is not corrective action.

When commitments are threatened, favor feasible compression or resequencing on the driving path before considering rebaseline changes.

Compressing the remaining driving-path work is the only option that can recover the threatened milestone without improperly replacing the approved baseline.

Question 12

Topic: Schedule Planning and Development

At the August 14 status date, a facility upgrade schedule is updated on a Monday-Friday calendar. Milestone Plant Ready for Startup is forecast 6 working days late because predecessor activity Regulator Approval has not finished, and no approved change request has changed the contractual target date. During a precedence-diagram review, which action would most clearly reduce the schedule model’s credibility?

• A. Replace a long waiting lag with an explicit approval activity.
• B. Model a separate calendar if the regulator works different days.
• C. Add a Must Finish On constraint to the startup milestone.
• D. Keep the finish-to-start link from approval to the milestone.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: Forcing the milestone with a Must Finish On date makes the diagram look cleaner, but it overrides the network logic that currently shows a delay. In a credible schedule model, forecast dates should come from status, relationships, and calendars unless an approved change justifies a different control action.

The core concept is schedule model integrity. Here, the milestone is late because a predecessor is late, and there is no approved change to the contractual target. Applying a hard Must Finish On constraint would suppress the logic-driven forecast, weaken critical-path and float analysis, and make the network diagram less trustworthy for decision-making.

A credible precedence diagram should let dates flow from:

• actual status as of the data date
• logical dependencies between activities
• valid calendars and realistic activity modeling

If stakeholders still need the original commitment shown, the scheduler should report the variance and pursue recovery action or formal change control, not force the milestone date. The closest distractors actually improve transparency because they preserve or clarify the logic behind the forecast.

This hard constraint hides the logic-driven late forecast and breaks traceable cause-and-effect in the schedule model.

Question 13

Topic: Schedule Closeout

A construction project has received final acceptance. The contract and the organization’s closeout procedure require archiving the native schedule files, approved baselines, update narratives, and approved change records in a controlled repository. The scheduler is preparing the archive package and discovers that one approved excusable-delay change form is missing. What should the scheduler do next?

• A. Send the final schedule status report to stakeholders and use that as the closeout record.
• B. Archive the final PDF schedule report now and add supporting records later if needed.
• C. Replace the baseline dates with final actual dates so the archive reflects completed work.
• D. Reconcile the package to the archive checklist, obtain the missing approved record, and archive the complete set.

Best answer: D

What this tests: Schedule Closeout

Explanation: The best next step is to validate the archive package against the required procedure and correct any missing records before archiving. A complete, controlled schedule history is needed to satisfy contractual closeout and forensic readiness.

In schedule closeout, archiving is not just storing a final report. The scheduler should first verify that the archive package matches the defined procedure and contract requirements, including the native schedule files, approved baseline history, update support, and change approvals. Because an approved change form is missing, the package is incomplete and should be reconciled before it is archived.

An incomplete archive weakens contractual compliance and makes later claims analysis or forensic review harder. Replacing baseline dates is also wrong because the baseline is the approved performance reference and should not be overwritten at closeout. The key action is to validate completeness and configuration control first, then archive the full record.

Closeout archiving should follow defined procedures and include a complete, controlled schedule record before storage.

Question 14

Topic: Schedule Monitoring and Controlling

Every Friday, a plant turnaround project updates its integrated schedule using a common data date. Four subcontractors propose different status submissions. Which proposal would weaken schedule control the most?

• A. Weekly template with actual dates and remaining durations
• B. Weekly email with the same fields in a different layout
• C. Weekly exception report with full driving-work status and no-change confirmation
• D. Weekly list showing only percent complete for each activity

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The weakest submission is the one that reports only percent complete. Effective schedule control requires actual dates and remaining duration so the schedule model can produce a reliable forecast and show true driving-path impact.

Schedule control depends on status data that can update the schedule model, not just summarize progress. A weekly list that shows only percent complete weakens control because it does not provide the actual start/finish dates and remaining duration needed to recalculate the forecast, detect logic effects, or assess whether a delay is driving. Percent complete can support communication, but by itself it is not a reliable control input.

• Actual dates show what has truly happened.
• Remaining duration drives the new forecast.
• Variance comments help explain impact on driving work.

A different format may be inconvenient, but missing core status content is the more serious control weakness.

Percent complete alone does not provide the actual dates and remaining work needed to recalculate a credible schedule forecast.

Question 15

Topic: Schedule Monitoring and Controlling

At the June 10 status date, milestone M4 is due in 18 working days. Activities Configure Interface (6 days remaining) and Validate Data Mapping (8 days remaining) are both on the driving path, each has 0 days total float, and both require the same database architect. Her availability just dropped from 8 hours/day to 4 hours/day for the next 10 working days; an alternate architect can take one activity after a 2-day handoff. Current SPI is 1.00, meaning progress has matched plan through June 10. Which schedule analysis approach should the scheduler use first to recommend the best response?

• A. Perform float analysis on non-driving paths for recovery time.
• B. Use SPI trend analysis to project the new finish date.
• C. Update the resource calendar and run what-if scenarios on the driving path.
• D. Compare baseline and forecast dates only at milestone M4.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The resource change affects future work on a zero-float driving path, so the scheduler needs scenario testing rather than a historical performance metric. Updating the resource calendar and running what-if analysis shows the forecast impact and compares practical responses such as resequencing or using the alternate architect.

When resource availability changes on a driving path, the first priority is to model the change and test feasible alternatives. In this scenario, both remaining activities have 0 total float and compete for the same specialist, so the milestone forecast now depends on resource-constrained sequencing and staffing choices. The strongest analysis is to update the affected resource calendar and run what-if scenarios that compare realistic options, such as keeping one architect, adding the alternate after the 2-day handoff, or resequencing the work. SPI of 1.00 only confirms that performance matched plan through the status date; it does not model a newly reduced future capacity. Milestone-only review or analysis of non-driving float may describe impact elsewhere, but they do not identify the best response for the affected driving work.

What-if analysis with the updated resource calendar tests realistic staffing and sequencing alternatives before any control decision is made.

Question 16

Topic: Schedule Monitoring and Controlling

As of September 9, float analysis shows this remaining work before milestone M5:

Both activities require the same specialist. The specialist’s resource calendar is updated to show availability on only 2 of the next 5 project workdays; after that, availability returns to normal. No alternate resource is approved, and the specialist will be assigned first to the activity driving M5. The schedule uses a 5-day project calendar.

What is the most accurate conclusion?

• A. M5 will likely slip 3 workdays.
• B. M5 stays on date because remaining duration is unchanged.
• C. The schedule baseline should be revised before measuring impact.
• D. M5 stays on date because training float absorbs the change.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: Resource calendars affect forecast dates through elapsed working time, even when remaining duration does not change. Because the driving activity has zero float and only 2 of the next 5 workdays are usable, the milestone forecast moves out by 3 workdays.

This is a resource-calendar interpretation using float analysis. The driving activity still needs 4 days of work, but the specialist is available for only 2 of the next 5 project workdays. That means the activity can complete only 2 days of progress during that period and must use 2 more days afterward. Under normal availability, 4 days of remaining work would finish in 4 elapsed workdays; with the restricted calendar, it finishes in 7 elapsed workdays, creating a 3-workday slip. Because that activity has 0 total float and drives M5, the milestone slips by the same amount. The non-driving activity’s float does not protect a different activity on the driving path, and the baseline is not replaced just to reflect a forecast change.

The zero-float driving activity loses three planned working periods, so its forecast finish and M5 move by three workdays.

Question 17

Topic: Schedule Planning and Development

During development of an integrated schedule for a hospital equipment installation, the scheduler has one 15-day work package: Commission imaging suite. A biomedical SME says separate 4-day calibration and 3-day operator training activities are normally required, and the hospital representative says a 2-day regulatory witness test must finish before the handover milestone. None of those steps is currently modeled, and handover has 2 days of total float. Which analysis approach best validates whether the work package is complete before baselining?

• A. Add the missing tasks and run what-if analysis.
• B. Wait for SPI after execution begins.
• C. Check total float at the handover milestone.
• D. Analyze the current critical path only.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: The main issue is possible omitted work, not performance on the current schedule. The best validation method is to incorporate the SME- and stakeholder-identified activities and logic into the model and use what-if analysis to see whether dates or float change before baselining.

When SMEs and stakeholders identify likely missing activities, approvals, or handoffs, the scheduler should test whether the work package is fully decomposed in the schedule model. What-if analysis is the best fit because it lets the scheduler add the proposed calibration, training, and witness-test work, link it correctly, and recalculate the handover milestone.

• Add the missing activities and required logic.
• Recalculate dates and total float.
• Confirm the work package includes all required deliverables and interfaces.
• Update the planned work package definition before baseline approval.

Critical path or float analysis on the current model only evaluates the work already shown, so missing tasks can remain invisible. SPI is an execution metric, so it is too late for validating completeness during schedule development.

What-if analysis tests the schedule impact of SME- and stakeholder-identified missing work and logic before the baseline is approved.

Question 18

Topic: Schedule Monitoring and Controlling

On June 14, a predictive project’s schedule update shows the contractual “Testing complete” milestone forecast 8 working days late. The schedule management plan requires corrective-action analysis when a contract milestone is forecast more than 5 working days late or when the driving path has negative float; the vendor interface build path is driving the milestone at -8 days total float, while user training has +10 days total float. The quality lead says starting system testing before interface configuration is stable will likely cause rework. What should the scheduler recommend?

• A. Update the forecast, analyze recovery on the vendor path, and use change control if recovery cannot restore the date.
• B. Crash user training to finish that path earlier.
• C. Fast-track testing before the interface is stable.
• D. Rebaseline the milestone to the new forecast date.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The schedule metrics show a real control issue: the contractual milestone exceeds the variance threshold and the driving path has negative float. The scheduler should keep the baseline intact, update the forecast, and focus recovery analysis on the path causing the slip, using formal change control only if the commitment cannot be recovered.

Schedule metrics should drive control decisions, not cosmetic reporting. Here, two triggers are present: the contractual milestone is more than 5 working days late and the driving path has negative float. That means the team should treat this as an active schedule issue, confirm the forecast, and evaluate realistic recovery actions on the vendor interface path because that path is causing the late milestone.

• Update and communicate the forecast as current expected performance.
• Analyze feasible recovery on the driving path.
• Use change control if the approved recovery still cannot meet the contractual date or requires an approved date change.

Rebaselining now would hide variance, and accelerating non-driving or unstable work would not provide credible schedule control.

Negative float on the driving path and an 8-day contractual slip trigger schedule control, so the forecast should be updated and credible recovery should focus on that path before any approved baseline change.

Question 19

Topic: Schedule Monitoring and Controlling

A plant upgrade has a contractual startup milestone baselined for July 30. At the June 10 data date, the forecast is August 6. Driving-path analysis shows the slip is caused by equipment commissioning and operator validation; validation cannot start until commissioning finishes because of safety rules. The same specialist is assigned 50% to those activities and 50% to a training package with 8 days of total float. Which corrective action best addresses the cause of the slippage?

• A. Overlap validation with commissioning to recover lost time.
• B. Reassign the specialist to commissioning/validation and resequence training within float.
• C. Crash the training package to preserve its remaining float.
• D. Rebaseline startup to the current August 6 forecast.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: The slippage is driven by limited specialist availability on the driving path, not by the training package. The best recovery action is to move the constrained resource to commissioning and validation and let the non-driving work absorb the impact within its float.

The key distinction is between work that drives the milestone and work that does not. Here, the startup delay comes from commissioning and validation, and both depend on a scarce specialist. Because validation has a mandatory finish-to-start relationship with commissioning, overlapping those activities is not a valid recovery option. The training package is the better place to absorb impact because it has 8 days of total float and is not driving the startup milestone.

A sound PMI-SP response is to act on the actual cause of the variance:

• Shift the constrained specialist to the driving-path activities.
• Use available float on the training package before compressing it.
• Keep the baseline as the control reference while updating the forecast.

Reporting or rebaselining may follow governance rules, but neither fixes the current source of slippage.

This action targets the constrained resource on the driving path while using available float on non-driving work.

Question 20

Topic: Schedule Strategy

A healthcare organization is deploying a patient-record platform. Infrastructure cutover, data migration, and regulator sign-off have fixed contractual dates, but user-facing features will be refined in two-week iterations as clinicians provide feedback during delivery. Which scheduling approach is most appropriate?

• A. Hybrid schedule with fixed milestone baseline and iterative release planning
• B. Fully agile cadence-based schedule for the entire project
• C. Informal lookahead planning until requirements stabilize
• D. Fully predictive baseline for all work upfront

Best answer: A

What this tests: Schedule Strategy

Explanation: This project has both fixed external commitments and evolving internal feature scope. A hybrid scheduling approach best supports baseline control for contractual and regulatory milestones while using iterative planning for work that cannot be credibly detailed upfront.

The key scheduling discriminator is the mix of fixed milestone commitments and emerging detailed scope. Work tied to contract and regulatory dates needs a baseline-managed schedule with clear dependencies and milestone control. At the same time, feature-level work that will evolve through clinician feedback should not be forced into a fully detailed predictive plan too early.

A hybrid approach fits these conditions by combining:

• baseline control for fixed milestones and cross-team dependencies
• iterative release or sprint planning for evolving product features
• ongoing forecast updates as feedback changes remaining work

A fully predictive approach would create low-credibility detail for work that is intentionally adaptive, while a fully agile approach would weaken schedule control for externally committed dates.

It preserves control of committed dates while allowing detailed planning to emerge iteratively for evolving feature work.

Question 21

Topic: Schedule Monitoring and Controlling

On the data date, a vendor component delivery on the driving path is forecast 3 working days late because a previously identified customs-delay risk occurred. The approved schedule baseline includes a 5-day contingency buffer before the contractual commissioning milestone, and a training work package has 8 days of total float. The schedule management plan requires reserve usage to be tracked and rebaselining only through approved change control. What should the scheduler recommend?

• A. Crash the training work package to recover time from its float.
• B. Fast track installation and commissioning to recover the 3-day slip.
• C. Use 3 days of approved contingency reserve, update the forecast and reserve tracking, and keep the baseline unchanged.
• D. Reset the baseline commissioning date to the current 3-day-late forecast.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: Reserve analysis compares current schedule impact with the time reserve that was planned for identified risks. Here, the delay is 3 days and the approved contingency buffer still has 5 days available, so the team should consume part of that reserve, update the forecast and reserve status, and continue measuring against the same baseline.

Reserve analysis supports schedule control by showing whether a variance caused by a known risk can be handled within approved time reserves or whether escalation and formal change control are needed. In this case, the risk was identified in advance, it occurred on the driving path, and the schedule baseline already contains a 5-day contingency buffer for that exposure. Because the impact is only 3 days, the proper action is to draw down part of that contingency, update the current forecast and reserve tracking, and keep the baseline intact. Rebaselining is only appropriate when approved change control authorizes replacing the control reference, not when planned reserve is simply being used. The key takeaway is that reserve analysis informs transparent control decisions without hiding variance.

Reserve analysis shows the 3-day driving-path delay can be absorbed by the approved contingency buffer, so no rebaseline is needed.

Question 22

Topic: Schedule Closeout

On a facilities project, all physical work is complete and the contract requires final acceptance of the as-built schedule, including actual dates for contractual milestones. In the closeout review, the turnover milestone has conflicting completion dates from the vendor and the site team, and the schedule still contains out-of-sequence progress on the commissioning path. The project manager asks the scheduler to issue the final accepted schedule today. What is the best next step?

• A. Rebaseline the turnover milestone and issue the closeout package.
• B. Archive the schedule and request acceptance based on physical completion.
• C. Validate the turnover date, fix status and logic, then resubmit.
• D. Send the final schedule report now and correct it later.

Best answer: C

What this tests: Schedule Closeout

Explanation: The final schedule cannot be accepted while a contractual milestone date is unresolved and the schedule logic is not credible. The scheduler should first validate the actual date and correct the final status and logic, then seek closeout acceptance.

In schedule closeout, acceptance depends on an accurate and supportable final schedule record, not just completed work. Here, the turnover milestone is contractually important, its actual finish date is disputed, and the schedule still shows out-of-sequence progress on the commissioning path. That means the final schedule is not yet reliable enough for acceptance.

Before requesting closeout acceptance, the scheduler should:

• verify the milestone date against objective records,
• correct the status and logic in the schedule model,
• then resubmit the final schedule package.

Rebaselining would replace the control reference instead of resolving the issue, and reporting or archiving the schedule without correction would leave an open closeout problem.

Closeout acceptance requires a credible final schedule with validated actual dates for contractual milestones.

Question 23

Topic: Schedule Monitoring and Controlling

On a predictive data-center project, the latest status update shows a critical-path installation activity finished 6 working days late. The turnover milestone is now forecast 4 working days late. A procurement activity outside the driving path has 12 days of total float. The sponsor asks the scheduler to “move the baseline to the forecast” while the team considers overtime on two remaining critical-path activities. What is the best next action?

• A. Analyze remaining critical-path options, reforecast, and keep the baseline until formal approval.
• B. Rebaseline the milestone now without formal approval.
• C. Crash the procurement activity with 12 days of float.
• D. Fast-track commissioning before installation is complete.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The best response is to test feasible recovery actions on the remaining critical path, then update the forecast while leaving the approved baseline intact. A late forecast signals the need for analysis and control, not an automatic rebaseline.

Schedule optimization should focus on the work that is actually driving the late milestone. Here, the delay is on the critical path, so the scheduler should evaluate feasible recovery options on the remaining critical-path activities, such as overtime or resequencing, and then issue an updated forecast based on that analysis. The approved baseline remains the performance reference until a justified change is formally approved through change control.

Rebaselining just because the forecast slipped would hide variance instead of controlling it. Likewise, accelerating an activity with positive float will not recover the milestone, and breaking valid logic to overlap work creates an unreliable schedule model. The key takeaway is to separate recovery forecasting from baseline replacement and use formal approval before changing the baseline.

It addresses the driving delay, creates a credible recovery forecast, and preserves baseline control until any change is formally approved.

Question 24

Topic: Schedule Strategy

During a weekly schedule update, a discipline lead overwrites two baseline milestone dates in the master schedule after a customer asks for a later handoff. The schedule management plan allows routine status updates to forecast dates, but baseline changes require approved change control. The impact of the requested shift has not been analyzed yet. What should the scheduler do next?

• A. Resequence downstream work to support the new dates before impact analysis.
• B. Issue the status report with the revised dates and seek approval later.
• C. Rebaseline the affected milestones now so the schedule matches the request.
• D. Restore the approved baseline, model the change in the forecast, and submit a change request.

Best answer: D

What this tests: Schedule Strategy

Explanation: The schedule baseline is a controlled reference and cannot be changed through routine statusing or an informal request. The best next step is to restore the authorized baseline, analyze the requested shift in the forecast, and route any baseline revision through formal change control.

Change-control procedures protect the schedule baseline by separating status, forecast, and baseline. In this scenario, the customer request has not been analyzed or approved, so the overwritten baseline dates are unauthorized. The scheduler should first restore the last approved baseline, then test the requested shift in the forecast or working schedule to understand its impact, and finally submit that impact through the formal change process.

• Keep the baseline as the approved performance reference.
• Use the forecast to evaluate proposed date changes.
• Update the baseline only after approval and version control.

Simply communicating the new dates, rebaselining immediately, or changing logic before credible analysis would weaken schedule control and hide true variance.

This preserves the authorized baseline while evaluating the requested change through formal change control before any baseline update occurs.

Question 25

Topic: Schedule Strategy

You are finalizing the schedule management plan for a design-build project before the baseline is approved. The contract requires a monthly CPM update using retained logic, a contractual substantial-completion milestone tied to liquidated damages, and time impact analysis for any excusable-delay request against the current accepted baseline. Your company normally uses informal email approval for schedule revisions. What is the BEST action?

• A. Track the contractual milestone in the schedule but manage delay claims separately.
• B. Use the company’s normal approval process unless the owner objects after baseline approval.
• C. Approve the baseline now and add the contract-specific controls in the first update.
• D. Incorporate the contract update, milestone, acceptance, and delay-analysis rules into the schedule management plan.

Best answer: D

What this tests: Schedule Strategy

Explanation: Contract schedule requirements must shape the schedule management plan before the baseline is approved. The required CPM update method, contractual milestone, accepted-baseline rule, and time impact analysis define how the schedule will be controlled and reported, so they cannot be deferred or handled informally.

The core concept is contract-driven schedule governance. The schedule management plan defines how schedule updates, approvals, control thresholds, reporting, and change analysis will work. Here, the contract already sets critical schedule rules: monthly CPM updates using retained logic, a milestone with liquidated-damages exposure, and time impact analysis against the current accepted baseline. Those requirements must be built into the plan before baseline acceptance so the team can status the schedule, measure variance, and evaluate delay entitlement consistently.

Internal practices such as informal email approvals or biweekly lookaheads may still be used, but only as supplements to the contract-required process. Baselining first and aligning later is the closest trap because it can leave the initial accepted baseline and update cycle misaligned with contractual control needs.

The schedule management plan must define the contract-required schedule control, reporting, and delay-analysis procedures before the baseline is accepted.

Questions 26-50

Question 26

Topic: Schedule Planning and Development

A scheduler is finalizing a draft schedule for a control-system project within a plant modernization program. The draft shows interface testing starting on August 18, but the program integrated master schedule requires interface readiness by August 11. The vendor contract also requires customer approval of design changes before equipment shipment, and that dependency is not yet in the logic. The schedule has not been baselined. What is the best next step?

• A. Send the draft dates to stakeholders and wait for the program office to select a recovery action.
• B. Reconcile the draft with the program milestone and contract requirements, add the missing dependency, and update the schedule model.
• C. Compress the project’s internal testing activities immediately to protect the August 11 milestone.
• D. Baseline the current dates and use variance reporting to show the conflict after execution starts.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: The schedule already conflicts with a required program milestone, and it is also missing a contract-driven dependency. Before baselining, reporting, or compressing work, the scheduler should first reconcile those external requirements and correct the schedule model.

In schedule planning and development, a draft schedule must be aligned with higher-level program commitments and contract documentation before it becomes a reliable basis for decisions. Here, the project schedule misses a program milestone and omits a contract-required dependency, so the model is not yet credible. The proper next step is to validate those external requirements, incorporate the missing logic, and then reassess the dates.

• Confirm the required milestone and contract condition.
• Add the missing external dependency to the schedule model.
• Recalculate the schedule and review the impact before seeking baseline approval.

Baselining, recovery, or stakeholder reporting should follow a valid aligned schedule, not replace that validation step.

The next step is to make the schedule credible by aligning external milestones and contract-required logic before baseline or recovery actions.

Question 27

Topic: Schedule Monitoring and Controlling

At the July 15 status date on a data center migration project, the forecast for the contractual cutover milestone is 8 workdays late because a firewall configuration activity on the driving path needs more time. The schedule management plan says any contractual milestone forecast more than 5 workdays late requires a corrective-action recommendation. Which response best reflects schedule control rather than simple status reporting?

• A. Publish the 8-day slip in the weekly status report only.
• B. Crash user training, which still has 6 workdays of float.
• C. Rebaseline the cutover milestone to the new forecast date.
• D. Recommend a driving-path recovery action with impact analysis for approval.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: This is a threshold-triggered control situation, not just a reporting update. Because the delayed work is on the driving path to a contractual milestone and exceeds the plan’s variance limit, the scheduler should propose a corrective action and route its impact through the approval process.

Reporting current status tells stakeholders the forecast is 8 workdays late; schedule control goes further by recommending how to respond when a defined threshold is exceeded. In this case, the slip affects a contractual milestone, the delayed work is on the driving path, and the schedule management plan explicitly requires a corrective-action recommendation once variance exceeds 5 workdays. The appropriate next step is to analyze feasible recovery options on the driving work, quantify their schedule impact, and present that recommendation through the project’s approval path if it changes commitments or the baseline. Simply communicating the slip is necessary but insufficient. Rebaselining would hide current performance, and accelerating work that still has float would not recover the threatened milestone. The key distinction is status visibility versus controlled action.

The forecast breach triggers schedule control, so the scheduler should recommend an approved recovery action on the driving path instead of merely reporting the delay.

Question 28

Topic: Schedule Strategy

A hybrid product rollout is moving from charter approval into detailed planning. Two vendors use different scheduling tools, the internal team tracks work on a board, and the sponsor wants one integrated schedule with monthly variance escalation. No schedule governance has been approved. What should the scheduler do next?

• A. Merge team dates and baseline the integrated schedule now.
• B. Develop and approve the schedule management plan with methods, tools, update rules, thresholds, and approval rules.
• C. Send a monthly milestone report before defining governance.
• D. Let teams keep local methods and rebaseline after the first update.

Best answer: B

What this tests: Schedule Strategy

Explanation: Before detailed schedule development, the project needs approved scheduling policies and procedures. Defining the schedule management plan sets the common methodology, tool standards, update parameters, variance thresholds, and approval requirements needed for a credible integrated schedule.

This is a Schedule Strategy decision. When multiple teams and vendors use different approaches, the first step is to define how the schedule will be created, updated, analyzed, and controlled. That governance is usually documented in the schedule management plan and should cover the scheduling methodology, tool or interface standards, update parameters, variance thresholds, and who approves changes or exceptions. Once those rules are approved, the team can build and baseline an integrated schedule with consistent data and control discipline. Building the schedule first creates weak schedule integrity, reporting first does not solve the policy gap, and rebaselining is not a substitute for missing governance.

This establishes the required scheduling policies before integrating or baselining schedule data from multiple sources.

Question 29

Topic: Stakeholder Communications Management

As of the status date March 12, 2026, the project uses a Monday-Friday calendar. Activity Interface test is a finish-to-start predecessor to the contractual milestone Go-live, which has 0 days total float and a Must Finish On date of March 31, 2026. A vendor delay now moves the forecast Go-live date to April 8, 2026.

Exhibit: Communication management plan excerpt

Who should receive this schedule issue information now?

• A. Core team and functional leads in the next weekly update
• B. Sponsor, customer project manager, and program manager
• C. PMO and affected workstream leads after a CCB decision
• D. Vendor manager only until recovery options are finalized

Best answer: B

What this tests: Stakeholder Communications Management

Explanation: This is already a schedule issue on a contractual milestone, not a routine status update. The communication management plan gives a clear trigger and recipient list, so the issue must be escalated immediately to the defined escalation audience.

The key concept is applying the communication management plan exactly as written when a schedule issue crosses a defined escalation threshold. Here, the forecast Go-live date slips from a fixed contractual date of March 31 to April 8 on a zero-float path, so the issue exceeds the plan’s trigger of more than 3 working days on a contractual milestone.

Because that trigger has been met, the scheduler should send the issue information to the sponsor, customer project manager, and program manager within 1 business day. The weekly status audience is for routine reporting, not threshold-based escalation. The PMO and affected leads are listed for communication after an approved baseline change, which has not happened yet. Waiting for recovery options before escalating would delay required communication and weaken timely decision-making.

The communication management plan requires immediate escalation to these recipients when a contractual milestone slips by more than 3 working days.

Question 30

Topic: Schedule Strategy

A hybrid product rollout will combine a vendor construction schedule and three agile release-team plans into one reporting schedule. The contract includes a fixed October 31 acceptance milestone, the PMO requires escalation for forecast slippage over 10 working days, and two teams currently use different tools and calendars. Before detailed scheduling begins, what is the best action for the scheduler?

• A. Collect weekly milestone dates only, and defer approval rules until a variance appears.
• B. Build the integrated schedule immediately, then define governance rules after baselining.
• C. Let each team keep its current tool and calendar, then normalize dates after the first status cycle.
• D. Approve a schedule management plan with common methods, tool standards, parameters, thresholds, and approvals.

Best answer: D

What this tests: Schedule Strategy

Explanation: The best action is to establish and approve the scheduling rules before detailed planning starts. With a fixed contractual milestone, a stated escalation threshold, and inconsistent tools and calendars, the project needs a common methodology and approval structure to produce a usable integrated schedule.

This tests schedule strategy: setting the policies and procedures that govern how the schedule will be created, maintained, and controlled. In this situation, the key problem is not yet a schedule variance; it is the absence of agreed scheduling standards across teams. The scheduler should first establish and obtain approval for the schedule management plan or equivalent governance guidance that defines the methodology, tool and data standards, calendar and coding parameters, variance thresholds, and who approves the baseline and later schedule changes. That creates a consistent schedule model and makes reporting against the October 31 commitment meaningful. Waiting until after status collection or baselining would allow inconsistent assumptions into the schedule and weaken control.

An approved scheduling policy framework is needed first so all teams build and control the integrated schedule using consistent methods, parameters, thresholds, and approval rules.

Question 31

Topic: Schedule Monitoring and Controlling

On the weekly data date, a vendor interface activity on the driving path is now forecast 6 working days late. Actual dates, remaining duration, and logic have already been validated with the activity owner and procurement lead. The schedule management plan requires stakeholder notification when a customer milestone slips by more than 3 days, and the steering committee update is due this afternoon. What should the scheduler do next?

• A. Publish a schedule status report with variance, forecast, and milestone impact.
• B. Update the baseline date to match the forecast before notifying stakeholders.
• C. Begin recovery actions first and report after dates stabilize.
• D. Share the current schedule file only and let stakeholders infer the impact.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: After status and logic are validated, the next step is to use schedule documentation to communicate the variance and revised forecast. Because the reporting threshold has been exceeded, stakeholders need a clear status report that preserves the baseline comparison and explains milestone impact.

The key concept is using the right schedule documentation once the forecast is credible. In this case, the delay has already been validated through actual dates, remaining duration, and logic review, so the scheduler should now document and communicate the impact. Since the schedule management plan requires notification when a customer milestone slips by more than 3 days, the appropriate next step is a schedule status report that shows baseline variance, updated forecast, and the effect on the milestone.

This keeps control data transparent:

• It preserves the approved baseline for performance measurement.
• It gives stakeholders a clear view of the current forecast.
• It supports later decisions on recovery or escalation.

Rebaselining would hide variance, while acting on recovery first or sending only a raw schedule file weakens stakeholder awareness.

A formal status report is the next step because the forecast is validated and the reporting threshold has been exceeded.

Question 32

Topic: Schedule Monitoring and Controlling

On a refinery turnaround, the status date is July 18, 2026. The project manager says, “We are finishing the activities that the baseline said should be done by now.” The baseline shows 52 activities should be complete by July 18, but only 39 are actually complete; several others are reported 80%-90% complete. Which metric or analysis output would BEST validate that claim?

• A. Schedule performance index, comparing earned value vs planned value
• B. Baseline execution index, comparing actual vs planned completions by the status date
• C. Total float analysis, comparing remaining flexibility on near-critical paths
• D. Milestone trend analysis, comparing forecast movement for key milestones

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: The claim is about whether activities planned to be finished by the status date are actually finished. Baseline execution index is the most direct metric for that check; with 39 complete versus 52 planned, the result is \(39/52 = 0.75\), which does not support the claim.

The key is to match the metric to the claim being made. This statement is not mainly about earned value efficiency, remaining path flexibility, or whether one milestone is still trending acceptably; it is about whether the work that the baseline expected to be complete by July 18 is in fact complete. Baseline execution index measures exactly that relationship: actual completed activities divided by baseline-planned completed activities as of the status date. Here, \(39/52 = 0.75\), so execution is behind the baseline. Schedule performance index can give partial credit for in-progress work, so many activities reported at 80%-90% complete could make status look healthier than actual completions. Float and milestone analyses are useful, but they do not directly validate this specific completion claim.

This directly tests whether baseline-planned completions have actually been finished, and here it would show only 39 of 52 planned completions were achieved.

Question 33

Topic: Schedule Planning and Development

A scheduler has completed the activity list, logic, and duration estimates for a facility upgrade. The project is still developing the schedule model, and the baseline has not been approved. Several required technicians are shared with another project and work different shift calendars. Before assigning resources to the activities, what is the best next step?

• A. Rebaseline the schedule for the expected staffing limits
• B. Confirm resource availability and calendars for the required roles
• C. Assign provisional resources and fix calendar conflicts later
• D. Publish a draft schedule status report for stakeholders

Best answer: B

What this tests: Schedule Planning and Development

Explanation: Before assigning resources, the scheduler needs validated resource availability and calendars. Shared specialists and different work patterns can change when work can actually occur, so assignments made without that input are not credible.

In schedule planning and development, resource assignment should be based on realistic working time and actual availability. The scenario already says the activity list, logic, and duration estimates are done, so the missing input is whether the needed technicians are available and which calendars apply to them. That information directly affects when activities can be staffed and whether planned dates are feasible.

If resources are shared or work different shifts, assigning them before confirming calendars can create an unrealistic schedule model. Reporting to stakeholders does not solve the planning gap, and rebaselining is inappropriate because no approved baseline exists yet. The closest distractor is provisional assignment, but it skips the validation that should come first.

Assignments should be based on validated availability and calendars so the schedule model reflects realistic working time and staffing constraints.

Question 34

Topic: Schedule Planning and Development

A scheduler is developing a predictive project schedule for a plant startup. Two critical-path activities are logically allowed to run in parallel, but both require the same certified test engineer, and only one engineer is available during the planned window. The current unleveled schedule meets the startup milestone only because those activities overlap; logic and durations have already been validated, and no approved extra staffing or overtime exists. What should the scheduler do next?

• A. Report the overlap risk and keep the current activity dates.
• B. Crash the activities immediately to preserve the startup milestone.
• C. Level the schedule using the engineer’s availability, then reassess dates.
• D. Submit a change request to move the startup milestone now.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: This is a resource overallocation problem. Since the logic and durations are already credible, the scheduler should first level the plan to reflect the single engineer’s actual availability, then see whether compression or formal change review is still needed.

When a schedule appears achievable only because one scarce resource is double-booked, the model is not yet executable. Here, the activity logic and durations have already been validated, and there is no approved overtime or additional staffing, so the immediate next step is to resolve the conflict through resource leveling. That produces a feasible sequence and a credible forecast based on real availability.

After leveling, the scheduler can evaluate the resulting milestone impact. If the startup date is still unacceptable, then schedule compression options or a formal scope/date change review may be appropriate. Reporting or rebaselining before fixing the resource conflict would rely on an unrealistic schedule model.

The key takeaway is to make the schedule feasible first, then decide whether recovery or change control is necessary.

Because the conflict is a known single-resource constraint in an otherwise validated model, the next step is to level the schedule before considering compression or change control.

Question 35

Topic: Schedule Planning and Development

A hospital equipment installation schedule has a regulatory go-live milestone on September 30. Logic, calendars, and remaining durations have been validated. Two activities that both require the same certified technician overlap by 3 days, but the current forecast still has 5 days of total float to the milestone and management wants the finish date protected if possible. What should the scheduler do next?

• A. Delay the work until the technician is free.
• B. Change the activity dependencies to a new sequence.
• C. Add resources or overtime to shorten durations.
• D. Shift one activity within available float.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: This is a resource smoothing situation. The conflict can be removed by moving work within available float, so the finish milestone stays protected and the logic model remains intact. Leveling, compression, and resequencing would have different schedule effects.

Resource smoothing adjusts activity timing within available float to remove a resource over-allocation without changing the project finish date. In this scenario, the scheduler has already validated logic, calendars, and remaining duration data, so the schedule model is credible. The overlap is 3 days, and there are 5 days of total float to the regulatory milestone, which means one activity can be shifted to resolve the technician conflict while still protecting the finish date. Resource leveling is different because it resolves resource limits even if dates slip. Schedule compression is used to shorten durations, usually with added cost or risk. Resequencing changes the work order or logic and is not the first choice when the existing logic is valid and float already provides a solution.

This is resource smoothing because it resolves the over-allocation within float without moving the finish milestone.

Question 36

Topic: Schedule Planning and Development

At the May 15 status date, a project handoff that feeds a program integration milestone is forecast to finish on July 18. The project’s approved schedule baseline and the program integrated master plan both show July 1 for that handoff, and the slip is on the project’s driving path. No recovery plan or approved change exists. What is the best alignment action?

• A. Add a finish-no-later-than constraint at July 1
• B. Keep reporting July 1 as the project date
• C. Move the schedule baseline handoff date to July 18
• D. Analyze dependency impact and raise recovery or change through program governance

Best answer: D

What this tests: Schedule Planning and Development

Explanation: The key distinction is baseline versus forecast. July 18 is the current forecast, not an approved new baseline, so the scheduler should analyze the inter-project impact and take recovery or change through program governance instead of forcing dates or overwriting the baseline.

When a project date no longer matches the program integrated master plan, the first question is whether the differing date is a forecast or an approved baseline change. Here, July 1 remains the approved baseline date, while July 18 is the current forecast based on status. The right alignment action is to evaluate the driving-path impact on the dependent program milestone, then present recovery options or a formal change request through the program’s governance process.

• retain the approved baseline for performance measurement
• show the current forecast and downstream dependency impact
• assess recovery on the driving work, not by forcing dates
• seek approval before any rebaseline

Manually constraining the date or replacing the baseline would make the schedule look aligned without actually improving control or decision quality.

This preserves schedule-model integrity by treating July 18 as a forecast variance and aligning through dependency analysis plus approved recovery or change control.

Question 37

Topic: Schedule Strategy

A PMO is reviewing schedule strategies for four projects. The objective is to match each schedule approach to the project’s uncertainty level and commitment needs. Which proposed approach is the poorest fit and should be challenged first?

• A. A refinery turnaround uses a resource-loaded predictive baseline tied to shutdown handoffs.
• B. A prototype R&D effort uses a locked 12-month activity baseline despite changing experiment paths.
• C. An ERP rollout uses fixed vendor milestones and rolling-wave detail for the next 90 days.
• D. An analytics product discovery effort uses release milestones with iteration forecasts.

Best answer: B

What this tests: Schedule Strategy

Explanation: The misfit is the locked 12-month detailed baseline for prototype R&D work. When task sequencing is expected to change frequently, the schedule should keep high-level commitments visible and use rolling-wave detail for near-term work rather than pretend the full activity network is stable.

A schedule approach should match how stable the work is, how firm the external dates are, and how much detailed logic is credible now. Stable, deadline-driven work supports a detailed predictive baseline. Agile or hybrid work with evolving scope is better managed with milestone commitments, release forecasts, and rolling-wave planning. Experimental prototype work has uncertain task paths, so locking a 12-month activity-level baseline creates false precision and weakens forecast credibility. It can push the team toward manual date forcing or repeated unnecessary change requests instead of honest replanning. A better fit is to baseline key milestones or decision points, then add detailed activity logic only for the near term as the work becomes knowable. The ERP rollout may also be adaptive, but its rolling-wave structure is appropriate because only near-term site detail varies.

Experimental work with changing task paths should not be controlled with a locked long-range activity baseline; it needs higher-level commitments and near-term detail.

Question 38

Topic: Schedule Monitoring and Controlling

As of the weekly data date, which update most clearly shows that resource information conflicts with the current activity forecast?

• A. A foundation task is 3 days late but still has 8 days of total float.
• B. A design lead reports 60% complete and confirms 4 days remaining.
• C. A sponsor asks for the milestone date to be highlighted in the status report.
• D. A critical test still forecasts a Friday finish using two technicians, but one technician was reassigned for 2 weeks and the resource calendar was not updated.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The technician reassignment directly contradicts the forecast assumption that two technicians are available. The schedule should be updated for current resource availability and recalculated before that finish date is trusted.

In schedule monitoring and controlling, a forecast is only credible if the schedule model still reflects current resource availability. Here, the critical test activity is forecast with two technicians, but one has been reassigned for the next 2 weeks and the resource calendar was not updated. That means the resource information now conflicts with the activity forecast, so the scheduler should update the resource data and recalculate the schedule.

A late activity with remaining float is a variance, not necessarily a resource-assumption conflict. A lead confirming percent complete and remaining duration is normal status input when it matches planned resourcing. A request to highlight a milestone affects communication, not schedule logic. The key takeaway is to question any forecast that still relies on resources that are no longer actually available.

The forecast depends on two technicians, so losing one without updating the resource data makes the current finish date unreliable.

Question 39

Topic: Schedule Planning and Development

A platform project in a transformation program must complete interface testing before two rollout projects can start user acceptance testing. An approved vendor change adds 15 working days to that interface milestone. In the integrated master plan, this milestone drives the program’s regulatory go-live date, which has 3 working days of total float left. What is the best scheduler action?

• A. Shift rollout project dates locally and report the impact later.
• B. Update the project and integrated schedules, analyze the driving path, and use program change control for any baseline shift.
• C. Start rollout testing early, before interface testing is complete.
• D. Reset the baseline milestone date to match the new forecast.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: The approved change affects a driving inter-project milestone, so the forecast must be updated in both the project schedule and the integrated master plan. Then the scheduler should assess the driving-path impact and use formal program change control for any baseline movement.

When an approved change affects a milestone that drives a program objective, the scheduler should first update the current forecast in the project schedule and the integrated master plan or schedule. That keeps the schedule model aligned across dependent projects and shows the real impact to the regulatory go-live date. Because the 15-day delay exceeds the 3 days of remaining total float, the program objective is at risk unless recovery on the driving path is found. Any shift to the approved baseline must go through formal program change control rather than being changed directly in the baseline. Starting downstream testing before the predecessor milestone is complete breaks logic and increases rework risk, while local date changes outside the integrated plan undermine program alignment.

It preserves baseline control while aligning the forecasted impact of the inter-project dependency with the program plan.

Question 40

Topic: Schedule Monitoring and Controlling

At the June 30 data date, a critical-path commissioning activity has an approved baseline finish of July 15. After the status update, its current forecast finish is July 25. No recovery plan or change request has been approved. The sponsor asks for one line in the weekly schedule dashboard. Which statement best distinguishes current status from a schedule control recommendation?

• A. Commissioning is 10 days late, so assign overtime now and report the milestone as recovered.
• B. Commissioning now finishes July 25, so report that as the new baseline date.
• C. Commissioning is forecast 10 days late to baseline; recovery options are being evaluated for possible change control.
• D. Commissioning is forecast late, but wait to report variance until a recovery option is selected.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The best statement reports factual schedule status first: the forecast is 10 days late versus the approved baseline. It keeps recovery action separate, because overtime, crashing, or rebaselining are control decisions that require analysis and approval.

In PMI-SP practice, a schedule status report should communicate current status as of the data date and show variance against the approved baseline. Here, the reportable fact is that commissioning is now forecast to finish on July 25, which is 10 days later than the July 15 baseline. That is status information.

A schedule control action is different. Recovery options such as overtime, crashing, resequencing, or rebaselining are recommendations or approved actions taken to address the variance. They should not be presented as if already decided, and the forecast should not replace the baseline in routine reporting.

The key distinction is simple: report where the project stands now, then separately analyze and govern what should be done about it.

It reports the current forecast variance against the approved baseline while keeping any corrective action separate until analyzed and approved.

Question 41

Topic: Schedule Monitoring and Controlling

On a data-center upgrade, a key equipment supplier missed an interim milestone, triggering a known delivery risk. The current forecast shows final cutover 9 working days late, and the project manager wants to add expediting and temporary test-bench activities to the schedule baseline immediately. What should the scheduler require before baselining that mitigation work?

• A. Obtain quantified evidence of driving-path risk impact and mitigation benefit, then baseline through approved change control.
• B. Crash a non-driving training package with overtime to offset the late forecast.
• C. Replace baseline dates with the current forecast after adding the mitigation tasks.
• D. Baseline the mitigation now so the next status report shows the recovery plan.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: Before adding mitigation work to the baseline, the scheduler needs evidence that the triggered risk threatens a driving path and that the proposed response materially improves the forecast. Only then should the schedule baseline or PMB be updated through formal change control.

Adding mitigation work to the baseline is a control decision, not just a schedule edit. The scheduler first needs schedule risk assessment evidence showing that the supplier risk affects the project finish or another driving milestone, and that the proposed expediting and test-bench work has a quantified, credible benefit. That means understanding the likely date impact without the response and the expected forecast improvement with it.

• Confirm the affected driving path or milestone.
• Quantify the risk exposure and the mitigation’s schedule benefit.
• Process the baseline or PMB update through approved change control.

A recovery idea may be reasonable, but without quantified evidence and approval it should not replace the approved baseline.

Mitigation should enter the baseline only after analysis shows it credibly improves the driving forecast and the change is formally approved.

Question 42

Topic: Stakeholder Communications Management

On the July 15 status date, interface testing on the driving path to an August 1 regulatory milestone is 40% complete. Its baseline finish was July 18, but the current forecast finish is July 23, which moves the milestone forecast to August 4. Weekend overtime could recover the date, but that corrective action is still awaiting approval. The sponsor needs today’s steering-committee status update. What is the best scheduling action?

• A. Report progress, variance, the August 4 forecast, and that recovery is unapproved.
• B. Replace the August 1 baseline milestone with August 4 in the report.
• C. Wait for the overtime decision before reporting any milestone slip.
• D. Report 40% complete and say the team is evaluating recovery options.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The update should show the current status, the variance against the approved baseline, the forecast date, and the effect on the milestone. Because overtime is still unapproved, it must be communicated as a proposed corrective action, not as a committed recovery or a new baseline.

Effective schedule status reporting links four things: actual progress as of the status date, variance from the approved baseline, the current forecast based on remaining work, and the resulting schedule impact. In this scenario, the activity is on the driving path, so its slip already affects the regulatory milestone. The steering committee therefore needs a status update that states the current progress, shows that the work is no longer aligned to the baseline finish, reports the August 4 forecast, and makes clear that weekend overtime is only a proposed corrective action awaiting approval.

A useful status update informs decisions without hiding variance or assuming recovery before it is authorized. The closest distractors either omit the forecast impact or confuse the forecast with the baseline.

This update connects current status, baseline variance, forecast, and milestone impact while keeping a proposed recovery separate from approved plan changes.

Question 43

Topic: Stakeholder Communications Management

On a hybrid implementation project, a vendor delay on the driving path has moved the cutover forecast 8 working days past the approved baseline. This afternoon, the steering committee must decide whether to fund weekend testing or accept the later date, while the delivery team needs to know how the next two weeks of work will be resequenced. What is the best action by the scheduler?

• A. Give executives an impact summary and decision request; give the team detailed resequencing instructions.
• B. Send executives the full activity network and ask them to choose overlaps.
• C. Crash non-driving documentation and training first, then confirm the original cutover date.
• D. Update the baseline to the new forecast before reporting the variance.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The best response tailors schedule communication to the audience. The steering committee needs a concise view of variance, forecast impact, options, and the decision required, while the delivery team needs detailed task-level instructions for execution.

This is a corrective-action impact communication question. When a driving-path delay creates a late forecast, the scheduler should communicate differently to decision-makers and to the working team. The steering committee needs an executive-level update that shows the baseline-versus-forecast impact, the recovery choices, the tradeoff, and the approval needed now. The delivery team needs operational detail such as resequenced work, owners, and near-term expectations. Rebaselining before approval hides the variance instead of controlling it, and compressing non-driving work does not address the real source of delay. Good schedule communication supports timely decisions without distorting the baseline or overwhelming stakeholders with unnecessary detail.

It matches each audience to its decision need: executives need impact, options, and approval, while the team needs executable detail.

Question 44

Topic: Schedule Strategy

Two similar infrastructure projects used the same scheduling tool and equally experienced discipline leads. On Project Alpha, the scheduler sent the baseline and asked for weekly percent-complete updates. On Project Beta, the scheduler first explained schedule procedures: how leads should identify activities and dependencies, report actual dates and remaining duration, and submit logic changes for approval. Beta had stronger team participation and more reliable schedule control. Which explanation best accounts for the difference?

• A. Percent-complete reporting made actual dates and remaining duration unnecessary.
• B. Direct baseline editing kept dates aligned with current forecasts.
• C. Clear procedures defined status inputs and how schedule changes are approved.
• D. Local date ownership reduced the need to review dependencies.

Best answer: C

What this tests: Schedule Strategy

Explanation: The difference is procedural clarity. When team members understand how to define work, provide status, and route schedule changes, they participate more effectively and the scheduler receives data that can support real control decisions.

Team understanding improves participation because it removes ambiguity about what each activity owner must contribute and how that input will be used in the schedule model. Clear procedures help the team provide complete development inputs such as activities and dependencies, and they also support control by clarifying update timing, actual dates, remaining duration, and change approval rules.

• Team members know what data is required.
• Updates are more consistent and timely.
• Logic or date changes follow change control instead of informal edits.
• Forecasts become more credible because status data is usable.

Simply making updates easier is not enough if the schedule model, baseline, or dependency logic is weakened.

Shared procedures make team input consistent and usable for schedule development, statusing, and controlled change decisions.

Question 45

Topic: Schedule Planning and Development

A scheduler is estimating the duration for testing 240 identical instrument loops during a plant shutdown. The same contractor used the same crew size on two recent shutdowns and averaged 12 loops per day, and the lead technicians say the current work is comparable with little expected variation. Which estimating approach is most appropriate for this activity?

• A. Use three-point estimating from optimistic, most likely, and pessimistic opinions.
• B. Use analogous estimating based on one prior shutdown task duration.
• C. Use the required startup date to back-calculate the activity duration.
• D. Use parametric estimating with the validated loop-per-day rate.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: This activity is repetitive, unit-based work with reliable historical productivity data and SME confirmation that conditions are comparable. That makes parametric estimating the strongest choice, because it converts known quantity into duration using a validated production rate.

When an activity consists of many similar units and you have credible historical productivity from comparable work, parametric estimating is usually the most appropriate duration technique. Here, the work is repetitive, the same contractor and crew size were used, and lead technicians confirmed that current conditions are similar and variation should be low. Expert judgment is still important because SMEs validate that the historical rate is applicable before it is used.

Analogous estimating is faster but less precise because it copies a prior duration at a higher level. Three-point estimating is more useful when uncertainty is significant and a range-based estimate is needed. A required startup date is a schedule constraint, not evidence for how long the activity should take.

The key distinction is choosing the estimating method that best matches the available evidence.

This is repetitive work with reliable historical productivity and SME confirmation, so a parametric duration estimate is the best fit.

Question 46

Topic: Stakeholder Communications Management

On the current update, a vendor confirms the test environment will arrive 6 working days late. That delivery is a predecessor on the critical path to a contractual go-live milestone, only 2 days of total float remain, the schedule baseline is unchanged, and the communication plan requires immediate escalation of any critical-path delay over 3 days. What is the BEST action?

• A. Escalate a schedule issue now with forecast impact and recovery options.
• B. Log a schedule risk for the next routine risk review.
• C. Wait for the weekly report before notifying stakeholders.
• D. Replace baseline dates with the vendor’s revised forecast.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: This is a schedule issue, not a schedule risk, because the vendor has already confirmed the late delivery. Since the delay affects a critical-path predecessor, threatens a contractual milestone, and exceeds the communication plan threshold, it should be escalated immediately with its forecast impact.

A schedule risk is an uncertain future event; a schedule issue is something that has already happened and now needs action. Here, the vendor has confirmed a 6-day delay, so the condition is no longer uncertain. Because the delayed activity drives the contractual go-live milestone, only 2 days of total float remain, and the communication plan requires immediate escalation for critical-path delays over 3 days, the scheduler should communicate this as an active issue now. The message should include the forecast effect on the milestone and credible recovery options so stakeholders can decide on corrective action or formal change control if needed. Treating it as a routine risk, hiding the variance by changing the baseline, or delaying communication would weaken schedule control and stakeholder decision quality.

The delay has already occurred and exceeds the escalation threshold on a critical-path predecessor, so it must be communicated as an issue with its forecast impact.

Question 47

Topic: Schedule Planning and Development

On a predictive facility-upgrade project, the status date is August 12 and all remaining activities use a Monday-Friday calendar. The contract requires the Ready for Operations milestone on August 30. After statusing, the driving path is equipment startup (4 days remaining) -> performance test (5 days) -> client witness (3 days), and client witness has a finish-to-start dependency because the client will attend only after testing is complete. The milestone now forecasts September 4 with -3 days total float. The project manager asks the scheduler to make the schedule show August 30. What is the best response?

• A. Change the baseline milestone date to September 4 for reporting.
• B. Add a 3-day lead so client witness overlaps performance test.
• C. Keep the contractual date visible, validate the driving path and status, and present recovery or change-control options.
• D. Add a finish-no-later-than August 30 constraint to the milestone.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: When a forecast misses a contractual milestone, the scheduler should preserve a truthful schedule model and make the variance visible. Validate the driving path and current status, then propose realistic recovery or formal change-control actions instead of forcing dates or breaking logic.

Contractual milestones should remain visible in the schedule, but the forecast must still come from current status, valid logic, calendars, and realistic remaining durations. In this case, the finish-to-start link to client witness is explicit, and the Monday-Friday calendar plus remaining work already produce a September 4 forecast. Forcing the milestone to August 30 with a hard constraint, artificial lead, or baseline change would make the report look cleaner but would weaken traceability and distort the driving path. The scheduler should confirm the status data, keep the commitment date for variance comparison, and analyze credible recovery options or escalate through formal change control if recovery is not feasible. A clean-looking schedule is not useful if the forecast is no longer believable.

This keeps the forecast truthful and traceable while addressing the contract conflict through recovery analysis or formal control, not cosmetic edits.

Question 48

Topic: Schedule Monitoring and Controlling

At the status date, a validated schedule update shows the contractual turnover milestone forecast to finish 10 working days late on the critical path. The sponsor tells the scheduler to change the baseline dates to the forecast before the steering committee meeting so the dashboard shows no variance; no change request has been approved. What should the scheduler do next?

• A. Preserve the approved baseline and report both variance and forecast; use formal change control for any rebaseline.
• B. Replace the baseline dates with the forecast and document the reason after the meeting.
• C. Add finish constraints to remaining critical activities before presenting the schedule.
• D. Show only forecast dates in the dashboard until recovery options are selected.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The approved schedule baseline is the control reference, so it cannot be changed just to remove a negative variance from the dashboard. The next step is to report the late forecast against the current baseline and use formal change control if a rebaseline is genuinely justified.

In schedule monitoring and controlling, the approved baseline is used to measure performance, while the forecast shows the current expected finish based on status data. Here, the update is already validated and shows a real slip on a contractual milestone. The proper control action is to keep the baseline intact, communicate the variance transparently, and then evaluate recovery or submit a formal change request if a baseline revision is warranted.

• Report the forecast and the variance against the approved baseline.
• Analyze recovery options separately from baseline control.
• Rebaseline only after formal approval.

Changing baseline dates first would hide performance instead of controlling it.

The baseline remains the approved control reference until an authorized change replaces it, so the variance must stay visible.

Question 49

Topic: Schedule Monitoring and Controlling

At the September 10 data date, activity Integration test on the driving path to milestone M4 had 8 working days remaining. A resource update shows the only qualified tester will be half-time for the rest of the work, and the activity’s remaining duration is revised to 12 working days. M4 currently has 3 working days of total float against its committed date. Which schedule analysis interpretation is best?

• A. Only percent complete matters; revised remaining duration does not affect forecast.
• B. Float analysis shows M4 slips 1 working day past commitment.
• C. SPI analysis alone can confirm whether M4 is still protected.
• D. The commitment holds because the baseline milestone date has not changed.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: Resource availability updates matter because they can change remaining duration, which then changes forecast dates. Here the remaining duration increases by 4 working days but only 3 days of float protect the milestone, so the forecast slips 1 working day beyond the commitment.

The key concept is that a resource update affects the schedule through remaining duration, not through the baseline itself. Once the activity’s remaining duration increases, the scheduler should use float analysis on the driving path to see whether the extra time is absorbed or pushes a milestone.

• Remaining duration changes from 8 to 12 working days: an increase of 4 days.
• Available total float to M4 is 3 working days.
• The extra duration consumes all float and creates a 1-day forecast slip.

So the milestone commitment is now at risk unless recovery action is taken. A project-level indicator like SPI or a static baseline date does not directly show this specific milestone impact as clearly as float analysis does.

The resource update adds 4 working days of remaining duration, which exceeds the 3 days of total float and moves the milestone forecast 1 day late.

Question 50

Topic: Stakeholder Communications Management

A scheduler is preparing weekly schedule visibility for two audiences.

Status date: September 12, 2026
Calendar: 5-day workweek
Driving path: Vendor delivery -> Equipment install -> Start-up (FS)
Near-critical path: Data migration (1 day total float)
Start-up milestone: no contractual date constraint

The sponsor wants a one-page update, while activity owners need actionable work for the next 2 weeks. Which approach best tailors visibility without weakening schedule model integrity?

• A. Use a milestone summary for the sponsor and an owner-filtered 2-week lookahead from the same statused model.
• B. Add finish constraints so the sponsor view matches target milestone dates.
• C. Use one percent-complete dashboard for both audiences and suppress float details.
• D. Create a separate simplified reporting schedule with manually typed forecast dates.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The best approach is to tailor the view, not alter or duplicate the schedule model. A sponsor needs concise milestone visibility, while activity owners need detailed near-term tasks, and both should come from the same validated, statused schedule.

Stakeholder-focused schedule visibility should change the level of detail, not the underlying schedule logic. Here, the sponsor needs a concise milestone and forecast view, while activity owners need an owner-specific 2-week lookahead tied to the same statused network. Because the model has a defined driving path and a near-critical path with only 1 day of total float, the reporting views should remain traceable to current status and forecast impact.

• Keep one statused schedule model as the source.
• Summarize key milestones for sponsor visibility.
• Filter upcoming detailed work by owner for execution.
• Preserve logic-based dates, float, and driving-path credibility.

Cleaner-looking reports are acceptable only when they do not break traceability or distort the forecast.

This keeps one traceable source of logic-based dates while giving each audience the level of detail it needs.

Questions 51-75

Question 51

Topic: Schedule Planning and Development

While establishing the performance measurement baseline for a plant expansion, the scheduler creates a logic-driven baseline finish of October 30. The cost team then time-phases the budget by quarterly spending targets, and a review shows 55% of planned value assigned by the end of Q2 even though only 22% of the control-account work and no major procurement milestones are scheduled by then. Which analysis is MOST needed before approving the PMB as credible?

• A. Planned value time-phasing against the baseline schedule
• B. Total float analysis of near-critical paths
• C. Monte Carlo analysis of finish-date confidence
• D. Critical path analysis of schedule logic

Best answer: A

What this tests: Schedule Planning and Development

Explanation: The main problem is not whether the finish date is achievable; it is that planned value is heavily front-loaded compared with the scheduled work. Before approving the performance measurement baseline, the team needs to verify that the cost baseline is aligned with activity timing.

A credible performance measurement baseline requires the cost baseline to be time-phased from the approved schedule, not from separate fiscal targets. In this scenario, 55% of planned value appears by the end of Q2, but only 22% of the control-account work and no major procurement milestones are scheduled by then. That mismatch shows the budget may not reflect when work is actually planned to occur.

• Compare planned value distribution to scheduled activity and milestone dates.
• Re-time-phase the budget to the approved work packages and control accounts.
• Confirm the resulting baseline supports valid future performance measurement.

Critical path, float, and Monte Carlo can assess date feasibility or risk, but they do not by themselves establish cost-schedule integration for PMB credibility.

The PMB is only credible if planned value is time-phased from scheduled work, so this analysis tests whether cost and schedule are properly integrated.

Question 52

Topic: Schedule Planning and Development

A hospital fit-out is forecasting turnover 7 working days late. The driving path now runs through final inspections, and the contract allows owner occupancy only after the regulator issues the occupancy certificate. To improve control of the recovery update, which milestone definition should the scheduler add to the schedule model?

• A. Owner occupies ward before certificate is issued
• B. Occupancy certificate issued by regulator
• C. Admin-suite furniture installed
• D. Turnover baseline reset to current forecast date

Best answer: B

What this tests: Schedule Planning and Development

Explanation: The best milestone is the regulator issuing the occupancy certificate because it is a clear, observable event on the driving path and a contractual prerequisite for turnover. Recovery control should track real approvals or commitments, not premature starts, baseline edits, or minor non-driving work.

A useful schedule milestone marks a discrete, measurable event with real control value, such as an external approval, contract commitment, or go/no-go decision. In this case, turnover cannot occur until the regulator issues the occupancy certificate, so that event is the right milestone for the recovery update. It is objective, verifiable, and directly tied to the driving path.

Beginning occupancy before approval would bypass a required decision gate rather than control it. Resetting the baseline to the forecast hides variance instead of managing it through normal schedule control. Tracking furniture installation in an admin area does not address the event that actually governs turnover. The key is to define milestones around significant events that release or constrain downstream work.

It is an objective approval event that represents a required decision point and contractual prerequisite for turnover.

Question 53

Topic: Schedule Strategy

At the July 15 status date, a vendor delay on the driving path moves the project finish 10 workdays later than the approved baseline. The sponsor asks the scheduler to align the baseline to the new dates before the monthly report because a recovery decision is still pending. What should the scheduler do?

• A. Add a finish-no-later-than constraint to preserve the milestone date.
• B. Crash a support activity that still has positive float.
• C. Replace baseline dates with the current forecast before reporting.
• D. Report the late forecast against the approved baseline and rebaseline only through approved change control.

Best answer: D

What this tests: Schedule Strategy

Explanation: The scheduler should update status and forecast honestly, then report the variance against the approved baseline. A rebaseline should occur only after formal approval so traceability is preserved.

This is a schedule data-control and configuration-management decision. The delay has already affected the driving path, so the current status and forecast should show that impact, while the approved baseline remains the control reference until an authorized change is approved. That preserves traceability between what actually happened, what is now expected to happen, and what was formally approved.

Changing the baseline to match the forecast before approval would hide variance. Adding a date constraint would mask the real forecast rather than reflect it. If management later approves a schedule change, the project can create a revised baseline through change control and retain the prior baseline history in the change log or archive.

Good schedule control starts with accurate, traceable data before recovery actions are approved.

This keeps status, forecast, and baseline distinct and preserves an auditable trail until a formal rebaseline is authorized.

Question 54

Topic: Schedule Monitoring and Controlling

On the June 30 status date, the schedule shows system testing with a finish-to-start dependency on environment configuration. Configuration has no actual finish, the contractual go-live milestone on July 15 has zero float, and the vendor test team charged 160 hours this week at 100% utilization. The project manager asks the scheduler to show testing as in progress for tomorrow’s steering committee report, but the schedule management plan requires verified actual dates and remaining duration from the activity owner. What is the best action?

• A. Mark testing started and estimate percent complete from timesheets.
• B. Forecast an early start for testing because the vendor team is engaged.
• C. Keep testing not started until status is verified; report hours separately.
• D. Request an immediate rebaseline of the go-live milestone.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: Hours charged and 100% utilization show that the vendor team used time, but they do not prove that the logic-driven testing activity actually started or progressed. Because the predecessor is unfinished and the plan requires verified actual dates and remaining duration, the scheduler should validate status first and report utilization separately.

The key distinction is that resource utilization evidence shows how much labor was used, while schedule progress evidence shows whether a scheduled activity actually advanced. Here, testing is a successor activity with an unfinished predecessor, and the schedule management plan requires verified actual dates and remaining duration from the activity owner. That means the scheduler should not convert timesheet hours into an actual start or percent complete.

Those hours could represent preparation, standby time, rework, or incorrect charging rather than true progress on the testing activity. On a zero-float contractual milestone, preserving schedule-model integrity matters more than making the dashboard look active. Report the utilization separately for stakeholder visibility, but update the schedule only after progress is confirmed with valid status data.

The closest distractors all fail because they treat effort consumption as proof of schedule advancement or jump to baseline changes without approved justification.

Utilization data show resource usage, not actual schedule progress, so testing should not be statused until its start and remaining duration are verified.

Question 55

Topic: Schedule Planning and Development

A scheduler is developing a predictive schedule for a plant upgrade. The draft logic meets the required mechanical completion date of September 30 only by assigning the same electrician to three parallel critical-path activities for a combined 18 hours per day over 8 working days. When the electrician is limited to the realistic 8-hour calendar, the finish moves to October 10. Which schedule analysis approach best shows the trade-off between holding the target date and preserving realistic resource assignments?

• A. Calculate SPI for the draft schedule
• B. Conduct Monte Carlo analysis on activity durations
• C. Perform total float analysis on noncritical activities
• D. Run what-if analysis on leveled and date-driven scenarios

Best answer: D

What this tests: Schedule Planning and Development

Explanation: What-if analysis is the best fit because the scheduler must compare two different planning assumptions: an overloaded resource plan that meets September 30 and a realistic resource plan that finishes October 10. The question is not current performance, but the impact of alternative schedule-development choices.

The core concept is selecting an analysis method that directly tests the effect of resource constraints on planned finish dates. Here, the schedule already shows a known overallocation: one electrician is loaded for 18 hours per day, while the realistic calendar allows 8 hours. The scheduler needs to compare alternatives, not measure status or uncertainty.

A what-if analysis is best because it can evaluate scenarios such as:

• keeping the September 30 target with unrealistic loading
• leveling the electrician to 8 hours and accepting October 10
• exploring other feasible sequencing or staffing options

This gives decision-makers a clear view of the date-versus-resource trade-off. Methods focused on performance metrics, float only, or probabilistic risk do not directly answer that planning question.

It compares alternative schedule outcomes under realistic resource limits versus target-date assumptions.

Question 56

Topic: Schedule Monitoring and Controlling

At the June 10 status date, a critical-path configuration activity is 4 days late. The proposed responses are overtime for the current team or a reforecast of the regulatory milestone. The same two integration engineers are also assigned next week to a near-critical defect stream. Before recommending either recovery or reforecast, which resource information is MOST important to confirm?

• A. Baseline finish dates for the delayed activity and milestone
• B. Current SPI and SV for the affected control account
• C. Hours charged by the engineers during the last status period
• D. Updated calendars and remaining assignments for the engineers on both paths

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The key decision is whether the shared engineers have enough actual future capacity to support recovery without delaying other driving work. Before recommending overtime or moving the milestone, the scheduler needs validated resource availability and remaining commitments, not just historical or summary performance data.

Recovery and reforecast decisions require forward-looking resource data. In this scenario, the same two engineers support the delayed critical-path work and a near-critical stream next week, so the deciding question is whether they are truly available and what remaining assignments already compete for their time. Confirming updated resource calendars, approved leave, and remaining work across both paths tells the scheduler whether overtime, resequencing, or another recovery action is realistic, or whether the milestone forecast should move.

Historical timesheet hours show past utilization, not future capacity. Baseline dates help measure variance, and SPI/SV summarizes schedule performance, but neither replaces current resource-availability data when shared resources may constrain the recovery plan. The closest distractors describe useful schedule information, but not the resource fact needed to recommend the next action credibly.

Forward-looking availability on the shared engineers is needed to judge whether recovery is feasible or the milestone must be reforecast.

Question 57

Topic: Schedule Monitoring and Controlling

On June 10, a facilities project is forecasting the Ready for energization milestone on July 5, against a contractual date of June 30. The scheduler runs four what-if recovery scenarios.

Which scenario is the most feasible execution option?

• A. Change the milestone baseline to July 5
• B. Move 1 concrete crew to transformer pad grouting
• C. Add 2 electricians to cable termination
• D. Start integrated testing 3 days earlier

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: A feasible what-if option must work in the real schedule model, not just produce an earlier date on paper. Moving the crew from a non-driving activity with available float to a driving activity meets the June 30 milestone without breaking logic or exceeding resource limits.

What-if analysis is used to test recovery scenarios against actual schedule constraints. The best choice is the scenario that achieves the required date and is still executable. Here, transferring a concrete crew is feasible because it improves a driving activity while the source activity still finishes before its own July 8 milestone, so the float absorbs the shift.

The other scenarios fail basic feasibility checks. Adding electricians would exceed the subcontract resource cap. Starting testing early violates a mandatory dependency because testing cannot begin until terminations are complete. Changing the baseline to July 5 is not schedule recovery at all; it only changes the reference point. In schedule optimization, a valid option must respect logic, resource limits, and baseline control.

It recovers the milestone while preserving schedule logic and staying within available float and resource limits.

Question 58

Topic: Schedule Monitoring and Controlling

A predictive project’s change control board approves adding a mandatory 7-day cybersecurity review between system testing and go-live. This new activity creates a driving predecessor and moves the contractual go-live milestone by 5 workdays. What is the best documentation action for the scheduler?

• A. Manually shift the milestone in reports and notify stakeholders by email.
• B. Add acceleration to a non-driving activity and document later.
• C. Update the schedule logic, record the approved impact, and archive the prior baseline.
• D. Replace the baseline dates with the new forecast dates.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: When an approved change alters driving logic or a milestone, the scheduler should update the schedule model and formally document the approved impact. The prior baseline must be preserved so variance history and audit traceability remain intact.

The key concept is controlled traceability. Because the change is approved and it affects driving logic plus a contractual milestone, the scheduler should document the new dependency in the schedule model, record the approval and schedule impact in the change record, and preserve the old baseline before issuing any authorized baseline revision. That keeps the model technically correct and preserves forensic readiness.

A forecast shows what is now expected to happen; a baseline is the approved reference for measuring performance. Replacing baseline dates with forecast dates would hide variance rather than control it. Cosmetic date shifts or delayed documentation also weaken schedule integrity because they do not preserve the reason, approval, and timing of the change. The best action is the one that updates both the logic and the audit trail.

Approved logic and milestone changes need a traceable schedule-model update and controlled baseline documentation.

Question 59

Topic: Schedule Monitoring and Controlling

On a facilities project, the status date is July 15. Activity A actually finished on July 15 instead of its July 8 baseline finish. Its successor, Activity B, is FS after A, has 4 workdays remaining, has not started, and still carries a Must Start On July 9 constraint added earlier to protect finish milestone M1. M1 is immediately after B, yet the update still shows M1 on its July 15 baseline date. Which schedule analysis approach best exposes that the manual date is hiding real impact and undermining control?

• A. Calculate SPI from the current update.
• B. Review baseline execution index from the current update.
• C. Remove B’s manual constraint in a what-if copy and analyze critical path and float.
• D. Plot M1 on a milestone trend chart using the current forecast.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The issue is schedule-model integrity, not just a performance metric. A what-if critical path and float analysis without the forced start date lets the network logic calculate the real forecast for B and M1, exposing the hidden delay.

When a delayed predecessor and an unstarted successor still produce an on-time finish milestone, the schedule is being cosmetically held in place. Here, the Must Start On date overrides the natural logic from Activity A to Activity B, so the forecast for M1 cannot be trusted for control or reporting. The best analysis is to copy the schedule, remove the manual date force on B, and then recalculate the critical path and total float. That shows the logic-driven forecast, reveals the actual schedule impact, and preserves the approved baseline and audit trail.

• Use the current status and actual finish for Activity A.
• Remove the forced date only in an analysis copy.
• Recalculate to see the true driving path and float effect.
• Use that result for recovery decisions or formal change control.

SPI, BEI, and milestone trends can signal execution problems, but they do not diagnose a forecast that has been distorted by a manual date constraint.

This restores logic-driven forecasting so the true driving-path impact and lost float become visible without overwriting the live record.

Question 60

Topic: Schedule Planning and Development

A scheduler for a hospital system implementation has built the draft schedule model from the WBS, calendars, and dependencies. Team members have validated activity logic and durations, and the critical path is credible. The customer and sponsor still disagree on two contractual milestone dates, but the project manager wants to freeze the baseline this week. What should the scheduler do next?

• A. Send a status report with draft dates and collect feedback later.
• B. Hold a baseline review with key stakeholders to resolve milestones and approve dates.
• C. Freeze the draft schedule now because internal logic is validated.
• D. Submit a rebaseline request using the customer’s preferred dates.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: An approved schedule baseline requires stakeholder agreement on the dates that will be used for control. Since the schedule model is technically sound but milestone commitments are still disputed, the next step is to resolve those differences and obtain formal approval.

In PMI-SP practice, the schedule baseline is established only after the draft schedule model is both credible and accepted by the parties who must commit to it. Here, the team has already validated activity logic, durations, and the critical path, so the remaining gap is consensus on the disputed contractual milestones. The best next step is a baseline review with the customer, sponsor, project manager, and team members to confirm assumptions, resolve the milestone disagreement, and formally approve the dates.

Once that approval is in place, the baseline becomes the reference for future schedule measurement and control. Freezing draft dates early, reporting them as if final, or using rebaseline language before an initial baseline exists would undermine proper schedule governance.

A baseline should be approved only after the validated schedule model and milestone commitments are jointly accepted by the key stakeholders.

Question 61

Topic: Schedule Planning and Development

The scheduler is asked to submit a baseline for approval on a power-plant upgrade. The finish date meets the client completion date only because commissioning has a Must Finish On constraint, two handoff activities on the driving path still have missing logic ties, a second electrical crew has not been approved, and the vendor equipment milestone is 3 weeks earlier than the draft contract. The schedule risk review for the long-lead equipment is still open. What is the best recommendation?

• A. Defer approval until logic, resources, contract dates, and risks are resolved.
• B. Approve now and correct the baseline through later forecast updates.
• C. Compress non-driving support work, then approve the baseline.
• D. Constrain the finish date and seek approval before contract finalization.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: Baseline approval is premature when the schedule only works because of unsupported constraints, unapproved resources, unresolved driving-path logic, open schedule risk, or contract dates that are not yet aligned. In this case, the schedule is not a credible control reference yet, so approval should wait until those issues are resolved.

A schedule baseline is an approved performance reference, so it must be built from a credible schedule model. Here, the planned finish depends on a hard finish constraint, incomplete driving-path logic, uncommitted resources, a vendor milestone that does not match the draft contract, and an unresolved schedule risk review. Those are warning signs that the model is not ready for baseline consensus or approval.

The best control decision is to keep the schedule in draft form, correct the logic, confirm resource availability, align vendor dates with the contract basis, and complete the risk review or planned responses before seeking approval. Approving first and fixing later would create an unreliable baseline and weaken future variance analysis.

A baseline should not be approved until the schedule model is logic-complete, resource-feasible, risk-reviewed, and aligned with contractual dates.

Question 62

Topic: Schedule Planning and Development

A scheduler has validated the network logic for a hospital fit-out. The logic-driven CPM schedule meets the July 30 regulatory turnover milestone, and equipment installation appears critical. After assigning the actual calendars for one shared commissioning team and one controls engineer, resource leveling delays several start-up activities and turnover moves to August 6. What is the best next step?

• A. Update the milestone date to August 6 and finalize the schedule.
• B. Crash equipment installation to recover time on the original critical path.
• C. Analyze the leveled schedule to confirm the new driving path and milestone feasibility.
• D. Keep reporting July 30 and treat the resource conflict as internal.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: When actual resource limits are added, the schedule may become resource-constrained and the former critical path may no longer drive completion. The next step is to analyze the leveled schedule to identify the new driving path and determine whether the July 30 milestone is still feasible.

A logic-valid CPM schedule is not enough when scarce resources change activity timing. Once the shared commissioning team and controls engineer are applied, the schedule forecast moves to August 6, which means the scheduler must treat the resource-constrained model as the credible basis for analysis. The immediate next step is to confirm which activities now drive the milestone and whether the regulatory turnover date is still achievable under the real resource limits.

• Review the constrained logic and resource-driven delays.
• Identify the new driving path to turnover.
• Confirm whether July 30 is feasible before choosing recovery options.

Acting on the old critical path or changing dates first would weaken schedule quality and decision making.

Resource limits can create a new driving path, so the constrained schedule must be analyzed before recovery actions or date commitments are made.

Question 63

Topic: Stakeholder Communications Management

A hospital system implementation has a monthly steering committee review with only 10 minutes for schedule discussion. Overall SPI is 1.01, but the regulatory go-live milestone is forecast 12 working days late after two vendor activities lost total float from 8 days to 0. The sponsor wants the clearest visibility into the external commitment date. Which schedule analysis approach should the scheduler emphasize in the executive report?

• A. Baseline execution index summary for planned versus completed work
• B. Milestone trend analysis for go-live and major approvals
• C. Detailed critical path analysis for all remaining driving work
• D. Activity-owner variance analysis by work package and assignee

Best answer: B

What this tests: Stakeholder Communications Management

Explanation: The sponsor needs a fast, high-level view of whether the committed milestone will be met. Because SPI is near 1.0 while the key milestone is still 12 days late, milestone trend analysis is the clearest way to show the real schedule exposure.

This is a stakeholder-tailoring decision. Senior management usually needs concise visibility into external commitments and major milestone movement, not detailed task-level control data. In this scenario, the overall SPI is essentially on plan, yet the regulatory go-live is forecast 12 working days late and its feeder activities have lost all total float. That means an aggregate performance metric is masking the schedule problem the sponsor actually needs to see. Milestone trend analysis highlights baseline date, current forecast date, and whether the milestone is improving or worsening across reporting periods. That makes it well suited for an executive review with limited time. Detailed critical-path and activity-owner views are better for the team managing recovery actions, while BEI indicates execution discipline rather than direct visibility into a specific commitment date. The key takeaway is to match the analysis to the stakeholder’s decision need, not just the data available.

It gives senior management a concise view of baseline versus forecast movement on the specific committed dates they care about most.

Question 64

Topic: Stakeholder Communications Management

On the status date, a data-center migration project’s environment-build activity on the critical path is 6 working days late. After validating the status data and schedule logic, the scheduler models an approved corrective action: add a weekend shift and resequence a noncritical documentation task. The updated forecast shows the go-live milestone still finishing 2 working days later than the schedule baseline, and the sponsor and operations manager expect weekly milestone outlooks. What is the best next step?

• A. Rebaseline the go-live milestone before sending any stakeholder update.
• B. Fast-track more downstream work before communicating the current forecast.
• C. Issue a schedule update to stakeholders with the corrective-action impact and revised forecast.
• D. Wait for the weekend shift results, then report actual progress only.

Best answer: C

What this tests: Stakeholder Communications Management

Explanation: Once the corrective action has been validated, approved, and reflected in a credible forecast, stakeholders should be informed right away. The update should show the revised milestone outlook and the remaining variance to the schedule baseline.

When corrective action has already been validated, approved, and incorporated into a credible forecast, the next communication step is to inform affected stakeholders of the schedule impact. The goal is to maintain awareness of the current outlook, not to wait for recovery work to finish or to hide the variance. In this case, the sponsor and operations manager need a status update that explains the approved recovery action, the revised go-live forecast, and the remaining 2-day slip against the schedule baseline.

A useful update should include:

• the affected milestone and revised forecast
• the corrective action being taken
• any key assumptions or remaining schedule risk

Rebaselining is a separate change-control decision, and launching new compression before communicating would change the situation again before stakeholders understand the current impact.

The corrective action is already validated and approved, so the next step is to communicate its effect on the forecast and remaining baseline variance to stakeholders.

Question 65

Topic: Schedule Planning and Development

During schedule development for a plant shutdown project, the scheduler runs a Monte Carlo analysis for the completion milestone. The criticality index is the percentage of simulations in which a path became critical.

Which path should be identified as the main near-critical path?

• A. Path B, because low float and high criticality make it most likely to turn critical
• B. Path A, because zero float is the strongest sign of near-criticality
• C. Path C, because any path with simulation criticality is near-critical
• D. Path D, because more float gives the team more recovery choices

Best answer: A

What this tests: Schedule Planning and Development

Explanation: A near-critical path is not the current critical path, but it has little float and a meaningful chance of becoming critical. Path B best fits that definition because it has only 2 days of float and the highest criticality index among the noncritical paths.

To identify a near-critical path, combine deterministic logic from CPM with probabilistic evidence from Monte Carlo results. The current critical path has zero total float, so Path A is already critical rather than near-critical. Among the remaining paths, Path B has the least positive float and a high criticality index, meaning it frequently becomes critical in the simulations.

Paths C and D have much more float and much lower criticality exposure, so they are less likely to drive the completion milestone. The key takeaway is that near-critical paths are the closest realistic threats to the finish date, not simply any path with a nonzero simulation result.

It has the smallest positive float and the highest criticality index among the noncritical paths, so it is the strongest near-critical candidate.

Question 66

Topic: Schedule Monitoring and Controlling

A scheduler is drafting a weekly control report for a predictive project.

Status date: September 18
Milestone: Regulatory test ready
Baseline finish: October 6
Forecast finish: October 17 (+9 working days)

Driving-path notes:
- Integrate module C is not finished.
- Regulatory test setup started 2 days ago.
- The finish-to-start relationship between these activities is still in the schedule model.
- No approved schedule change exists.

Which schedule-management message should be added next to make this report actionable?

• A. Replace the baseline date with the forecast date for cleaner reporting.
• B. Validate out-of-sequence driving-path status before proposing recovery dates.
• C. Crash setup activities immediately to recover the milestone.
• D. Issue the variance report now and revisit control actions next week.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: The report shows a milestone slip, but it also shows out-of-sequence progress on the driving path. The missing message is that status and logic must be validated before recovery commitments or further control decisions are made.

A control report should not only show variance; it should indicate whether the forecast is credible and what control step comes next. Here, a successor has started even though the predecessor is unfinished and the finish-to-start logic still remains in the schedule model. That signals out-of-sequence progress, incorrect logic, or status data that need validation before the team recommends compression, escalation, or change control.

• Confirm actual progress and remaining duration with the activity owners.
• Verify whether the relationship should remain finish-to-start or be revised.
• Recalculate the forecast from the corrected schedule model.
• Then assess recovery options or change control if needed.

Simply reporting the delay, compressing work immediately, or replacing the baseline with the forecast would bypass proper schedule control.

The forecast is not yet fully credible because out-of-sequence progress exists while the driving-path logic remains unchanged.

Question 67

Topic: Schedule Strategy

On a predictive project, at the July 31 data date, 40 activities were planned to be complete. The schedule file shows only 22 with actual finish dates, so BEI = 22/40 = 0.55, where BEI compares completed activities with activities planned to be complete. Field supervisors report 36 are physically complete, and three baseline finish dates were edited even though the schedule change log shows no approved requests. Which schedule analysis approach best confirms that unclear roles are weakening schedule data quality and baseline control?

• A. Reconcile BEI with verified actual finishes and approved baseline changes.
• B. Run Monte Carlo on remaining duration uncertainty.
• C. Analyze the current longest path and near-critical paths.
• D. Model a crashing scenario for delayed activities.

Best answer: A

What this tests: Schedule Strategy

Explanation: The low BEI suggests poor execution, but the field reports show much more work is actually finished, so the larger issue is unreliable status data. Unapproved baseline edits also indicate weak control authority, making BEI reconciliation with change records the best analysis approach.

BEI is the right analysis here because it tests whether the schedule is accurately recording completed work against what the baseline expected by the data date. A value of 0.55 would normally suggest poor execution, but the separate report of 36 physical completions shows the schedule may be missing actual finish entries. The three edited baseline dates with no approved requests add a second warning: baseline control authority is not being followed. Together, these facts point to unclear responsibilities for providing status, entering actuals, and approving baseline changes. Before trusting forecast or variance results, the scheduler should reconcile recorded completions and baseline edits against verified field progress and approved change records. Critical path analysis might show where delay is driving, but it cannot prove the schedule data itself is reliable.

This directly tests whether missing actuals and unauthorized baseline edits are role-clarity problems rather than true schedule performance problems.

Question 68

Topic: Schedule Strategy

A predictive project has an approved schedule baseline and weekly status updates. While defining scheduling responsibilities, the sponsor says every forecast slip needs sponsor approval, and the functional manager says engineers should not estimate remaining work. Which role assignment best reflects sound schedule governance?

• A. Activity owners report status, the scheduler updates the forecast, and the project manager manages baseline changes through change control.
• B. The sponsor approves every forecast movement before variance is reported to stakeholders.
• C. The scheduler approves baseline date changes, and the project manager only distributes the weekly report.
• D. The functional manager records task status and rewrites logic because the resources report there.

Best answer: A

What this tests: Schedule Strategy

Explanation: The scheduler maintains and analyzes the schedule model, but does not approve baseline changes. Activity owners provide actual progress and remaining work, while the project manager uses that information to manage recovery and formal change control when the baseline must change.

In PMI-SP practice, clear role boundaries protect schedule integrity. Activity owners are the primary source for actual starts, actual finishes, and realistic remaining duration. The scheduler then updates the schedule model, validates logic, and produces the current forecast and variance analysis. The project manager owns day-to-day schedule control decisions, corrective actions, and the routing of any needed baseline change through the approved change-control process. Functional managers support resource commitments and availability, while sponsors and other stakeholders receive schedule impact information and may approve major governance changes when required. They do not approve every routine forecast movement.

• Activity owners provide status inputs.
• The scheduler maintains and analyzes the model.
• The project manager manages corrective action and formal schedule changes.
• Sponsors and stakeholders are informed or approve major governance actions, not routine forecast updates.

The key distinction is forecast maintenance versus baseline approval.

Routine forecast updates come from owner status and scheduler analysis, while baseline changes are handled through formal project change control.

Question 69

Topic: Schedule Closeout

Final acceptance for a rail upgrade project was signed yesterday. The contract requires the schedule archive within 5 business days, and company procedure requires retaining the native schedule files, all approved baselines and rebaselines, monthly update copies, schedule narratives, and schedule change approvals. A delay claim is still possible, and the project manager says, “Just save the final PDF and clear the working folders.” What is the BEST action?

• A. Archive only the latest schedule after overwriting prior baseline versions.
• B. Submit only the final PDF report and delete older schedule files.
• C. Archive the full controlled schedule record now, including native files and approved history.
• D. Postpone archiving until any delay claim is formally raised.

Best answer: C

What this tests: Schedule Closeout

Explanation: The best action is to archive the complete schedule record immediately according to the defined procedure. Contractual closeout and possible claims require an auditable history, not just a final report or latest file.

In schedule closeout, archiving is about preserving a complete, retrievable, and defensible record of how the schedule was planned, updated, approved, and changed. Here, the contract sets a 5-day deadline and the company procedure explicitly requires the native files, baseline history, update copies, narratives, and change approvals. Because a delay claim is still possible, forensic readiness matters: the archive must preserve the underlying schedule model and its approval trail.

A final PDF alone is only a stakeholder report. It does not retain the logic, calendars, status history, and baseline evolution needed to validate schedule performance or support a claim review. Overwriting earlier baselines or waiting until a claim appears would both weaken control and violate the closeout requirement. The key takeaway is to archive the full schedule history promptly and exactly as the defined procedure requires.

This preserves the complete auditable schedule record required by contract and procedure for closeout and possible forensic review.

Question 70

Topic: Schedule Monitoring and Controlling

The project’s Performance Measurement Baseline was approved three months ago. A vendor interface certification is on the driving path to a contractual go-live milestone on November 15, 2026. After a schedule risk review, the change control board approves a mitigation response to add a rehearsal environment and an extra integration test, use $85,000 of management reserve, and move two internal baseline milestones by one week while still meeting the contract date. What is the best scheduling action?

• A. Update the risk register and reports, but leave the PMB unchanged.
• B. Wait until the certification risk occurs before changing any baselines.
• C. Update the affected PMB components to include the approved work, dates, and budget.
• D. Add the mitigation only to the forecast and keep the current PMB.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: An approved risk response requires a PMB update when it changes the authorized work, baseline dates, or baseline budget used for performance measurement. Here, the board approved added mitigation activities, reserve use, and revised internal milestones, so the control baseline itself must be updated.

An approved risk response does not require a new PMB just because a risk exists. It requires a PMB update when the approved response changes the authorized plan that performance will be measured against. In this scenario, the mitigation adds new activities, moves internal baseline milestones, and transfers $85,000 from management reserve into planned work. Those are changes to baseline scope, schedule, and cost content, so the scheduler should incorporate the approved change into the affected PMB components and then measure future performance against that revised baseline.

Keeping the old PMB would distort variance reporting because the team would be executing approved work that the baseline does not contain. The key distinction is an approved baseline change versus a routine forecast change.

The approved mitigation changes authorized baseline scope, schedule, and cost content, so the PMB must be updated rather than treated as forecast-only data.

Question 71

Topic: Schedule Monitoring and Controlling

At the status date for a facility upgrade, EVM shows EV = 480,000 USD, PV = 540,000 USD, and AC = 450,000 USD. The next contractual milestone is on the critical path and is forecast 10 working days late. What is the best scheduler recommendation?

• A. Analyze the driving path, develop recovery action, and keep the baseline unchanged.
• B. Replace baseline dates with forecast dates before reporting status.
• C. Crash a non-driving work package using the budget underrun.
• D. Defer action because favorable cost variance means performance is acceptable.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The EVM data shows two different conditions: favorable cost variance and unfavorable schedule variance. Because the milestone is late on the critical path, the scheduler should act on the schedule problem with recovery planning and an updated forecast, while keeping the approved baseline for control.

Cost variance and schedule variance measure different things. Here, CV = EV - AC = 30,000, so the project is under budget for the work completed. But SV = EV - PV = -60,000, so the project has earned less progress than planned by the status date and is behind schedule. Since the delayed milestone is on the critical path, the control response must address schedule performance: confirm status quality, analyze the driving activities, and develop a realistic recovery action and forecast. The approved baseline remains the reference for measuring variance unless a formal change is approved. Positive cost performance does not cancel negative schedule performance when a key milestone is forecast late.

EV exceeds AC but is below PV, so the project is under budget yet behind schedule; action should target the driving delay without rebaselining.

Question 72

Topic: Schedule Monitoring and Controlling

A predictive infrastructure project has a contractual energization milestone with zero total float. At the status date, a supplier delay on the driving path moves the forecast finish 10 working days later, and no scope change has been approved. The sponsor asks the scheduler to make the next report “show the original baseline date” while the team looks for recovery options. Which action is true schedule optimization?

• A. Test resequencing and crashing on the driving path, and keep baseline and forecast separate.
• B. Move the baseline milestone date to the current forecast until recovery is decided.
• C. Send a status report with actual progress only and defer the late forecast.
• D. Add a finish-no-later-than constraint to preserve the contractual report date.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: Schedule optimization improves the forecast through valid analysis of the schedule model. It does not mean changing the approved baseline or hiding variance in reports when no change has been approved.

The key distinction is recovery action versus hiding variance. Because the delay is already affecting a zero-float driving path milestone, the scheduler should use what-if analysis to test legitimate optimization options, such as resequencing feasible work or crashing work that can actually shorten duration. The approved schedule baseline remains the control reference until a formal change is approved, while the forecast reflects the current expected finish based on status and remaining work. Replacing baseline dates, adding artificial constraints to force the old date, or omitting the slipped forecast may make the report look better, but those actions damage schedule model integrity and weaken control decisions. The closest trap is temporarily moving the baseline to the forecast; that is still unauthorized rebaselining.

This is true optimization because it applies recovery analysis to driving work while preserving the approved baseline for variance reporting.

Question 73

Topic: Stakeholder Communications Management

As of the status date, vendor design approval on the driving path is forecast to finish 8 working days late, moving a customer demo beyond its committed date. A separate system testing path still has 6 days of total float. The sponsor asks you to “smooth the message” for this week’s steering meeting, but the vendor manager and engineering lead can still influence recovery. What should the scheduler do next?

• A. Show the variance, review driving-path recovery with key influencers, and use change control for any baseline change.
• B. Crash the separate testing path with overtime.
• C. Add leads and a milestone constraint to keep the date.
• D. Rebaseline to the forecast before the steering meeting.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The best action is transparent communication plus targeted stakeholder alignment. It keeps the late forecast and variance visible, brings in the people who can help recover the driving path, and preserves formal change control if the baseline must change.

When a committed milestone is threatened by a driving-path delay, the scheduler should strengthen support through honest schedule communication and focused stakeholder collaboration. Here, the vendor manager and engineering lead can influence the delayed approval, so the right move is to show the current forecast and variance, discuss realistic recovery actions, and escalate or process any baseline change through approved change control. That builds trust and improves the chance of recovery without damaging schedule integrity. Replacing the baseline with the forecast, manually forcing dates, or spending effort on a separate path with float may make reports look better, but those actions either hide variance or fail to address the real driver of the delay. Good schedule support comes from visibility and coordinated action, not cosmetic reporting.

It preserves honest schedule visibility while engaging the stakeholders who can actually influence recovery on the driving path.

Question 74

Topic: Schedule Strategy

A contractor on a hospital expansion has an approved schedule baseline, and any baseline change must have an approved change request. The contract also requires monthly native schedule archives and logs for potential delay claims. With the substantial-completion milestone now forecast 18 days late, the owner requests a forensic review, but the scheduler finds three current files with different logic, a PDF report from last month, and a change log that stopped two months ago. What is the BEST action?

• A. Ask activity owners which file looks most accurate, then analyze that version.
• B. Identify the approved baseline, recover archived files by data date, and match each revision to approved change records before analyzing delay.
• C. Use the newest file and last month’s PDF to estimate the delay cause for the owner.
• D. Rebaseline to the current forecast so future updates are easier to compare.

Best answer: B

What this tests: Schedule Strategy

Explanation: The files are not under sufficient configuration control for audit or forensic use. The best action is to restore traceability to the approved baseline, data dates, and approved change records before performing any delay analysis or issuing conclusions.

Forensic or audit use depends on evidence quality, not just having a recent schedule file. Here, the project has an approved baseline, contractual archive requirements, a slipped commitment milestone, and formal change-control rules, but the available files are inconsistent and the log is incomplete. That makes the schedule record unreliable for a defensible analysis.

The scheduler should first rebuild a controlled version history that ties together:

• the approved baseline,
• each archived native file and its data date,
• approved change requests or rebaseline decisions,
• and the supporting update logs.

Only after that record is restored should the team analyze the driving delay. The key takeaway is that the latest file is not automatically an auditable file.

Audit-ready delay analysis requires a traceable chain from the approved baseline through dated status files and approved changes.

Question 75

Topic: Schedule Planning and Development

A scheduler is developing activity durations for a hospital monitoring-system rollout. The activity list, dependency logic, and calendars are already confirmed. In a pilot ward, the same crew installed 20 identical devices in 8 crew-hours, and 180 identical devices remain in materially similar wards. What should the scheduler do next?

• A. Begin compressing successor testing activities to protect the finish date.
• B. Use parametric estimating from the pilot productivity rate.
• C. Issue a schedule status report on the pilot result before estimating the remaining work.
• D. Approve the schedule baseline now and refine durations after more actuals are available.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: Parametric estimating is appropriate when repetitive work can be scaled from a reliable unit rate. Here, the scheduler already has confirmed activities, logic, and calendars plus a measured pilot productivity rate for materially similar work.

The key is to match the estimating technique to the evidence available. Parametric estimating is well suited when work is repetitive and a credible production rate exists, such as devices installed per crew-hour. In this case, the planning prerequisites are already in place: activities are defined, dependencies are confirmed, and calendars are known. The pilot ward provides observed performance from the same crew on materially similar work, so the next logical step is to use that rate to estimate the remaining installation durations.

Rebaselining or compressing later work would be premature because credible durations for the current work are not yet fully developed. Reporting the pilot result may be useful later, but it does not replace building the schedule model with sound duration estimates.

Repeated, similar units with an observed production rate make parametric estimating the best next step once logic and calendars are confirmed.

Questions 76-100

Question 76

Topic: Schedule Planning and Development

A healthcare program targets one go-live on August 15. Each component schedule has already passed internal critical-path review. Before baseline approval, the PMO must confirm that cross-project handoffs in the draft schedules align to the integrated master plan.

Which schedule analysis approach is most appropriate?

• A. Critical path analysis of each component schedule
• B. Monte Carlo analysis of completion uncertainty
• C. SPI trend analysis using earned value data
• D. Milestone analysis of program handoff dates

Best answer: D

What this tests: Schedule Planning and Development

Explanation: Milestone analysis is the best fit because the need is to compare component handoff dates with required integrated master plan dates. This checks program-level alignment before baseline approval, rather than internal path logic, execution performance, or probabilistic uncertainty.

The core concept is matching component schedules to the program’s required milestones and inter-project handoffs. Here, the scheduler already knows the component schedules passed internal critical-path review, so the remaining question is whether the draft dates support the integrated master plan. Milestone analysis is designed for exactly that comparison: required program dates versus scheduled component handoff dates.

• Compare each component milestone to the required program milestone.
• Identify any early, late, or missequenced handoff.
• Resolve misalignment before approving the schedule baseline.

The July 2 platform date already shows a program-level mismatch, which milestone analysis reveals more directly than the other methods.

It directly compares component handoff dates with required program milestones to verify alignment before baselining.

Question 77

Topic: Schedule Monitoring and Controlling

As of the status date August 12, 2026, the integrated master schedule uses a Monday-Friday project calendar; the vendor team uses a Monday-Saturday calendar. Data migration complete drives Cutover rehearsal, which drives the contractual milestone Operational cutover. Change request CR-27 is approved to mitigate interface-defect risk by adding a 4-day Vendor mock conversion and a 2-day Defect fix window before Cutover rehearsal, and the schedule management plan requires approved changes to be modeled as discrete activities with traceable logic and correct calendars. What is the best way to incorporate this mitigation?

• A. Lengthen Data migration complete by 6 days and keep the existing logic unchanged.
• B. Keep the baseline unchanged and manually move Operational cutover 6 days later in the forecast.
• C. Add both mitigation activities with logic, correct calendars/resources, and baseline them per CR-27.
• D. Insert a 6-day lag before Cutover rehearsal and note that it represents mitigation work.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: Approved risk mitigation should be incorporated as real schedule activities, not hidden inside durations, lags, or manually forced dates. That preserves logic, calendar accuracy, traceability to the approved change, and a credible forecast and baseline.

The key concept is schedule model integrity during change implementation. Because CR-27 is approved, the scheduler should add Vendor mock conversion and Defect fix window as separate activities, connect them logically on the driving path before Cutover rehearsal, assign the correct working calendars and resources, and update the schedule baseline through the defined change-control process. This keeps the mitigation visible, statusable, and traceable to the approved risk response.

Using a longer predecessor duration or a lag may make the schedule look simpler, but both hide real work and weaken analysis of ownership, progress, and driving relationships. Manually moving a milestone date is even worse because it bypasses network logic and damages forecast credibility. The best schedule update is the one that reflects approved scope change in the model itself, not just in dates.

Approved mitigation work should be added as discrete, traceable activities with proper logic and calendars, then reflected in the baseline through the approved change.

Question 78

Topic: Schedule Strategy

A scheduler is defining update rules for a facility startup schedule that uses a Monday-Friday calendar. As of the July 15, 2026 status date, Integrated Test is finish-to-start after Install Panels, and the contract milestone Ready for Energization has a finish-no-later-than August 29, 2026 constraint. Field reports show testing started in one area before all panels were installed, and management wants weekly reports to preserve forecast credibility and baseline variance. Which procedure best protects traceability between current status, forecast, and approved baseline?

• A. Enter actuals and remaining duration at the July 15 status date, split the work to model area handoffs, and keep baseline changes under change control.
• B. Delete the finish-to-start link so testing can continue and describe the overlap in narrative.
• C. Enter forecast finish dates manually and use the August 29 constraint to hold the milestone.
• D. Update only percent complete, then copy the latest forecast into the baseline each week.

Best answer: A

What this tests: Schedule Strategy

Explanation: The best procedure is to preserve separate schedule records: status actuals as of the data date, logic-driven forecast, and the approved baseline. Because work is handing off by area, the model should be refined to represent that overlap explicitly instead of forcing dates or overwriting baseline history.

The core control principle is traceability: current status should come from actual dates and remaining duration at the stated status date, the forecast should be recalculated from valid logic, and the baseline should remain the approved reference until a formal change is approved. In this scenario, testing started before all installation finished, which means the existing finish-to-start relationship is too coarse for the way work is actually being released. The sound procedure is to model that partial handoff explicitly, such as by splitting the activities by area or other valid work package, while preserving the original approved baseline for variance reporting. Hard constraints, deleted logic, and copied forecast dates may make the schedule look cleaner, but they weaken model integrity and hide real variance.

This keeps status, forecast, and baseline separate while correcting the logic model with controlled, traceable changes.

Question 79

Topic: Schedule Planning and Development

A software implementation schedule has a contractual milestone, Go-Live Accepted, due June 30. The SOW defines it as deployment complete, successful vendor testing, and customer sign-off. The current forecast is July 8 because vendor testing and sign-off remain on the driving path; end-user training has 15 days of total float. The sponsor asks to rename the milestone Code Deployed so June 30 still appears on target. What is the best action?

• A. Manually hold the milestone finish date at June 30 until acceptance is complete.
• B. Crash end-user training to recover the milestone date.
• C. Keep the contract milestone definition, assess achievability from the driving path, and report the late forecast.
• D. Rename the milestone to Code Deployed and track acceptance separately.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: The milestone definition is already established by the SOW, so it should not be changed to make reporting look better. The scheduler should separately analyze whether the remaining driving work can still achieve that defined milestone by June 30 and communicate the real forecast.

Milestone definition answers what event counts as complete. In this case, the contract already defines Go-Live Accepted as deployment, successful vendor testing, and customer sign-off. Milestone achievability analysis is different: it evaluates whether the current schedule logic, remaining work, and driving path can still meet the required date.

Because testing and sign-off are driving the milestone and the forecast is July 8, the correct control action is to keep the contractual milestone definition intact and analyze the remaining path against June 30. If recovery cannot restore the date, the variance must be reported and any date change handled through formal change control. Changing the milestone name or forcing its date would hide variance and weaken schedule integrity.

Milestone definition must stay tied to the contractual event, while achievability analysis tests whether the remaining driving work can still meet the required date.

Question 80

Topic: Schedule Monitoring and Controlling

A telecom rollout is behind plan. Status updates arrive by work package, resource managers report by crew code, cost data are loaded by control account, and schedule risks are tracked by separate IDs. In the schedule model, these elements are not consistently linked, so the scheduler cannot trace a delayed activity to its owner, cost impact, or related risk response. Before recommending recovery actions, what should the scheduler do next?

• A. Rebaseline the schedule so all source systems use the same dates.
• B. Publish the current forecast and refine the cross-references next cycle.
• C. Define and validate common coding links across activities, resources, costs, and risks.
• D. Compress the slipped activities immediately.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The scheduler first needs a logical data structure that ties each activity to the right resource, cost account, and risk item. Without those links, forecast analysis and recovery decisions are not reliable.

Logical data organization in schedule control means using consistent codes, IDs, or mapped attributes so related information can be connected without guesswork. Here, status, resources, costs, and risks are all reported differently, so the schedule cannot support integrated analysis. The best next step is to create and validate the linking structure across those elements in the schedule model and supporting records. Once that traceability exists, the scheduler can identify ownership, explain schedule and cost impacts, relate risks to affected activities, and recommend targeted recovery actions. Issuing reports first only communicates weak analysis, and acting on compression or rebaselining before the data are connected undermines control quality.

A shared coding structure creates traceable links across the data sets, which is the prerequisite for credible analysis and control action.

Question 81

Topic: Schedule Strategy

At the data date, a facility-upgrade project forecast shows final turnover 10 working days late. Several activity owners reported only percent complete and did not provide remaining duration or logic impacts, and one lead asked the scheduler to “move the dates back” before sending the report. To support a credible recovery decision and stronger team participation in future updates, what should the scheduler do first?

• A. Replace baseline dates with the current forecast before issuing the status report.
• B. Shorten critical-path durations now and ask owners to support the new dates later.
• C. Accelerate a visible non-driving procurement activity to show recovery progress this week.
• D. Review update procedures with activity owners, validate remaining duration and logic, then reforecast.

Best answer: D

What this tests: Schedule Strategy

Explanation: The best first action is to fix the quality of schedule inputs. When the team understands update procedures and provides remaining-duration and logic information consistently, the forecast becomes credible and the team can participate meaningfully in schedule control.

This situation is a schedule-control problem caused by weak procedure understanding, not just a late date. Activity owners are giving incomplete status, and a lead is asking for cosmetic date changes, so the current forecast is not reliable enough to drive recovery decisions. The scheduler should reinforce the agreed update and change procedures, collect valid remaining-duration and logic-impact data from the team, and then refresh the forecast.

Clear procedures improve participation because team members know what information is required, how their updates affect the schedule model, and when formal change control is needed. That produces better status data, better forecasts, and better recovery choices focused on the real driving path. Compressing work, overwriting the baseline, or acting on non-driving work would weaken control rather than improve it.

This improves schedule-data quality, so the team can participate correctly and the recovery decision is based on a credible forecast.

Question 82

Topic: Schedule Planning and Development

A program scheduler is integrating a new vendor workstream into the program schedule. The integrated master plan requires the vendor’s Facility Ready milestone before system integration testing can start, but the vendor schedule shows testing starting 5 working days earlier and has no external dependency link to that milestone. The program baseline has not been approved yet. What is the best next step?

• A. Issue a status report showing the date conflict and revisit it in the next update cycle
• B. Rebaseline the program milestone to match the vendor’s earlier testing start
• C. Validate the dependency and milestone mapping, then update the schedule model before baseline approval
• D. Add a manual start constraint so testing matches the master plan date

Best answer: C

What this tests: Schedule Planning and Development

Explanation: The issue is a planning and alignment gap, not a reporting or baseline-control problem yet. The best next step is to validate the cross-project dependency and milestone alignment, then correct the schedule model so the workstream supports the integrated master plan.

When a workstream schedule conflicts with the integrated master plan before baseline approval, the priority is to make the schedule model credible. Here, the vendor schedule is missing the external dependency that should drive the testing start, so the scheduler should first validate the dependency, milestone mapping, and related assumptions with the responsible leads, then update the logic in the schedule model. That supports program objectives because the detailed schedule must align with program-level milestones and inter-project dependencies before it becomes the approved reference. Reporting the conflict alone does not fix alignment, rebaselining is inappropriate before validating the logic, and manually constraining dates hides the real dependency instead of modeling it correctly.

Before baselining, the scheduler should confirm inter-project logic and align the workstream schedule to the integrated master plan.

Question 83

Topic: Stakeholder Communications Management

An ERP rollout has a contractual cutover milestone on July 30. At the July 10 data date, a vendor interface activity on the driving path is 6 working days late, and the forecast now shows cutover on August 4. End-user training is not driving and has 8 days of total float. The schedule management plan requires escalation within 1 business day whenever a committed external milestone is forecast to slip by more than 2 working days. What is the best action now?

• A. Escalate the issue now with forecast impact and recovery options.
• B. Fast-track end-user training first and report the delay next week.
• C. Replace the baseline cutover date with August 4.
• D. Crash testing immediately and escalate only if recovery fails.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The issue has already crossed the project’s explicit escalation threshold: a committed external milestone is forecast to slip by 5 working days. That requires prompt stakeholder escalation with the current forecast and recovery options, not delayed reporting or changing the baseline.

When a delay has already occurred and the forecast shows a committed milestone missing its date beyond a defined threshold, it is a schedule issue that should be elevated through the communication plan. Here, the late vendor activity is on the driving path, the cutover forecast moves from July 30 to August 4, and the slip exceeds the 2-working-day trigger. The best response is to escalate now with the current impact, cause, and feasible recovery options. The schedule baseline remains the approved reference unless formal change control authorizes a change.

• Use the driving-path forecast to judge impact.
• Communicate within the required escalation window.
• Evaluate any compression or recovery through normal approval channels.

Delaying escalation or overwriting the baseline would reduce schedule control and transparency.

The forecasted 5-day slip on a committed milestone exceeds the stated escalation threshold, so stakeholders must be notified now while the baseline stays unchanged unless a change is approved.

Question 84

Topic: Schedule Planning and Development

A scheduler is building the baseline for a warehouse automation project. Activity Install 240 scanners has a finish-to-start dependency on Rack wiring complete and is on the driving path to the contractual go-live milestone. The crew works a 5-day, 8-hour calendar, and the same subcontractor previously installed 480 similar scanners at a verified rate of 40 scanners per day using the same crew size and calendar. Which estimating approach would give the most credible, traceable duration for this activity?

• A. Use expert judgment only from the subcontractor superintendent.
• B. Use analogous duration from the most similar prior site.
• C. Use parametric estimating from verified historical productivity data.
• D. Use PERT-style ranges from optimistic, most likely, and pessimistic values.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: Parametric estimating is best when work is repetitive, measurable, and supported by validated productivity data. Here, the activity has a known unit count and the same crew/calendar as the historical work, so a rate-based estimate is more credible than rough comparison, pure judgment, or uncertainty ranges.

The key is matching the estimating method to the type of work and the quality of available evidence. This activity is repetitive, has a defined quantity, and has verified historical productivity from the same subcontractor using the same crew size and calendar. That makes parametric estimating the strongest choice because the duration can be traced to units of work and a proven production rate, which supports schedule model credibility on a driving-path activity.

Analogous estimating would reuse a past overall duration, which is faster but less precise. Expert judgment can still help validate assumptions, but by itself it is weaker than documented rate data here. Three-point or PERT-style estimating is more useful when uncertainty is high and the work cannot be estimated as reliably from stable unit productivity. The closest distractor is analogous estimating, but it sacrifices precision that the stem’s historical rate data already supports.

Known quantity, verified production rate, and the same crew calendar make a parametric estimate the most defensible basis.

Question 85

Topic: Schedule Monitoring and Controlling

A hybrid deployment project has an approved release baseline of September 30. On the July 15 status date, interface testing on the driving path is forecast to finish 7 working days late, and a scope change adding 4 more days of testing was approved yesterday. The change board approved the added work but said any replacement of the schedule baseline requires a separate rebaseline decision. What should the scheduler do next?

• A. Crash the training activity with float before updating the model to offset the delay.
• B. Add a finish constraint to the release milestone so reports still show the baseline date.
• C. Replace the current baseline with the new forecast because the added work is already approved.
• D. Update the model with status and the approved work, issue a new forecast, and keep the current baseline until rebaseline approval.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The scheduler should immediately update the schedule model with actual status and the approved change so the forecast is credible. The approved baseline must remain intact until a separate rebaseline decision is formally authorized, which preserves variance visibility and baseline history.

In schedule control, the live schedule model should reflect current facts: actual progress, remaining work, logic effects, and approved scope changes. That produces a reliable forecast for decision-making. However, the approved schedule baseline is the reference for measuring variance and maintaining historical evidence, so it should not be overwritten just because the forecast slipped or added work was approved.

Here, governance explicitly says baseline replacement needs separate approval. The right action is to update the model, show the new forecast and variance, and preserve the existing baseline until a formal rebaseline is approved. Manual date constraints would hide the real impact, and compressing work with float would not address the driving-path delay.

The key distinction is forecast update now, baseline replacement only with approval.

This keeps the live schedule model accurate while preserving the approved baseline as the control reference until formal rebaseline approval exists.

Question 86

Topic: Schedule Strategy

At the July 31 data date, a vendor design package on the driving path is 10 working days late. After entering actual dates and remaining duration, the forecast shows the regulatory approval milestone will slip 8 working days past the approved baseline. The schedule management plan allows baseline date changes only through configuration-controlled approval. What should the scheduler do next?

• A. Crash a training activity that has 12 days of float to recover the slip.
• B. Replace the baseline milestone date with the new forecast before sending the report.
• C. Issue the revised forecast and variance, keep the baseline, and use change control for any rebaseline.
• D. Fast-track regulatory review before the design package is complete.

Best answer: C

What this tests: Schedule Strategy

Explanation: The correct action is to update status and forecast information while preserving the approved baseline. A late forecast shows variance against the control reference; it does not authorize changing that reference without formal approval.

This tests the difference between routine schedule status updates and configuration-controlled baseline changes. Actual dates, remaining duration, and the resulting forecast should be updated as part of normal status collection and schedule analysis. The approved baseline is different: it is the control reference used to measure variance, so it must remain unchanged unless a formal change is approved through the project’s configuration or change-control process.

A good sequence is:

• enter status data
• recalculate the forecast
• communicate the variance and impact
• submit a change request only if an approved baseline change is needed

Changing the baseline just because the forecast is late would hide variance rather than control it. The key takeaway is that forecast movement is routine; baseline movement is controlled.

Routine status updates change the forecast, but the approved baseline stays intact until a formal baseline-change approval is granted.

Question 87

Topic: Schedule Strategy

A project sponsor wants a monthly one-page update focused on contractual delivery milestones and any slip against approved commitments. The team will continue using the full detailed schedule model for control. Which presentation format best fits the sponsor’s needs while preserving accurate schedule information?

• A. Workstream dashboard showing percent complete
• B. Detailed Gantt of all in-progress activities
• C. Milestone report showing forecast dates only
• D. Milestone report showing baseline, forecast, and variance

Best answer: D

What this tests: Schedule Strategy

Explanation: The sponsor needs a high-level milestone view, not the full activity network. A milestone report that shows baseline dates beside forecast dates and variance keeps the update concise while preserving accurate control information.

When tailoring a schedule presentation, match the level of detail to the stakeholder’s decision need and keep the control data intact. For an executive sponsor focused on contractual milestones, a milestone report is the best format because it highlights only the major commitments. To preserve accuracy, it should show the approved baseline date, the current forecast date, and the variance or impact for each milestone. That lets the sponsor quickly see whether commitments are slipping without losing the distinction between the approved plan and the current expectation. A forecast-only view hides variance, a detailed Gantt adds unnecessary detail, and percent complete does not reliably communicate milestone date performance.

It gives the sponsor a concise milestone view while preserving the key distinction between approved baseline dates and current forecast dates.

Question 88

Topic: Schedule Planning and Development

A scheduler is reviewing a predictive project schedule that uses a 5-day workweek calendar. The status date is August 14, 2026. One item below is modeled as an activity, but it should be a milestone to preserve schedule logic and reporting quality.

Which item should be remodeled as a milestone rather than an activity?

• A. Deploy release
• B. Conduct readiness review
• C. Configure interface
• D. Steering committee approval received

Best answer: D

What this tests: Schedule Planning and Development

Explanation: A milestone marks a point in time, such as an approval or commitment, while an activity represents scheduled work with duration. “Steering committee approval received” is a gating event between two activities, so modeling it as a 2-day task weakens milestone reporting and schedule traceability.

The key distinction is work versus event. An activity consumes time and usually resources; a milestone is a zero-duration marker used for approvals, handoffs, commitments, or completion points. In this schedule, “Steering committee approval received” is the decision point that gates deployment, not the work of preparing for that decision. Because it has no resource assignment and represents a received approval, it should be modeled as a milestone, with any required date tracked through an appropriate milestone constraint if needed. If lead time is genuinely needed before approval, that time should be represented by separate preparatory or review activities, not by giving duration to the approval event itself. By contrast, configuration, conducting the readiness review, and deployment all represent actual work and should remain activities.

Approval received is a point-in-time decision event, so it should be modeled as a zero-duration milestone.

Question 89

Topic: Schedule Strategy

On a plant upgrade, the client approved a scope change adding compliance testing before the contractual turnover milestone. After incorporating the change, the schedule model forecasts turnover 12 working days late on the driving path. The scope change is approved, but no schedule baseline or contract-date revision has been approved. Which action best supports the overall project management process?

• A. Shorten the new compliance testing and direct the team to recover without formal approval.
• B. Publish the later forecast, assess driving-path recovery, and request any schedule baseline or contract revision.
• C. Replace the baseline date with the forecast and report one current turnover date.
• D. Fast-track a documentation package with float to show immediate schedule recovery.

Best answer: B

What this tests: Schedule Strategy

Explanation: The best action is to keep the later date as a forecast, analyze recovery on the driving path, and use change control for any baseline or contract revision. That supports the wider project management process by aligning schedule control with approved scope, contract obligations, and governance.

When an approved scope change affects a contractual milestone, the scheduler’s objective is to provide an accurate forecast that helps the project team make integrated decisions. The schedule model should reflect the added work, the delay should remain visible against the approved baseline, and any recovery should be evaluated on the driving path. If the contract date or schedule baseline must change, that revision needs formal approval through change control rather than being applied automatically.

• Keep the new turnover date as the forecast until a baseline change is approved.
• Evaluate only feasible recovery actions that affect the driving path.
• Document the contract impact and route any date revision for approval.

Changing dates unilaterally or compressing required testing would reduce schedule credibility and weaken overall project control.

This preserves baseline integrity, focuses recovery on the driving path, and routes any contract-date change through formal change control.

Question 90

Topic: Schedule Planning and Development

The status date is June 10. A plant upgrade has a contractual startup milestone. The latest schedule update shows:

- Calibration -> Startup test -> Startup milestone: total float 0 days; calibration slipped 4 working days; startup milestone now forecasts 4 working days late.
- Controls interface -> Startup test -> Startup milestone: total float 2 days; no current slip.
- Operator training -> Readiness review: total float 6 days; training slipped 3 working days; startup milestone unchanged.

Which scheduling action is BEST?

• A. Replace the startup baseline with the new forecast so contractual reporting stays aligned.
• B. Start startup testing before calibration is complete, then request approval after the overlap.
• C. Recover calibration/startup-test work, watch the 2-day-float interface path, and treat training as float consumption.
• D. Crash operator training first because any late activity should be recovered immediately.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: Recovery should focus on the path that is actually driving the late startup milestone. The zero-float calibration path is critical and driving, the 2-day-float interface path is near-critical, and the training delay is non-driving because it consumes float without moving startup.

The key concept is to recover the threatened milestone by acting on the path that currently drives it, not on any activity that merely looks late. In this update, calibration to startup test has zero total float and its delay moves the startup milestone, so that path is both critical and driving for this milestone. The controls interface path has only 2 days of float, so it is near-critical and should be monitored closely because a small slip could make it driving. Operator training has slipped, but the milestone is unchanged, which means the delay is non-driving and is being absorbed by available float.

A sound scheduling response is to reforecast from valid status, target corrective action on the driving path, and avoid rebaselining unless an approved change justifies it. Recovering non-driving work will not fix the late startup date.

It targets the current driving path with zero float, monitors the near-critical path, and avoids spending recovery effort on a non-driving delay.

Question 91

Topic: Schedule Planning and Development

A facility-upgrade project has an approved schedule baseline and a contractual requirement for monthly progress reports by building system owner. The scheduler can status activities, but the schedule model does not clearly show who is accountable for each scope area, so progress cannot be rolled up consistently. Change control rules do not allow baseline dates to be replaced during routine reporting. What is the best action?

• A. Update baseline dates to match current forecasts
• B. Assign a resource name to every activity
• C. Reorganize the schedule only by project phase
• D. Create control accounts aligned to the WBS and OBS

Best answer: D

What this tests: Schedule Planning and Development

Explanation: The best choice is to use control accounts aligned to both the WBS and the OBS. That structure supports clear responsibility assignment and progress control without changing the approved baseline during routine status reporting.

This situation is about choosing a schedule-supporting structure, not changing dates or adding detail for its own sake. When the project needs progress rolled up by accountable owner, the schedule should connect scope decomposition and organizational responsibility. Control accounts do that by linking WBS elements to OBS ownership, creating clear points for status, control, and reporting.

In this scenario, the key facts are:

• the baseline is already approved
• reporting is required by system owner
• accountability is unclear in the current model
• routine reporting cannot replace baseline dates

A phase-based grouping may help presentation, but it does not solve ownership. Resource assignments on activities can show who performs work, but not necessarily who is accountable for controlling and reporting progress for a defined scope area. Replacing baseline dates with forecasts would violate baseline control discipline.

Control accounts provide management control points that tie scope areas to accountable organizational owners and support consistent schedule progress reporting.

Question 92

Topic: Schedule Monitoring and Controlling

The data date is May 16. A driving activity is being updated, and the sponsor wants a revised milestone forecast today.

Activity: Factory acceptance test
Baseline duration: 8 working days
Actual start: May 8
Actual finish: May 14
Percent complete: 75%
Remaining duration: 3 working days
Estimate to complete: 3 working days

What should the scheduler do next?

• A. Submit a rebaseline request for the affected milestone.
• B. Issue the revised milestone forecast using the current update.
• C. Begin compressing successor activities to offset the delay.
• D. Validate the status with the owner and correct the inconsistent fields before forecasting.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: This update is not credible because an activity cannot be finished, only 75% complete, and still have 3 days remaining at the same time. The next step is to validate and correct status data before forecasting or taking schedule-control action.

In schedule monitoring and controlling, status quality comes before schedule analysis. Here, the activity shows an actual finish date, but it also shows less than 100% complete and positive remaining work. Those fields cannot all be true at once, so the forecast based on them would be unreliable.

• Verify the actual status with the activity owner.
• Correct the actual date, percent complete, and remaining duration/ETC so they tell one consistent story.
• Then recalculate the schedule and assess any milestone impact.

Publishing a forecast, compressing work, or requesting a rebaseline before validating the status would turn bad data into bad decisions.

The status data conflict with each other, so they must be verified and corrected before any forecast is trusted.

Question 93

Topic: Schedule Strategy

A project milestone is now forecast 8 working days late. During the last two update cycles, several team leads changed activity dates directly in the schedule tool, while others sent status by email and assumed the scheduler could approve the changes. What is the best action for the scheduler to take next?

• A. Let the scheduler continue correcting dates manually without waiting for team approval
• B. Replace the schedule baseline with the current forecast so reports match the latest dates
• C. Run a focused briefing on update and approval procedures, then require future status and changes through the defined process
• D. Fast track remaining critical-path activities to recover the lost time immediately

Best answer: C

What this tests: Schedule Strategy

Explanation: The main problem is not yet recovery technique selection; it is poor understanding of schedule update and approval procedures. The best response is to communicate the required process clearly so future status is reliable and changes are handled through proper approval paths.

In PMI-SP terms, schedule strategy includes defining and communicating how schedule updates, approvals, and change control will work. Here, inconsistent status methods and unauthorized date changes make the forecast unreliable. The scheduler should first reset team understanding with targeted communication on the approved procedure, including what status data team members submit, who can change dates or logic, and which changes need formal approval before entering the schedule model.

This protects schedule model integrity and improves decision quality. Compressing work before fixing bad input can lead to the wrong recovery action, and changing the baseline or manually forcing dates would hide variance instead of controlling it. The key takeaway is to correct the communication and governance gap before acting on a questionable forecast.

This corrects the root cause by clarifying who provides status, who approves schedule changes, and how updates enter the schedule model.

Question 94

Topic: Stakeholder Communications Management

A steering committee says the project team’s weekly messages show activity completions, but not whether the approved launch date is still achievable or which current delays threaten it. The scheduler needs a routine artifact that improves stakeholder visibility without changing the baseline. Which artifact is the best fit?

• A. The schedule baseline showing approved milestone dates
• B. The schedule management plan defining reporting and control rules
• C. A schedule change log with requested and approved schedule changes
• D. A schedule status report with variance, forecast, and impact details

Best answer: D

What this tests: Stakeholder Communications Management

Explanation: The visibility problem is about communicating current schedule condition, not redefining control rules or replacing the approved reference. Stakeholders need an artifact that compares baseline and forecast, explains variance, and shows impacts to milestones, which is the role of a schedule status report.

The key distinction is between a control artifact and a communication artifact. Here, stakeholders already receive fragments of status, but they still cannot tell whether the approved date is at risk or what current delays mean for delivery. A schedule status report is designed to communicate exactly that: actual progress, variance from the schedule baseline, forecast dates, and the effect of issues or corrective actions on key milestones.

By contrast, the schedule baseline is only the approved reference point, the schedule management plan explains how schedule control and reporting will be performed, and the schedule change log tracks change requests and approvals. Those artifacts support governance, but they do not provide the routine visibility stakeholders are asking for.

When the problem is schedule awareness, use the artifact that turns schedule data into clear stakeholder-facing impact information.

A schedule status report is the routine stakeholder communication artifact that shows current progress against the baseline, updated forecast dates, and schedule impact.

Question 95

Topic: Schedule Planning and Development

A hospital EHR upgrade schedule is being finalized for baseline approval. The current model shows two driving-path activities—data migration build and data validation—overlapping, but both require the same database specialist. That specialist is available only 50% next month, the budget does not allow overtime or a second specialist, and the September 30 regulatory go-live milestone cannot move. What is the BEST scheduling action?

• A. Add date constraints to hold September 30, then baseline the plan.
• B. Keep the overlap and rely on overtime from the specialist.
• C. Reflect the 50% calendar, level the conflict, and resequence feasible work.
• D. Add a second specialist to preserve the current activity dates.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: Known constraints should be built into the schedule model before it is approved. Updating the resource calendar and leveling the shared specialist’s work gives a credible forecast against the fixed milestone without violating the budget.

In schedule planning and development, the model must reflect actual resource availability, funding limits, and fixed commitments before baseline approval. Here, the overlap is not realistic because both driving-path activities need the same specialist, while overtime and an added resource are explicitly unavailable. The best action is to update the specialist’s calendar, level the resource conflict, and resequence any feasible work that still respects logic.

• Model the real 50% availability.
• Remove the impossible overlap through leveling or resequencing.
• Check the resulting forecast against the fixed September 30 milestone.
• Use that realistic result for approval or escalation.

Forcing dates may preserve the milestone on paper, but it does not produce a valid schedule model.

This creates a realistic schedule model that respects the known resource and budget constraints before baseline approval.

Question 96

Topic: Schedule Planning and Development

A scheduler is reviewing a project schedule against a contractual service-cutover date of November 30. Which situation most clearly calls for schedule risk analysis, rather than immediate escalation or direct schedule adjustment?

• A. Regulatory approval feeds a near-critical path, varies from 5 to 20 days, and draft cutover is November 28.
• B. A supplier has confirmed a 7-day delay, moving forecast cutover to December 3.
• C. Draft logic shows cutover on December 4 because a vendor handoff is sequenced too late.
• D. User training slipped 3 days, but it still has 9 days total float.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: Schedule risk analysis is appropriate when the contractual date is still achievable, but uncertainty could push it late. Here, the draft cutover still meets November 30, yet the highly variable regulatory approval on a near-critical path could easily consume the 2-day margin.

The key distinction is uncertainty versus an existing problem. If the schedule model already shows December 4 because of current logic, the team needs direct schedule adjustment; risk analysis does not fix a known deterministic miss. If a supplier delay is confirmed and the forecast moves to December 3, the contractual commitment is already threatened and should be escalated as a schedule issue. By contrast, regulatory approval duration is still uncertain, it affects a near-critical path, and the draft cutover has only 2 days of margin, so schedule risk analysis is the best next step to assess the likelihood of meeting November 30. Training slippage with 9 days of float does not currently threaten the contract date. The deciding factor is whether the date is at risk from uncertainty, a known model shortfall, or an actual delay.

The contractual date is still achievable, but uncertainty on a near-critical path could consume the small margin, so schedule risk analysis is the right next step.

Question 97

Topic: Stakeholder Communications Management

A vendor’s late equipment delivery has already occurred and now drives a 7-day slip to the contractual commissioning milestone needed for final scope handover. The schedule management plan requires sponsor escalation within 24 hours for any forecast slip greater than 5 working days on a contractual milestone; the weekly dashboard is for routine status only. What is the best communication response?

• A. Escalate it now as a schedule issue with baseline-versus-forecast milestone impact and required action.
• B. Replace the baseline milestone date with the new forecast before sharing the update.
• C. Log it as a schedule risk and wait for the next weekly dashboard to report it.
• D. Send current percent complete and actual dates only until recovery actions are approved.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The delay is no longer uncertain, so it is a schedule issue rather than a schedule risk. Because the forecast slip exceeds the escalation threshold for a contractual milestone, the communication should be immediate and should show baseline-to-forecast impact plus the action or decision needed.

When a delay has already happened and is forecast to breach a contractual milestone beyond the plan’s escalation threshold, it must be communicated as a schedule issue, not routine status. The best communication preserves schedule-control discipline by showing the approved baseline date, the current forecast date, the affected milestone or scope delivery, and the decision or recovery action needed from stakeholders.

Simply reporting status data such as percent complete or actual dates is not enough, because stakeholders need the schedule impact. Waiting for the next dashboard delays required escalation, and replacing baseline dates with forecast dates hides variance instead of communicating it. In PMI-SP terms, effective schedule communication distinguishes issue from risk and status from impact while following the schedule management plan.

The delay already occurred and exceeded the escalation threshold, so stakeholders need immediate issue communication that shows impact against the baseline.

Question 98

Topic: Schedule Planning and Development

A scheduler has a complete activity list and duration estimates for a fiber rollout across two regions. North crews work a 5-day calendar, South crews work a 6-day calendar, and South trenching cannot start before June 1 because of an environmental restriction. The contract requires a client inspection milestone after testing and before handover, and each site needs local permit approval before mobilization. Team leads have supplied desired start dates, and the sponsor wants a finish-date forecast. What should the scheduler do next?

• A. Issue a milestone forecast from desired dates, then refine logic later.
• B. Fast track field work now, then validate the sequence if needed.
• C. Set finish-no-later-than constraints to protect the contract, then baseline.
• D. Build permit and inspection milestone logic, assign regional calendars, apply the June 1 constraint, then calculate dates.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: Before forecasting completion, the scheduler must first make the schedule model credible. That means sequencing the work with the real permit and inspection dependencies, using the correct regional calendars, and applying only the valid June 1 constraint.

In schedule planning and development, once activities and durations are defined, the next step is to build the sequence correctly in the schedule model. Here, geography affects working time through different regional calendars, permits create predecessor logic before mobilization, the contract adds a mandatory inspection milestone before handover, and the environmental rule creates a justified date constraint for South trenching. After those elements are modeled, the scheduler can calculate dates and evaluate the driving path with confidence. Using desired start dates as a forecast, forcing dates with blanket constraints, or compressing work before validating logic all weaken schedule integrity and can hide the true source of schedule risk.

A reliable finish forecast requires a credible schedule model first, with real dependencies, the contractual inspection milestone, the valid June 1 constraint, and correct regional calendars.

Question 99

Topic: Stakeholder Communications Management

At the weekly review, the sponsor asks for an update on a delayed system-integration activity that is on the driving path to user acceptance testing (UAT) and the July 8 readiness review. By the status date, the activity was planned to be 100% complete, but it is 75% complete with 3 working days remaining. UAT was baselined to start on June 24 and is now forecast to start on June 27. Which update best communicates the schedule situation?

• A. Integration is 75% complete versus 100% planned, slipping UAT from the June 24 baseline to a June 27 forecast and putting the July 8 readiness review at risk.
• B. Integration is behind the baseline at the status date; a schedule variance exists.
• C. Integration is 75% complete with 3 days remaining; the team is working to recover.
• D. Integration is 75% complete, so UAT is now planned for June 27 and the baseline should be updated.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The best status update connects four things: current progress, variance against the approved baseline, the new forecast, and the effect on downstream dates. That gives stakeholders usable schedule information instead of only a progress note or an improper baseline change.

A strong PMI-SP schedule update should tell stakeholders what has happened, how that compares with the baseline, what dates are now expected, and why the change matters. Here, the useful message is that integration is 75% complete when 100% was planned by the status date, UAT has moved from its June 24 baseline start to a June 27 forecast, and the readiness review is now at risk because the delayed activity is on the driving path.

Reporting only percent complete is weak because it does not show variance or impact. Reporting only that variance exists is also incomplete because stakeholders still need the forecast and affected milestone. Treating the new forecast as the new baseline is incorrect unless formal change control approves a rebaseline.

The key takeaway is that schedule communication should preserve baseline-versus-forecast discipline and clearly state downstream impact.

It links actual progress, baseline variance, forecasted dates, and downstream schedule impact without confusing the baseline with the forecast.

Question 100

Topic: Stakeholder Communications Management

Status date is August 14, 2026. On a Monday-Friday calendar, Factory acceptance test → Site installation → contractual Go-live are all finish-to-start. The vendor now forecasts the test will finish 8 working days late; this driving path had 2 days of total float, the escalation threshold is any forecast variance over 5 working days, and only the sponsor and contract manager may approve actions affecting contract dates. What is the best communication response?

• A. Constrain Go-live to the contract date, then send the weekly report.
• B. Escalate the validated forecast impact and recovery options to the sponsor and contract manager.
• C. Replace the baseline milestone date with the forecast date before reporting.
• D. Add a lead between testing and installation, then report the improved forecast.

Best answer: B

What this tests: Stakeholder Communications Management

Explanation: The 8-day delay consumes the 2 days of float and forecasts the contractual milestone 6 working days late, which is beyond the 5-day escalation threshold. Because contract-date actions are outside the scheduler’s authority, the right response is to escalate a validated forecast and impact analysis, not alter logic or baseline data.

When a schedule issue crosses a stated tolerance and affects a contractual milestone, the scheduler should communicate through the defined escalation path using a valid schedule model. Here, the finish-to-start driving path loses more time than its available float, so Go-live is forecast late and the issue exceeds the escalation threshold. That means the scheduler should preserve the current logic and baseline, confirm the forecast impact, and escalate the issue with clear recovery options to the sponsor and contract manager, who hold the approval authority.

• Validate the driving path and remaining durations.
• State the forecast variance against the baseline commitment.
• Communicate feasible recovery options separately from current status.

Changing constraints, leads, or baseline dates may make the report look cleaner, but it weakens traceability and forecast credibility.

The delay exceeds available float and the escalation threshold, so it must be communicated through the authorized contract-date escalation path using a credible forecast.

Questions 101-125

Question 101

Topic: Schedule Planning and Development

A scheduler is developing a contract schedule for a system rollout. The SOW already defines the milestone Go-live approved as: user training complete, all critical defects closed, and steering committee approval received.

Exhibit:

The contract requires Go-live approved by September 30. Which interpretation is best?

• A. The milestone date should be changed to October 3 in the baseline.
• B. The milestone is clearly defined, but the current schedule does not achieve it.
• C. The milestone is achievable because one predecessor path still finishes early.
• D. The milestone is not yet defined because resources are missing.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: The milestone definition is already complete because the SOW states what conditions must be met for Go-live approved. The remaining question is achievability, and the driving path finishes October 3 with -3 days of total float, so the current schedule misses the September 30 contract date.

Milestone definition and milestone achievability are different checks. Definition answers what the milestone means and what completion criteria must be satisfied. In this scenario, the SOW already does that by stating the required conditions for Go-live approved.

Achievability analysis answers whether the schedule model can realistically meet the milestone date. The path and float data show that one predecessor path finishes on October 3, which is 3 days after the contractual date, with -3 days total float. That means the milestone is properly defined but currently forecast late.

A path finishing early does not offset a late driving path, and a forecast slip does not justify changing the baseline without approved change control.

The SOW already states the completion criteria, and the negative float on the driving path shows the date is not currently achievable.

Question 102

Topic: Schedule Closeout

A facilities upgrade is complete, and the customer has accepted the installed system. The contract requires written customer acceptance of three contractual milestone dates before the final invoice and project closeout. The schedule baseline remained controlled, and one milestone date was changed through approved change control. What is the BEST action now?

• A. Send the latest forecast with the final invoice and close.
• B. Ask the sponsor to close out because deliverables were accepted.
• C. Compare actual milestones with approved dates and get customer sign-off.
• D. Replace baseline milestone dates with actual dates, then archive.

Best answer: C

What this tests: Schedule Closeout

Explanation: Contractual schedule closeout requires formal acceptance from the party named in the contract, using the approved baseline and approved changes as the reference. Because the contract requires written customer acceptance of milestone dates, the scheduler should document final milestone performance and obtain customer sign-off before closing out.

The key concept is formal closeout of contractual schedule components. Even though the installed system has been accepted, the contract still requires written customer acceptance of the milestone commitments. The scheduler should therefore prepare final milestone performance information using the approved schedule baseline, adjusted only for the milestone date that was formally changed through approved change control, and then obtain the customer’s written acceptance.

This protects schedule-control integrity because it:

• uses the approved reference, not a rewritten baseline
• shows final performance against contractual commitments
• satisfies the contract condition tied to invoicing and closeout

Sponsor awareness, forecasting, and archiving may still occur, but they do not replace formal customer acceptance of the contractual schedule record.

It uses the approved contractual baseline, including the approved milestone change, and secures the required written customer acceptance before closeout.

Question 103

Topic: Schedule Planning and Development

A construction project has approved scope and schedule baselines. The estimator is still finalizing the time-phased budget for control accounts. The sponsor asks whether the project already has a Performance Measurement Baseline for monthly earned value reporting. Which response is most accurate?

• A. No; the PMB is only the approved cost baseline.
• B. Yes; approved scope and schedule alone establish the PMB.
• C. Yes; the schedule baseline already includes the time-phased cost budget.
• D. No; PMB integrates approved scope, schedule baseline, and cost baseline.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: The project does not yet have a complete PMB because the cost baseline is still being finalized. In PMI-SP terms, the schedule baseline is the approved date reference, the cost baseline is the approved time-phased budget, and the PMB integrates scope, schedule, and cost for performance measurement.

A schedule baseline and a cost baseline are separate control references. The schedule baseline is the approved version of planned dates and logic used to measure schedule performance. The cost baseline is the approved time-phased budget used to measure cost performance. The Performance Measurement Baseline combines the approved scope baseline with the schedule and cost baselines so the project can measure integrated performance, including earned value.

In this scenario, scope and schedule are approved, but the time-phased budget for control accounts is not yet finalized. That means the cost baseline is not approved, so the PMB is not fully established. A schedule baseline is a component of the PMB, not a substitute for it. The closest distractor is the idea that scope plus schedule is enough, but integrated performance measurement also needs the approved cost reference.

The PMB is not complete until the approved cost baseline is integrated with the approved scope and schedule baselines.

Question 104

Topic: Schedule Monitoring and Controlling

A scheduler updates a predictive construction schedule monthly on a 5-day calendar. At the April 30 status date, auditors must determine when a driving Finish-to-Start dependency was changed to a Start-to-Start relationship with lag and when date constraints were added to hold a contract milestone. Which electronic file storage and retrieval standard best supports that ongoing audit analysis?

• A. Save only milestone and critical-path extracts in a shared spreadsheet.
• B. Store each monthly native file centrally with standard naming, status date, baseline ID, and linked change log.
• C. Archive monthly PDF bar charts and delete prior native schedule files.
• D. Keep only the current native file and retain prior PDF status reports.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: Ongoing schedule audits require the exact native file from each update cycle, not just snapshots or summaries. A standard repository with consistent naming, status date, baseline reference, and change-log links lets auditors trace when logic or constraint changes altered the forecast.

The key concept is auditability of the schedule model across updates. To analyze when a dependency, lag, or constraint changed, auditors need to retrieve the exact native schedule file used at each status date and connect it to the approved baseline reference and change history. Standard electronic storage and retrieval rules—such as one central repository, consistent file naming, version control, status date tagging, and linked change logs—make that comparison reliable and repeatable.

Without those standards, the audit trail becomes incomplete. PDF reports may show dates, but they usually do not preserve the full editable logic, calendars, constraints, float, and other model details needed for schedule analysis. Keeping only summaries or the latest file makes the archive look cleaner, but it weakens traceability and reduces confidence in the forecast history.

Standardized, versioned storage of native schedule files preserves the audit trail needed to compare logic, constraint, and forecast changes over time.

Question 105

Topic: Stakeholder Communications Management

At the data date, the scheduler has already validated status, logic, and remaining durations. The forecast now shows the critical-path cutover milestone finishing five days late. The sponsor wants a recovery plan, but only the operations director can approve the weekend outage window and production acceptance. What should the scheduler do next?

• A. Send the forecast variance report to the steering committee.
• B. Rebaseline the cutover milestone to the forecast finish.
• C. Fast-track testing and deployment immediately.
• D. Confirm acceptable recovery windows with the operations director.

Best answer: D

What this tests: Stakeholder Communications Management

Explanation: The forecast is already credible, so the next step is not more validation, reporting alone, or rebaselining. Because the operations director controls the outage window and production acceptance, the scheduler should confirm that stakeholder’s recovery constraints before choosing a compression action.

The key concept is stakeholder influence on schedule recovery and acceptance. In this case, the delay has already been validated, so the issue is no longer status quality; it is whether any recovery option will be acceptable and executable. Because the operations director is the approval authority for the weekend outage window and production acceptance, that stakeholder’s expectations and constraints directly affect which recovery scenarios are viable. The scheduler should engage that decision-maker before selecting fast tracking, crashing, or another corrective action. Sending reports improves visibility, but visibility alone does not resolve the recovery decision. Rebaselining is also inappropriate until an approved change justifies replacing the control reference. The best next step is to involve the stakeholder who can actually accept or reject the recovery window.

That stakeholder controls both the recovery window and schedule acceptance, so their constraints must be confirmed before selecting a recovery action.

Question 106

Topic: Schedule Closeout

A facility upgrade project closed 12 working days late. Delay analysis showed the missed finish was driven by a vendor design package released 17 days late because interface requirements were incomplete. The team used an approved resequencing plan and recovered 5 days. A site-inspection package also slipped, but it had 8 days of total float and did not affect completion. During closeout, which action best improves organizational process assets?

• A. Replace baseline dates with the final forecast so the closeout record reflects the recovered schedule.
• B. Highlight the site-inspection delay in lessons learned because it is easier to standardize across projects.
• C. Capture the driving-path delay, recovery results, and root cause, then update vendor-interface and dependency-planning templates.
• D. Require future teams to fast track design and construction by default when vendor deliverables look late.

Best answer: C

What this tests: Schedule Closeout

Explanation: Closeout lessons learned should capture what actually drove the finish date, why it happened, and how effective the approved recovery was. The best update converts that evidence into reusable templates or checklists without hiding variance or focusing on non-driving work.

In schedule closeout, lessons learned should improve organizational process assets by documenting the real schedule driver, its root cause, and the observed effect of the approved response. Here, the vendor design package was on the driving path, incomplete interface requirements caused the delay, and the approved resequencing recovered only part of the loss. That means the most valuable OPA update is a practical one: strengthen future vendor-interface planning and dependency definition using what this project proved.

Do not overwrite the baseline with forecast dates, because the baseline must remain the approved performance reference. Do not make default fast tracking the standard response, because compression should be analyzed and approved case by case. Do not center the lesson on the site-inspection slip, because it was non-driving and did not affect completion.

Good closeout records preserve variance history and make future schedules better.

It preserves true schedule performance and turns the actual driving-path cause and approved recovery results into reusable scheduling assets.

Question 107

Topic: Schedule Monitoring and Controlling

On the status date, a critical-path installation activity had a baseline duration of 10 working days and has consumed 9 days. The owner entered 90% complete, but field inspection shows 6 of 12 units installed and indicates at least 5 working days remain. The completion milestone is now forecast 4 days late. What is the best scheduler action?

• A. Keep 90% complete and add a finish constraint to hold the planned date.
• B. Crash a downstream activity that still has float to recover the slip.
• C. Validate the status, correct actuals and remaining duration, then rerun the forecast.
• D. Replace the baseline finish date with the current forecast date.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The activity status is inconsistent because the reported percent complete does not match the physical progress or the stated remaining work. The best action is to validate and correct the status data first, then rerun the schedule forecast before deciding on recovery or change control.

This is a status-quality problem first, not a compression problem first. A critical-path activity cannot be treated as 90% complete when only 6 of 12 units are installed and at least 5 days of work remain after 9 days have already been used. That mismatch makes the forecast unreliable.

The scheduler should:

• confirm the actual progress with the activity owner and field evidence
• update actuals and remaining duration to reflect credible remaining work
• rerun the schedule model to produce a valid forecast
• then evaluate recovery options or change control if the milestone is still late

Using bad status data leads to bad recovery decisions. The closest distractors act on dates instead of fixing the underlying status credibility issue.

The reported 90% complete conflicts with observed physical progress and remaining work, so the status data must be corrected before any forecast or recovery action is reliable.

Question 108

Topic: Schedule Monitoring and Controlling

A construction project has an approved schedule baseline and a contractual turnover milestone of September 30. At the August 15 data date, schedule analysis still shows turnover on September 30 with 0 days total float. The audit finds that a mandatory finish constraint was added to the milestone in the last update to keep that date, and activity Cable Pull started on August 10 even though predecessor Tray Inspection is forecast to finish on August 18. No change request has been approved. What is the best action?

• A. Add more date constraints to predecessor activities so the sequence matches actual work.
• B. Rebaseline now because field execution no longer matches the original sequence.
• C. Keep the current forecast because the contractual milestone still appears on time.
• D. Validate the out-of-sequence status, remove the forced milestone constraint, and rerun the forecast.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The schedule result is unreliable because the milestone date is being held by a manually added constraint while progress is also out of sequence. Before reporting or acting on the forecast, the scheduler should restore model integrity and recalculate the schedule.

In schedule monitoring and controlling, analysis results are only useful if the schedule model is credible. Here, the apparent on-time milestone is being preserved by a newly added mandatory finish constraint, and the update contains out-of-sequence progress. Those two facts mean the current forecast may be masking the true driving path and real float position.

A sound response is to:

• verify actual status and remaining duration with the activity owners
• remove the unsupported date-forcing constraint
• rerun the schedule analysis and then assess any real milestone impact

Because no change request has been approved, the baseline should not be replaced. Acting on or reporting a constraint-driven forecast would weaken schedule control rather than improve it.

The forecast is not credible until the artificial constraint and out-of-sequence status are corrected in the schedule model.

Question 109

Topic: Schedule Monitoring and Controlling

A facilities upgrade project has an approved schedule baseline. On the status date, two commissioning activities on the driving path to a contractual occupancy milestone both require the same specialist, who will be only 50% available for the next three weeks. Those activities have zero total float, no qualified backup is available, the weekly status report is due today, and any baseline change requires approved change control. What is the best action?

• A. Rebaseline the occupancy milestone now so the schedule matches the specialist’s reduced availability.
• B. Compress a non-driving activity with float to offset the resource loss on the milestone.
• C. Describe the shortage in the status report but keep current forecast dates until the next update.
• D. Update the specialist’s calendar and affected remaining durations, recalculate the driving-path forecast, and report recovery or change-control needs.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: A resource availability change on zero-float driving work must be reflected in the schedule model immediately. The scheduler should update the resource calendar and remaining durations, recalculate the forecast, and then use that analysis to communicate recovery needs or request formal change control.

Resource availability updates affect the schedule forecast, not the approved baseline by themselves. In this scenario, the same specialist drives two zero-float activities that lead directly to a contractual milestone, so the scheduler’s first responsibility is to preserve schedule model integrity: update the resource calendar and affected remaining durations, then recalculate the forecast.

That analysis shows the real impact on the driving path and supports an evidence-based response. If the recalculated forecast threatens the milestone, the team can evaluate recovery options and, if needed, submit a formal change request. The weekly report should communicate the updated forecast and its impact, not outdated dates. Reporting the issue without updating the model leaves stakeholders with unreliable schedule information, while rebaselining before approval would hide variance instead of controlling it.

This keeps the forecast credible by modeling the actual resource constraint on zero-float driving work before any recovery decision or baseline change.

Question 110

Topic: Schedule Monitoring and Controlling

At the weekly schedule update, the owner of a near-critical activity says it is “about 70% complete,” but provides no actual start date, no current remaining duration, and no update since the last data date 10 days ago. The activity feeds a key internal milestone next month. What is the best follow-up by the scheduler?

• A. Keep the prior update and report the milestone as unchanged
• B. Raise a rebaseline request for the activity immediately
• C. Use the 70% complete figure to recalculate the finish date
• D. Request current status details before updating the forecast

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The best action is to validate the status data first. A percent-complete estimate without current actual dates or remaining duration is not reliable enough to support a forecast for near-critical work.

This tests status quality versus schedule impact. When an activity owner provides incomplete or stale status, the scheduler should first obtain usable status inputs such as actual start or finish information, current remaining duration, and any blockers or changed assumptions. Only then should the forecast be updated and any milestone impact assessed.

Using percent complete alone can distort the forecast because it does not show how much work is truly left. Leaving the prior update unchanged ignores the risk of using outdated data, and rebaselining is a change-control action, not a routine response to poor status collection. The key takeaway is to improve status data quality before performing schedule analysis or reporting impact.

Incomplete or stale status should be validated with current actuals and remaining duration before the schedule forecast is revised.

Question 111

Topic: Schedule Closeout

A healthcare system rollout had one schedule rebaseline approved through change control after new regulatory testing was added. At closeout, the project actually finished on November 12, 2025. The original baseline finish was October 20, 2025, the approved revised baseline finish was November 5, 2025, and the final forecast before completion was November 12, 2025. For the final schedule performance evaluation, which comparison should the scheduler use?

• A. Compare actual finish to the final forecast finish.
• B. Compare actual finish to the original baseline finish.
• C. Compare actual finish to the approved revised baseline finish.
• D. Compare the approved revised baseline finish to the original baseline finish.

Best answer: C

What this tests: Schedule Closeout

Explanation: At closeout, final schedule variance is assessed by comparing actual results with the approved schedule baseline that governed the work after authorized changes. A forecast is only a prediction, and the original baseline is no longer the formal performance reference once a rebaseline is approved.

The key distinction is baseline versus forecast. Final schedule performance evaluation uses actual dates against the current approved schedule baseline, because that baseline is the control reference after formal change approval. In this scenario, the correct closeout comparison is the actual finish of November 12, 2025, against the approved revised baseline finish of November 5, 2025, showing the project finished 7 days late against the approved baseline.

The final forecast is useful for judging how accurate the team’s prediction was, but it does not measure schedule variance. The original baseline may still help with lessons learned and change-impact analysis, but once the schedule was officially rebaselined, it is no longer the primary reference for final performance reporting.

At closeout, measure execution performance against the approved baseline, not against what the team last expected to happen.

Final schedule performance at closeout is measured against the approved baseline in effect, not against a forecast or a superseded baseline.

Question 112

Topic: Schedule Monitoring and Controlling

As of the July 15 data date, a construction project’s schedule update has been validated with activity owners and the critical-path logic has been reviewed. Because a permit was approved late, the contractual handover milestone is now forecast 8 working days later than the approved baseline; the schedule management plan requires explanation in reports for any milestone variance over 5 working days. No approved change affects the baseline, and no schedule reserve has been consumed. What should the scheduler do next?

• A. Add reserve analysis to the report before any further action.
• B. Add schedule risk analysis to assess whether delay may occur.
• C. Issue the status report with variance explanation and forecast impact.
• D. Request rebaselining so the milestone matches the current forecast.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The milestone is already forecast late versus the approved baseline, and the report threshold has been exceeded. Since status and logic are credible, the next report should include a variance explanation and updated forecast, not reserve analysis, risk analysis, or rebaselining.

In schedule monitoring and controlling, reporting content should match the type of schedule condition that has been confirmed. Here, the update has already been validated, the critical path reviewed, the baseline is still in force, and the milestone variance exceeds the reporting threshold. That makes variance explanation the immediate reporting need.

Reserve analysis is appropriate when schedule contingency or buffer consumption must be evaluated or explained. Risk analysis is appropriate when uncertainty about future dates is still the main issue. In this case, the delay driver is already known and the milestone is already forecast late, so this is a current variance to explain against the approved baseline. Rebaselining would require approved change control, not just an unfavorable forecast. The key takeaway is to report verified variance honestly before considering any separate control actions.

The variance is already verified against the approved baseline and exceeds the reporting threshold, so the next step is to report its cause and forecast effect.

Question 113

Topic: Schedule Planning and Development

A scheduler is building a predictive project schedule. Activity definitions, durations, and logic are complete, and the contract includes a fixed acceptance milestone. The current model uses one Monday-Friday, 8-hour project calendar, but key activities require a DBA who is unavailable on Mondays and a test lead shared with another project until June 14. Before assigning resources to the activities, which input is most important to obtain?

• A. Total float values for the critical and near-critical activities
• B. Additional mandatory constraints for the acceptance milestone
• C. A resource breakdown structure aligned to the WBS
• D. Resource calendars and confirmed availability for the specialists

Best answer: D

What this tests: Schedule Planning and Development

Explanation: Before assigning resources, the scheduler needs the actual availability and working-time calendars of the required specialists. Shared resources and different workweeks can change dates and driving paths, so using only a default project calendar would weaken forecast credibility.

The key concept is that resource assignments should be based on real resource availability, not just activity logic and a generic project calendar. In this scenario, the DBA and test lead do not follow the default calendar, so assigning them without resource-specific calendar and availability data would produce a schedule that looks complete but may show impossible dates, misleading float, and an unreliable critical or near-critical path.

• Confirm each required resource’s working days, hours, and current commitments.
• Apply those calendars or availability limits in the schedule model.
• Then review the resulting dates, float, and milestone impact.

Using structure, float, or extra constraints instead of actual availability makes the model cleaner on paper but weaker for decision-making.

Realistic assignments require each needed resource’s working time and availability so forecast dates reflect actual capacity.

Question 114

Topic: Schedule Planning and Development

A scheduler is preparing the baseline for a hospital imaging-suite upgrade. The WBS and OBS are approved, and each control account has draft work packages. The facilities manager says handoffs between room readiness, vendor installation, network activation, and clinical acceptance may be missing. Before decomposing the work packages into detailed activities, what is the best way to validate work package completeness?

• A. Run critical path analysis on the current draft schedule
• B. Review each work package with discipline SMEs and affected stakeholders to confirm deliverables, interfaces, and acceptance events
• C. Assign every work package to an OBS owner and proceed to baseline
• D. Compare the draft work packages with a similar project’s template

Best answer: B

What this tests: Schedule Planning and Development

Explanation: Work package completeness is best validated by the people who understand the work and the people affected by its outputs. A structured review with SMEs and relevant stakeholders confirms missing deliverables, interfaces, and acceptance events before those gaps become schedule defects.

In schedule planning and development, a complete work package must cover all work needed to produce its defined output, including key handoffs and acceptance points. The strongest validation method is a structured review with subject-matter experts who know how the work is performed and stakeholders who receive, approve, or depend on the result. That review helps confirm missing deliverables, interface work, and downstream needs before the work package is decomposed into activities and loaded into the schedule model.

Critical path analysis, historical templates, and OBS ownership can support development, but they do not prove that omitted work is actually represented. If scope is missing at the work package level, later schedule logic and baseline dates will rest on an incomplete foundation. The key distinction is completeness validation versus analysis of work that is already defined.

A cross-functional review is the most reliable way to detect omitted deliverables and handoffs before detailed scheduling begins.

Question 115

Topic: Stakeholder Communications Management

A scheduler is preparing an escalation note for the weekly governance meeting.

• Status date: September 18
• Calendar: Monday-Friday
• API security fix: critical path, 0 total float, forecast 4 working days late
• System integration test: 5 working days, finish-to-start after the fix
• Launch milestone: Finish No Later Than September 30
• Current forecast: launch 2 working days late
• Next path: 2 days total float

Which escalation content best meets the communication need?

• A. Overall progress is still acceptable, so keep September 30 in the report and revisit the issue after the next status cycle.
• B. The date pressure comes from the milestone constraint, so remove the constraint and align the baseline to the forecast before escalating.
• C. As of September 18, the API security fix is 4 working days late on the critical path; because system integration test is finish-to-start after it, launch is forecast 2 working days late. Options are weekend testing to recover time or approval to move the launch through change control; decision needed by September 20.
• D. The training path has 2 days of float, so report a general risk to launch and wait to escalate unless that path also slips.

Best answer: C

What this tests: Stakeholder Communications Management

Explanation: Good schedule escalation should identify the issue, show its forecast impact from the schedule logic, present response options, and request a decision. The best option does that using the critical-path delay, the finish-to-start dependency, the constrained milestone, and a clear decision date.

In PMI-SP practice, escalation content should be evidence-based, not cosmetic. Here, the issue is already real: the API security fix is 4 working days late on the critical path with 0 float. Because system integration test cannot start until that work finishes, the finish-to-start logic pushes the launch forecast 2 working days beyond the constrained September 30 milestone. A strong escalation note therefore includes four elements: the issue, the quantified schedule impact, viable options, and the specific decision needed by a stated date. That gives stakeholders enough information to act without weakening the schedule model.

The near-critical path with 2 days of float is not the current driver. Changing constraints or baselines to make the dates look cleaner would damage traceability instead of communicating the real forecast.

It states the issue, ties the impact to the driving logic and milestone constraint, presents options, and requests a time-bound decision.

Question 116

Topic: Schedule Monitoring and Controlling

As of the July 10 status date, the approved schedule uses a Monday-Friday calendar. Cable Pull drives Power-On Test with a finish-to-start dependency and no lag; this path has 0 total float, and Power-On Test has no date constraint. Cable Pull is now forecast to finish July 18 instead of July 16, moving the contractual Ready for Energization milestone from July 21 to July 23. No recovery plan or overtime approval has been issued. What should the scheduler do?

• A. Keep the logic-driven forecast and assess recovery through change control.
• B. Change the link to overlap work so the milestone still shows July 21.
• C. Add a Must Finish On July 21 constraint to Power-On Test.
• D. Use a temporary 7-day calendar for Power-On Test.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: The schedule should continue to show the July 23 forecast because the driving-path delay has already occurred and no approved recovery action exists. Manually forcing dates or changing logic or calendars just to keep the milestone on time would hide real impact and weaken schedule control.

When a delayed activity sits on a zero-float driving path, the forecast should move unless the team has an approved, realistic change to the work plan. In this case, the correct action is to keep the existing logic and calendar, show the contractual milestone slipping to July 23, and then evaluate recovery options through normal control processes.

• Keep status data and relationships fact-based.
• Show variance against the approved baseline.
• Analyze real recovery options before changing the model.
• Use change control if an alternate plan is approved.

A date that looks cleaner is not better if it breaks traceability between actual status, forecast, and baseline.

This keeps the delay visible and preserves traceable, logic-based control until an approved recovery plan changes the model.

Question 117

Topic: Schedule Monitoring and Controlling

On a predictive data-center migration project, Database cutover rehearsal is on the driving path to a contractual go-live milestone on July 31. At the Friday data date, the activity owner’s weekly report says the task is 75% complete, but the two assigned database engineers’ timesheets show only 20 of 40 planned hours, and one engineer may be reassigned next week. The schedule management plan requires resource updates to be collected through timesheets and the Monday resource review meeting before any forecast is issued. What is the best action?

• A. Reconcile the report and timesheets, confirm remaining work and next week’s availability in the resource review meeting, then update the forecast.
• B. Use the 75% weekly report value for this cycle and check resource availability after Monday.
• C. Keep the current forecast until a formal change request is approved for the go-live milestone.
• D. Level the engineers immediately from the timesheet data and issue a revised finish date to stakeholders.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: When resource data conflict, the scheduler should validate actual usage, remaining duration, and near-term availability through the project’s defined status process before updating the forecast. On a driving-path activity tied to a contractual milestone, using unverified information would reduce forecast credibility.

This situation is about collecting reliable resource updates, not changing the baseline or rushing out a date. The weekly report, timesheets, and possible reassignment do not agree, so the scheduler should follow the standard update procedure to reconcile actual hours with the activity owner’s progress claim and confirm next week’s resource commitment in the scheduled review meeting. After actual effort, remaining duration, and future availability are validated, the schedule model can be updated and any forecast effect on the contractual milestone can be communicated. The baseline remains the control reference unless a later approved change justifies rebaselining.

• Confirm actual hours charged and any missing entries.
• Validate physical progress and remaining duration with the activity owner.
• Confirm near-term availability with the resource manager before publishing the forecast.

The closest trap is treating change control as a reason to avoid routine status collection and forecast updating.

It uses the required update sources to validate actual effort, remaining duration, and future availability before changing the forecast.

Question 118

Topic: Schedule Planning and Development

During development of the baseline schedule for a hospital equipment installation, the contract requires Go-live by September 30 and the schedule must be submitted for approval tomorrow. In the draft precedence diagram, many downstream tasks use Start No Earlier Than constraints, and the team inserted a 15-day lag after Equipment shipped instead of modeling receipt, inspection, and site readiness work. What is the BEST action?

• A. Replace artificial constraints and lags with explicit handoff activities and dependencies.
• B. Baseline the draft now and revise the logic after approval.
• C. Insert schedule reserve before Go-live and keep the current logic.
• D. Level installation resources before revising the network logic.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: A credible precedence diagram should explain dates through activities and dependencies, not by forcing dates with unnecessary constraints or long lags. Here, the best action is to model the missing handoffs explicitly before baseline approval, while keeping only any truly external date requirement.

The core issue is schedule-model credibility. When a network diagram uses many hard date constraints and long lags to make dates work, it often means real work or dependencies are missing, so critical path, float, and forecast results become unreliable. In this case, the contractual Go-live date is a legitimate external requirement, but receipt, inspection, site readiness, and similar handoffs should be represented as actual activities or milestones with proper logic relationships. That correction should happen before the baseline is approved, because a flawed logic model becomes a weak control reference for later status and recovery decisions. Adding reserve or leveling resources may help later, but neither fixes a precedence diagram that is date-driven instead of logic-driven.

Explicit logic makes the driving path and float credible, while artificial constraints and lags can hide missing dependencies.

Question 119

Topic: Schedule Planning and Development

During a status update, the contractual milestone Go-live approved is forecast 8 workdays late. The project manager asks the scheduler to give the milestone a 5-day duration and assign recovery resources so percent complete can be reported directly on it. What is the best action?

• A. Manually constrain the milestone to the committed date.
• B. Replace the baseline milestone date with the current forecast.
• C. Give the milestone duration and add extra staff to compress it.
• D. Keep the milestone zero-duration and recover the driving activities.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: A milestone marks a significant event; it does not carry duration, resources, or percent complete. When a milestone is late, recovery should be planned and statused on the driving activities while the milestone remains the reporting point.

In schedule planning and reporting, an activity represents work and therefore can have duration, logic, resources, and progress updates. A milestone represents a point in time, usually with zero duration. Because the late item here is a contractual milestone, the scheduler should keep it as a milestone and focus recovery on the predecessor activities that drive its forecast date. If extra work, resequencing, or compression is needed, that effort must be shown on activities, not on the milestone itself. This preserves schedule model integrity and gives stakeholders a credible forecast. Adding duration to the milestone, forcing its date, or replacing the baseline with the forecast would hide the real source of the delay rather than control it.

A milestone is a zero-duration event, so recovery effort and status must be modeled on the activities that drive it.

Question 120

Topic: Schedule Planning and Development

A scheduler is building the baseline for a medical-equipment rollout from Germany to Brazil. Hospital installation can start only after factory acceptance is signed, ocean transit takes 10 calendar days, customs clearance follows Brazil’s weekday calendar, and the contract requires a Ready for Clinical Use milestone by September 30. Which approach best sequences this work?

• A. Use one standard calendar and manually enter vendor logistics dates.
• B. Link acceptance, transit, customs, and installation with proper calendars and a contract milestone.
• C. Link acceptance to installation, then use a Start No Earlier Than on installation.
• D. Link acceptance to installation, then use a Must Finish On for September 30.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: The best method is to model the actual sequence of work and location effects in the schedule model. Geography, transit, customs, and the contract milestone should be represented through activities, logic, calendars, and a milestone—not by forcing dates with constraints.

In schedule planning and development, sequencing should reflect the real handoffs that drive dates. Here, factory acceptance must finish before shipment, shipment must finish before customs clearance, and customs must finish before hospital installation. The Germany-to-Brazil move adds a real transit activity, and customs uses a different working calendar, so those factors belong in the schedule logic and calendars. The contractual September 30 date should be shown as a milestone for measuring commitment, not as a hard date that replaces logic. Start constraints, finish constraints, and manual date entry can make the schedule look orderly, but they hide the true impact of upstream slips and weaken forecast credibility. The closest distractor is the start-constraint approach because it still breaks the dependency chain.

This models the real dependency chain and calendars while keeping the contract date visible without overriding logic.

Question 121

Topic: Schedule Monitoring and Controlling

As of the status date June 3, 2026, the integrated schedule uses a Monday-Friday calendar. The schedule management plan allows a temporary Saturday calendar when approved and staffed. The contract go-live milestone has a finish-no-later-than date of June 28, but the current forecast is July 3.

The sponsor asks for five workdays of compression. Which proposal should the scheduler flag as unacceptable?

• A. Change system test and UAT to overlap with a 3-day lead.
• B. Pull training updates forward within their available float.
• C. Add an available qualified reviewer to the regulatory package.
• D. Use an approved Saturday calendar for config build.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: Overlapping UAT with system test looks like fast tracking, but it breaks the schedule model’s stated logic. UAT has an explicit quality gate and uses the same QA specialists as system test, so the lead creates both rework risk and a resource conflict instead of a credible recovery.

Schedule compression is acceptable only when the revised model remains executable. Here, UAT is not just another downstream task: it has a stated entry condition that system test must be complete and Sev-1 defects closed, and it shares the same QA team with system test. Changing that finish-to-start logic to an overlap lead removes a real quality gate from the model and creates concurrent demand for the same constrained resource. That may make the forecast appear earlier, but it weakens traceability and credibility.

• Validate whether compression changes a true dependency or only hides it.
• Check whether the same people are now assigned to overlapping driving activities.
• Prefer transparent compression through approved calendar changes or added qualified resources.

Using float on separate work may not recover the milestone, but it does not corrupt the driving-path logic.

This overlap violates the stated UAT entry criteria and double-books the same QA team, so it shortens the plan on paper while increasing quality and resource risk.

Question 122

Topic: Stakeholder Communications Management

On the July 10 status date, a vendor interface defect has delayed critical-path system testing, and the forecast now shows the contractual go-live milestone for the approved scope 8 working days late. The schedule management plan requires escalation to the sponsor and customer within 24 hours whenever a key milestone is forecast to slip by more than 5 days; baseline changes require approved change control. What should the scheduler do next?

• A. Fast-track training and cutover tasks that do not drive go-live.
• B. Replace the baseline milestone with the forecast date before reporting.
• C. Wait for next status cycle and assign weekend overtime first.
• D. Escalate now with the forecast impact and recovery options.

Best answer: D

What this tests: Stakeholder Communications Management

Explanation: Because the forecasted milestone slip exceeds the escalation threshold in the schedule management plan, the issue must be communicated immediately through the defined stakeholder path. The update should show the forecast impact and recovery options without changing the approved baseline.

When a schedule issue has already occurred and the forecast breach exceeds a defined escalation threshold, the scheduler should communicate it immediately using the communication path in the schedule management plan. That message should state the current forecast, the affected delivery milestone, the likely impact to scope delivery, and realistic recovery options or decisions needed from stakeholders. The schedule baseline remains the approved control reference unless formal change control authorizes a change.

• Confirm the delay is on the critical path.
• Report the forecast variance and milestone impact.
• Present feasible recovery options and needed decisions.
• Keep baseline dates unchanged until approval.

The key point is to communicate accurate forecast impact and decision needs, not to hide variance or act on non-driving work.

The plan requires immediate escalation of a forecast milestone slip beyond the threshold, while the approved baseline remains the performance reference until any change is approved.

Question 123

Topic: Schedule Monitoring and Controlling

On a pharmaceutical facility project, the data date is August 1. Two driving-path activities, control system validation and cleanroom qualification, are planned for next week, and each requires full-time support from the same commissioning engineer. A resource availability update shows the engineer is available only 5 working days total, while the current forecast assumes 8 working days and still shows the contractual startup milestone on time with 0 total float. What should the scheduler do first?

• A. Crash a training activity that has 10 days of float.
• B. Level the engineer’s assignments in the schedule model and reforecast startup.
• C. Replace the baseline dates with the current forecast before reporting.
• D. Overlap both activities and assume the engineer can support each part-time.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: This is a resource-feasibility problem, not just a date problem. When one full-time engineer is scheduled for 8 days of driving work in a 5-day window, the schedule needs a resource allocation technique to create a realistic forecast before any further recovery action is chosen.

When updated resource availability makes the planned dates impossible, the schedule is no longer feasible even if the logic still shows an on-time milestone. Here, the same full-time engineer is assigned 8 days of driving-path work in a 5-day window with 0 total float, so the schedule model must be corrected using a resource allocation technique such as resource leveling. That creates a credible forecast based on actual capacity.

• Confirm the updated resource availability in the schedule model.
• Level the overallocated driving activities.
• Reforecast the startup milestone and then decide whether approved recovery or change control is needed.

Trying to preserve the date by assumption or by changing the baseline would hide the problem instead of controlling it.

The forecast is infeasible because the same full-time resource is overallocated on driving work, so leveling is needed before any valid recovery or change decision.

Question 124

Topic: Stakeholder Communications Management

A hybrid facilities project has this communication-plan excerpt:

Routine schedule status: weekly to PMO and workstream leads
Schedule issue affecting an internal milestone by >3 working days: same day to project manager
Schedule issue affecting any contractual or regulatory milestone: within 24 hours to sponsor and customer representative

A supplier delay has already occurred, and the current forecast shows the regulatory inspection milestone will slip by 7 working days. According to the plan, which stakeholder group must be notified now?

• A. Project manager only
• B. PMO and workstream leads
• C. Change control board
• D. Sponsor and customer representative

Best answer: D

What this tests: Stakeholder Communications Management

Explanation: Use the communication plan’s escalation rule, not the routine reporting cadence. Because the delay is already a schedule issue and it affects a regulatory milestone, the required audience is the sponsor and customer representative.

The key is to match the issue to the communication trigger in the plan. This is not routine schedule status; the delay has already occurred, so it is a schedule issue. The deciding fact is that the impacted milestone is regulatory, and the plan says any schedule issue affecting a contractual or regulatory milestone must be communicated within 24 hours to the sponsor and customer representative.

The internal-milestone rule for notifying the project manager applies only when the affected milestone is internal. Weekly distribution to the PMO and workstream leads is for routine status reporting, not immediate escalation. A change control board may review corrective action or baseline changes later, but that does not replace the required issue communication.

The plan requires escalation of any issue affecting a regulatory milestone to the sponsor and customer representative within 24 hours.

Question 125

Topic: Schedule Monitoring and Controlling

On a predictive facilities project, the approved schedule baseline still shows contractual handover on September 30. At the June 15 status date, critical-path work is on baseline dates, but delivery of custom switchgear from a sole supplier drives site energization and now has a high probability of slipping 3 weeks; using the planned mitigation would consume most of the schedule contingency reserve. The owner asks the next schedule report to show whether the handover date is still credible. What is the best action?

• A. Report only current variance because dates still match baseline.
• B. Rebaseline handover to the supplier’s most likely delivery date.
• C. Emphasize installation progress and the next two-week lookahead.
• D. Include schedule risk analysis and reserve analysis for handover.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: This report needs more than a variance note. Because the contractual milestone is still on baseline but threatened by an uncertain driving dependency that may consume schedule reserve, the report should include schedule risk analysis and reserve analysis.

Schedule reporting should match the control question being asked. Here, the owner wants to know whether a contractual milestone is still credible, not just whether current dates match the baseline today. Since the supplier delay is still an uncertainty on a driving path, this is a schedule risk, and the planned response would use most of the schedule contingency reserve. That means the report should include both the milestone risk exposure and the remaining reserve position.

A simple variance explanation is not enough because no actual milestone variance has occurred yet. Rebaselining is also inappropriate because the approved baseline remains the control reference until a change is formally approved. The key takeaway is to report risk and reserve information when forecast credibility depends on uncertain events and available schedule protection.

The baseline has not slipped yet, but a driving supplier risk could consume contingency, so the report should show milestone risk exposure and remaining schedule protection.

Questions 126-150

Question 126

Topic: Schedule Monitoring and Controlling

During an audit of an integrated schedule, the scheduler reviews this excerpt.

Status date: April 15, 2026
Master schedule calendar: Mon-Fri
Subcontractor field calendar: 7 days/week
In-house activity: Site release to subcontractor
  Forecast finish: April 28
Loaded in master schedule: milestone "Mechanical completion"
  Constraint: Must Finish On May 20
  Driving predecessor: Contract award SS+15d
  No links to site release, equipment delivery,
  installation, or testing
  Reported total float: 0 days

The subcontractor has a detailed installation and test schedule, but only the completion milestone was loaded into the master schedule. Which action best improves schedule model integrity and forecast credibility?

• A. Load detailed subcontractor activities, tie them logically, apply the 7-day calendar, and recalculate float.
• B. Extend the contract-award lag until the milestone date looks realistic.
• C. Add a matching finish constraint to the in-house handoff activity.
• D. Keep the milestone and explain the contractual date in the report.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: A schedule audit should favor logic-driven, traceable work over date-forced milestones. Since the subcontractor’s detailed work exists, the master schedule should integrate that work, connect it to the real handoff and execution dependencies, use the correct calendar, and then recalculate float and driving path.

The core issue is schedule model quality. A milestone with a Must Finish On constraint and a single long lag from contract award does not credibly forecast subcontractor execution, especially when the actual work depends on site release, delivery, installation, and testing. Because the subcontractor already has a detailed schedule, best practice is to integrate the relevant detail or interface activities into the master schedule, apply the correct 7-day field calendar, and let logic drive the forecast.

This improves the model because it:

• makes predecessor and successor relationships traceable
• reflects the actual working calendar
• produces meaningful total float and driving-path results
• supports auditability across in-house and subcontractor work

A narrative, a longer lag, or more constraints may make the schedule look cleaner, but they weaken analysis and can distort the reported critical path.

This restores logic-driven forecasting so the reported critical path is based on executable work, not a constrained milestone and lag.

Question 127

Topic: Schedule Planning and Development

A scheduler is developing the detailed schedule for a pharmaceutical packaging-line upgrade. The schedule baseline has not been approved, but the contract requires a “qualified for production” milestone by September 30. Installation, automation, validation, and operations handoff are in separate control accounts, and the draft WBS has no work package for operator training or final production-readiness approval. Company policy requires approved change control for scope added after baseline. What is the BEST action?

• A. Conduct a validation review with SMEs and key stakeholders to confirm each work package’s deliverables, interfaces, and acceptance steps before baselining.
• B. Insert contingency before the September 30 milestone to absorb any missing work.
• C. Collect duration estimates for the existing work packages and continue building logic.
• D. Baseline the current schedule and add any missing tasks during execution as forecast updates.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: The draft WBS already shows likely omissions, so the right move is to validate work package completeness with the people who perform, receive, and approve the work before baselining. That protects schedule quality and avoids unnecessary change control after approval.

The key concept is validating work package completeness before the schedule baseline is approved. When work crosses multiple control accounts, the scheduler should use subject-matter experts and affected stakeholders to confirm that each work package includes all required deliverables, handoffs, approvals, and acceptance activities. In this scenario, missing operator training and production-readiness approval indicate the decomposition is incomplete. Because the contractual milestone is fixed and added scope after baseline requires change control, correcting omissions now is far better than patching the schedule later.

A complete review should confirm:

• required outputs for each work package
• interface handoffs between control accounts
• acceptance and approval activities
• dependencies needed to support the milestone

Better estimates or extra contingency do not fix incomplete scope definition.

This is best because it uses expert and stakeholder input to verify complete work packages before baseline approval makes omissions harder to correct.

Question 128

Topic: Schedule Monitoring and Controlling

A contractor finished a data-center upgrade 18 working days late, and the owner asks for a forensic schedule analysis to assign delay responsibility. The available records are:

Approved baseline: archived
Monthly update files: February and May only
Final schedule file: archived
Actual dates in final file: several replaced by forecast dates
Approved logic-change log: not maintained

Which conclusion is most defensible?

• A. Pause attribution because the records are insufficient for reliable forensic analysis.
• B. Base the conclusion on what-if simulations of the final file.
• C. Base the conclusion on SPI trend from February to May.
• D. Base the conclusion on the final critical path.

Best answer: A

What this tests: Schedule Monitoring and Controlling

Explanation: Forensic schedule analysis depends on contemporaneous evidence, not just a baseline and a final file. Missing update snapshots, overwritten actual dates, and no approved logic-change record mean the scheduler cannot reliably reconstruct the driving path or assign the 18-day delay.

Forensic schedule analysis is used to determine what the schedule showed at the time and which events actually drove delay. That requires enough preserved evidence to trace status over time: contemporaneous update files or narratives with status dates, intact actual start/finish data, and records of approved logic or scope changes. In this scenario, only two update files survive, several actual dates were overwritten by forecasts, and logic revisions were not logged. Any critical path, float, SPI, or milestone analysis would therefore rest on incomplete reconstructed history rather than reliable contemporaneous data. A final schedule can show where the project ended, but it cannot by itself prove responsibility for each delay period. What-if modeling can test assumptions, but it cannot replace missing factual records.

Forensic delay analysis requires contemporaneous status, preserved actuals, and approved change history, and those records are missing or corrupted here.

Question 129

Topic: Schedule Planning and Development

A scheduler is validating a draft predictive schedule before baselining. The project uses a 5-day workweek. Activity Migrate 1,200 user accounts has a finish-to-start predecessor of Environment ready, a finish-to-start successor of User acceptance, is on the current critical path to the contractual Cutover milestone, and has no date constraint. The technical lead proposed a 5-day duration based only on 480 labor hours. Two migration specialists are available at only 50% each, and pilot results ranged from 180 to 300 accounts per day. What is the best action?

• A. Insert lag after Environment ready to cover uncertainty
• B. Keep 5 days and add a Cutover deadline
• C. Reestimate using confirmed staffing and likely migration throughput
• D. Apply a Must Finish On constraint to migration

Best answer: C

What this tests: Schedule Planning and Development

Explanation: A credible duration estimate needs more than total labor hours. Here, limited resource availability and wide productivity variation mean the 5-day estimate is not reliable enough for a critical-path activity until it is reestimated with better input.

The key concept is that duration is not the same as effort. A figure of 480 labor hours does not support a 5-day duration unless the scheduler also knows the actual resource availability and realistic productivity. In this case, the work is on the critical path, the two specialists are only half available, and pilot results show meaningful uncertainty in throughput. That means the duration estimate needs additional input before it can be trusted in the schedule model. The right response is to reestimate using confirmed staffing, expected production rate, and documented assumptions or ranges. Adding lag, deadlines, or hard constraints may make the schedule appear cleaner, but those actions hide estimating uncertainty instead of improving forecast quality.

Duration must be based on effort converted through actual availability and expected productivity, so the estimate needs more input before it is credible.

Question 130

Topic: Schedule Planning and Development

During schedule development for a data center cutover, activity logic and durations have been validated. The scheduler has approved calendars for the night-shift test team, weekend electricians, and vendor specialists, but activities still have no resource assignments, so the draft dates reflect only activity calendars. What should the scheduler do next to define a resource-constrained schedule?

• A. Report the draft finish date as the forecast
• B. Rebaseline the draft dates before resource loading
• C. Fast track critical work before resource assignment
• D. Assign qualified resources to activities and recalculate with resource calendars

Best answer: D

What this tests: Schedule Planning and Development

Explanation: To create a resource-constrained schedule, the scheduler must next assign the actual qualified resources to the activities and apply their calendars. Until that is done, the model shows an unconstrained, logic-only result, so baselining, reporting, or compression decisions are premature.

A resource-constrained schedule is built only after the work is tied to the people or crews who will perform it and their real availability is applied. In this scenario, logic and durations are already credible, but the draft dates still ignore who is actually available and when. The next step is therefore to assign the qualified resources to each activity and recalculate the schedule using those resource calendars. That converts the model from an unconstrained activity sequence into a schedule that reflects real execution capacity. Once that resource-loaded result is credible, the team can evaluate impacts, consider compression if needed, and establish or maintain the proper baseline. Compressing or communicating dates before resource loading risks acting on a schedule that is not yet realistic.

Resource assignments plus resource calendars are needed before the schedule reflects real availability constraints.

Question 131

Topic: Schedule Planning and Development

A vendor-supported rollout has these contractual milestones. The contract treats each listed milestone as a required deadline.

Based on this milestone analysis, which conclusion is best?

• A. The delivery estimates miss required deadlines on two milestones.
• B. The delivery estimates meet the contract because two milestones are early.
• C. The delivery estimates should be rebaselined before checking compliance.
• D. The delivery estimates cannot be assessed until project SPI is calculated.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: Milestone analysis compares each required milestone date with the current forecast. Here, Test environment ready is forecast 4 days late and Go-live is forecast 2 days late, so the current delivery estimates do not meet all required deadlines.

When the question is whether current delivery estimates satisfy stated deadlines, the direct method is milestone analysis: compare each forecast milestone date to its required date. In this table, API spec approved and User training complete are forecast before their deadlines, but Test environment ready is forecast after July 15 and Go-live is forecast after August 31. Because the contract says each listed milestone is a required deadline, even one late forecast means the schedule model does not currently meet the deadline requirement. You do not need SPI or a rebaseline to make that determination, because the supplied milestone dates already show compliance status. The key point is to assess each required milestone individually, not average or offset them.

Comparing each forecast date to its required date shows Test environment ready and Go-live are late.

Question 132

Topic: Schedule Monitoring and Controlling

On the June 14, 2026 status date, a software deployment schedule uses a 5-day workweek. An approved change adds a mandatory 10-workday cybersecurity review between System Test Complete and the contractual milestone Ready for Deployment. The milestone currently has no date constraint and drives go-live. Which documentation action best preserves schedule model integrity and traceability?

• A. Replace the milestone baseline date with the new forecast and note it in the status report.
• B. Apply a start-no-earlier-than constraint to the milestone and leave the logic unchanged.
• C. Insert a 10-workday lag before the milestone to keep the network simpler.
• D. Add the review activity and dependencies, update milestone records, and log the approved impact while retaining the baseline unless rebaselining is separately approved.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: An approved change that adds real work and changes milestone logic should be documented in the schedule model, not hidden with a constraint or lag. The approval and impact should be traceable in the schedule change log, while the existing baseline remains the performance reference unless a separate rebaseline is approved.

When an approved change affects schedule logic or milestones, the best documentation action is the one that keeps the schedule model technically correct and fully traceable. Here, the cybersecurity review is real work on the 5-day calendar, so it should be added as its own activity with explicit dependencies to the predecessor and the contractual milestone. The affected milestone record should also be updated so the new logic and commitment impact are clear. The approved change and its date effect belong in the schedule change log for audit and forensic readiness. The forecast may move after the update, but the baseline should not be replaced unless formal rebaselining is separately approved.

• Add the new review as an explicit activity.
• Link it with the correct logic.
• Update the affected milestone documentation.
• Record approval, rationale, and impact in the change log.

A cleaner-looking network is not better if it hides work or destroys variance history.

This makes the new work and logic explicit, preserves auditability, and avoids overwriting the control baseline without separate rebaseline approval.

Question 133

Topic: Schedule Planning and Development

A contract requires a Mechanical Completion milestone by September 30. The draft schedule uses a Monday-Friday calendar; procurement -r installation -r testing drive that milestone, and the testing crew is available only from September 23. As of the August 1 status date, procurement is 5 working days late and the path to the milestone had only 3 working days total float. Which action is milestone achievability analysis rather than milestone definition?

• A. Apply a Must Finish On September 30 constraint to the milestone.
• B. Add a reporting milestone after procurement for better visibility.
• C. Define a zero-duration milestone using the contract wording.
• D. Review the driving path, calendars, remaining durations, and crew availability.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: Milestone definition states what the checkpoint is; milestone achievability analysis tests whether it can realistically be met. With late procurement, limited float, and crew availability constraints, the scheduler must analyze the driving path and forecast logic, not just label or constrain the milestone.

The core distinction is simple: milestone definition identifies and documents the required checkpoint, while milestone achievability analysis evaluates whether current schedule conditions support reaching it. In this scenario, the contract date is already known, but the schedule now includes a 5-day procurement delay, only 3 days of float, a specific work calendar, and a resource-availability limit for testing. Those facts require analysis of the driving path, remaining durations, calendars, and resource timing to determine whether September 30 is still feasible.

Hard-coding the date with a constraint or adding extra milestones may make the schedule look cleaner, but neither tests forecast realism. Defining the contractual milestone is necessary, but it does not prove the milestone is achievable.

Achievability analysis tests whether the forecast can still meet the milestone using current logic, calendars, status, and resource constraints.

Question 134

Topic: Schedule Monitoring and Controlling

A project is updated on the August 15 data date.

Baseline milestone: August 25
Current forecast milestone: August 28
Activities planned complete by August 15: 20
Activities with actual finish by August 15: 14
Incomplete activities with forecast finish on/before August 15: 4

The sponsor wants an analysis that separates work actually completed from dates that are only forecast or planned. Which analysis method is most appropriate?

• A. Use milestone trend analysis of forecast dates
• B. Run Monte Carlo schedule risk analysis
• C. Review baseline execution index at the data date
• D. Perform total float analysis on near-critical paths

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: Baseline execution index is designed to measure executed progress at the data date. Here, only 14 of the 20 activities planned to be complete actually have finish dates, so the method separates real status from the 4 activities that are only forecast to finish.

To distinguish actual progress from planned or forecast dates, use baseline execution index. BEI asks how many activities that should have been completed by the data date are actually completed, based on recorded actual finish dates. In this case, the project has 14 actual completions out of 20 planned completions, so executed progress is only 70% of what the baseline expected by August 15. The 4 incomplete activities with forecast finishes on or before the data date are still estimates of future completion, not evidence of completed work.

• Actual progress comes from actual start and finish status.
• Planned dates come from the approved baseline.
• Forecast dates come from current remaining-duration expectations.

Methods focused on risk, float, or milestone forecast movement may help later, but they do not answer this specific status-quality question as directly.

BEI compares actual completions with baseline-planned completions by the data date, so forecast dates are not mistaken for real progress.

Question 135

Topic: Stakeholder Communications Management

On a hybrid product rollout, the status date is September 1. The baseline go-live milestone is November 15, the current forecast is November 27, and the slip has worsened from 4 to 8 to 12 workdays over the last three updates. Any recovery plan will require resource commitments from the vendor and operations managers, and the sponsor says the team must not hide current variance. Which schedule analysis approach should the scheduler use next?

• A. Report only SPI and percent complete without logic-based scenarios
• B. Rebaseline go-live first, then discuss recovery scenarios
• C. Run a joint what-if analysis on the driving path
• D. Use milestone trend analysis alone to show the worsening slip

Best answer: C

What this tests: Stakeholder Communications Management

Explanation: The team already knows the milestone is slipping, and recovery will require stakeholder commitments. A joint what-if analysis on the driving path is the best next step because it tests realistic options while keeping the baseline variance visible.

When stakeholder support is needed for schedule recovery, the best analysis is one that is both transparent and collaborative. The worsening milestone trend shows the problem, but it does not tell the vendor and operations managers which recovery actions are feasible or what each action would do to the forecast. A what-if analysis on the driving path uses the current baseline, current status, and forecast to compare realistic scenarios such as resequencing, added resources, or changed handoff timing.

This approach helps because it:

• keeps the existing variance visible rather than replacing it
• focuses discussion on the work that actually drives the finish date
• gives stakeholders evidence to support commitments and trade-offs

Rebaselining first would hide performance variance, and summary metrics alone are not enough to build agreement on a credible recovery plan.

What-if analysis lets stakeholders compare feasible recovery scenarios against the unchanged baseline, building support without masking variance or risk.

Question 136

Topic: Schedule Planning and Development

A hospital construction project has a regulatory occupancy milestone committed for October 15. The sponsor’s stated risk tolerance allows at most a 20% chance of missing any regulatory milestone. A schedule risk analysis produced the following results:

What is the best interpretation?

• A. Outside tolerance because October 15 has only 62% confidence
• B. Within tolerance because the P50 date is before October 15
• C. Within tolerance because the deterministic forecast is before October 15
• D. Outside tolerance only if total float is already negative

Best answer: A

What this tests: Schedule Planning and Development

Explanation: Risk tolerance here is probability-based, so the deciding measure is the chance of meeting October 15. Because the sponsor allows only a 20% miss probability, the milestone needs at least 80% confidence; 62% is below that threshold.

To judge whether a milestone is achievable within stated risk tolerance, compare the required confidence level with the schedule risk analysis result for that specific date. A maximum 20% chance of missing the milestone means the team needs at least 80% confidence of finishing on or before October 15. The analysis shows only 62% confidence, so the milestone is outside tolerance even though the deterministic forecast and the P50 date are earlier than the target.

• Deterministic forecast gives one expected date, not the confidence of meeting it.
• A P50 date reflects about a 50% confidence level.
• A P80 date reflects about an 80% confidence level.

The key point is to match the milestone commitment to the required confidence level, not to the most optimistic-looking date.

A 20% maximum miss probability requires at least 80% confidence of meeting the milestone, and 62% does not satisfy that tolerance.

Question 137

Topic: Schedule Closeout

A facilities project has received final acceptance. The scheduler has already issued the final schedule report comparing baseline, forecast, and actual milestone dates, and all schedule issues are closed. During closeout, the team notes that monthly vendor logic reviews prevented out-of-sequence progress and should be reused on future projects. What should the scheduler do next?

• A. Add the note to the final schedule report and resend it.
• B. Rebaseline the finished schedule to reflect the successful practice.
• C. Capture the practice in lessons learned and update organizational process assets.
• D. Log the note as an open schedule issue for PMO follow-up.

Best answer: C

What this tests: Schedule Closeout

Explanation: The project’s final schedule reporting is already complete, and there is no unresolved schedule issue left to control. A useful insight about a scheduling practice that should help future projects is a lesson learned, so the next step is to record it and update organizational process assets.

In schedule closeout, each artifact has a different purpose. The final schedule report documents how this project performed against its approved baseline. An issue log tracks problems that still need action. A lesson learned captures a reusable insight that can improve future scheduling work.

Here, final acceptance is complete, the final schedule report has already been issued, and all schedule issues are closed. The observation about monthly vendor logic reviews is not new status information and not an unresolved problem; it is a practice that improved schedule execution and should be available for future projects. Therefore, the right next step is to record it in lessons learned and update organizational process assets.

The key distinction is that lessons learned preserve reusable scheduling knowledge, while reports summarize results and issues require ongoing action.

Because this is a reusable closeout insight rather than current performance data or an open problem, it belongs in lessons learned and organizational process assets.

Question 138

Topic: Schedule Strategy

On a predictive project with a 5-day work calendar, the data date is August 1. A 45-day critical-path activity, Integrate and validate control system, currently drives regulatory review, operator training, and site acceptance, which must support a contractual turnover milestone on October 31. After four weekly updates, the owner has reported 50%, 60%, 60%, and 75% complete, but the team still cannot forecast the three handoffs separately. Which change would best improve the schedule model for progress measurement and control?

• A. Add a finish-no-earlier-than constraint on the activity to protect October 31.
• B. Keep one activity and require daily percent-complete updates from the owner.
• C. Decompose the work into measurable handoff activities with interim milestones and logic to each successor.
• D. Split the work into many one-day engineer assignments linked only to the final turnover milestone.

Best answer: C

What this tests: Schedule Strategy

Explanation: The activity is too coarse to support credible forecasting because three downstream handoffs depend on it but cannot be statused separately. Breaking it into discrete, measurable deliverables with logic and interim milestones improves both progress measurement and schedule control.

Activity granularity should be detailed enough to support objective status and meaningful control, but not so detailed that the model becomes noisy and loses useful logic. Here, one 45-day critical-path activity is too coarse because it hides the internal handoffs needed for regulatory review, training, and site acceptance. That forces the team to rely on subjective percent-complete updates instead of actual finishes and remaining-duration data for each deliverable.

Decomposing the work into measurable handoff activities improves the model because it:

• creates traceable logic to each successor
• allows separate forecasting of each handoff
• supports more credible status based on real progress points
• shows where slippage is actually affecting the critical path

More frequent reporting or added constraints may make the schedule look cleaner, but they do not fix the underlying model-quality problem.

This adds the right level of detail for objective status, separate handoff forecasts, and logic-based control of the critical path.

Question 139

Topic: Schedule Strategy

A scheduler is assigned to a newly awarded hybrid system rollout. The PMO has organizational process assets from similar rollouts: an integrated schedule template, approved team calendars, a 10-workday variance escalation threshold, and standard weekly and monthly reporting cadences. Before the detailed schedule model is developed, the sponsor asks for the project’s schedule approach. What should the scheduler do next?

• A. Issue the standard status report to confirm stakeholder expectations
• B. Build activity logic now using the default corporate calendar
• C. Baseline the proposal dates now and rebaseline later if needed
• D. Tailor the relevant organizational assets into the schedule approach first

Best answer: D

What this tests: Schedule Strategy

Explanation: Organizational process assets shape the schedule approach before detailed modeling begins. The scheduler should first tailor the organization’s standard template, calendars, thresholds, and reporting cadence to the project’s characteristics, then use that approach to develop the detailed schedule.

Organizational process assets such as schedule templates, calendars, variance thresholds, and reporting cadences are inputs to schedule strategy. In this situation, the project has not yet established how those standard assets fit the hybrid rollout, so the next step is to review and tailor them before building the detailed schedule model. That creates a credible basis for later logic development, baseline approval, variance measurement, and stakeholder reporting.

• Use the standard template as a starting point, not as an automatic final approach.
• Confirm which organizational calendars apply to each workstream and shared resource group.
• Adopt or tailor thresholds and reporting cadence to match this project’s governance needs.

Building logic, sending reports, or baselining dates before this tailoring would act on assumptions instead of an approved schedule approach.

Relevant organizational process assets should be reviewed and tailored first because they define how the schedule will be built, measured, and reported for this project.

Question 140

Topic: Schedule Planning and Development

A facilities project is building a logic-driven schedule on a 5-day workweek calendar with no date constraints. Temporary fire watch must remain active until permanent alarm monitoring begins. To keep the handoff traceable through logic rather than a manual finish constraint, which relationship should link Begin permanent alarm monitoring to Maintain temporary fire watch?

• A. Start-to-finish
• B. Start-to-start
• C. Finish-to-finish
• D. Finish-to-start

Best answer: A

What this tests: Schedule Planning and Development

Explanation: Use start-to-finish when one activity must stay in place until another activity begins. Here, temporary fire watch can end only after permanent monitoring starts. That keeps the handoff logic-driven and more traceable than using a manual finish constraint.

This situation is a start-to-finish relationship because the finish of Maintain temporary fire watch depends on the start of Begin permanent alarm monitoring. That logic matches the real operational handoff and preserves schedule model integrity by letting dependency logic, not a forced date, drive the forecast.

• Finish-to-start: successor start depends on predecessor finish.
• Start-to-start: successor start depends on predecessor start.
• Finish-to-finish: successor finish depends on predecessor finish.
• Start-to-finish: successor finish depends on predecessor start.

The closest distractor is finish-to-finish, but that would require permanent monitoring to finish before the fire watch ends, which is later than the stated need.

The temporary fire watch can finish only after permanent monitoring starts, which is a start-to-finish dependency.

Question 141

Topic: Schedule Planning and Development

Four integrated schedules are seeking baseline approval. In which case is approval clearly premature?

• A. Near-critical work has 3 days float and is marked for close monitoring.
• B. Risk response activities and contingency are included from the documented schedule risk review.
• C. Specialist resource calendars are loaded and functional managers confirmed assignments.
• D. The contractual finish date is held by a mandatory constraint while vendor interface links are still unresolved.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: Baseline approval requires a credible schedule model, not just an acceptable finish date. If a hard constraint is forcing the contractual completion while interface logic is still unresolved, the baseline is premature because the dates are not yet supported by valid dependencies.

A schedule baseline should be approved only after the model is logically sound, aligned to contract commitments, resourced realistically, and informed by schedule risk review. Here, the key warning sign is the use of a mandatory finish constraint to hold the contractual completion date while vendor interface links are still unknown. That masks the real driving path instead of modeling it. A baseline built this way is not a reliable control reference, because later variance could reflect missing logic rather than actual execution performance. By contrast, near-critical paths can be monitored, confirmed resource calendars strengthen schedule realism, and documented risk responses improve readiness for approval. The main distinction is constraint versus logic: forcing a date is not the same as demonstrating a valid path to that date.

A forced contractual date with unresolved interface logic means the baseline is not yet supported by a credible schedule model.

Question 142

Topic: Schedule Planning and Development

A project team is preparing the schedule baseline for a data-center move. Management requires a completion date with at least 80% confidence before approval. The scheduler’s risk analysis shows 84% confidence, but several driving-path activities still have single-point durations, one external utility-cutover dependency is missing from the logic, and identified permit risks have not been mapped to activities. What should the scheduler do next?

• A. Commit to the 84% date and document the gaps later.
• B. Complete the missing inputs and rerun the risk analysis.
• C. Crash driving-path activities immediately to increase confidence.
• D. Shorten non-driving setup tasks that still have float.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: A confidence percentage is only reliable when the schedule model and risk-analysis inputs are complete enough to represent the true drivers of completion. Missing driving-path uncertainty, incomplete dependency logic, and unmapped risks mean the 84% result is not strong enough to support a schedule confidence conclusion.

Schedule risk analysis supports a confidence conclusion only when the underlying inputs are decision-ready. In this scenario, the reported 84% confidence is not trustworthy because key inputs are incomplete in three ways: driving-path activities still use single-point durations, an external dependency is missing from the logic, and identified permit risks are not tied to affected activities. Any of those gaps can materially change the finish-date distribution.

• Validate and complete the schedule logic.
• Add appropriate uncertainty ranges for the driving work.
• Map relevant risks to the affected activities and rerun the analysis.

The key takeaway is that you should not commit, compress, or reframe the date until the analysis reflects the real schedule risk drivers.

A schedule confidence conclusion is credible only after the logic, uncertainty ranges, and risk mappings reflect the actual finish-date drivers.

Question 143

Topic: Schedule Monitoring and Controlling

As of the July 15 status date, a project has a contractual commissioning milestone protected by 10 workdays of approved schedule contingency. Six workdays of that contingency have already been consumed. The remaining open schedule risks, after current mitigations, have a combined estimated impact of 7 workdays. The schedule management plan says to escalate when remaining contingency is less than remaining exposure. Which analysis and interpretation are most appropriate?

• A. Use total float analysis; available float means no reserve decision is needed.
• B. Use critical path analysis; wait unless the milestone forecast actually slips.
• C. Use reserve analysis; contingency is insufficient and should be escalated.
• D. Use SPI trend analysis; current performance shows the reserve is still adequate.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: Reserve analysis is used to test whether the remaining time contingency is enough to absorb residual schedule risk. Here, only 4 workdays remain against 7 workdays of remaining exposure, so the project has crossed its escalation threshold and needs a control decision.

Reserve analysis compares remaining schedule contingency with the residual impact of open schedule risks so the team can decide whether the current schedule buffer is still sufficient. In this case, the project has 4 workdays of contingency left and 7 workdays of remaining quantified exposure, so the reserve no longer covers the remaining risk. Because the schedule management plan requires escalation when contingency is less than exposure, the scheduler should raise a control action now, such as added mitigation, recovery planning, or a formal change request if approved dates or reserves must change.

• Approved contingency: 10 workdays
• Contingency already consumed: 6 workdays
• Remaining contingency: 4 workdays
• Remaining exposure: 7 workdays

Critical path, float, and SPI can support status analysis, but they do not answer whether the remaining reserve is enough for known schedule risk.

Reserve analysis compares the 4 remaining workdays of contingency with 7 workdays of residual exposure, showing the buffer is no longer sufficient.

Question 144

Topic: Schedule Monitoring and Controlling

During a monthly schedule audit, the auditor finds that the scheduler added Must Finish On constraints to four incomplete activities so the customer acceptance milestone still matches its baseline date. The schedule management plan requires forecasts to be logic-driven and permits hard constraints only for documented external dates with approval. No approved change request exists. What is the best action?

• A. Keep the constraints temporarily, choose recovery later, and use the constrained dates in status reporting.
• B. Update the baseline milestone date to the constrained forecast so reports match the current commitment.
• C. Replace the hard constraints with added lag so the milestone still finishes on the planned date.
• D. Remove the unjustified constraints, recalculate the logic-driven forecast, and raise change control if the baseline must change.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The audit finding shows the forecast was being forced to match the baseline, which violates schedule model integrity. The correct response is to restore a logic-driven forecast first, then use formal change control only if the approved baseline must change.

In schedule control, this is primarily a model-integrity issue. Forecast dates should come from network logic, status, calendars, and remaining duration, not from manually imposed dates added to preserve the appearance of meeting the baseline. Because the organization allows hard constraints only for documented external dates with approval, the added constraints must be removed or formally validated first. After recalculating the schedule, the team can see the true milestone impact, evaluate recovery options, and submit a change request only if the approved baseline itself needs revision. The key distinction is that correcting a distorted forecast is not the same as changing the baseline.

Organizational procedure requires a logic-driven forecast and approved change control for any baseline change, so unjustified hard constraints must be removed.

Question 145

Topic: Schedule Monitoring and Controlling

At the July 10 data date, an identified supplier risk has delayed a critical-path fabrication activity by 6 working days. The schedule management plan includes 8 working days of schedule contingency for this delivery chain and requires reserve analysis when a triggered risk affects a milestone. What should the scheduler do next?

• A. Fast-track successor work immediately to recover the six-day slip.
• B. Issue a variance report and wait for sponsor direction.
• C. Analyze schedule reserve against forecast impact before choosing control action.
• D. Request a rebaseline to reflect the new expected milestone date.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: When a known risk occurs, the next control step is to assess available schedule contingency against the updated forecast. That reserve analysis shows whether the delay can be absorbed or whether corrective action or formal change control is needed.

Reserve analysis supports schedule control by connecting a realized risk event to the amount of schedule contingency still available and the resulting forecast. In this case, the delay is already known, the activity is on the critical path, and the plan explicitly requires reserve analysis, so the scheduler should first test whether the 6-day impact can be covered by the 8-day contingency and whether any residual exposure remains.

• Confirm the delay is reflected in current status and forecast.
• Compare the forecast impact with available schedule reserve.
• Then decide whether reserve use is sufficient or whether recovery action or change control is needed.

This is better than compressing work or rebaselining first, because those actions should follow a credible reserve-based impact assessment.

Reserve analysis should come first because it shows whether approved contingency can absorb the delay before recovery actions or baseline changes are proposed.

Question 146

Topic: Schedule Monitoring and Controlling

Status date is August 8. The next 2 weeks already reflect each group’s working calendar. The scheduler summarizes remaining effort by RBS resource group:

Only the controls-engineering activities are on the driving path to the commissioning milestone. Which report statement is most accurate?

• A. Flag field electricians because they have the larger total workload.
• B. Report no issue because combined availability exceeds combined demand.
• C. Use SPI only; resource calendars do not affect forecast dates.
• D. Flag controls engineers as overallocated by 40 h on driving work.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: Resource utilization should be reported by resource group against each group’s calendar availability, not in aggregate. Here, controls engineers have 200 h of demand and only 160 h available, so the report should highlight a 40 h shortage on driving-path work.

For resource utilization and availability updates, the key analysis is a time-phased comparison of remaining demand versus calendar-based capacity for each RBS resource group. In this case, controls engineers are overallocated by 40 h (200 h demand minus 160 h availability) , and their work is on the driving path to the commissioning milestone. That makes this a meaningful schedule concern to report.

A combined total across groups is misleading because surplus electrician capacity cannot automatically solve a shortage in a different skill group. Likewise, SPI or milestone variance may show schedule performance, but they do not explain that the immediate constraint is resource availability tied to a specific calendar and resource group. The best report identifies the specific overallocated group and its schedule impact.

This correctly compares demand with calendar availability by resource group and identifies the 40 h shortfall affecting driving-path work.

Question 147

Topic: Schedule Closeout

A hybrid system deployment finishes 1 week late after an approved interface change on the driving path. Several non-driving training tasks also slipped, and a vendor has hinted at a delay claim. During closeout, which action best supports schedule archive and forensic readiness?

• A. Keep the sponsor’s approval email and omit the formal change log.
• B. Archive the final schedule model, schedule management plan, status reports, and change log.
• C. Rebaseline to the final forecast before archiving the schedule files.
• D. Archive only the non-driving training-task records that slipped last.

Best answer: B

What this tests: Schedule Closeout

Explanation: Closeout should preserve the full scheduling evidence trail, not just a cleaned-up end state. The final schedule model, schedule management plan, status reports, and change log show how the schedule was managed, updated, and changed over time.

In schedule closeout, the goal is to retain enough evidence to reconstruct what happened and why. Here, the project finished late, an approved driving-path change occurred, and a vendor may dispute delay responsibility. That means the archive must include the final schedule model, the schedule management plan, status reports, and the change log. Together, these artifacts show the approved control approach, periodic status and forecast movement, and the history of requested and approved schedule changes. They support lessons learned, final reporting, and forensic review if a claim arises. Replacing the baseline with the forecast, relying on informal approvals, or saving only a narrow subset of records weakens the control record. The key takeaway is to archive the complete schedule-management evidence, not a simplified summary.

These artifacts preserve the full schedule-control history needed to explain performance, approved changes, and delay attribution.

Question 148

Topic: Schedule Planning and Development

A scheduler is preparing the first detailed schedule for a facility upgrade. The team has an approved level-2 WBS, a draft OBS showing accountable departments, and an RBS (resource breakdown structure) listing labor categories. Management wants a logic-driven activity schedule, but no control accounts or work packages have been defined. What should the scheduler do next?

• A. Publish a preliminary milestone baseline and refine the structure later.
• B. Use the RBS to resource-load major deliverables before decomposition.
• C. Use the OBS to assign departments and let them enter activities directly.
• D. Decompose the WBS into control accounts and work packages before defining activities.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: The next step is to use the WBS to decompose approved scope into control accounts and work packages. That creates the schedule-ready structure needed to define activities with clear traceability; the OBS and RBS support accountability and resources, but they do not replace scope decomposition.

In schedule development, the WBS is the scope-based framework from which schedulable work is derived. When the WBS is still too high level, the scheduler should first establish appropriate control accounts as management control points and decompose the work into work packages. Those work packages are the level from which detailed activities can be identified, sequenced, and later measured.

The OBS shows who is accountable, and the RBS shows resource categories, but neither one defines the scope decomposition needed for a credible schedule model. Building activities directly from departments or resource types can break traceability to scope. Baselines and reports come after the schedule structure is credible, not before.

WBS-based decomposition creates schedule-ready work packages and management control points, while the OBS and RBS do not replace scope decomposition.

Question 149

Topic: Schedule Strategy

An approved baseline is under configuration control for a plant shutdown project. In the weekly update, activity owners send actual starts, remaining durations, and one manually revised finish date for a critical-path activity. The project manager wants a new completion date for today’s steering report. What should the scheduler do next to protect traceability between status, forecast, and the approved baseline?

• A. Replace baseline dates with the revised expected dates for this report.
• B. Send the steering report from the submitted dates and fix discrepancies later.
• C. Run the schedule now and begin recovery planning before checking update quality.
• D. Validate status and logic in the update copy, preserve the approved baseline, then recalculate the forecast.

Best answer: D

What this tests: Schedule Strategy

Explanation: Before calculating or reporting a new finish date, the scheduler should validate the update inputs and leave the approved baseline unchanged. That keeps current status, forecast results, and baseline reference dates traceable and defensible.

The key data-control principle is to keep status collection, forecast calculation, and baseline management distinct. In this scenario, the team submitted mixed update data, including a manually revised finish date on critical-path work, so the scheduler must first confirm the status inputs and logic in the controlled update copy. Once the update is credible, the schedule can be recalculated to produce a forecast and compared against the approved baseline. This preserves traceability from actual status data to forecast dates to baseline variance. Reporting first or changing baseline dates would weaken control and make later variance analysis unreliable.

It separates status validation from forecasting and keeps the approved baseline intact for variance analysis and change control.

Question 150

Topic: Stakeholder Communications Management

On May 20, a data-center migration project has a contract go-live milestone baselined for June 30. After the latest status update, the driving path forecasts go-live on July 14. The schedule management plan requires escalation when a key milestone slips more than 10 calendar days, and a change request has been submitted; only the change control board can approve baseline changes. The steering committee will review the weekly dashboard tomorrow. Which schedule analysis/reporting approach best provides schedule visibility without implying approval of the slip?

• A. Show a milestone variance analysis with June 30 baseline, July 14 forecast, and approval pending.
• B. Report only the SPI trend and defer the milestone date until the board decides.
• C. Replace the dashboard baseline date with July 14 because the committee will review it.
• D. Publish the best-case what-if recovery date as the current commitment.

Best answer: A

What this tests: Stakeholder Communications Management

Explanation: The key need is stakeholder awareness, not silent approval of a new commitment. A milestone variance analysis makes the 14-day slip visible against the June 30 baseline and supports escalation, while keeping the baseline unchanged until the change control board approves any revision.

In schedule communications, visibility means showing the approved baseline beside the current forecast so stakeholders can see variance and act on it. It does not mean the forecast automatically becomes the new commitment. Here, the forecast slip is 14 calendar days, which exceeds the 10-day escalation threshold, so the scheduler should communicate that variance now and note that baseline approval is still pending. A milestone variance analysis is the best fit because the issue is a key contractual milestone and stakeholders need a clear baseline-versus-forecast comparison. Replacing the baseline date, hiding the slipped milestone behind a summary metric, or presenting an analytical scenario as the commitment would weaken schedule control. Good visibility reports the impact; formal approval changes the baseline.

This shows the approved baseline and current forecast side by side, making the slip visible while preserving formal change approval.

Questions 151-170

Question 151

Topic: Stakeholder Communications Management

As of May 15, a vendor interface delivery is 10 working days late and is driving the critical path. The approved baseline still shows system go-live on June 30, but the current forecast is July 8; user training has 12 days of float. The sponsor asks the scheduler to keep the dashboard green until a recovery plan is approved. What should the scheduler do?

• A. Wait to report the slip until the team confirms recovery and can present one date.
• B. Crash user training first so early finishes improve the dashboard before stakeholders see the delay.
• C. Issue a status report showing the June 30 baseline, July 8 forecast, and commitment risk; use change control for any rebaseline.
• D. Replace the baseline go-live date with July 8 so the dashboard reflects the latest plan.

Best answer: C

What this tests: Stakeholder Communications Management

Explanation: Useful schedule visibility requires showing the approved baseline, the current forecast, and the threatened commitment together. The scheduler should communicate the slip now and preserve the baseline unless a formal rebaseline is approved through change control.

When a forecasted delay affects a driving-path activity and threatens a committed milestone, the scheduler should make the impact visible rather than cosmetically on time. The approved baseline remains the control reference for measuring variance, while July 8 is the current forecast based on status. Stakeholders need both dates to understand current performance and make informed recovery or approval decisions.

• Show current status against the approved baseline.
• Communicate the revised forecast and the affected commitment.
• Use formal change control before any rebaseline.

Updating the forecast transparently is appropriate; changing or hiding the baseline is not.

This preserves baseline integrity while giving stakeholders immediate visibility of the variance, forecast, and threatened commitment.

Question 152

Topic: Schedule Monitoring and Controlling

As of the data date September 16, a contractor still reports the contractual milestone Factory acceptance complete on September 25, which is 8 workdays away on the project calendar.

Activity                  Logic                  Status
Install control panels    --                     Actual finish Sep 13
Wire and test panels      FS after Install       In progress; 7 workdays remaining
Client witness test       FS after Wire          Not started; 3 workdays duration
Milestone: Factory acceptance complete           FS after Client witness test
Calendar: 5-day workweek; remaining duration counts from the next workday; no leads/lags or date constraints; total float on this path = 0 days

What is the best interpretation of the reported September 25 milestone date?

• A. It is credible unless the project SPI falls below 1.00.
• B. It is not credible because the driving path needs 10 workdays and only 8 remain.
• C. It is credible because the current activity already started.
• D. It cannot be judged until the schedule baseline is revised.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: The milestone date is not credible because the only logic path to that milestone has 10 workdays of remaining work, while only 8 workdays remain. With zero float and no constraints or alternate logic relief, the forecast cannot reasonably stay on September 25.

This is a schedule logic credibility check using the driving path. The milestone depends on two remaining finish-to-start activities with no leads, lags, or date constraints, and the path has zero total float.

• Remaining work on the path = 7 + 3 = 10 workdays
• Available time to the milestone = 8 workdays
• Since 10 > 8, the reported milestone date is not logic-feasible

A credible forecast must align with current status, remaining duration, and predecessor logic. An unchanged baseline date or a project-level SPI does not make a specific milestone forecast believable when the driving path itself cannot fit in the available time. For date credibility, logic and remaining duration on the driving path are the deciding evidence.

Zero float and 10 workdays of logic-driven remaining work make an 8-workday milestone forecast impossible without recovery changes.

Question 153

Topic: Schedule Strategy

A facilities project is buying a custom chiller under a fixed-date contract. The WBS and cost baseline use procurement, installation, and commissioning work packages; the quality plan requires a factory acceptance test before shipment; the resource plan shows the commissioning engineer available starting September 10; the risk register includes an approved air-freight response if customs delay triggers; and the communication plan requires weekly forecast reporting on any threat to the September 30 site-acceptance milestone. Which scheduling approach best integrates these requirements?

• A. Baseline high-level dates now and add procurement and risk activities only after a delay is reported.
• B. Keep only the September 30 acceptance milestone in the schedule and track vendor details elsewhere.
• C. Impose a mandatory finish on September 30 and let the quality and resource plans govern the intermediate dates.
• D. Model the work packages as discrete activities with logic, resource calendars, the contract milestone, a triggered risk-response path, and weekly forecast reporting.

Best answer: D

What this tests: Schedule Strategy

Explanation: The best choice builds one integrated, logic-driven schedule model from the work packages and contract requirements. It includes the quality gate, resource availability, risk response, and reporting needs so the forecast for the September 30 milestone is credible and controllable.

Schedule integration means the schedule should represent the real work and obligations that drive delivery, not just a few target dates. In this case, the schedule needs activities for the scope-based work packages that also support cost tracking, the factory acceptance test required by the quality plan, procurement and shipment steps, the commissioning resource calendar, the contractual site-acceptance milestone, and the approved response if the customs-delay risk triggers. That allows the team to calculate a reliable forecast and communicate milestone threats through planned reporting.

A hard date constraint or separate offline tracking may make reports look simple, but it weakens schedule control because the true driving relationships are no longer visible. The key distinction is a logic-based integrated schedule model versus isolated dates or manual constraints.

It creates a logic-driven schedule model aligned to scope and cost work packages while integrating contract, quality, resource, risk, and reporting requirements.

Question 154

Topic: Schedule Closeout

A rail signaling project closed 18 workdays late. Monthly status reports showed SPI falling from 1.00 to 0.87, and five approved date changes affected contract milestones. During closeout, the PMO wants the archive to support later critical-path reconstruction and variance-trend analysis if a claim arises. Which archive set should be retained?

• A. Final milestone report, lessons learned log, meeting minutes, and acceptance form
• B. Baseline schedule printout, vendor invoices, timesheets, and procurement register
• C. Final schedule PDF, risk register, issue log, and executive dashboard
• D. Final schedule model, schedule management plan, status reports, and schedule change log

Best answer: D

What this tests: Schedule Closeout

Explanation: For closeout and forensic readiness, the archive must support reconstruction of schedule logic, trend performance, and approved changes. The final schedule model, schedule management plan, status reports, and change log together provide that full evidence trail.

Archive decisions in schedule closeout should match the kind of later analysis the organization may need. Here, the PMO wants to reconstruct the critical path, review worsening SPI trends, and trace five approved milestone changes. That requires the final schedule model because it retains logic, calendars, constraints, and driving relationships that a PDF or milestone summary cannot show. It also requires the schedule management plan to explain how updates and controls were supposed to work, status reports to preserve time-phased variance and forecast evidence, and the schedule change log to show which date changes were requested and approved.

• The final model supports path and float reconstruction.
• Status reports preserve the trend history.
• The change log ties date movement to approved changes.
• The management plan explains the schedule-control rules.

Summary documents help, but they do not replace the underlying schedule evidence.

This set preserves the logic, control rules, historical status evidence, and approved date-change history needed for later schedule analysis.

Question 155

Topic: Schedule Planning and Development

While developing the schedule model before baseline approval for a warehouse project, Rack load testing may start only 3 days after Apply floor coating finishes because the coating must cure. The Ready for occupancy milestone is contractually committed, and the schedule management plan says physical waiting time must be modeled in logic rather than with manual date constraints. What is the best scheduling action?

• A. Model a finish-to-start link with a 3-day lag.
• B. Add a start-no-earlier-than constraint 3 days later.
• C. Extend the load-testing duration by 3 days.
• D. Model a finish-to-start link with a 3-day lead.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: The key fact is that load testing can begin only after floor coating finishes and a 3-day wait passes. That is a finish-to-start dependency with positive lag, which keeps the curing delay visible in the schedule logic and supports a credible forecast for the contractual milestone.

Leads and lags adjust the timing of a logical relationship; they do not replace the relationship type. Here, the successor can start only 3 days after the predecessor finishes, so the correct interpretation is finish-to-start + 3 days lag. A lead would pull the successor earlier, which violates the curing requirement. A manual date constraint would force a date without preserving the real dependency, and adding 3 days to the successor duration would misstate the actual work content of load testing. The best practice is to represent the waiting period directly in schedule logic so downstream dates and milestone forecasts remain trustworthy.

A required waiting period after the predecessor finishes is modeled as a finish-to-start relationship with positive lag.

Question 156

Topic: Schedule Planning and Development

You are developing the schedule model for a system rollout. Integration testing has a finish-to-start dependency after build completion and must finish before a contract demo milestone. The baseline is not yet approved. Estimating notes say the work will take 5 days with two testers, 8 days with one tester, and a separate 30% risk of defect rework adding 2 days; only one tester is available in the planned window. What is the BEST scheduling action?

• A. Use 8 days and document the one-tester basis.
• B. Use 10 days to absorb possible rework.
• C. Use 6.5 days as a compromise estimate.
• D. Use 5 days and add a finish-no-later-than constraint.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: Use the duration estimate that matches the planned execution conditions. Because only one tester is available, 8 days is the supported activity duration, while the possible rework remains a separate schedule risk instead of being built into the base estimate.

In schedule model development, the best duration estimate is the one that aligns with the actual planned resource assumption. Here, the estimating information is explicit: 5 days requires two testers, but only one tester is available, so the supported duration is 8 days. The possible 2-day rework is uncertain, so it should be treated as schedule risk information, not automatically added to the deterministic activity duration.

Using the 5-day estimate would ignore the stated resource limit, and adding a date constraint would mask the real schedule effect instead of modeling it correctly. A compromise average is also weak because it is not tied to any actual execution scenario. Good schedule development uses the provided estimating basis, resource reality, and logic relationships to build a credible model before baseline approval.

It uses the estimate supported by actual resource availability and keeps uncertain rework separate from the base duration.

Question 157

Topic: Schedule Monitoring and Controlling

A project is forecast to finish 15 working days late after an approved scope addition. The remaining critical path is vendor validation, regulatory inspection, and deployment, all in mandatory finish-to-start order. The vendor confirms extra staff will not reduce the 10-day validation duration, and a training-package activity has 12 days of total float. Which action is MOST appropriate to optimize the schedule?

• A. Add more vendor resources to shorten validation.
• B. Review scope with the sponsor for a phased delivery through change control.
• C. Overlap regulatory inspection and deployment.
• D. Move the training-package activity earlier to recover the milestone.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: Scope review is appropriate when the late forecast is driven by critical-path work that cannot be shortened credibly or overlapped safely. Here, crashing is ineffective, fast tracking would violate mandatory logic, and resequencing a float-rich activity will not improve the finish date.

Schedule optimization should focus on the driving path, not on any activity that happens to be available for adjustment. In this scenario, the forecast slip comes from remaining critical-path work. Crashing is not justified because the vendor has already confirmed that additional staff will not reduce the validation duration. Fast tracking is also inappropriate because the remaining critical-path activities have mandatory finish-to-start logic, so overlapping them would create an unsafe or invalid sequence. Resequencing the training-package activity does not help because it has 12 days of total float and is not driving project completion. When credible compression options on the driving path are exhausted, the scheduler should review scope or delivery content with the sponsor and use formal change control to evaluate a phased delivery or other approved scope adjustment. Moving non-driving work may change appearance, but it will not recover the milestone.

When critical-path work cannot be crashed or fast tracked safely and only non-driving work can move, scope review through formal change control is the sound recovery option.

Question 158

Topic: Schedule Strategy

A facilities project has an approved schedule baseline and a contract milestone to energize the site by September 30. On the current status date, a late switchgear delivery has pushed the driving path forecast 10 working days beyond that milestone. The schedule management plan says baseline dates may change only after change control approval, but the weekly stakeholder report is due today. What is the best action?

• A. Wait to publish status until rebaseline is decided
• B. Replace affected baseline dates with the forecast dates
• C. Constrain the milestone date until change approval
• D. Status the schedule, report the variance, and raise a change request

Best answer: D

What this tests: Schedule Strategy

Explanation: An approved baseline stays in force until a formal change is approved. The scheduler should update status and forecast now, show the slippage against the existing baseline, and route any requested rebaseline through change control.

The key distinction is between a routine status update and a configuration-controlled baseline change. Statusing the schedule means entering actual progress and remaining work at the current data date so the forecast reflects reality. The baseline, however, is the approved control reference and cannot be overwritten just because the forecast moved.

Here, the delay has already affected the driving path, the contractual milestone is now forecast late, and stakeholders need a report today. The scheduler should therefore update the schedule, communicate the variance against the current baseline, and initiate or escalate a change request if a rebaseline or other approved action is needed. Hiding the variance or forcing dates would damage the schedule model and weaken decision quality.

Routine status updates should show current forecast variance, while any baseline change must wait for formal approval.

Question 159

Topic: Schedule Monitoring and Controlling

A construction project has an approved schedule baseline and a contractual turnover milestone in 18 working days. At the Wednesday data date, three driving-path activity owners submitted the weekly status template with only percent complete, and a site inspection shows one of those activities started two days later than planned. The schedule management plan requires weekly updates to include actual dates and remaining duration before the client forecast is issued on Thursday. What should the scheduler do next?

• A. Revise the late activity date from inspection and report it.
• B. Use percent complete alone to forecast and send the report.
• C. Validate actual dates and remaining duration with owners, then update and report.
• D. Wait for next week’s cycle and keep baseline dates in this report.

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The best action is to validate the missing and conflicting status data with the activity owners before updating the schedule. Because the weekly procedure requires actual dates and remaining duration, and the affected work is on the driving path to a contractual milestone, the forecast must be based on reconciled status, not percent complete alone.

High-quality schedule control starts with collecting status at the defined interval and in the required format before recalculating the forecast. Here, the weekly update process requires actual dates and remaining duration from activity owners, and an inspection has already exposed a conflict in reported progress on driving-path work tied to a near-term contractual milestone. The scheduler should immediately reconcile the discrepancy with the relevant owners, confirm the real start dates and remaining work, and then update the schedule model and issue the client forecast. That preserves both data credibility and reporting timeliness. A faster update based only on percent complete or a manually forced date would weaken the forecast and the integrity of the schedule model.

Defined status procedures require reconciled actual dates and remaining duration before issuing a credible forecast.

Question 160

Topic: Schedule Monitoring and Controlling

At this week’s status date, a critical-path cable installation activity is forecast 8 workdays late. The field supervisor says it is “about 80% complete,” but daily inspection logs show only half the locations installed, and electricians’ timesheets show one of the two planned crews was reassigned last week. The downstream training activity has 10 days of float. The schedule management plan requires standard timesheets, inspection reports, and the weekly resource review before forecast changes; overtime needs approval. What should the scheduler do next?

• A. Start unapproved overtime on all site activities and update later.
• B. Validate timesheets and inspection data, confirm crew availability, then update remaining duration and reforecast the driving work.
• C. Align the baseline finish date with the new late forecast.
• D. Fast track the downstream training activity to recover the milestone date.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: The best action is to collect and reconcile objective resource information before deciding on recovery. Because the percent-complete claim conflicts with inspection logs and timesheets on a critical-path activity, the scheduler should validate actual utilization and availability, then update remaining duration and reforecast.

This is a schedule control problem driven by unreliable resource status data. When a supervisor’s estimate conflicts with inspection evidence and timesheet usage, the scheduler should first collect and reconcile resource updates through the project’s standard procedures. That means confirming actual work accomplished, verifying whether the crew reassignment affects ongoing availability, and then updating remaining duration and the forecast for the driving path.

• Use objective sources already defined in the schedule management plan.
• Confirm current and near-term crew availability before selecting recovery action.
• Reforecast only after the status data are credible.

Changing non-driving work, hiding the variance by shifting the baseline, or applying overtime without approval weakens schedule control instead of improving it.

This uses the required resource-update sources to establish credible status before changing the forecast on the driving path.

Question 161

Topic: Schedule Planning and Development

You are preparing the initial schedule baseline for a hospital system upgrade. Baseline approval is tomorrow, and a 15-day regulatory interface test activity is on the driving path to a contractual go-live milestone. The duration was entered by the scheduler, but its assumptions are not documented, no historical data from similar deployments were used, and the test lead has not reviewed it. What is the BEST action?

• A. Keep the duration and add schedule reserve before go-live.
• B. Baseline now and revise the activity in the first update.
• C. Replace it with an average from other testing tasks.
• D. Delay baseline approval until the estimate is validated and documented.

Best answer: D

What this tests: Schedule Planning and Development

Explanation: The estimate is weak because it lacks three basic quality checks: documented assumptions, historical support, and SME validation. Since the activity drives a contractual milestone and the baseline is not yet approved, the best action is to strengthen the estimate before baselining it.

Estimate quality depends on a credible basis of estimate. For a critical or driving-path activity, that means the duration should be supported by clear assumptions, relevant historical information, and review by the responsible subject-matter expert. In this scenario, none of those elements is present, yet the activity affects a contractual go-live milestone and the baseline has not been approved yet.

The best scheduling action is to pause baseline approval long enough to validate the duration, document its assumptions, and reference comparable prior work. That protects schedule model integrity and makes the baseline a reliable control reference. Adding reserve, averaging other tasks, or planning to fix the estimate after baseline approval only masks uncertainty instead of improving estimate quality.

The key takeaway is that weak estimate basis should be corrected before baselining, not hidden in later control actions.

A driving-path duration tied to a contractual milestone should not enter the baseline without documented assumptions, relevant history, and SME validation.

Question 162

Topic: Schedule Planning and Development

A scheduler has built a draft schedule for a medical device deployment. The customer must accept the go-live milestone, the sponsor wants monthly variance reporting against an approved baseline, and key team members have identified resource-driven sequencing changes. The project manager wants to baseline the plan this week. Which action best establishes an approved baseline schedule?

• A. Reconcile the draft in a joint review and get formal approval from all parties.
• B. Get sponsor sign-off first and direct others to work to it.
• C. Freeze the schedule now and refine logic after execution starts.
• D. Set the current forecast as the baseline for initial reporting.

Best answer: A

What this tests: Schedule Planning and Development

Explanation: A schedule baseline is the approved reference for measuring future performance, not just the latest schedule version. The best approach is to resolve logic and commitment issues with the customer, sponsor, project manager, and team members, then formally approve the baseline.

The key distinction is between a draft or forecast schedule and an approved baseline. A baseline should be created only after the schedule model has been validated and the affected stakeholders agree on milestone dates, sequencing, assumptions, calendars, and resource commitments. In this scenario, team members have already identified sequencing changes, so the schedule needs a joint review before it is frozen. Once those conflicts are resolved, formal approval from the customer, sponsor, project manager, and key team members establishes a credible control reference for future variance reporting. Using the latest forecast as the baseline, freezing an unvalidated draft, or relying on sponsor-only approval would create weak schedule control because the reference dates were not fully agreed.

An approved baseline requires validated logic and commitments plus formal agreement from the customer, sponsor, project manager, and team members.

Question 163

Topic: Schedule Closeout

At project closeout, a system rollout that used rolling-wave planning finished on November 6. The approved schedule baseline finish was October 30, the last forecast before completion was November 8, and no rebaseline was approved. Which conclusion best belongs in the final schedule performance evaluation?

• A. Report 2 days early because actual finish beat the final forecast.
• B. Replace the baseline with the final forecast for the closeout report.
• C. Report 7 days late to baseline; note the final forecast was 2 days conservative.
• D. Evaluate success mainly on forecast accuracy because rolling-wave planning was used.

Best answer: C

What this tests: Schedule Closeout

Explanation: Final schedule performance at closeout is evaluated against the approved schedule baseline, not the last forecast. Here, the project finished 7 days late to baseline, while the November 8 forecast simply shows the planning approach produced a forecast that was 2 days later than actual.

In schedule closeout, the primary performance comparison is actual results versus the approved schedule baseline because the baseline is the formal control reference. In this scenario, an actual finish of November 6 against a baseline finish of October 30 means the project completed 7 calendar days late.

The scheduling approach should still be evaluated, but separately. The final forecast of November 8 shows that rolling-wave planning produced a reasonably close forecast, finishing 2 days earlier than expected. That is useful evidence about forecast quality and approach effectiveness, but it does not change the final schedule variance. Because no rebaseline was approved, the baseline remains the correct reference for final performance reporting.

Beating the last forecast is helpful context, not the main closeout performance result.

Closeout performance is measured against the approved baseline, while forecast accuracy and the scheduling approach are evaluated separately.

Question 164

Topic: Schedule Planning and Development

A scheduler is building a plant shutdown schedule. Activity A needs 3 certified welders for 2 days, and Activity B needs 4 certified welders for 3 days. The two activities are planned to overlap, and the resource calendar shows only 5 certified welders available that week. Before deciding whether to apply resource leveling, which statement is correct?

• A. The 5-welder limit is resource availability, each activity’s crew need is a capacity requirement, the 7-welder overlap is a resource requirement, and leveling is mainly a reporting method.
• B. The 5-welder limit is resource availability, each activity’s crew need is a resource requirement, the 7-welder overlap is a capacity requirement, and resource leveling is a resource allocation technique.
• C. The 5-welder limit is a capacity requirement, each activity’s crew need is resource availability, the 7-welder overlap is a resource calendar limit, and leveling assigns the baseline.
• D. The 5-welder limit is resource availability, each activity’s crew need is a resource requirement, the 7-welder overlap is a capacity requirement, and leveling should wait until execution confirms an issue.

Best answer: B

What this tests: Schedule Planning and Development

Explanation: The key distinction is supply versus demand at different levels. The 5 available welders are resource availability, each activity’s crew size is a resource requirement, the 7-welder overlap is the capacity requirement for that time period, and leveling is the allocation technique used to remove the overload.

In schedule planning, distinguish the resource pool from what the schedule is asking that pool to support. The resource calendar gives supply, so 5 certified welders is resource availability. The need for 3 welders on one activity and 4 on another are resource requirements because they are activity-level demands. Since the activities overlap, the shared pool must support 7 welders at the same time; that aggregated demand for the period is the capacity requirement. Resource leveling is a resource allocation technique used to adjust dates or sequencing so demand fits available capacity. The closest trap is treating leveling as something that starts only after execution; it is also used during schedule development to make the plan feasible.

It correctly separates calendar-based supply, activity-level demand, period demand, and the technique used to resolve an overload.

Question 165

Topic: Schedule Strategy

During a monthly update, a scheduler enters actual starts, actual finishes, and revised remaining durations as of the data date. The completion milestone now forecasts 12 working days later than the approved baseline. Which data-control procedure best preserves traceability between current status, forecast, and the approved baseline?

• A. Copy each new forecast into the baseline after every reporting cycle.
• B. Update status at the data date, keep the approved baseline, and rebaseline only through approved change control.
• C. Maintain a separate forecast file and leave the controlled schedule unchanged.
• D. Add date constraints so key milestones stay aligned with baseline dates.

Best answer: B

What this tests: Schedule Strategy

Explanation: Traceability requires keeping the approved baseline separate from current status and the resulting forecast. The best procedure is to update actuals and remaining work at the data date, let the model calculate the forecast, and change the baseline only through approved change control.

The core control concept is separation of reference data from performance data. The approved schedule baseline is the measurement reference, so it should remain fixed during routine status updates. Each reporting cycle, the scheduler should enter actual dates and remaining durations as of the data date, allowing the schedule model to produce a current forecast. If a change is formally approved, that decision is documented through change control and then applied to the baseline.

This approach preserves a clear audit trail of three different things: what was approved, what has actually happened, and what is now expected. Overwriting the baseline with the forecast, forcing dates with constraints, or splitting updates into disconnected files weakens variance analysis and damages schedule traceability.

This preserves a fixed control reference while allowing status and forecast to change, with baseline changes made only after formal approval.

Question 166

Topic: Schedule Planning and Development

A data center project has a contractual energization milestone on August 15. The schedule management plan says an external milestone may be reported as achievable only when schedule risk analysis shows at least 80% confidence of meeting it. After a supplier delay, the latest results are:

What should the scheduler recommend?

• A. Rebaseline the milestone to August 26 so variance no longer appears.
• B. Fast-track commissioning before safety tests finish to pull the date in.
• C. Declare August 15 outside tolerance, assess driving-path recovery, and use change control if needed.
• D. Keep August 15 as achievable because the deterministic forecast still meets it.

Best answer: C

What this tests: Schedule Planning and Development

Explanation: The stated tolerance requires at least 80% confidence, so the milestone must be checked against the P80 date, not the deterministic forecast. Because P80 is August 26, the August 15 commitment is not achievable within tolerance and should trigger recovery analysis and, if needed, formal change control.

This question tests whether a milestone is achievable within a defined schedule risk tolerance. When the rule says an external commitment needs 80% confidence, the scheduler should compare the required date to the P80 result from schedule risk analysis. Here, the deterministic forecast happens to equal August 15, but that does not satisfy the stated tolerance. The risk-adjusted date that meets the confidence requirement is August 26, so the contractual milestone is outside tolerance.

The right control decision is to:

• flag the milestone as not achievable within tolerance,
• evaluate credible recovery options on the driving path, and
• use formal change control if recovery cannot restore the date.

A deterministic date that looks acceptable is not enough when the agreed decision rule is probabilistic confidence.

The 80% confidence rule makes the P80 date the test of achievability, and P80 is later than August 15.

Question 167

Topic: Schedule Monitoring and Controlling

A project is in dispute over a 5-week delay to a contract milestone, and the scheduler is asked to perform a forensic schedule analysis. The team has the current schedule file and monthly PDF status reports, but it does not have the archived update files for the delayed period, the approved change log for several logic revisions, or the status narratives showing the data dates used. What should the scheduler do next?

• A. Rebaseline the schedule to align it with the current forecast before starting analysis
• B. Run the delay analysis with the current file and PDFs, then refine it if questions arise
• C. Inventory the missing records and obtain or reconstruct contemporaneous schedule evidence before analyzing the delay
• D. Issue a stakeholder report identifying the most likely source of the delay

Best answer: C

What this tests: Schedule Monitoring and Controlling

Explanation: The documentation is insufficient for a reliable forensic schedule analysis because key contemporaneous records are missing. Before assigning delay responsibility or running analysis techniques, the scheduler should first secure or reconstruct the missing update basis, change history, and data-date evidence.

Forensic schedule analysis depends on a credible record of what the schedule model looked like at the time of each update, how it was statused, and what approved changes altered logic or dates. Here, the archived update files, change log, and status narratives are missing, so the analysis basis is not yet reliable. The correct next step is to perform a documentation sufficiency check, identify the gaps, and obtain or reconstruct contemporaneous evidence before selecting or running any delay-analysis method.

Without that foundation, conclusions about causation, responsibility, or critical-path impact may be unsupported because the model integrity for the affected period cannot be verified. Reporting or rebaselining would not fix the missing audit trail.

Forensic analysis requires credible contemporaneous schedule data, so the next step is to validate and fill documentation gaps before drawing delay conclusions.

Question 168

Topic: Schedule Monitoring and Controlling

As of June 1, the weekly update is complete, status is validated, and the schedule has been recalculated. Mechanical completion is now forecast 7 workdays late because regulatory review of control panel drawings is the driving path constraint. The project manager proposes fast-tracking cable installation, which has 12 days of total float. What should the scheduler do next?

• A. Rebaseline the milestone to the new completion date.
• B. Fast-track cable installation to recover the milestone.
• C. Publish the slipped forecast and proposed fast-track.
• D. Model recovery options on the regulatory review path.

Best answer: D

What this tests: Schedule Monitoring and Controlling

Explanation: The best next step is to run what-if analysis on the validated schedule model and test options that directly affect the driving path. Because the delay is caused by regulatory review, accelerating cable installation with available float will not recover the milestone.

In schedule optimization, the next action should target the constraint that is actually driving the late forecast. Here, the update is already complete and the schedule logic is credible, so the scheduler should analyze recovery scenarios that shorten or relieve the regulatory review path. Since cable installation still has 12 days of total float, it is not currently driving mechanical completion; accelerating it may consume float, but it will not improve a milestone controlled by another path.

• Confirm which activity or path is driving the slip.
• Test alternatives that directly change that path or its constraint.
• Compare the resulting milestone dates before recommending action.

Reporting the delay is necessary later, but it is not the control step, and a forecast change does not justify rebaselining by itself.

Only options that affect the driving path can recover the milestone; cable installation still has float and is not the current constraint.

Question 169

Topic: Schedule Monitoring and Controlling

On a predictive project, the status date is May 15. A vendor interface activity on the driving path is 6 working days late, and an approved scope change added 4 days to system testing. The sponsor asks for a schedule report to decide whether recovery is needed for the July 30 go-live milestone. Which report content is best?

• A. Phase percent complete and a proposal to crash training activities that still have float.
• B. Baseline vs forecast milestone dates, variance split by approved change and delay, driving-path impact, issue owners, and corrective-action options.
• C. Forecast dates only, using the latest plan as the new reporting reference and removing prior baseline dates.
• D. Updated finish dates after overlapping testing with unfinished design work, without documenting change or issue impacts.

Best answer: B

What this tests: Schedule Monitoring and Controlling

Explanation: A useful schedule report for control decisions must show current status against the approved baseline, the latest forecast, and the specific causes of slippage. Here, the sponsor needs the driving-path impact, the approved change impact, open issues, and realistic corrective-action choices.

A schedule report used for control decisions should make variance visible, not hide it. In this case, decision-makers need to see the approved baseline date, the current forecast date, and a clear separation between delay caused by execution performance and delay caused by an approved change. They also need the effect on the driving path, the key open issues with ownership, and the corrective-action options being evaluated. That combination explains status, impacts, changes, and issues in a way that supports an informed recovery decision. Reporting only forecast dates effectively replaces the baseline, while percent complete or aggressive overlap proposals do not explain the true schedule impact or preserve schedule-control discipline.

This content shows status against the approved baseline, explains the sources of slip, and supports a sound recovery decision.

Question 170

Topic: Stakeholder Communications Management

In a data-center migration project, the current forecast shows the cutover milestone slipping by 7 working days because server validation is taking longer than planned. Stakeholder-impact analysis shows the sponsor needs recovery decision support, the operations team needs revised blackout dates, and the cybersecurity reviewer is not affected this cycle. Which communication approach best uses stakeholder-impact analysis?

• A. Share percent complete now and hold forecast dates for later.
• B. Tailor forecast-impact messages to affected stakeholders and exclude unaffected ones.
• C. Wait until the baseline cutover date is missed before tailoring updates.
• D. Send one identical schedule status report to all stakeholders.

Best answer: B

What this tests: Stakeholder Communications Management

Explanation: Stakeholder-impact analysis helps convert schedule data into targeted communication. The best approach is to communicate the forecasted impact and needed actions to affected stakeholders, while not sending unnecessary targeted detail to stakeholders who are currently unaffected.

The key concept is the difference between schedule status and schedule impact. Stakeholder-impact analysis is used to identify who is affected by a forecasted change, what schedule information matters to them, and whether they need to make a decision or prepare for a date change. In this scenario, the sponsor needs the forecasted cutover slip and recovery information, while operations needs revised blackout dates because its work depends on them. The cybersecurity reviewer is not affected in this update cycle, so a targeted impact message is not needed.

• Identify which stakeholders are affected by the forecast.
• Match the message to each stakeholder’s decision or preparation need.
• Communicate forecasted impact, not just raw status data.

A uniform report may be consistent, but it is less useful than impact-based communication.

Stakeholder-impact analysis should drive targeted communication based on each stakeholder’s affected dates and decision needs, not a generic status broadcast.

Continue with full practice

Use the PMI-SP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Focused topic pages

• PMI-SP: Schedule Strategy
• PMI-SP: Schedule Planning and Development
• PMI-SP: Schedule Monitoring and Controlling
• PMI-SP: Schedule Closeout
• PMI-SP: Stakeholder Communications Management

Free review resource

Read the PMI-SP guide on PMExams.com for concept review, then return here for PM Mastery practice.