CompTIA PK0-005 (CompTIA Project+) Practice Test 40

Question 390

In the log monitoring deployment, the team proposes the practice Perform an initial risk assessment to identify early threats and opportunities while the plan is still adaptable. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Cutover planning coordinates timing, dependencies, verification, and recovery.
  2. Early risk assessment exposes constraints that should shape scope and reserves.
  3. Operational training closes adoption and support skill gaps before handoff.
  4. Milestone baselines identify significant control dates for delivery monitoring.

Explanation

Correct Answer

B:

This is observable evidence of Perform an initial risk assessment for the log monitoring deployment purpose to identify early threats and opportunities while the plan is still adaptable; operational mechanism: Early risk assessment exposes constraints that should shape scope and reserves; specific limitation: Risks will still need periodic review during execution.

Incorrect Answers

A:

This behavior would demonstrate Plan go-live cutover for sequence the switch from an old system to the new production environment, rather than Perform an initial risk assessment for identify early threats and opportunities while the plan is still adaptable in the log monitoring deployment; the practical reason is: Cutover planning coordinates timing, dependencies, verification, and recovery; important boundary: The team needs a rollback criterion for unacceptable release results.

C:

This behavior would demonstrate Plan operational training for prepare support staff and users to operate the delivered system after release, rather than Perform an initial risk assessment for identify early threats and opportunities while the plan is still adaptable in the log monitoring deployment; operational mechanism: Operational training closes adoption and support skill gaps before handoff; specific limitation: Deployment without trained owners can leave an unusable service.

D:

This behavior would demonstrate Milestone baseline approval for define key completion checkpoints as reference dates agreed by authorized stakeholders, rather than Perform an initial risk assessment for identify early threats and opportunities while the plan is still adaptable in the log monitoring deployment; the practical reason is: Milestone baselines identify significant control dates for delivery monitoring; important boundary: A forecast change alone does not authorize silently moving them.

Question 391

In the procurement automation rollout, the team proposes the practice Reconcile final budget to match actual invoices and commitments to approved final expenditures. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Budget reconciliation resolves the project's financial position at close.
  2. A closeout report preserves an auditable overview of delivery results.
  3. Final validation checks what was delivered against agreed acceptance rules.
  4. Recognition supports morale and marks the conclusion of temporary work.

Explanation

Correct Answer

A:

This is observable evidence of Reconcile final budget for the procurement automation rollout purpose to match actual invoices and commitments to approved final expenditures; the practical reason is: Budget reconciliation resolves the project's financial position at close; important boundary: A forecast from the middle of the project is not a final accounting.

Incorrect Answers

B:

This behavior would demonstrate Project closeout report for summarize final outcomes, variances, lessons, unresolved transitions, and acceptance, rather than Reconcile final budget for match actual invoices and commitments to approved final expenditures in the procurement automation rollout; operational mechanism: A closeout report preserves an auditable overview of delivery results; specific limitation: It is broader than an ordinary weekly status email.

C:

This behavior would demonstrate Final deliverable validation for confirm contractual and functional acceptance conditions have evidence of completion, rather than Reconcile final budget for match actual invoices and commitments to approved final expenditures in the procurement automation rollout; operational mechanism: Final validation checks what was delivered against agreed acceptance rules; specific limitation: It should occur before declaring the project complete.

D:

This behavior would demonstrate Closure celebration and recognition for acknowledge the team's contribution after delivery obligations are met, rather than Reconcile final budget for match actual invoices and commitments to approved final expenditures in the procurement automation rollout; the practical reason is: Recognition supports morale and marks the conclusion of temporary work; important boundary: It complements rather than replaces legal or financial closure.

Question 392

In the microservice authentication update, the team proposes the practice Pareto chart to rank defect categories to identify the few causes responsible for most incidents. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. A scatterplot reveals direction and strength of a possible relationship.
  2. This approach sorts category contributions and often adds cumulative percentages.
  3. Velocity tracks observed delivery capacity to inform short-term forecasting.
  4. These techniques display accumulated completion and may reveal scope growth.

Explanation

Correct Answer

B:

