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

Question 1070

The procurement automation rollout team already uses Informal conversation to resolve a minor everyday coordination question without a governance decision. A new workstream must also document a contractual decision for an external supplier with a durable record. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Archived project correspondence
  2. Formal written notice
  3. Synchronous conversation
  4. Informal conversation

Explanation

Correct Answer

B:

Adding Formal written notice addresses the new procurement automation rollout need to document a contractual decision for an external supplier with a durable record; Informal conversation already serves the separate need to resolve a minor everyday coordination question without a governance decision; the practical reason is: Formal written communication provides an attributable and retrievable decision trail; important boundary: A casual chat may not satisfy prescribed contract notice terms.

Incorrect Answers

A:

Archived project correspondence would instead address preserve decision and approval history for later handoff or audit; the procurement automation rollout still needs to document a contractual decision for an external supplier with a durable record, in addition to its existing Informal conversation; operational mechanism: Communication archiving retains retrievable evidence of what was agreed and when; specific limitation: It is separate from merely notifying a person in real time.

C:

Synchronous conversation would instead address resolve a time-sensitive ambiguity through immediate two-way exchange; the procurement automation rollout still needs to document a contractual decision for an external supplier with a durable record, in addition to its existing Informal conversation; the practical reason is: Synchronous communication enables live questioning and rapid clarification; important boundary: It requires participants to overlap in time.

D:

Informal conversation is already present in the procurement automation rollout to resolve a minor everyday coordination question without a governance decision; repeating it does not fulfill the distinct requirement to document a contractual decision for an external supplier with a durable record; functional evidence: Informal communication supports quick working relationships and clarifications; qualification to consider: Substantive approvals still need the records and channels required by the plan.

Question 1071

The ERP integration program team already uses Conduct a phase-gate review to check defined exit criteria before funding or starting the next controlled phase. A new workstream must also send a sponsor-approved project summary to an outside customer or partner. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Report a risk trigger
  2. Update actual project expenditure
  3. Conduct a phase-gate review
  4. Issue external status reporting

Explanation

Correct Answer

D:

Adding Issue external status reporting addresses the new ERP integration program need to send a sponsor-approved project summary to an outside customer or partner; Conduct a phase-gate review already serves the separate need to check defined exit criteria before funding or starting the next controlled phase; functional evidence: External status reports communicate relevant commitments beyond the internal team; qualification to consider: Sensitive internal details need not be shared indiscriminately.

Incorrect Answers

A:

Report a risk trigger would instead address tell decision makers that a named uncertainty's likelihood or impact has changed; the ERP integration program still needs to send a sponsor-approved project summary to an outside customer or partner, in addition to its existing Conduct a phase-gate review; the practical reason is: Risk reporting highlights evolving exposure and response triggers; important boundary: It is forward-looking unless the event already became an active issue.

B:

Update actual project expenditure would instead address record incurred costs so variance and remaining funds can be monitored; the ERP integration program still needs to send a sponsor-approved project summary to an outside customer or partner, in addition to its existing Conduct a phase-gate review; operational mechanism: Budget updates compare committed and actual spending with the authorized reference; specific limitation: Ignoring new invoices creates an inaccurate completion forecast.

C:

Conduct a phase-gate review is already present in the ERP integration program to check defined exit criteria before funding or starting the next controlled phase; repeating it does not fulfill the distinct requirement to send a sponsor-approved project summary to an outside customer or partner; operational mechanism: A phase gate provides a formal continue, redirect, or stop decision; specific limitation: Simply reaching a calendar milestone does not prove readiness.

Question 1072

The customer-support application release team already uses Run chart to plot an operational metric over time to spot patterns or trends. A new workstream must also compare a team's completed story points across successive iterations. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Velocity chart
  2. Pareto chart
  3. Control chart
  4. Run chart

Explanation

Correct Answer

A:

Adding Velocity chart addresses the new customer-support application release need to compare a team's completed story points across successive iterations; Run chart already serves the separate need to plot an operational metric over time to spot patterns or trends; the practical reason is: Velocity tracks observed delivery capacity to inform short-term forecasting; important boundary: It should not be used to compare unrelated teams as a productivity ranking.

Incorrect Answers

B:

