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

Question 550

In the device enrollment automation, the team proposes the practice Decision tree to compare uncertain decisions with branching outcomes, probabilities, and payoffs. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. These techniques trend remaining work against time and a target trajectory.
  2. These techniques group possible causes into categories for investigation.
  3. These techniques organize alternatives and their conditional consequences.
  4. Velocity tracks observed delivery capacity to inform short-term forecasting.

Explanation

Correct Answer

C:

This is observable evidence of Decision tree for the device enrollment automation purpose to compare uncertain decisions with branching outcomes, probabilities, and payoffs; the practical reason is: Decision trees organize alternatives and their conditional consequences; important boundary: The quality of the recommendation depends on credible outcome assumptions.

Incorrect Answers

A:

This behavior would demonstrate Burndown chart for show estimated work remaining across a sprint or release, rather than Decision tree for compare uncertain decisions with branching outcomes, probabilities, and payoffs in the device enrollment automation; operational mechanism: Burndown charts trend remaining work against time and a target trajectory; specific limitation: They can conceal added scope unless the backlog changes are also reviewed.

B:

This behavior would demonstrate Fishbone diagram for organize hypotheses about underlying causes of recurrent service defects, rather than Decision tree for compare uncertain decisions with branching outcomes, probabilities, and payoffs in the device enrollment automation; operational mechanism: Fishbone diagrams group possible causes into categories for investigation; specific limitation: They show possible mechanisms rather than measured causal proof.

D:

This behavior would demonstrate Velocity chart for compare a team's completed story points across successive iterations, rather than Decision tree for compare uncertain decisions with branching outcomes, probabilities, and payoffs in the device enrollment automation; 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.

Question 551

In the cloud workload relocation, the team proposes the practice Report a risk trigger to tell decision makers that a named uncertainty's likelihood or impact has changed. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Risk reporting highlights evolving exposure and response triggers.
  2. Regular status meetings expose current delivery health and near-term decisions.
  3. Rules of engagement clarify permissible vendor behavior and escalation.
  4. External status reports communicate relevant commitments beyond the internal team.

Explanation

Correct Answer

A:

This is observable evidence of Report a risk trigger for the cloud workload relocation purpose to tell decision makers that a named uncertainty's likelihood or impact has changed; operational mechanism: Risk reporting highlights evolving exposure and response triggers; specific limitation: It is forward-looking unless the event already became an active issue.

Incorrect Answers

B:

This behavior would demonstrate Hold project status updates for share agreed progress and blockers with stakeholders at the scheduled cadence, rather than Report a risk trigger for tell decision makers that a named uncertainty's likelihood or impact has changed in the cloud workload relocation; operational mechanism: Regular status meetings expose current delivery health and near-term decisions; specific limitation: They should be supported by traceable actions rather than vague optimism.

C:

This behavior would demonstrate Enforce vendor engagement rules for ensure subcontractors follow agreed access, communication, and work protocols, rather than Report a risk trigger for tell decision makers that a named uncertainty's likelihood or impact has changed in the cloud workload relocation; the practical reason is: Rules of engagement clarify permissible vendor behavior and escalation; important boundary: A capable supplier still must comply with contract and site controls.

D:

This behavior would demonstrate Issue external status reporting for send a sponsor-approved project summary to an outside customer or partner, rather than Report a risk trigger for tell decision makers that a named uncertainty's likelihood or impact has changed in the cloud workload relocation; the practical reason is: External status reports communicate relevant commitments beyond the internal team; important boundary: Sensitive internal details need not be shared indiscriminately.

Question 552

In the network segmentation upgrade, the team proposes the practice Project schedule to map activity dependencies, expected durations, resources, and milestones. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Risk planning standardizes how project threats and opportunities will be managed.
  2. A communication plan maps stakeholders to information needs and timing.
  3. A QA plan specifies how quality will be managed before defects are found.
  4. This approach shows when planned work should happen and in what order.

Explanation