This is observable evidence of Pareto chart for the microservice authentication update purpose to rank defect categories to identify the few causes responsible for most incidents; operational mechanism: A Pareto chart sorts category contributions and often adds cumulative percentages; specific limitation: It supports prioritization but does not establish root cause by itself.

Incorrect Answers

A:

This behavior would demonstrate Scatter diagram for test whether two numeric variables appear associated across observations, rather than Pareto chart for rank defect categories to identify the few causes responsible for most incidents in the microservice authentication update; functional evidence: A scatterplot reveals direction and strength of a possible relationship; qualification to consider: A visible correlation does not prove one variable causes the other.

C:

This behavior would demonstrate Velocity chart for compare a team's completed story points across successive iterations, rather than Pareto chart for rank defect categories to identify the few causes responsible for most incidents in the microservice authentication update; operational mechanism: Velocity tracks observed delivery capacity to inform short-term forecasting; specific limitation: It should not be used to compare unrelated teams as a productivity ranking.

D:

This behavior would demonstrate Burnup chart for show delivered work against a separately visible total scope line, rather than Pareto chart for rank defect categories to identify the few causes responsible for most incidents in the microservice authentication update; functional evidence: Burnup charts display accumulated completion and may reveal scope growth; qualification to consider: They do not by themselves explain why new work was added.

Question 393

The mobile enrollment service team has a specific outstanding requirement: record active blockers with assignment, severity, progress, and resolution. At the delivery review, which action or practice is the most appropriate response?

  1. Risk register
  2. Risk report
  3. Project dashboard
  4. Issue log

Explanation

Correct Answer

D:

Issue log fits the mobile enrollment service requirement to record active blockers with assignment, severity, progress, and resolution; operational mechanism: An issue log tracks realized delivery problems through closure; specific limitation: Forecast concerns alone belong in a risk register.

Incorrect Answers

A:

Risk register is intended to record future uncertainties with probability, impact, owner, and planned response, not to meet the mobile enrollment service requirement to record active blockers with assignment, severity, progress, and resolution; operational mechanism: The risk register tracks exposure before a potential event occurs; specific limitation: Actual current problems belong in issue tracking.

B:

Risk report is intended to summarize significant current exposures, trends, and response effectiveness for decision makers, not to meet the mobile enrollment service requirement to record active blockers with assignment, severity, progress, and resolution; operational mechanism: A risk report aggregates risk information for oversight; specific limitation: The underlying risk register holds event-level detail.

C:

Project dashboard is intended to present a compact set of current indicators and exceptions across project workstreams, not to meet the mobile enrollment service requirement to record active blockers with assignment, severity, progress, and resolution; the practical reason is: A dashboard consolidates metrics for quick monitoring; important boundary: A narrative status report can supply more context behind the numbers.

Question 394

For the payment-service migration, a draft plan relies only on Stakeholder register because the team wants to identify interested parties and their influence before engagement begins. A reviewer identifies a separate unmet obligation: decide which affected parties need close management versus routine communication. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Measurable success criteria
  2. Responsibility assignment matrix
  3. Stakeholder power-interest analysis
  4. Stakeholder register

Explanation

Correct Answer

C:

The payment-service migration plan must add Stakeholder power-interest analysis to decide which affected parties need close management versus routine communication; its current Stakeholder register is already intended to identify interested parties and their influence before engagement begins; functional evidence: Power-interest analysis evaluates influence and degree of concern for an initiative; qualification to consider: It supports engagement strategy rather than assigning developer work packages.

Incorrect Answers

A:

Measurable success criteria is intended to define evidence that stakeholders will use to judge final delivery success; that is different from the overlooked payment-service migration obligation to decide which affected parties need close management versus routine communication; the practical reason is: Success criteria state objectively testable target outcomes; important boundary: General aspirations alone do not provide an acceptance threshold.

B:

Responsibility assignment matrix is intended to make ownership and consultation relationships explicit for important deliverables; that is different from the overlooked payment-service migration obligation to decide which affected parties need close management versus routine communication; the practical reason is: A RAM maps activities to roles and their responsibilities; important boundary: It avoids gaps and overlapping claims of authority.

