CompTIA Project+ (PK0-005) — Free Practice Questions
10 free sample questions from a bank of 861, with the correct answers and explanations. No signup required — start practising right now.
1As a result of an approved change request, the project manager updates the project plan to reflect the new feature addition and the revised production release date. Which of the following change control processes should the project manager do NEXT?
Validate the change implementation.
Implement the change.
Conduct an impact assessment.
Communicate the change deployment.
Answer: B
The short version
B — Implement the change. The request was already approved and the plan already updated, so impact analysis and approval are complete; the next step in change control is to implement the approved change.
Key concepts in this question
Change control sequence: request, analyze impact, approve or reject, implement, validate or verify, then communicate and update logs.
Approved change: once approved and reflected in the plan, the planning steps of the change are finished.
Validate versus communicate: validation confirms the implementation satisfies the request; communicating the deployment is the last step.
Why B is correct
The stem states the change request was approved and the project plan was already updated for the new feature and revised release date, which puts the request, analysis, and approval steps behind the project manager. The step immediately following approval in the standard change control process is implementation, so the PM should implement the change next and only afterward validate it and communicate the deployment.
Why the others are wrong
A. Validation follows implementation, so it cannot be next when nothing has been implemented yet.
C. The impact assessment precedes the approval decision, and approval has already happened.
D. Communicating the change deployment is the final step, after implementation and validation.
PK0-005 exam tip
Change control order: request, analyze, approve, implement, validate, communicate. Approval just passed, so implement.
2A PM is responsible for implementing a new customer relationship management system and has learned that the sales organization is reluctant to utilize the new system. The organization’s reluctance could jeopardize the success of the project. Which of the following steps should be taken to understand the adoption issues and gain organizational acceptance of the initiative? (Choose two.)
Train users on the proper use of the system.
Escalate the issue to the CCB.
Hold sessions to understand user challenges.
Track system usage and report user activity.
Log the issue in the project risk register.
Create a memorandum of acceptable use.
Answer: C, E
The short version
CE — hold sessions to learn challenges plus log risk to gain acceptance. Empathy plus formal risk tracking moves reluctant sales toward use.
Key concepts in this question
Adoption resistance: reluctance from sales that can jeopardize CRM success if unaddressed.
Discovery sessions: facilitated conversations uncovering workflow pain, fit gaps, and training needs.
Risk register logging: recording adoption threat with owner and response so it is managed visibly.
Premature training: teaching proper use before understanding barriers wastes effort and trust.
Escalation and surveillance: CCB action, usage tracking, or acceptable use memos without diagnosis.
Why CE is correct
CE is correct because understanding adoption issues requires holding sessions to understand user challenges and logging the issue in the risk register. Sessions surface real obstacles such as process mismatch or time cost, while the register ensures the threat is owned, assessed, and mitigated rather than wished away. Training helps after diagnosis, escalation is for decisions beyond authority, tracking reports symptoms, and memos mandate without insight. The settled pair pairs diagnosis with governance.
Why the others are wrong
A. Wrong because training on proper use helps after causes are known, not as the first diagnostic step.
B. Wrong because CCB escalation is for change decisions, not for learning adoption barriers.
D. Wrong because usage tracking reports behavior but does not explain why resistance exists.
F. Wrong because acceptable use memo mandates compliance without building understanding or acceptance.
PK0-005 exam tip
Reluctance plus acceptance equals listen first plus log risk: train after you learn, never mandate first.
3Following a successful release, a project manager sent a survey to all stakeholders to gain an understanding of opportunity areas for the team. Which of the following can use the survey results as an input?
Daily stand-up
Project momentum
Performance feedback
Meeting minutes
Answer: C
The short version
C — performance feedback consumes post release survey results. Stakeholder views on opportunities feed growth and review cycles.
Key concepts in this question
Post release survey: capturing stakeholder perceptions of what worked and where to improve.
Performance feedback: structured review input that improves individual and team effectiveness.
Daily standup: short coordination event focused on today plus blockers, not survey synthesis.
Project momentum: informal sense of pace, not a formal input consumer of survey data.
Meeting minutes: record of discussion, not a development process fed by surveys.
Why C is correct
C is correct because survey results from stakeholders on opportunity areas serve as an input to performance feedback. Feedback discussions use that evidence to reinforce strengths and target improvements for the team. Standups coordinate daily work, momentum describes energy, and minutes document meetings. Only performance feedback is the people improvement use that systematically consumes survey insight after release.
Why the others are wrong
A. Wrong because daily standup coordinates immediate work, rather than consuming post release surveys.
B. Wrong because momentum is an informal pace impression, not a formal survey consumer.
D. Wrong because meeting minutes record events, but do not develop people from survey results.
4Which of the following is an activity that should be used in the closing phase of a project to support the project triple constraint?
Evaluating the project
Releasing the resources
Closing the contracts
Reconciling the budget
Answer: D
The short version
D — reconciling the budget supports triple constraint in closing. Cost closure validates spend against plan and funding.
Key concepts in this question
Triple constraint: scope plus schedule plus cost balance that closing must confirm.
Budget reconciliation: comparing actuals to budget, settling variances, and closing accounts.
Project evaluation: lessons and performance review that support learning more than constraint proof.
Resource release: returning people and assets, important administratively but not constraint evidence.
Contract closure: finalizing vendor obligations, narrower than overall cost reconciliation.
Why D is correct
D is correct because reconciling the budget in the closing phase directly supports the cost side of the triple constraint while confirming scope delivered within time and funds. It ties invoices, actuals, and forecasts to the approved budget and documents final position for sponsors. Evaluation captures learning, release frees resources, and contract closure ends vendor work, yet none proves cost fidelity like reconciliation. The settled closing activity is budget proof.
Why the others are wrong
A. Wrong because evaluating the project aids learning, but does not validate cost against constraint.
B. Wrong because releasing resources is administrative closure, not triple constraint support.
C. Wrong because closing contracts ends vendor scope, narrower than full budget reconciliation.
PK0-005 exam tip
Closing plus triple constraint plus cost equals reconcile budget: evaluate learns, release frees.
5During a quality analysis review, the causes of several issues have been highlighted. Which of the following should the project manager use to identify the MOST important causes?
Ishikawa diagram
Scatter diagram
Pareto chart
Decision tree
Answer: C
The short version
C — Pareto chart isolates the most important causes. Vital few bars guide focus where impact is greatest.
Key concepts in this question
Pareto principle: roughly eighty percent of effects stem from twenty percent of causes.
Pareto chart: ordered bars plus cumulative line highlighting highest frequency contributors.
Ishikawa diagram: fishbone categorization of potential causes without ranking importance.
Scatter diagram: paired correlation view, not ranked cause importance.
Decision tree: option analysis under uncertainty, not defect cause ranking.
Why C is correct
C is correct because a project manager seeking the most important causes among highlighted issues should use a Pareto chart. Sorted bars quantify which defects dominate, letting the team attack the vital few first for maximum quality gain. Ishikawa organizes theories, scatter tests association, and decision trees value choices. Only Pareto ranks importance by frequency or cost for prioritized action.
Why the others are wrong
A. Wrong because Ishikawa brainstorms cause categories but does not rank which matter most.
B. Wrong because scatter shows correlation between two variables, not ranked cause priority.
D. Wrong because decision tree evaluates choices under risk, not most important quality causes.
PK0-005 exam tip
Most important causes equals Pareto: fishbone lists, scatter links, Pareto ranks.
6Which of the following BEST describes how an organization should coordinate management of multiple related projects?
Apply the SDLC process.
Establish a program.
Consult the CCB.
Use different frameworks.
Answer: B
The short version
B — establish a program to coordinate multiple related projects. Programs align benefits, governance, and dependencies centrally.
Key concepts in this question
Program management: coordinating related projects for benefits unattainable when managed separately.
Relatedness value: shared goals, resources, and dependencies needing unified oversight.
SDLC process: software lifecycle for single product build, not multi project coordination.
CCB role: change authority for baselines, not an organizational coordination model.
Different frameworks: divergent methods increase friction rather than coordination.
Why B is correct
B is correct because an organization coordinating multiple related projects should establish a program. The program provides common governance, dependency management, and benefits tracking across components while projects deliver outputs. SDLC guides single builds, CCB rules changes, and different frameworks fragment approach. Only a program supplies the coordination layer for related efforts.
Why the others are wrong
A. Wrong because SDLC structures software delivery, not coordination of multiple related projects.
C. Wrong because CCB decides changes, but does not coordinate benefits across projects.
D. Wrong because different frameworks reduce consistency and hinder joint management.
PK0-005 exam tip
Multiple related projects equals program: SDLC builds one, CCB controls change, program coordinates.
7A project team gathers weekly to review its progress. Which of the following is the project manager MOST likely to have prepared to ensure team members who are absent remain informed about assignments?
Status report
Project plan
Change log
Meeting minutes
Answer: D
The short version
D — meeting minutes keep absent members informed on assignments. Written records preserve decisions and ownership.
Key concepts in this question
Weekly progress review: regular coordination where assignments evolve and accountability is set.
Meeting minutes: documented attendees, topics, decisions, and action items with owners.
Status report: point in time health summary that may lack assignment detail continuity.
Project plan: overall direction document, too broad for weekly assignment catch up.
Change log: record of baseline changes, not weekly task assignments.
Why D is correct
D is correct because a project manager preparing for weekly reviews to keep absent members informed on assignments would most likely prepare meeting minutes. Minutes capture who owns what by when plus context discussed, letting absentees act without rework. Status reports summarize health, plans set direction, and change logs track baseline edits. Only minutes provide the assignment level continuity the stem demands.
Why the others are wrong
A. Wrong because status reports summarize health but do not reliably carry assignment continuity.
B. Wrong because project plan defines approach, too static for weekly absent follow up.
C. Wrong because change log tracks baseline changes, not weekly task ownership.
8A project manager prefers to have immediate contact with team members because it allows for faster response times and more interactive discussions. Which of the following communication methods should the project manager use?
Synchronous
Informal
Asynchronous
Formal
Answer: A
The short version
A — synchronous communication gives immediate interactive contact. Real time exchange speeds response and discussion depth.
Key concepts in this question
Synchronous: same time interaction such as calls or co located sessions with instant feedback.
Immediate contact goal: faster responses plus richer back and forth for complex or urgent topics.
Asynchronous: delayed exchange such as email, useful for records but slower for dialogue.
Formal versus informal: tone and documentation level, independent of timing immediacy.
Interactivity need: rapid clarification that only real time channels deliver.
Why A is correct
A is correct because a project manager wanting immediate contact for faster responses and interactive discussion should use synchronous communication. Phone, video, or face to face sessions allow instant questions, tone cues, and convergence. Asynchronous waits on replies, while formal or informal describe style rather than timing. The settled match for immediacy plus interactivity is synchronous.
Why the others are wrong
B. Wrong because informal describes tone, not real time immediacy.
C. Wrong because asynchronous delays response, opposite the stated need for immediacy.
D. Wrong because formal describes documentation rigor, not timing or interactivity.
PK0-005 exam tip
Immediate plus interactive equals synchronous: async waits, formal plus informal style tone.
9As part of the planning phase, a PM has defined tasks, durations, resources, and costs. Which of the following is the NEXT step in the process?
Update the work breakdown structure.
Review the backlog.
Seek baseline approval.
Establish the resource pool.
Answer: C
The short version
C — seek baseline approval next after defining tasks plus costs. Planning completes when scope plus schedule plus cost are frozen.
Key concepts in this question
Planning completeness: tasks, durations, resources, and costs defined but not yet committed.
Baseline approval: formal acceptance locking scope, schedule, and cost for control.
WBS update: decomposition already reflected in defined tasks, not the next gate.
Backlog review: agile refinement, mismatched to baseline driven planning context.
Resource pool: sourcing channel that precedes assignment more than follows costing.
Why C is correct
C is correct because after defining tasks, durations, resources, and costs, the next step is seeking baseline approval. Approval converts estimates into committed scope, schedule, and cost baselines against which execution and change are measured. Updating WBS revisits decomposition, backlog review fits iterative planning, and establishing the pool addresses sourcing. The settled planning gate is baseline sign off.
Why the others are wrong
A. Wrong because WBS decomposition already underpins the defined tasks, not the next approval gate.
B. Wrong because backlog review suits agile flow, not formal baseline approval sequencing.
D. Wrong because resource pool establishment supports resourcing earlier, not post costing approval.
PK0-005 exam tip
Tasks plus costs done equals seek baseline: WBS builds, baseline locks, then execute.
10A project manager realizes that a project will not be completed on time due to resource constraints. Which of the following actions should the project manager take NEXT?
Trigger the contingency plan and communicate with the stakeholders.
Work with the functional managers to create a work-around.
Submit a change request to the change control board.
Transfer the risk by hiring a new vendor who was successful on a previous project.
Set up an escalation meeting with the sponsor.
Answer: C
The short version
C — submit a change request to the CCB when resources threaten time. Formal control evaluates impact before replanning.
Key concepts in this question
Resource driven delay: forecast miss caused by constraints, requiring baseline or approach change.
Change request: documented proposal for scope, schedule, or cost adjustment with justification.
CCB authority: body approving or rejecting baseline changes after impact review.
Contingency trigger: using reserves for known risks, premature before formal assessment.
Workarounds and escalation: informal fixes or sponsor talks that bypass disciplined control.
Why C is correct
C is correct because a project that will not finish on time due to resource constraints must next submit a change request to the change control board. The request forces analysis of schedule, cost, and scope options and secures authorized direction. Triggering contingency presumes the situation matches a planned risk, workarounds lack approval, vendor transfer adds risk, and escalation alone decides nothing. The settled next step preserves governance through CCB review.
Why the others are wrong
A. Wrong because contingency applies to planned risks with reserves, not any resource shortfall.
B. Wrong because functional manager workarounds bypass formal impact and approval discipline.
D. Wrong because vendor transfer is a risky response, not the governed next step for delay.
E. Wrong because escalation meeting discusses, but CCB change decides baseline fate.
PK0-005 exam tip
Late plus resources equals change request next: assess plus approve before workaround or transfer.