Correct Answer

D:

This is observable evidence of Project schedule for the network segmentation upgrade purpose to map activity dependencies, expected durations, resources, and milestones; functional evidence: A project schedule shows when planned work should happen and in what order; qualification to consider: Budget alone cannot reveal logical task constraints.

Incorrect Answers

A:

This behavior would demonstrate Risk management plan for define methods, thresholds, owners, and review cadence for uncertainty, rather than Project schedule for map activity dependencies, expected durations, resources, and milestones in the network segmentation upgrade; operational mechanism: Risk planning standardizes how project threats and opportunities will be managed; specific limitation: The individual risk register contains specific event entries.

B:

This behavior would demonstrate Communications management plan for specify which audiences get which messages through what channel and frequency, rather than Project schedule for map activity dependencies, expected durations, resources, and milestones in the network segmentation upgrade; the practical reason is: A communication plan maps stakeholders to information needs and timing; important boundary: It should include escalation and confidentiality where relevant.

C:

This behavior would demonstrate Quality assurance plan for define preventive reviews, standards, test responsibilities, and acceptance evidence, rather than Project schedule for map activity dependencies, expected durations, resources, and milestones in the network segmentation upgrade; functional evidence: A QA plan specifies how quality will be managed before defects are found; qualification to consider: It complements rather than replaces actual product testing.

Question 553

Two manufacturing sensor deployment alternatives have forecast (cost, benefit) A=($100,000,$140,000) and B=($80,000,$120,000). How far apart are their ROI percentages?

  1. 20%
  2. 40%
  3. 50%
  4. 10%

Explanation

Correct Answer

D:

ROI A=40%; ROI B=50%; absolute gap=10 percentage points. These stated figures yield 10% for the requested ROI percentage-point gap in the manufacturing sensor deployment case.

Incorrect Answers

A:

Gross benefit gap is not ROI difference. The resulting 20% does not match the requested ROI percentage-point gap for the manufacturing sensor deployment: the governing arithmetic is ROI A=40%; ROI B=50%; absolute gap=10 percentage points, yielding 10%.

B:

This is A’s ROI, not the gap. The resulting 40% does not match the requested ROI percentage-point gap for the manufacturing sensor deployment: the governing arithmetic is ROI A=40%; ROI B=50%; absolute gap=10 percentage points, yielding 10%.

C:

This is B’s ROI, not the difference. The resulting 50% does not match the requested ROI percentage-point gap for the manufacturing sensor deployment: the governing arithmetic is ROI A=40%; ROI B=50%; absolute gap=10 percentage points, yielding 10%.

Question 554

In the supplier onboarding portal, the team proposes the practice Perform a post-project evaluation to compare realized results and delivery performance with original goals and assumptions. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Recognition supports morale and marks the conclusion of temporary work.
  2. Sign-off records the customer's or sponsor's formal acceptance decision.
  3. Closure meetings align parties on remaining support and final outcomes.
  4. Evaluation assesses project effectiveness and improvement opportunities.

Explanation

Correct Answer

D:

This is observable evidence of Perform a post-project evaluation for the supplier onboarding portal purpose to compare realized results and delivery performance with original goals and assumptions; the practical reason is: Evaluation assesses project effectiveness and improvement opportunities; important boundary: It is different from only checking whether a ticket was closed.

Incorrect Answers

A:

This behavior would demonstrate Closure celebration and recognition for acknowledge the team's contribution after delivery obligations are met, rather than Perform a post-project evaluation for compare realized results and delivery performance with original goals and assumptions in the supplier onboarding portal; 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.

B:

This behavior would demonstrate Formal deliverable sign-off for obtain authorized acknowledgment that required project outputs satisfy acceptance criteria, rather than Perform a post-project evaluation for compare realized results and delivery performance with original goals and assumptions in the supplier onboarding portal; the practical reason is: Sign-off records the customer's or sponsor's formal acceptance decision; important boundary: Internal testing alone does not replace an authorized acceptance act.

