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

Question 740

In the ERP integration program, the team proposes the practice Control scope creep to stop informal feature additions from bypassing approved scope and change procedures. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Preliminary review identifies invalid or incomplete requests early in the workflow.
  2. Scope control compares requested work with the approved baseline and routes deviations through change control.
  3. Validation checks actual results against the approved request and expected outcome.
  4. The change log captures proposed scope changes before decision and implementation.
  5. Plan updates make an approved decision operational for subsequent tracking.

Explanation

Correct Answer

B:

This is observable evidence of Control scope creep for the ERP integration program purpose to stop informal feature additions from bypassing approved scope and change procedures; operational mechanism: Scope control compares requested work with the approved baseline and routes deviations through change control; specific limitation: Well-intentioned extras still consume time and resources unless authorized.

Incorrect Answers

A:

This behavior would demonstrate Conduct a preliminary change review for screen a request for completeness, duplication, and obvious policy conflicts before detailed analysis, rather than Control scope creep for stop informal feature additions from bypassing approved scope and change procedures in the ERP integration program; functional evidence: Preliminary review identifies invalid or incomplete requests early in the workflow; qualification to consider: It does not itself grant final approval for a material baseline change.

C:

This behavior would demonstrate Validate the implemented change for confirm that a deployed amendment achieves the agreed acceptance criteria, rather than Control scope creep for stop informal feature additions from bypassing approved scope and change procedures in the ERP integration program; the practical reason is: Validation checks actual results against the approved request and expected outcome; important boundary: A completed work ticket is not sufficient proof of intended business behavior.

D:

This behavior would demonstrate Register a change request for create an auditable record when a stakeholder proposes unplanned functionality, rather than Control scope creep for stop informal feature additions from bypassing approved scope and change procedures in the ERP integration program; operational mechanism: The change log captures proposed scope changes before decision and implementation; specific limitation: A verbal request alone cannot establish authorization or a decision trail.

E:

This behavior would demonstrate Update the approved project plan for reflect an authorized change in schedules, budget, and scope baselines as required, rather than Control scope creep for stop informal feature additions from bypassing approved scope and change procedures in the ERP integration program; operational mechanism: Plan updates make an approved decision operational for subsequent tracking; specific limitation: They should follow authorization rather than silently legitimize unauthorized work.

Question 741

In the customer-support chatbot pilot, the team proposes the practice Scheduled maintenance window to plan a disruptive infrastructure cutover during an approved low-impact period. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Change approval enforces the required operational decision authority.
  2. A maintenance window aligns expected service interruption with operations constraints.
  3. Post-change verification checks expected results before declaring success.
  4. Shared responsibility assigns control ownership according to the cloud service model.
  5. Notifications prepare stakeholders for expected impact and timing.

Explanation

Correct Answer

B:

This is observable evidence of Scheduled maintenance window for the customer-support chatbot pilot purpose to plan a disruptive infrastructure cutover during an approved low-impact period; the practical reason is: A maintenance window aligns expected service interruption with operations constraints; important boundary: The window should be communicated and supported by recovery plans.

Incorrect Answers

A:

This behavior would demonstrate Formal production change approval for obtain authorized acceptance of operational risk before modifying a live environment, rather than Scheduled maintenance window for plan a disruptive infrastructure cutover during an approved low-impact period in the customer-support chatbot pilot; functional evidence: Change approval enforces the required operational decision authority; qualification to consider: Passing tests does not itself bypass mandatory authorization.

C:

This behavior would demonstrate Post-change validation checks for confirm functionality and monitoring are healthy after an infrastructure modification, rather than Scheduled maintenance window for plan a disruptive infrastructure cutover during an approved low-impact period in the customer-support chatbot pilot; operational mechanism: Post-change verification checks expected results before declaring success; specific limitation: A green deployment command alone does not prove service health.

D:

This behavior would demonstrate Cloud shared-responsibility review for identify which change tasks belong to the hosted provider versus the customer, rather than Scheduled maintenance window for plan a disruptive infrastructure cutover during an approved low-impact period in the customer-support chatbot pilot; operational mechanism: Shared responsibility assigns control ownership according to the cloud service model; specific limitation: Moving to hosted infrastructure does not erase customer access and configuration duties.

E:

This behavior would demonstrate Customer downtime notification for alert affected users before a planned change interrupts service, rather than Scheduled maintenance window for plan a disruptive infrastructure cutover during an approved low-impact period in the customer-support chatbot pilot; the practical reason is: Notifications prepare stakeholders for expected impact and timing; important boundary: They do not by themselves verify the change's technical success.