D:

Stakeholder register is already serving identify interested parties and their influence before engagement begins in the payment-service migration; the corrected plan must also address the unmet obligation to decide which affected parties need close management versus routine communication; operational mechanism: A stakeholder register records people and groups affected by the project; specific limitation: The communication plan can then tailor updates to their needs.

Question 395

The device enrollment automation team has a specific outstanding requirement: model a range of schedule or cost outcomes by repeatedly sampling uncertain estimates. At the planning review, which action or practice is the most appropriate response?

  1. Quantitative risk assessment
  2. Monte Carlo simulation
  3. Risk-to-issue transition
  4. Fallback plan

Explanation

Correct Answer

B:

Monte Carlo simulation fits the device enrollment automation requirement to model a range of schedule or cost outcomes by repeatedly sampling uncertain estimates; operational mechanism: Simulation produces probability distributions rather than one deterministic date; specific limitation: Its results depend on the chosen input distributions and correlations.

Incorrect Answers

A:

Quantitative risk assessment is intended to estimate potential cost or completion-time effects using numeric probability models, not to meet the device enrollment automation requirement to model a range of schedule or cost outcomes by repeatedly sampling uncertain estimates; the practical reason is: Quantitative analysis evaluates numerical exposure or distributions of possible outcomes; important boundary: It needs defensible assumptions and is not merely a high-medium-low label.

C:

Risk-to-issue transition is intended to move a forecast risk into active issue management after the event occurs, not to meet the device enrollment automation requirement to model a range of schedule or cost outcomes by repeatedly sampling uncertain estimates; the practical reason is: A realized risk becomes an issue requiring action, tracking, and escalation; important boundary: Keeping it only as a future possibility would hide a present delivery obstacle.

D:

Fallback plan is intended to define a secondary response if the initial contingency action does not work, not to meet the device enrollment automation requirement to model a range of schedule or cost outcomes by repeatedly sampling uncertain estimates; the practical reason is: A fallback plan provides another route when the first risk response is insufficient; important boundary: It should have activation criteria and available resources of its own.

Question 396

A engineering change-management system design review reduces a task’s pessimistic duration from 13 to 10 days while optimistic 3 and most likely 7 stay unchanged. By how much does weighted expected duration fall?

  1. 0 days
  2. 3 days
  3. 6.83333 days
  4. 0.5 days

Explanation

Correct Answer

D:

PERT falls from 7.33333 to 6.83333 days; improvement = 0.5 day. These stated figures yield 0.5 days for the requested PERT reduction in the engineering change-management system case.

Incorrect Answers

A:

A changed pessimistic bound does affect the PERT weighted mean. The resulting 0 days does not match the requested PERT reduction for the engineering change-management system: the governing arithmetic is PERT falls from 7.33333 to 6.83333 days; improvement = 0.5 day, yielding 0.5 days.

B:

This treats the entire worst-case reduction as the weighted change. The resulting 3 days does not match the requested PERT reduction for the engineering change-management system: the governing arithmetic is PERT falls from 7.33333 to 6.83333 days; improvement = 0.5 day, yielding 0.5 days.

C:

This is the revised expectation, not the difference. The resulting 6.83333 days does not match the requested PERT reduction for the engineering change-management system: the governing arithmetic is PERT falls from 7.33333 to 6.83333 days; improvement = 0.5 day, yielding 0.5 days.

Question 397

For the cloud workload relocation, a draft plan relies only on Issue external status reporting because the team wants to send a sponsor-approved project summary to an outside customer or partner. A reviewer identifies a separate unmet obligation: recalculate likely completion dates after task durations or dependencies change. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Monitor vendor performance
  2. Revise schedule forecast
  3. Issue external status reporting
  4. Enforce vendor engagement rules

Explanation

Correct Answer

B:

The cloud workload relocation plan must add Revise schedule forecast to recalculate likely completion dates after task durations or dependencies change; its current Issue external status reporting is already intended to send a sponsor-approved project summary to an outside customer or partner; functional evidence: Schedule forecast updates show probable outcomes from current progress; qualification to consider: They do not automatically authorize a new baseline.