C:

This behavior would demonstrate Conduct closure meeting for confirm handoffs, final responsibilities, and official completion with stakeholders, rather than Perform a post-project evaluation for compare realized results and delivery performance with original goals and assumptions in the supplier onboarding portal; functional evidence: Closure meetings align parties on remaining support and final outcomes; qualification to consider: They should not be mistaken for the project's initial kickoff.

Question 555

The fleet maintenance platform team has a specific outstanding requirement: assign system rights according to defined job responsibilities rather than shared accounts. At the governance checkpoint, which action or practice is the most appropriate response?

  1. National-security classification handling
  2. Role-based permissions
  3. Trade-secret handling restrictions
  4. Restricted remote access

Explanation

Correct Answer

B:

Role-based permissions fits the fleet maintenance platform requirement to assign system rights according to defined job responsibilities rather than shared accounts; operational mechanism: Role-based access aligns permissions with job tasks and supports easier review; specific limitation: It still requires least-privilege role design and timely removal.

Incorrect Answers

A:

National-security classification handling is intended to apply mandated security markings and authorized processing rules to classified records, not to meet the fleet maintenance platform requirement to assign system rights according to defined job responsibilities rather than shared accounts; operational mechanism: National-security handling follows classification, clearance, and compartmented access restrictions; specific limitation: Ordinary corporate confidentiality labels may be inadequate for classified material.

C:

Trade-secret handling restrictions is intended to protect proprietary algorithms and confidential commercial designs from unauthorized disclosure, not to meet the fleet maintenance platform requirement to assign system rights according to defined job responsibilities rather than shared accounts; the practical reason is: Trade-secret safeguards limit access and downstream use of commercially valuable nonpublic information; important boundary: Public project summaries should omit protected proprietary details.

D:

Restricted remote access is intended to allow off-site administration only through approved secure access paths, not to meet the fleet maintenance platform requirement to assign system rights according to defined job responsibilities rather than shared accounts; operational mechanism: Remote restrictions limit where and how privileged systems can be reached; specific limitation: A valid password does not bypass network-access policy.

Question 556

In the backup restoration redesign, the team proposes the practice Financial accounting system to record financial transactions, accounts, and approved reporting data. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Identity services authenticate principals and support policy-driven access.
  2. Middleware connects systems and handles interface communication requirements.
  3. A CMS manages reusable digital content and publishing workflows.
  4. Financial systems support budgeting, accounting, reconciliation, and reporting.

Explanation

Correct Answer

D:

This is observable evidence of Financial accounting system for the backup restoration redesign purpose to record financial transactions, accounts, and approved reporting data; operational mechanism: Financial systems support budgeting, accounting, reconciliation, and reporting; specific limitation: They are not the primary tool for user-story sequencing.

Incorrect Answers

A:

This behavior would demonstrate Directory and identity service for centrally manage user identities and access relationships across applications, rather than Financial accounting system for record financial transactions, accounts, and approved reporting data in the backup restoration redesign; operational mechanism: Identity services authenticate principals and support policy-driven access; specific limitation: They do not automatically specify a project's acceptance criteria.

B:

This behavior would demonstrate Integration middleware for exchange and transform information between two business applications, rather than Financial accounting system for record financial transactions, accounts, and approved reporting data in the backup restoration redesign; the practical reason is: Middleware connects systems and handles interface communication requirements; important boundary: It is not itself the end-user business application.

C:

This behavior would demonstrate Content management system (CMS) for let editors publish and maintain web or intranet content without coding each page, rather than Financial accounting system for record financial transactions, accounts, and approved reporting data in the backup restoration redesign; operational mechanism: A CMS manages reusable digital content and publishing workflows; specific limitation: It does not replace a financial general ledger.

Question 557

The mobile-application release team has a specific outstanding requirement: describe the stages a software solution traverses from requirements to maintenance. At the planning review, which action or practice is the most appropriate response?

  1. Waterfall
  2. DevOps
  3. Extreme programming (XP)
  4. Software development life cycle (SDLC)