Pareto chart would instead address rank defect categories to identify the few causes responsible for most incidents; the customer-support application release still needs to compare a team's completed story points across successive iterations, in addition to its existing Run chart; the practical reason is: A Pareto chart sorts category contributions and often adds cumulative percentages; important boundary: It supports prioritization but does not establish root cause by itself.

C:

Control chart would instead address monitor a process metric over time against calculated statistical control limits; the customer-support application release still needs to compare a team's completed story points across successive iterations, in addition to its existing Run chart; functional evidence: Control charts help distinguish common-cause variation from unusual signals; qualification to consider: A control-limit breach calls for investigation, not an assumption about its cause.

D:

Run chart is already present in the customer-support application release to plot an operational metric over time to spot patterns or trends; repeating it does not fulfill the distinct requirement to compare a team's completed story points across successive iterations; operational mechanism: Run charts display observations in chronological order; specific limitation: Without control limits they do not establish formal statistical control.

Question 1073

The supplier onboarding portal team already uses Release approval gate to require a named release authority to review acceptance and risk evidence before rollout. A new workstream must also deploy an approved release to the live service used by actual customers. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Production environment
  2. Automated test pipeline
  3. Continuous integration
  4. Release approval gate

Explanation

Correct Answer

A:

Adding Production environment addresses the new supplier onboarding portal need to deploy an approved release to the live service used by actual customers; Release approval gate already serves the separate need to require a named release authority to review acceptance and risk evidence before rollout; the practical reason is: Production hosts real operational transactions under active service controls; important boundary: Testing there without safeguards can harm users.

Incorrect Answers

B:

Automated test pipeline would instead address run repeatable checks on each software change before release; the supplier onboarding portal still needs to deploy an approved release to the live service used by actual customers, in addition to its existing Release approval gate; functional evidence: Automated tests provide consistent rapid evidence of specified behavior; qualification to consider: They complement rather than eliminate exploratory manual verification.

C:

Continuous integration would instead address merge changes frequently and run automatic builds and tests to detect conflicts early; the supplier onboarding portal still needs to deploy an approved release to the live service used by actual customers, in addition to its existing Release approval gate; operational mechanism: Continuous integration validates combined source updates through a shared pipeline; specific limitation: It does not necessarily deploy every successful build into production.

D:

Release approval gate is already present in the supplier onboarding portal to require a named release authority to review acceptance and risk evidence before rollout; repeating it does not fulfill the distinct requirement to deploy an approved release to the live service used by actual customers; functional evidence: A release gate makes go/no-go authorization explicit and traceable; qualification to consider: Successful test automation is input to the decision rather than an automatic waiver.

Question 1074

For the engineering change-management system, a draft plan relies only on Agree communication channels because the team wants to establish where project participants will exchange approvals and operational updates. A reviewer identifies a separate unmet obligation: select a feasible architecture direction that meets the charter's major constraints. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Review inherited project artifacts
  2. Conduct the kickoff meeting
  3. Agree communication channels
  4. Define access requirements
  5. Confirm high-level solution design

Explanation

Correct Answer

E:

The engineering change-management system plan must add Confirm high-level solution design to select a feasible architecture direction that meets the charter's major constraints; its current Agree communication channels is already intended to establish where project participants will exchange approvals and operational updates; functional evidence: Early solution design resolves critical technical assumptions for planning; qualification to consider: Detailed build specifications may still be refined later.

Incorrect Answers

A:

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 engineering change-management system obligation to select a feasible architecture direction that meets the charter's major constraints; functional evidence: Reviewing inherited artifacts prevents accidental conflict with previous commitments; qualification to consider: A new team should not treat prior approvals as nonexistent.

B:

Conduct the kickoff meeting is intended to align the team on objectives, roles, constraints, and initial ways of working; that is different from the overlooked engineering change-management system obligation to select a feasible architecture direction that meets the charter's major constraints; functional evidence: A kickoff introduces shared project direction and working expectations; qualification to consider: It is not the contract-closeout event at the end of delivery.

C:

Agree communication channels is already serving establish where project participants will exchange approvals and operational updates in the engineering change-management system; the corrected plan must also address the unmet obligation to select a feasible architecture direction that meets the charter's major constraints; operational mechanism: Agreed channels reduce missed information and conflicting records; specific limitation: Different audiences may require different cadence and confidentiality levels.