Incorrect Answers

A:

Monitor vendor performance is intended to check a contractor's milestones and quality against the agreed SOW; that is different from the overlooked cloud workload relocation obligation to recalculate likely completion dates after task durations or dependencies change; functional evidence: Vendor monitoring uses contractual deliverables and measures to detect slippage; qualification to consider: Paying an invoice without validation does not establish performance.

C:

Issue external status reporting is already serving send a sponsor-approved project summary to an outside customer or partner in the cloud workload relocation; the corrected plan must also address the unmet obligation to recalculate likely completion dates after task durations or dependencies change; operational mechanism: External status reports communicate relevant commitments beyond the internal team; specific limitation: Sensitive internal details need not be shared indiscriminately.

D:

Enforce vendor engagement rules is intended to ensure subcontractors follow agreed access, communication, and work protocols; that is different from the overlooked cloud workload relocation obligation to recalculate likely completion dates after task durations or dependencies change; operational mechanism: Rules of engagement clarify permissible vendor behavior and escalation; specific limitation: A capable supplier still must comply with contract and site controls.

Question 398

For the branch-network refresh, a draft plan relies only on Detailed scope statement because the team wants to specify boundaries, major deliverables, assumptions, and exclusions for project execution. A reviewer identifies a separate unmet obligation: prepare deployment, business handoff, training, cutover, and stabilization activities. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Transition and release plan
  2. Detailed scope statement
  3. Prioritized product backlog
  4. Integrated project management plan

Explanation

Correct Answer

A:

The branch-network refresh plan must add Transition and release plan to prepare deployment, business handoff, training, cutover, and stabilization activities; its current Detailed scope statement is already intended to specify boundaries, major deliverables, assumptions, and exclusions for project execution; functional evidence: A transition plan describes how delivered capabilities will become supported operations; qualification to consider: A technically complete product still needs readiness for real use.

Incorrect Answers

B:

Detailed scope statement is already serving specify boundaries, major deliverables, assumptions, and exclusions for project execution in the branch-network refresh; the corrected plan must also address the unmet obligation to prepare deployment, business handoff, training, cutover, and stabilization activities; functional evidence: A detailed scope statement makes proposed work sufficiently clear to control additions; qualification to consider: It supports decomposition and acceptance criteria.

C:

Prioritized product backlog is intended to maintain an ordered inventory of agile product features awaiting implementation; that is different from the overlooked branch-network refresh obligation to prepare deployment, business handoff, training, cutover, and stabilization activities; the practical reason is: The backlog captures work candidates and their relative product priority; important boundary: Not every item is a committed sprint deliverable.

D:

Integrated project management plan is intended to combine subsidiary plans, baselines, and governance into the delivery reference; that is different from the overlooked branch-network refresh obligation to prepare deployment, business handoff, training, cutover, and stabilization activities; functional evidence: The integrated plan coordinates scope, schedule, cost, quality, risks, and stakeholders; qualification to consider: Fragmented plans can produce contradictory assumptions.

Question 399

In the supplier onboarding portal, the team proposes the practice Kanban to visualize incoming tickets and limit work in progress to improve continuous flow. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. SAFe provides planning and coordination patterns for agile delivery across multiple teams.
  2. An SDLC model organizes software work through analysis, design, build, test, deployment, and support.
  3. This approach uses a visible workflow and work-in-progress limits to expose queues and bottlenecks.
  4. This approach integrates development and operations responsibilities across delivery and support.
  5. This approach organizes work into sprints with specific accountabilities, events, and artifacts.

Explanation

Correct Answer

C:

This is observable evidence of Kanban for the supplier onboarding portal purpose to visualize incoming tickets and limit work in progress to improve continuous flow; operational mechanism: Kanban uses a visible workflow and work-in-progress limits to expose queues and bottlenecks; specific limitation: It does not require fixed-length iterations or a prescribed sprint role set.

Incorrect Answers

A:

This behavior would demonstrate Scaled Agile Framework (SAFe) for coordinate several agile teams working on a shared large solution, rather than Kanban for visualize incoming tickets and limit work in progress to improve continuous flow in the supplier onboarding portal; the practical reason is: SAFe provides planning and coordination patterns for agile delivery across multiple teams; important boundary: Single-team Scrum alone does not define all enterprise-level synchronization needs.

B:

This behavior would demonstrate Software development life cycle (SDLC) for describe the stages a software solution traverses from requirements to maintenance, rather than Kanban for visualize incoming tickets and limit work in progress to improve continuous flow in the supplier onboarding portal; the practical reason is: An SDLC model organizes software work through analysis, design, build, test, deployment, and support; important boundary: It is a life-cycle description rather than one specific project-governance method.

D:

This behavior would demonstrate DevOps for reduce friction between software delivery and IT operations through collaboration and automation, rather than Kanban for visualize incoming tickets and limit work in progress to improve continuous flow in the supplier onboarding portal; operational mechanism: DevOps integrates development and operations responsibilities across delivery and support; specific limitation: Security can participate, but explicit security-by-design is the DevSecOps emphasis.

E:

This behavior would demonstrate Scrum for deliver complex software incrementally with a product backlog and short timeboxed iterations, rather than Kanban for visualize incoming tickets and limit work in progress to improve continuous flow in the supplier onboarding portal; the practical reason is: Scrum organizes work into sprints with specific accountabilities, events, and artifacts; important boundary: It relies on empirical inspection rather than finalizing every requirement at the outset.

Question 400

In the payment-service migration, the team proposes the practice Wiki knowledge base to publish living troubleshooting instructions that many support staff can maintain. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Whiteboards support spatial collaborative sketching and grouping.
  2. Calendaring tools coordinate schedules, reminders, and invitees.
  3. File sharing centralizes content access and permissions across a team.
  4. In-person workshops support rich live engagement and physical collaboration.
  5. Video meetings provide real-time conversation and shared visual context.
  6. Wikis organize linked operational knowledge with accessible revision history.

Explanation

Correct Answer

F:

This is observable evidence of Wiki knowledge base for the payment-service migration purpose to publish living troubleshooting instructions that many support staff can maintain; functional evidence: Wikis organize linked operational knowledge with accessible revision history; qualification to consider: Their access and editorial rules should protect sensitive information.

Incorrect Answers

A:

This behavior would demonstrate Virtual whiteboard for map process ideas and relationships visually during a remote brainstorming session, rather than Wiki knowledge base for publish living troubleshooting instructions that many support staff can maintain in the payment-service migration; operational mechanism: Whiteboards support spatial collaborative sketching and grouping; specific limitation: They are not ideal as the sole authoritative contract repository.

B:

This behavior would demonstrate Calendar scheduler for find common available times and distribute meeting invitations, rather than Wiki knowledge base for publish living troubleshooting instructions that many support staff can maintain in the payment-service migration; functional evidence: Calendaring tools coordinate schedules, reminders, and invitees; qualification to consider: They do not by themselves run a meeting or capture decisions.

C:

This behavior would demonstrate Shared file repository for give authorized collaborators a central location for working documents, rather than Wiki knowledge base for publish living troubleshooting instructions that many support staff can maintain in the payment-service migration; functional evidence: File sharing centralizes content access and permissions across a team; qualification to consider: It should be governed by classification and retention rules.

D:

This behavior would demonstrate Face-to-face workshop for resolve a complex sensitive disagreement where direct collaboration is valuable, rather than Wiki knowledge base for publish living troubleshooting instructions that many support staff can maintain in the payment-service migration; operational mechanism: In-person workshops support rich live engagement and physical collaboration; specific limitation: Travel and availability cost more than asynchronous channels.

E:

This behavior would demonstrate Video conference for discuss a design visually with dispersed staff who need live interaction, rather than Wiki knowledge base for publish living troubleshooting instructions that many support staff can maintain in the payment-service migration; the practical reason is: Video meetings provide real-time conversation and shared visual context; important boundary: Time zones and connectivity can limit attendance.

CompTIA Project+ (PK0-005) Practice Tests