Explanation

Correct Answer

D:

Software development life cycle (SDLC) fits the mobile-application release requirement to describe the stages a software solution traverses from requirements to maintenance; functional evidence: An SDLC model organizes software work through analysis, design, build, test, deployment, and support; qualification to consider: It is a life-cycle description rather than one specific project-governance method.

Incorrect Answers

A:

Waterfall is intended to deliver a tightly specified integration using planned sequential phase approvals, not to meet the mobile-application release requirement to describe the stages a software solution traverses from requirements to maintenance; functional evidence: Waterfall commonly completes planned stages in sequence with formal stage outputs; qualification to consider: It is less accommodating of major late requirement changes than iterative approaches.

B:

DevOps is intended to reduce friction between software delivery and IT operations through collaboration and automation, not to meet the mobile-application release requirement to describe the stages a software solution traverses from requirements to maintenance; the practical reason is: DevOps integrates development and operations responsibilities across delivery and support; important boundary: Security can participate, but explicit security-by-design is the DevSecOps emphasis.

C:

Extreme programming (XP) is intended to improve code quality with pair programming, continuous integration, and test-first engineering, not to meet the mobile-application release requirement to describe the stages a software solution traverses from requirements to maintenance; operational mechanism: Extreme programming applies disciplined engineering practices and rapid developer feedback; specific limitation: It is a software development practice set, not an enterprise portfolio framework.

Question 558

In the hybrid meeting room expansion, the team proposes the practice Issue log to record active blockers with assignment, severity, progress, and resolution. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. This approach aggregates risk information for oversight.
  2. Version control maintains a history of changes to files and code.
  3. This approach tracks realized delivery problems through closure.
  4. This approach preserves the history of controlled alterations.
  5. Traceability makes it possible to verify that defined requirements were addressed.
  6. This approach tracks flaws found in a deliverable under test.

Explanation

Correct Answer

C:

This is observable evidence of Issue log for the hybrid meeting room expansion purpose to record active blockers with assignment, severity, progress, and resolution; the practical reason is: An issue log tracks realized delivery problems through closure; important boundary: Forecast concerns alone belong in a risk register.

Incorrect Answers

A:

This behavior would demonstrate Risk report for summarize significant current exposures, trends, and response effectiveness for decision makers, rather than Issue log for record active blockers with assignment, severity, progress, and resolution in the hybrid meeting room expansion; the practical reason is: A risk report aggregates risk information for oversight; important boundary: The underlying risk register holds event-level detail.

B:

This behavior would demonstrate Version control system for track who changed source artifacts and allow review or restoration of earlier revisions, rather than Issue log for record active blockers with assignment, severity, progress, and resolution in the hybrid meeting room expansion; the practical reason is: Version control maintains a history of changes to files and code; important boundary: It does not itself prioritize project risk or resource allocations.

D:

This behavior would demonstrate Change log for trace proposed changes, approvals, status, and implementation references, rather than Issue log for record active blockers with assignment, severity, progress, and resolution in the hybrid meeting room expansion; functional evidence: A change log preserves the history of controlled alterations; qualification to consider: It cannot substitute for a risk response register.

E:

This behavior would demonstrate Requirements traceability matrix for connect each requirement to design elements, test cases, and acceptance evidence, rather than Issue log for record active blockers with assignment, severity, progress, and resolution in the hybrid meeting room expansion; operational mechanism: Traceability makes it possible to verify that defined requirements were addressed; specific limitation: A task board alone does not show end-to-end requirement evidence.

F:

This behavior would demonstrate Defect log for manage observed product faults with reproduction steps, severity, and correction status, rather than Issue log for record active blockers with assignment, severity, progress, and resolution in the hybrid meeting room expansion; the practical reason is: A defect log tracks flaws found in a deliverable under test; important boundary: It is more product-error-specific than a broad project issue register.