D:

Define access requirements is intended to specify which participants require permissions to proposed environments and documents; that is different from the overlooked engineering change-management system obligation to select a feasible architecture direction that meets the charter's major constraints; the practical reason is: Access requirements connect work roles with appropriate privileges; important boundary: Permissions should be least-privilege and reviewed as membership changes.

Question 1075

In the customer-billing replacement, the team proposes the practice Locally installed scheduling software to give a single planner offline access to a desktop project schedule. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Browser-based collaboration centralizes access and current plan data.
  2. A local installation runs on the user's workstation with limited cloud dependence.
  3. Diagramming tools represent logic, processes, and relationships visually.
  4. These techniques support numeric modeling, filtering, and comparisons.
  5. This approach supports durable asynchronous correspondence to a defined audience.

Explanation

Correct Answer

B:

This is observable evidence of Locally installed scheduling software for the customer-billing replacement purpose to give a single planner offline access to a desktop project schedule; the practical reason is: A local installation runs on the user's workstation with limited cloud dependence; important boundary: Sharing an authoritative version across many users requires additional coordination.

Incorrect Answers

A:

This behavior would demonstrate Browser-based collaborative scheduler for let multiple authorized staff edit shared plans without installing desktop software, rather than Locally installed scheduling software for give a single planner offline access to a desktop project schedule in the customer-billing replacement; functional evidence: Browser-based collaboration centralizes access and current plan data; qualification to consider: Network access and service availability can affect work.

C:

This behavior would demonstrate Diagramming application for create flowcharts showing how approval decisions and systems interact, rather than Locally installed scheduling software for give a single planner offline access to a desktop project schedule in the customer-billing replacement; the practical reason is: Diagramming tools represent logic, processes, and relationships visually; important boundary: They do not automatically calculate actual project costs.

D:

This behavior would demonstrate Spreadsheet for perform tabular cost calculations and resource forecasts with transparent formulas, rather than Locally installed scheduling software for give a single planner offline access to a desktop project schedule in the customer-billing replacement; operational mechanism: Spreadsheets support numeric modeling, filtering, and comparisons; specific limitation: They can introduce formula and version risks if poorly controlled.

E:

This behavior would demonstrate Email for send attributable written updates and attachments without requiring simultaneous attendance, rather than Locally installed scheduling software for give a single planner offline access to a desktop project schedule in the customer-billing replacement; the practical reason is: Email supports durable asynchronous correspondence to a defined audience; important boundary: High urgency may require a more immediate escalation channel.

Question 1076

Before using Risk register on the log monitoring deployment, the steering group asks about its limitations. Which qualification specifically prevents an overbroad interpretation of this practice for the goal to record future uncertainties with probability, impact, owner, and planned response?

  1. A task board alone does not show end-to-end requirement evidence.
  2. It does not itself prioritize project risk or resource allocations.
  3. Actual current problems belong in issue tracking.
  4. It usually gives less dependency detail than a project network diagram.

Explanation

Correct Answer

C:

This is the actual limitation of Risk register when the log monitoring deployment uses it to record future uncertainties with probability, impact, owner, and planned response; operational mechanism: The risk register tracks exposure before a potential event occurs; specific limitation: Actual current problems belong in issue tracking.

Incorrect Answers

A:

This warning concerns Requirements traceability matrix used to connect each requirement to design elements, test cases, and acceptance evidence, not the specified Risk register used to record future uncertainties with probability, impact, owner, and planned response in the log monitoring deployment; functional evidence: Traceability makes it possible to verify that defined requirements were addressed; qualification to consider: A task board alone does not show end-to-end requirement evidence.

B:

This warning concerns Version control system used to track who changed source artifacts and allow review or restoration of earlier revisions, not the specified Risk register used to record future uncertainties with probability, impact, owner, and planned response in the log monitoring deployment; operational mechanism: Version control maintains a history of changes to files and code; specific limitation: It does not itself prioritize project risk or resource allocations.

D:

This warning concerns Task board used to visualize current work moving through columns such as queued, in progress, and done, not the specified Risk register used to record future uncertainties with probability, impact, owner, and planned response in the log monitoring deployment; functional evidence: A task board displays workflow state and ownership of current tasks; qualification to consider: It usually gives less dependency detail than a project network diagram.

