Try 10 focused Project+ questions on Project Management Concepts, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | Project+ |
| Topic area | Project Management Concepts |
| Blueprint weight | 33% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Project Management Concepts for Project+. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 33% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Project Management Concepts
A project team is implementing a new HR SaaS platform. A change request is submitted to add SSO with MFA before go-live.
The project manager schedules a 30-minute change review meeting but invites only the development lead and the HR product owner. The organization’s process requires approval from the system owner and the security/compliance approver for authentication changes.
What is the most likely near-term impact of holding the meeting with the current attendee list?
Best answer: D
What this tests: Project Management Concepts
Explanation: Meeting attendees should be selected based on who provides required inputs and who has decision rights. Because the required system owner and security/compliance approver are missing, the change cannot be formally decided in that meeting. The most likely immediate consequence is a pending decision and the need to reconvene or route for approval.
For decision-focused meetings (like change control), the attendee list must include (1) the people who can approve/reject the decision and (2) the SMEs needed to provide required input. In this scenario, the organization explicitly requires the system owner and the security/compliance approver to approve authentication changes. If they are not present, the meeting may gather discussion but cannot produce a valid decision, so the change remains in a “pending” state.
A practical way to avoid this is to invite only roles with:
The key takeaway is that missing decision-makers creates immediate decision latency, which then threatens schedule through rework and additional meetings.
Without attendees who have decision rights for authentication changes, the meeting cannot produce an approval or rejection.
Topic: Project Management Concepts
You are managing an internal HR system modernization project. A stakeholder submits the following change request.
Exhibit: Change request excerpt
ID: CR-07
Change: Add automated data-validation rules
Reason: Reduce post-go-live defects
Estimated effort: +120 hrs dev, +40 hrs QA
Constraints: Go-live date fixed (regulatory)
Constraints: Budget capped at \$250,000
Status: Pending PM review
Which is the BEST next action based on the exhibit?
Best answer: A
What this tests: Project Management Concepts
Explanation: The exhibit shows a classic constraint tradeoff: the change increases work while both the go-live date and budget are fixed. In that situation, the project team must adjust scope or expectations elsewhere to remain within schedule and cost. Deferring lower-priority features is the most appropriate tradeoff to accommodate the change without violating stated constraints.
Projects are constrained by scope, schedule, cost, and quality, and changing one constraint typically forces tradeoffs in one or more of the others. Here, the change request adds 160 hours of effort, which will pressure both schedule and cost. Because the exhibit explicitly states the go-live date is fixed (regulatory) and the budget is capped, you cannot rely on extending the timeline or adding funded resources as the primary response.
A practical next step is to work with stakeholders to re-baseline scope by:
The key takeaway is that when schedule and cost are fixed, scope is the most common lever to adjust without sacrificing required quality outcomes.
With schedule and budget fixed, adding work requires reducing other scope to maintain the constraints.
Topic: Project Management Concepts
You are building the schedule for an identity project to deliver “Enable SSO for the company’s SaaS HR system.” You are decomposing the deliverable into activities and defining logical dependencies before creating the Gantt chart.
Which approach is INCORRECT when identifying activity dependencies?
Best answer: A
What this tests: Project Management Concepts
Explanation: Logical dependencies describe the required sequence of work (technical or mandatory relationships), not who happens to be available. Resource constraints are handled through resource assignments and schedule optimization after the activity network is built. Creating “availability-based” links can hide true parallel work and distort the critical path.
When decomposing a deliverable into activities, the goal is to define the work and its true sequencing so the schedule reflects how the solution must be built and validated. Dependencies should be driven by logical relationships (mandatory/technical, discretionary, or external) such as “configure IdP before testing SSO” or “security approval before production enablement.” Resource availability affects who performs an activity and may create resource-driven delays later, but it should not be represented as a dependency between otherwise independent activities.
A practical sequence is:
This keeps the network diagram and critical path based on work logic rather than staffing artifacts.
Resource availability can influence assignment, but dependencies should reflect required technical/sequence relationships between activities.
Topic: Project Management Concepts
A Scrum team works in 2-week iterations. The product owner’s backlog shows 96 story points remaining for the MVP. The team’s average velocity over the last five iterations is 24 story points per iteration, and the team composition is expected to stay the same.
Which TWO forecasts are accurate based on this information? (Select TWO)
Correct answers: A, F
What this tests: Project Management Concepts
Explanation: A simple agile forecast uses remaining work in story points and the team’s historical velocity. With 96 points remaining and 24 points completed per iteration on average, the team needs about 4 more iterations. At 2 weeks per iteration, that equates to about 8 weeks remaining.
Iteration forecasting in agile commonly estimates time by dividing remaining backlog work (in story points) by the team’s average velocity (story points per iteration). Because the team’s composition is stable and an average velocity is provided, you can create a straightforward forecast without converting points to hours.
This produces an iteration-based and calendar-time forecast that can be communicated as an estimate, often with appropriate uncertainty language.
Divide remaining work (96 points) by velocity (24 points/iteration) to get 4 iterations.
4 iterations 2 weeks per iteration = about 8 weeks.
Topic: Project Management Concepts
A hybrid project is migrating a customer portal to a new SaaS platform. During integration testing, the vendor identifies a data-mapping defect that could delay go-live by one week. The project team is unsure who can approve a schedule change, and the product owner and sponsor are only contacted ad hoc, causing decision delays.
What is the BEST next step?
Best answer: A
What this tests: Project Management Concepts
Explanation: The project is blocked by unclear decision authority and irregular stakeholder communication. The best next step is to establish a defined communication cadence and escalation path so the right people are engaged quickly and decisions are made within an agreed timeframe. This directly addresses the root cause of delayed decisions while keeping escalation appropriate and repeatable.
When decisions are being delayed, the immediate need is to formalize how decisions are made and how issues are escalated. Updating the communications plan (and aligning it with roles/decision authority) creates a predictable cadence (e.g., daily triage during testing, twice-weekly risk/issue review) and a clear escalation path (who is notified first, when to involve the sponsor, and when to route to a steering group). In this scenario, the issue has potential schedule impact, but the team’s bigger problem is that they don’t know who can approve changes and they contact leaders inconsistently. Establishing that structure first speeds up this decision and prevents repeated delays for the rest of testing.
Key takeaway: set the cadence and escalation path before jumping to emergency escalation or waiting for routine meetings.
Defining a clear cadence and escalation path enables timely decisions on the schedule impact without premature escalation.
Topic: Project Management Concepts
You are the project coordinator for a hybrid project migrating a customer portal to a new SaaS platform. During execution, the vendor confirms their integration toolkit release is delayed by 2 weeks, which pushes a dependency for system testing on your critical path. The go-live date is fixed due to a regulatory deadline, and changes to scope or schedule require CAB approval. The business sponsor asks for an update by end of day.
What is the BEST next action?
Best answer: B
What this tests: Project Management Concepts
Explanation: The project has a confirmed dependency delay on the critical path, a fixed regulatory deadline, and a governance requirement for CAB approval. The next step is to update the schedule forecast (not the approved baseline), assess impacts and response options, and communicate those impacts to stakeholders immediately. In parallel, you should initiate the formal change-control path required by the project.
When a schedule-impacting change occurs, the project team should update the plan to reflect the new forecast, analyze the impact to milestones/critical path, and communicate implications quickly to affected stakeholders. In environments with formal governance, you should not change the approved schedule baseline until the required authority (here, CAB) reviews and approves the change.
A practical next-step sequence is:
This balances timely stakeholder communication with proper change control.
This updates the plan, quantifies the schedule impact and alternatives, and communicates promptly while following the required change-control governance.
Topic: Project Management Concepts
You are managing a small infrastructure upgrade project. A vendor reports that activity D will finish 3 business days late. You need to validate whether this delay will move the go-live date.
Exhibit: Activity network (duration; predecessors)
Which evidence best validates the schedule impact of the delay?
Best answer: A
What this tests: Project Management Concepts
Explanation: The most direct way to validate whether a task delay affects go-live is to recompute the network schedule using CPM and review the critical path and total float. If the delayed activity has zero float, the project finish date moves by the same amount as the delay. An updated CPM analysis provides objective, schedule-based evidence of the impact.
To determine whether a delay changes the project end date, use Critical Path Method (CPM) on the network diagram to identify the longest path (critical path) and each activity’s total float. In the exhibit, the path A→B→D→F is 12 days, while A→C→E→F is 8 days, so A→B→D→F is critical and activities on it have 0 float. Therefore, a 3-day slip in D pushes the finish milestone (F) and go-live by 3 days unless the schedule is changed (e.g., crashing/fast-tracking). The best validation is an updated CPM calculation (updated network diagram or schedule report) that shows critical path and float after applying the delay.
A recalculated critical path/float analysis directly shows whether the delayed activity is on the critical path and quantifies the project end-date impact.
Topic: Project Management Concepts
Midway through a CRM migration project, a data-cleansing task is estimated to take two additional weeks due to unexpected duplicates. The task is on the critical path, and the go-live date is a contractual milestone. You have confirmed the new estimate with the technical lead.
Which action should the project manager NOT take when managing this schedule change?
Best answer: D
What this tests: Project Management Concepts
Explanation: Once a schedule-impacting change is validated—especially on the critical path—the project manager should update the plan and promptly communicate impacts so stakeholders can make decisions (approve changes, adjust scope, add resources, or move dates). Waiting until work completes keeps the schedule baseline and stakeholder expectations misaligned and reduces options to mitigate the delay.
Schedule change management requires keeping the project plan current and ensuring stakeholders understand the impacts in time to act. In this scenario, the task is on the critical path and affects a contractual milestone, so the project manager should update the schedule forecast (dates, dependencies, and critical path) and communicate the implications (go-live shift, downstream work, and options for recovery). If the organization uses formal change control for baselines or contractual milestones, the schedule change should be routed for review/approval and the baseline updated if approved. The key anti-pattern is withholding a known schedule impact until after the work finishes, which prevents timely mitigation and undermines governance and expectations management.
Delaying the plan update and communication hides known impacts and prevents timely decisions on mitigation or approval.
Topic: Project Management Concepts
During UAT for a CRM upgrade, the QA lead reports that 480 test cases have been executed: 432 passed and 48 failed. The sponsor asks if the project should proceed to the production deployment window next week.
Before you interpret what this result means and make a recommendation, what should you obtain/verify FIRST?
Best answer: A
What this tests: Project Management Concepts
Explanation: From the data, the team’s current test pass rate is 90% \(432/480\). Whether 90% indicates “ready to deploy” depends on the project’s predefined quality threshold (acceptance criteria/Definition of Done). Verifying that criterion first enables an objective go/no-go decision instead of an opinion-based one.
This is a quality/performance interpretation decision: you can calculate a simple percentage from the test results, but you cannot judge it as acceptable or not without the baseline target the project agreed to meet. In UAT, that target is typically documented as release/acceptance criteria (often including minimum pass rate and limits on open critical/high-severity defects).
Without the acceptance criteria, any interpretation of “90%” is ungrounded because the required quality level may be higher or lower depending on risk tolerance and business impact.
A 432/480 result is a 90% pass rate, but you need the predefined acceptance threshold to judge readiness.
Topic: Project Management Concepts
You are coordinating an endpoint security project to enable full-disk encryption on 1,200 laptops using a new management platform. Constraints:
A pilot found that about 15% of laptops fail encryption and become unusable until repaired. What is the BEST next action to address this risk?
Best answer: A
What this tests: Project Management Concepts
Explanation: A phased rollout with fixes and a tested rollback plan is a mitigation response: it reduces the likelihood and impact of the known pilot failures. It also fits the constraints because it does not change the audit-driven deadline or remove required scope. The approach limits operational disruption given the constrained help desk capacity.
Selecting a risk response type should match both the risk and the project constraints. Here, the risk is already validated (15% failure rate) and could cause significant business disruption during a hard-deadline deployment. Avoidance would require changing scope or approach in a way the sponsor has ruled out, and transferring the risk is not feasible without approved funding.
Mitigation is appropriate because you can reduce probability/impact before broad rollout by:
The key takeaway is to reduce exposure to the known failure mode while still meeting the non-negotiable audit date.
This mitigates the failure risk while still meeting the fixed audit deadline and staffing limits.
Use the Project+ Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Use the full PM Mastery practice page above for the latest review links and practice route.