Question 559

In the microservice authentication update, the team proposes the practice Validate the implemented change to confirm that a deployed amendment achieves the agreed acceptance criteria. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Validation checks actual results against the approved request and expected outcome.
  2. The change log captures proposed scope changes before decision and implementation.
  3. Impact analysis gives authorized reviewers evidence about trade-offs of a proposed change.
  4. Implementation puts the approved change into the actual product or project workflow.

Explanation

Correct Answer

A:

This is observable evidence of Validate the implemented change for the microservice authentication update purpose to confirm that a deployed amendment achieves the agreed acceptance criteria; 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.

Incorrect Answers

B:

This behavior would demonstrate Register a change request for create an auditable record when a stakeholder proposes unplanned functionality, rather than Validate the implemented change for confirm that a deployed amendment achieves the agreed acceptance criteria in the microservice authentication update; 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.

C:

This behavior would demonstrate Perform change impact analysis for quantify effects on delivery date, cost, scope, quality, and risk before approval, rather than Validate the implemented change for confirm that a deployed amendment achieves the agreed acceptance criteria in the microservice authentication update; the practical reason is: Impact analysis gives authorized reviewers evidence about trade-offs of a proposed change; important boundary: Implementing first would bypass the information needed for a sound decision.

D:

This behavior would demonstrate Implement the authorized change for carry out an approved solution adjustment using the agreed implementation plan, rather than Validate the implemented change for confirm that a deployed amendment achieves the agreed acceptance criteria in the microservice authentication update; operational mechanism: Implementation puts the approved change into the actual product or project workflow; specific limitation: It follows assessment and authorization rather than replacing those controls.

Question 560

In the online reservation system, the team proposes the practice Continuous integration to merge changes frequently and run automatic builds and tests to detect conflicts early. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Manual testing applies human judgment to edge cases and usability.
  2. Cloud change planning distinguishes customer-controlled settings from provider-operated infrastructure.
  3. Automated tests provide consistent rapid evidence of specified behavior.
  4. Production hosts real operational transactions under active service controls.
  5. This approach validates combined source updates through a shared pipeline.

Explanation

Correct Answer

E:

This is observable evidence of Continuous integration for the online reservation system purpose to merge changes frequently and run automatic builds and tests to detect conflicts early; functional evidence: Continuous integration validates combined source updates through a shared pipeline; qualification to consider: It does not necessarily deploy every successful build into production.

Incorrect Answers

A:

This behavior would demonstrate Manual exploratory testing for investigate unexpected user journeys not fully captured by scripted test cases, rather than Continuous integration for merge changes frequently and run automatic builds and tests to detect conflicts early in the online reservation system; the practical reason is: Manual testing applies human judgment to edge cases and usability; important boundary: It should not be the only control for highly repetitive regression suites.

B:

This behavior would demonstrate Cloud-provider change coordination for account for shared-responsibility boundaries when changing managed cloud services, rather than Continuous integration for merge changes frequently and run automatic builds and tests to detect conflicts early in the online reservation system; the practical reason is: Cloud change planning distinguishes customer-controlled settings from provider-operated infrastructure; important boundary: Traditional on-site maintenance responsibilities may differ.

C:

This behavior would demonstrate Automated test pipeline for run repeatable checks on each software change before release, rather than Continuous integration for merge changes frequently and run automatic builds and tests to detect conflicts early in the online reservation system; the practical reason is: Automated tests provide consistent rapid evidence of specified behavior; important boundary: They complement rather than eliminate exploratory manual verification.

D:

This behavior would demonstrate Production environment for deploy an approved release to the live service used by actual customers, rather than Continuous integration for merge changes frequently and run automatic builds and tests to detect conflicts early in the online reservation system; operational mechanism: Production hosts real operational transactions under active service controls; specific limitation: Testing there without safeguards can harm users.

CompTIA Project+ (PK0-005) Practice Tests