Question 1077

Before using Risk management plan on the financial reporting migration, the steering group asks about its limitations. Which qualification specifically prevents an overbroad interpretation of this practice for the goal to define methods, thresholds, owners, and review cadence for uncertainty?

  1. The individual risk register contains specific event entries.
  2. It should include escalation and confidentiality where relevant.
  3. Not every item is a committed sprint deliverable.
  4. Fragmented plans can produce contradictory assumptions.

Explanation

Correct Answer

A:

This is the actual limitation of Risk management plan when the financial reporting migration uses it to define methods, thresholds, owners, and review cadence for uncertainty; functional evidence: Risk planning standardizes how project threats and opportunities will be managed; qualification to consider: The individual risk register contains specific event entries.

Incorrect Answers

B:

This warning concerns Communications management plan used to specify which audiences get which messages through what channel and frequency, not the specified Risk management plan used to define methods, thresholds, owners, and review cadence for uncertainty in the financial reporting migration; operational mechanism: A communication plan maps stakeholders to information needs and timing; specific limitation: It should include escalation and confidentiality where relevant.

C:

This warning concerns Prioritized product backlog used to maintain an ordered inventory of agile product features awaiting implementation, not the specified Risk management plan used to define methods, thresholds, owners, and review cadence for uncertainty in the financial reporting migration; 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:

This warning concerns Integrated project management plan used to combine subsidiary plans, baselines, and governance into the delivery reference, not the specified Risk management plan used to define methods, thresholds, owners, and review cadence for uncertainty in the financial reporting migration; functional evidence: The integrated plan coordinates scope, schedule, cost, quality, risks, and stakeholders; qualification to consider: Fragmented plans can produce contradictory assumptions.

Question 1078

The public cloud adoption project team already uses Trade-secret handling restrictions to protect proprietary algorithms and confidential commercial designs from unauthorized disclosure. A new workstream must also require a second independent factor for sensitive remote project access. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Trade-secret handling restrictions
  2. Data classification labels
  3. Role-based permissions
  4. Company branding policy
  5. Multifactor authentication

Explanation

Correct Answer

E:

Adding Multifactor authentication addresses the new public cloud adoption project need to require a second independent factor for sensitive remote project access; Trade-secret handling restrictions already serves the separate need to protect proprietary algorithms and confidential commercial designs from unauthorized disclosure; operational mechanism: MFA combines independent evidence of identity to reduce compromised-password risk; specific limitation: It does not decide which files an authenticated user should see.

Incorrect Answers

A:

Trade-secret handling restrictions is already present in the public cloud adoption project to protect proprietary algorithms and confidential commercial designs from unauthorized disclosure; repeating it does not fulfill the distinct requirement to require a second independent factor for sensitive remote project access; operational mechanism: Trade-secret safeguards limit access and downstream use of commercially valuable nonpublic information; specific limitation: Public project summaries should omit protected proprietary details.

B:

Data classification labels would instead address mark project records based on sensitivity to drive handling and sharing rules; the public cloud adoption project still needs to require a second independent factor for sensitive remote project access, in addition to its existing Trade-secret handling restrictions; functional evidence: Classification translates business sensitivity into protective requirements; qualification to consider: Labels are useful only when corresponding access and storage controls apply.

C:

Role-based permissions would instead address assign system rights according to defined job responsibilities rather than shared accounts; the public cloud adoption project still needs to require a second independent factor for sensitive remote project access, in addition to its existing Trade-secret handling restrictions; functional evidence: Role-based access aligns permissions with job tasks and supports easier review; qualification to consider: It still requires least-privilege role design and timely removal.

D:

Company branding policy would instead address prevent a supplier from publishing unauthorized logos and claims in project materials; the public cloud adoption project still needs to require a second independent factor for sensitive remote project access, in addition to its existing Trade-secret handling restrictions; operational mechanism: Branding controls govern approved use of company identity and public statements; specific limitation: They address corporate policy rather than network packet encryption.

Question 1079

The manufacturing sensor deployment team already uses Computing service redundancy to design alternate processing capacity so a server fault does not stop the whole application. A new workstream must also use a ready-made hosted business application through a browser. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Software as a service (SaaS)
  2. Computing service redundancy
  3. Network connectivity
  4. Directory and identity service
  5. Multitier architecture