Question 742

The smart-building control upgrade team already uses Revise schedule forecast to recalculate likely completion dates after task durations or dependencies change. A new workstream must also direct work according to the authorized project plan and agreed deliverables. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Revise schedule forecast
  2. Execute baseline-approved tasks
  3. Train impacted employees
  4. Issue external status reporting
  5. Update actual project expenditure

Explanation

Correct Answer

B:

Adding Execute baseline-approved tasks addresses the new smart-building control upgrade need to direct work according to the authorized project plan and agreed deliverables; Revise schedule forecast already serves the separate need to recalculate likely completion dates after task durations or dependencies change; functional evidence: Execution converts planned work into products through assigned activities; qualification to consider: Material deviations still require appropriate change control.

Incorrect Answers

A:

Revise schedule forecast is already present in the smart-building control upgrade to recalculate likely completion dates after task durations or dependencies change; repeating it does not fulfill the distinct requirement to direct work according to the authorized project plan and agreed deliverables; functional evidence: Schedule forecast updates show probable outcomes from current progress; qualification to consider: They do not automatically authorize a new baseline.

C:

Train impacted employees would instead address prepare users whose daily processes will change after a new IT rollout; the smart-building control upgrade still needs to direct work according to the authorized project plan and agreed deliverables, in addition to its existing Revise schedule forecast; functional evidence: Organizational change training enables staff to perform future workflows; qualification to consider: Technical deployment alone does not guarantee adoption.

D:

Issue external status reporting would instead address send a sponsor-approved project summary to an outside customer or partner; the smart-building control upgrade still needs to direct work according to the authorized project plan and agreed deliverables, in addition to its existing Revise schedule forecast; operational mechanism: External status reports communicate relevant commitments beyond the internal team; specific limitation: Sensitive internal details need not be shared indiscriminately.

E:

Update actual project expenditure would instead address record incurred costs so variance and remaining funds can be monitored; the smart-building control upgrade still needs to direct work according to the authorized project plan and agreed deliverables, in addition to its existing Revise schedule forecast; the practical reason is: Budget updates compare committed and actual spending with the authorized reference; important boundary: Ignoring new invoices creates an inaccurate completion forecast.

Question 743

The cross-border reporting service team already uses Conferencing platform to host distributed participants with audio, screen sharing, and meeting controls. A new workstream must also find common available times and distribute meeting invitations. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Real-time polling
  2. Printed meeting packet
  3. Wiki knowledge base
  4. Conferencing platform
  5. Calendar scheduler

Explanation

Correct Answer

E:

Adding Calendar scheduler addresses the new cross-border reporting service need to find common available times and distribute meeting invitations; Conferencing platform already serves the separate need to host distributed participants with audio, screen sharing, and meeting controls; operational mechanism: Calendaring tools coordinate schedules, reminders, and invitees; specific limitation: They do not by themselves run a meeting or capture decisions.

Incorrect Answers

A:

Real-time polling would instead address capture quick preferences from a large group during a facilitated meeting; the cross-border reporting service still needs to find common available times and distribute meeting invitations, in addition to its existing Conferencing platform; operational mechanism: Live polling gathers immediate structured feedback; specific limitation: A majority vote is not automatically a contractually valid approval.

B:

Printed meeting packet would instead address provide approved reference materials to participants in a network-restricted location; the cross-border reporting service still needs to find common available times and distribute meeting invitations, in addition to its existing Conferencing platform; the practical reason is: Print media allows offline distribution of fixed information; important boundary: Revision and secure disposal become important once printed.

C:

Wiki knowledge base would instead address publish living troubleshooting instructions that many support staff can maintain; the cross-border reporting service still needs to find common available times and distribute meeting invitations, in addition to its existing Conferencing platform; operational mechanism: Wikis organize linked operational knowledge with accessible revision history; specific limitation: Their access and editorial rules should protect sensitive information.

D:

Conferencing platform is already present in the cross-border reporting service to host distributed participants with audio, screen sharing, and meeting controls; repeating it does not fulfill the distinct requirement to find common available times and distribute meeting invitations; the practical reason is: Conferencing tools enable remote synchronous sessions; important boundary: They need accessibility and connectivity planning for attendees.

Question 744