Explanation

Correct Answer

A:

Adding Software as a service (SaaS) addresses the new manufacturing sensor deployment need to use a ready-made hosted business application through a browser; Computing service redundancy already serves the separate need to design alternate processing capacity so a server fault does not stop the whole application; functional evidence: SaaS delivers application functionality managed by the provider; qualification to consider: Customers configure use and access but usually do not patch its code or servers.

Incorrect Answers

B:

Computing service redundancy is already present in the manufacturing sensor deployment to design alternate processing capacity so a server fault does not stop the whole application; repeating it does not fulfill the distinct requirement to use a ready-made hosted business application through a browser; the practical reason is: Redundant compute instances can improve availability when failover is properly designed; important boundary: Duplicate hardware alone does not prove applications and data will recover.

C:

Network connectivity would instead address identify routes, bandwidth, and reliable communication between integrated services; the manufacturing sensor deployment still needs to use a ready-made hosted business application through a browser, in addition to its existing Computing service redundancy; the practical reason is: Connectivity planning ensures system components can exchange needed traffic; important boundary: A faster server alone cannot repair a blocked network path.

D:

Directory and identity service would instead address centrally manage user identities and access relationships across applications; the manufacturing sensor deployment still needs to use a ready-made hosted business application through a browser, in addition to its existing Computing service redundancy; operational mechanism: Identity services authenticate principals and support policy-driven access; specific limitation: They do not automatically specify a project's acceptance criteria.

E:

Multitier architecture would instead address separate presentation, application logic, and data responsibilities into distinct layers; the manufacturing sensor deployment still needs to use a ready-made hosted business application through a browser, in addition to its existing Computing service redundancy; operational mechanism: Multitier designs isolate tiers with different duties and scaling requirements; specific limitation: Dependencies and interfaces still need coordination across tiers.

Question 1080

For the network equipment lifecycle program, a draft plan relies only on Report a risk trigger because the team wants to tell decision makers that a named uncertainty's likelihood or impact has changed. A reviewer identifies a separate unmet obligation: send a sponsor-approved project summary to an outside customer or partner. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Report a risk trigger
  2. Revise schedule forecast
  3. Monitor vendor performance
  4. Provide a targeted ad hoc report
  5. Issue external status reporting

Explanation

Correct Answer

E:

The network equipment lifecycle program plan must add Issue external status reporting to send a sponsor-approved project summary to an outside customer or partner; its current Report a risk trigger is already intended to tell decision makers that a named uncertainty's likelihood or impact has changed; functional evidence: External status reports communicate relevant commitments beyond the internal team; qualification to consider: Sensitive internal details need not be shared indiscriminately.

Incorrect Answers

A:

Report a risk trigger is already serving tell decision makers that a named uncertainty's likelihood or impact has changed in the network equipment lifecycle program; the corrected plan must also address the unmet obligation to send a sponsor-approved project summary to an outside customer or partner; the practical reason is: Risk reporting highlights evolving exposure and response triggers; important boundary: It is forward-looking unless the event already became an active issue.

B:

Revise schedule forecast is intended to recalculate likely completion dates after task durations or dependencies change; that is different from the overlooked network equipment lifecycle program obligation to send a sponsor-approved project summary to an outside customer or partner; the practical reason is: Schedule forecast updates show probable outcomes from current progress; important boundary: They do not automatically authorize a new baseline.

C:

Monitor vendor performance is intended to check a contractor's milestones and quality against the agreed SOW; that is different from the overlooked network equipment lifecycle program obligation to send a sponsor-approved project summary to an outside customer or partner; the practical reason is: Vendor monitoring uses contractual deliverables and measures to detect slippage; important boundary: Paying an invoice without validation does not establish performance.

D:

Provide a targeted ad hoc report is intended to answer a newly raised executive question about a specific delivery issue; that is different from the overlooked network equipment lifecycle program obligation to send a sponsor-approved project summary to an outside customer or partner; the practical reason is: Ad hoc reporting responds to an exceptional information need outside routine cadence; important boundary: It need not replace the normal reporting process.

CompTIA Project+ (PK0-005) Practice Tests