During the microservice authentication update, the stakeholder liaison has two distinct obligations: (1) describe the stages a software solution traverses from requirements to maintenance; (2) govern an initiative through defined management stages and business-case justification. Which TWO complementary practices satisfy the two different obligations? Choose TWO.

  1. Software development life cycle (SDLC)
  2. Scrum
  3. PRINCE2
  4. Scaled Agile Framework (SAFe)
  5. DevOps
  6. Extreme programming (XP)

Explanation

Correct Answers

A:

An SDLC model organizes software work through analysis, design, build, test, deployment, and support; in the microservice authentication update, this fulfills requirement (1) to describe the stages a software solution traverses from requirements to maintenance. For the microservice authentication update, it is a life-cycle description rather than one specific project-governance method.

C:

PRINCE2 emphasizes continued business justification, roles, stage controls, and exceptions; in the microservice authentication update, this fulfills requirement (2) to govern an initiative through defined management stages and business-case justification. For the microservice authentication update, it is a governance-oriented project method rather than a source-code branching practice.

Incorrect Answers

B:

Scrum organizes work into sprints with specific accountabilities, events, and artifacts; this differs from the listed needs for the microservice authentication update, which are describe the stages a software solution traverses from requirements to maintenance and govern an initiative through defined management stages and business-case justification. In the microservice authentication update, it relies on empirical inspection rather than finalizing every requirement at the outset.

D:

SAFe provides planning and coordination patterns for agile delivery across multiple teams; this differs from the listed needs for the microservice authentication update, which are describe the stages a software solution traverses from requirements to maintenance and govern an initiative through defined management stages and business-case justification. In the microservice authentication update, single-team Scrum alone does not define all enterprise-level synchronization needs.

E:

DevOps integrates development and operations responsibilities across delivery and support; this differs from the listed needs for the microservice authentication update, which are describe the stages a software solution traverses from requirements to maintenance and govern an initiative through defined management stages and business-case justification. In the microservice authentication update, security can participate, but explicit security-by-design is the DevSecOps emphasis.

F:

Extreme programming applies disciplined engineering practices and rapid developer feedback; this differs from the listed needs for the microservice authentication update, which are describe the stages a software solution traverses from requirements to maintenance and govern an initiative through defined management stages and business-case justification. In the microservice authentication update, it is a software development practice set, not an enterprise portfolio framework.

Question 745

For the online reservation system, a draft plan relies only on Gantt chart because the team wants to display planned activities as bars against calendar dates with overlapping durations. A reviewer identifies a separate unmet obligation: show predecessor relationships between activities to analyze task sequencing. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Project network diagram
  2. Budget burndown chart
  3. Milestone chart
  4. Gantt chart

Explanation

Correct Answer

A:

The online reservation system plan must add Project network diagram to show predecessor relationships between activities to analyze task sequencing; its current Gantt chart is already intended to display planned activities as bars against calendar dates with overlapping durations; operational mechanism: A network diagram represents tasks and logical dependencies as a graph; specific limitation: It emphasizes paths rather than a simple list of reporting dates.

Incorrect Answers

B:

Budget burndown chart is intended to show how remaining budget decreases as project spending occurs; that is different from the overlooked online reservation system obligation to show predecessor relationships between activities to analyze task sequencing; the practical reason is: A budget burndown visualizes budget consumption over time; important boundary: It does not alone explain the deliverables earned for that spending.

C:

Milestone chart is intended to give executives a compact view of major achievement dates without every underlying task; that is different from the overlooked online reservation system obligation to show predecessor relationships between activities to analyze task sequencing; the practical reason is: A milestone chart highlights significant events and completion checkpoints; important boundary: It omits the activity-level effort detail shown on full schedules.

D:

Gantt chart is already serving display planned activities as bars against calendar dates with overlapping durations in the online reservation system; the corrected plan must also address the unmet obligation to show predecessor relationships between activities to analyze task sequencing; functional evidence: A Gantt chart plots tasks and planned timing along a timeline; qualification to consider: It helps see schedule relationships but does not by itself prove user acceptance.

Question 746

For the ERP integration program, a draft plan relies only on Plan operational training because the team wants to prepare support staff and users to operate the delivered system after release. A reviewer identifies a separate unmet obligation: compare required effort and skills with people and equipment actually available. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Plan operational training
  2. Audience-specific release briefing
  3. Assess available resource capacity
  4. Train the project team

Explanation

Correct Answer

C:

The ERP integration program plan must add Assess available resource capacity to compare required effort and skills with people and equipment actually available; its current Plan operational training is already intended to prepare support staff and users to operate the delivered system after release; functional evidence: Resource assessment exposes capacity constraints before assigning work; qualification to consider: It reduces commitments based on imaginary availability.

Incorrect Answers

A:

Plan operational training is already serving prepare support staff and users to operate the delivered system after release in the ERP integration program; the corrected plan must also address the unmet obligation to compare required effort and skills with people and equipment actually available; the practical reason is: Operational training closes adoption and support skill gaps before handoff; important boundary: Deployment without trained owners can leave an unusable service.

B:

Audience-specific release briefing is intended to adapt go-live messages for internal support teams and external affected customers; that is different from the overlooked ERP integration program obligation to compare required effort and skills with people and equipment actually available; the practical reason is: Release briefing plans tailor content and channels to stakeholder responsibilities; important boundary: An internal technical runbook is not a complete external notification.

D:

Train the project team is intended to close tool or workflow knowledge gaps before work depends on new skills; that is different from the overlooked ERP integration program obligation to compare required effort and skills with people and equipment actually available; functional evidence: Training improves team readiness to use unfamiliar methods and platforms; qualification to consider: An untrained assignment creates quality and schedule risk.

Question 747

For the customer loyalty application, a draft plan relies only on Hybrid delivery because the team wants to combine stage-gated infrastructure procurement with iterative application development. A reviewer identifies a separate unmet obligation: keep scope and specifications stable before detailed design and implementation. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Dedicated cross-functional team
  2. Hybrid delivery
  3. Incremental delivery
  4. Iterative prototyping
  5. Timeboxed work
  6. Predictive planning

Explanation

Correct Answer

F:

The customer loyalty application plan must add Predictive planning to keep scope and specifications stable before detailed design and implementation; its current Hybrid delivery is already intended to combine stage-gated infrastructure procurement with iterative application development; functional evidence: Predictive delivery establishes substantial requirements and plans before execution; qualification to consider: Uncontrolled changes later normally require formal impact review.

Incorrect Answers

A:

Dedicated cross-functional team is intended to avoid repeated handoffs by assigning design, build, and test capabilities within one stable team; that is different from the overlooked customer loyalty application obligation to keep scope and specifications stable before detailed design and implementation; functional evidence: Cross-functional team composition supports end-to-end delivery and rapid feedback; qualification to consider: Shared specialists can become bottlenecks if their allocation is not planned.

B:

Hybrid delivery is already serving combine stage-gated infrastructure procurement with iterative application development in the customer loyalty application; the corrected plan must also address the unmet obligation to keep scope and specifications stable before detailed design and implementation; operational mechanism: Hybrid delivery intentionally applies different delivery methods to different workstreams; specific limitation: Its coordination plan must reconcile milestone dependencies and cadences.

C:

Incremental delivery is intended to release usable functions in slices rather than waiting for the entire feature set; that is different from the overlooked customer loyalty application obligation to keep scope and specifications stable before detailed design and implementation; operational mechanism: Incremental work adds deployable capability in successive deliveries; specific limitation: Each increment increases usable scope even when underlying features are not redesigned.

D:

Iterative prototyping is intended to show users successive mockups to discover usability requirements before final design; that is different from the overlooked customer loyalty application obligation to keep scope and specifications stable before detailed design and implementation; the practical reason is: Iterations test assumptions through repeated evaluation of a working model; important boundary: The purpose is learning and revision rather than declaring the first draft final.

E:

Timeboxed work is intended to protect a fixed short delivery interval while adjusting the amount of feasible work; that is different from the overlooked customer loyalty application obligation to keep scope and specifications stable before detailed design and implementation; the practical reason is: Timeboxing constrains an iteration's duration and forces priority decisions; important boundary: It does not guarantee that every initially proposed story will fit.

Question 748

The procurement automation rollout team has a specific outstanding requirement: document a contractual decision for an external supplier with a durable record. At the planning review, which action or practice is the most appropriate response?

  1. Formal written notice
  2. Informal conversation
  3. Archived project correspondence
  4. Controlled confidential channel

Explanation

Correct Answer

A:

Formal written notice fits the procurement automation rollout requirement to document a contractual decision for an external supplier with a durable record; functional evidence: Formal written communication provides an attributable and retrievable decision trail; qualification to consider: A casual chat may not satisfy prescribed contract notice terms.

Incorrect Answers

B:

Informal conversation is intended to resolve a minor everyday coordination question without a governance decision, not to meet the procurement automation rollout requirement to document a contractual decision for an external supplier with a durable record; operational mechanism: Informal communication supports quick working relationships and clarifications; specific limitation: Substantive approvals still need the records and channels required by the plan.

C:

Archived project correspondence is intended to preserve decision and approval history for later handoff or audit, not to meet the procurement automation rollout requirement to document a contractual decision for an external supplier with a durable record; the practical reason is: Communication archiving retains retrievable evidence of what was agreed and when; important boundary: It is separate from merely notifying a person in real time.

D:

Controlled confidential channel is intended to send sensitive delivery data only to authorized recipients using approved protection, not to meet the procurement automation rollout requirement to document a contractual decision for an external supplier with a durable record; the practical reason is: Confidential communication restricts disclosure through access and secure channels; important boundary: Convenience alone cannot override data-handling requirements.

Question 749

The service quality and software-release reporting Pareto categories have counts 48, 30, 14, 8. What is the percentage-point difference in share between the two largest categories?

  1. 18 percentage points
  2. 19 percentage points
  3. 48 percentage points
  4. 30 percentage points

Explanation

Correct Answer

A:

Share difference=(48−30)/100×100=18 percentage points. These stated figures yield 18 percentage points for the requested category share gap in the service quality and software-release reporting case.

Incorrect Answers

B:

An adjustment beyond the stated information has no quantitative basis. The resulting 19 percentage points does not match the requested category share gap for the service quality and software-release reporting: the governing arithmetic is Share difference=(48−30)/100×100=18 percentage points, yielding 18 percentage points.

C:

This is the largest category’s complete share. The resulting 48 percentage points does not match the requested category share gap for the service quality and software-release reporting: the governing arithmetic is Share difference=(48−30)/100×100=18 percentage points, yielding 18 percentage points.

D:

This is the second category’s share. The resulting 30 percentage points does not match the requested category share gap for the service quality and software-release reporting: the governing arithmetic is Share difference=(48−30)/100×100=18 percentage points, yielding 18 percentage points.

Question 750

For the virtual desktop rollout, a draft plan relies only on Confirm high-level solution design because the team wants to select a feasible architecture direction that meets the charter's major constraints. A reviewer identifies a separate unmet obligation: define how project documents and data will be stored, accessed, retained, and disposed. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Set records retention rules
  2. Agree communication channels
  3. Define access requirements
  4. Confirm high-level solution design
  5. Review inherited project artifacts

Explanation

Correct Answer

A:

The virtual desktop rollout plan must add Set records retention rules to define how project documents and data will be stored, accessed, retained, and disposed; its current Confirm high-level solution design is already intended to select a feasible architecture direction that meets the charter's major constraints; operational mechanism: Records management identifies custody, classification, and retention needs; specific limitation: It should be designed before uncontrolled document proliferation.

Incorrect Answers

B:

Agree communication channels is intended to establish where project participants will exchange approvals and operational updates; that is different from the overlooked virtual desktop rollout obligation to define how project documents and data will be stored, accessed, retained, and disposed; functional evidence: Agreed channels reduce missed information and conflicting records; qualification to consider: Different audiences may require different cadence and confidentiality levels.

C:

Define access requirements is intended to specify which participants require permissions to proposed environments and documents; that is different from the overlooked virtual desktop rollout obligation to define how project documents and data will be stored, accessed, retained, and disposed; operational mechanism: Access requirements connect work roles with appropriate privileges; specific limitation: Permissions should be least-privilege and reviewed as membership changes.

D:

Confirm high-level solution design is already serving select a feasible architecture direction that meets the charter's major constraints in the virtual desktop rollout; the corrected plan must also address the unmet obligation to define how project documents and data will be stored, accessed, retained, and disposed; the practical reason is: Early solution design resolves critical technical assumptions for planning; important boundary: Detailed build specifications may still be refined later.

E:

Review inherited project artifacts is intended to identify existing contracts, requirements, and constraints before re-planning a handed-over project; that is different from the overlooked virtual desktop rollout obligation to define how project documents and data will be stored, accessed, retained, and disposed; the practical reason is: Reviewing inherited artifacts prevents accidental conflict with previous commitments; important boundary: A new team should not treat prior approvals as nonexistent.

CompTIA Project+ (PK0-005) Practice Tests