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

Question 710

The log monitoring deployment team has a specific outstanding requirement: reduce immediate tension by emphasizing areas of agreement. At the delivery review, which action or practice is the most appropriate response?

  1. Collaboration
  2. Forcing
  3. Hold project status updates
  4. Smoothing
  5. Issue external status reporting

Explanation

Correct Answer

D:

Smoothing fits the log monitoring deployment requirement to reduce immediate tension by emphasizing areas of agreement; operational mechanism: Smoothing foregrounds shared goals to maintain relationships temporarily; specific limitation: It can leave the underlying substantive dispute unresolved.

Incorrect Answers

A:

Collaboration is intended to seek a durable solution satisfying the underlying needs of both conflicting specialists, not to meet the log monitoring deployment requirement to reduce immediate tension by emphasizing areas of agreement; functional evidence: Collaboration examines interests to construct a mutually beneficial resolution; qualification to consider: It can take more time than a temporary compromise.

B:

Forcing is intended to make an urgent authoritative decision when safety or critical operations cannot wait, not to meet the log monitoring deployment requirement to reduce immediate tension by emphasizing areas of agreement; operational mechanism: Forcing applies decisive authority to select a course despite disagreement; specific limitation: It can damage relationships if used routinely for nonurgent disputes.

C:

Hold project status updates is intended to share agreed progress and blockers with stakeholders at the scheduled cadence, not to meet the log monitoring deployment requirement to reduce immediate tension by emphasizing areas of agreement; 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.

E:

Issue external status reporting is intended to send a sponsor-approved project summary to an outside customer or partner, not to meet the log monitoring deployment requirement to reduce immediate tension by emphasizing areas of agreement; 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 711

For the log monitoring deployment, a draft plan relies only on Risk register because the team wants to record future uncertainties with probability, impact, owner, and planned response. A reviewer identifies a separate unmet obligation: track who changed source artifacts and allow review or restoration of earlier revisions. Which choice corrects the gap instead of mistaking the first activity for the second?

  1. Version control system
  2. Issue log
  3. Project dashboard
  4. Risk register

Explanation

Correct Answer

A:

The log monitoring deployment plan must add Version control system to track who changed source artifacts and allow review or restoration of earlier revisions; its current Risk register is already intended to record future uncertainties with probability, impact, owner, and planned response; functional evidence: Version control maintains a history of changes to files and code; qualification to consider: It does not itself prioritize project risk or resource allocations.

Incorrect Answers

B:

Issue log is intended to record active blockers with assignment, severity, progress, and resolution; that is different from the overlooked log monitoring deployment obligation to track who changed source artifacts and allow review or restoration of earlier revisions; functional evidence: An issue log tracks realized delivery problems through closure; qualification to consider: Forecast concerns alone belong in a risk register.

C:

Project dashboard is intended to present a compact set of current indicators and exceptions across project workstreams; that is different from the overlooked log monitoring deployment obligation to track who changed source artifacts and allow review or restoration of earlier revisions; operational mechanism: A dashboard consolidates metrics for quick monitoring; specific limitation: A narrative status report can supply more context behind the numbers.

D:

Risk register is already serving record future uncertainties with probability, impact, owner, and planned response in the log monitoring deployment; the corrected plan must also address the unmet obligation to track who changed source artifacts and allow review or restoration of earlier revisions; functional evidence: The risk register tracks exposure before a potential event occurs; qualification to consider: Actual current problems belong in issue tracking.

Question 712

For the device enrollment automation, a draft plan relies only on Control chart because the team wants to monitor a process metric over time against calculated statistical control limits. A reviewer identifies a separate unmet obligation: group defect counts into numeric ranges to inspect their frequency distribution. Which choice corrects the gap instead of mistaking the first activity for the second?

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

Explanation

Correct Answer

B:

The device enrollment automation plan must add Histogram to group defect counts into numeric ranges to inspect their frequency distribution; its current Control chart is already intended to monitor a process metric over time against calculated statistical control limits; operational mechanism: A histogram shows how observations are distributed among measured intervals; specific limitation: It does not depict the time order of individual measurements.

Incorrect Answers

A:

Pareto chart is intended to rank defect categories to identify the few causes responsible for most incidents; that is different from the overlooked device enrollment automation obligation to group defect counts into numeric ranges to inspect their frequency distribution; functional evidence: A Pareto chart sorts category contributions and often adds cumulative percentages; qualification to consider: It supports prioritization but does not establish root cause by itself.

C:

Velocity chart is intended to compare a team's completed story points across successive iterations; that is different from the overlooked device enrollment automation obligation to group defect counts into numeric ranges to inspect their frequency distribution; functional evidence: Velocity tracks observed delivery capacity to inform short-term forecasting; qualification to consider: It should not be used to compare unrelated teams as a productivity ranking.

D:

Control chart is already serving monitor a process metric over time against calculated statistical control limits in the device enrollment automation; the corrected plan must also address the unmet obligation to group defect counts into numeric ranges to inspect their frequency distribution; operational mechanism: Control charts help distinguish common-cause variation from unusual signals; specific limitation: A control-limit breach calls for investigation, not an assumption about its cause.

Question 713

The security operations tooling refresh team has a specific outstanding requirement: protect project documents stored on lost phones and tablets. At the governance checkpoint, which action or practice is the most appropriate response?

  1. Security awareness briefing
  2. Role-based permissions
  3. Company branding policy
  4. Removable-media restrictions
  5. Mobile-device security policy

Explanation

Correct Answer

E:

Mobile-device security policy fits the security operations tooling refresh requirement to protect project documents stored on lost phones and tablets; operational mechanism: Mobile security policies may require encryption, lock screens, and remote wipe; specific limitation: A private meeting alone will not protect misplaced portable devices.

Incorrect Answers

A:

Security awareness briefing is intended to teach contractors required handling and incident-reporting procedures before access, not to meet the security operations tooling refresh requirement to protect project documents stored on lost phones and tablets; operational mechanism: Awareness briefings explain expected practices and prohibited behavior; specific limitation: Training complements rather than replaces technical access controls.

B:

Role-based permissions is intended to assign system rights according to defined job responsibilities rather than shared accounts, not to meet the security operations tooling refresh requirement to protect project documents stored on lost phones and tablets; 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.

C:

Company branding policy is intended to prevent a supplier from publishing unauthorized logos and claims in project materials, not to meet the security operations tooling refresh requirement to protect project documents stored on lost phones and tablets; the practical reason is: Branding controls govern approved use of company identity and public statements; important boundary: They address corporate policy rather than network packet encryption.

D:

Removable-media restrictions is intended to prevent uncontrolled use of USB drives that may carry or expose confidential project data, not to meet the security operations tooling refresh requirement to protect project documents stored on lost phones and tablets; operational mechanism: Removable-media controls govern portable storage to reduce malware and data loss; specific limitation: Endpoint authentication does not make every USB transfer permissible.

Question 714

In the inventory synchronization project, the team proposes the practice Architecture documentation to record components, interfaces, dependencies, and constraints for future maintainers. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Redundant compute instances can improve availability when failover is properly designed.
  2. A warehouse structures integrated data for analytical workloads.
  3. Technical documentation preserves infrastructure design knowledge across handoffs.
  4. Connectivity planning ensures system components can exchange needed traffic.

Explanation

Correct Answer

C:

This is observable evidence of Architecture documentation for the inventory synchronization project purpose to record components, interfaces, dependencies, and constraints for future maintainers; operational mechanism: Technical documentation preserves infrastructure design knowledge across handoffs; specific limitation: An undocumented drawing on a whiteboard is fragile evidence.

Incorrect Answers

A:

This behavior would demonstrate Computing service redundancy for design alternate processing capacity so a server fault does not stop the whole application, rather than Architecture documentation for record components, interfaces, dependencies, and constraints for future maintainers in the inventory synchronization project; 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.

B:

This behavior would demonstrate Data warehouse for consolidate historical information from multiple sources for reporting and analytics, rather than Architecture documentation for record components, interfaces, dependencies, and constraints for future maintainers in the inventory synchronization project; operational mechanism: A warehouse structures integrated data for analytical workloads; specific limitation: It is not necessarily the operational system of record for live transactions.

D:

This behavior would demonstrate Network connectivity for identify routes, bandwidth, and reliable communication between integrated services, rather than Architecture documentation for record components, interfaces, dependencies, and constraints for future maintainers in the inventory synchronization project; 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.

Question 715

The employee directory replacement team has a specific outstanding requirement: run repeatable checks on each software change before release. At the governance checkpoint, which action or practice is the most appropriate response?

  1. Automated test pipeline
  2. Continuous deployment
  3. Continuous integration
  4. Manual exploratory testing
  5. Cloud-provider change coordination

Explanation

Correct Answer

A:

Automated test pipeline fits the employee directory replacement requirement to run repeatable checks on each software change before release; functional evidence: Automated tests provide consistent rapid evidence of specified behavior; qualification to consider: They complement rather than eliminate exploratory manual verification.

Incorrect Answers

B:

Continuous deployment is intended to release each qualifying change automatically into production after required automated gates, not to meet the employee directory replacement requirement to run repeatable checks on each software change before release; operational mechanism: Continuous deployment automates promotion of accepted changes to live service; specific limitation: It requires careful safeguards and differs from manual release approval.

C:

Continuous integration is intended to merge changes frequently and run automatic builds and tests to detect conflicts early, not to meet the employee directory replacement requirement to run repeatable checks on each software change before release; 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:

Manual exploratory testing is intended to investigate unexpected user journeys not fully captured by scripted test cases, not to meet the employee directory replacement requirement to run repeatable checks on each software change before release; functional evidence: Manual testing applies human judgment to edge cases and usability; qualification to consider: It should not be the only control for highly repetitive regression suites.

E:

Cloud-provider change coordination is intended to account for shared-responsibility boundaries when changing managed cloud services, not to meet the employee directory replacement requirement to run repeatable checks on each software change before release; functional evidence: Cloud change planning distinguishes customer-controlled settings from provider-operated infrastructure; qualification to consider: Traditional on-site maintenance responsibilities may differ.

Question 716

The network equipment lifecycle program team has a specific outstanding requirement: discuss a design visually with dispersed staff who need live interaction. At the delivery review, which action or practice is the most appropriate response?

  1. Team chat
  2. Video conference
  3. Enterprise social platform
  4. Email

Explanation

Correct Answer

B:

Video conference fits the network equipment lifecycle program requirement to discuss a design visually with dispersed staff who need live interaction; functional evidence: Video meetings provide real-time conversation and shared visual context; qualification to consider: Time zones and connectivity can limit attendance.

Incorrect Answers

A:

Team chat is intended to resolve quick coordination questions among available colleagues through shared message threads, not to meet the network equipment lifecycle program requirement to discuss a design visually with dispersed staff who need live interaction; functional evidence: Team chat enables rapid informal text exchanges and mentions; qualification to consider: A decision requiring signed approval may need a formal record elsewhere.

C:

Enterprise social platform is intended to broadcast project community updates and maintain discussion for a broad internal audience, not to meet the network equipment lifecycle program requirement to discuss a design visually with dispersed staff who need live interaction; operational mechanism: Enterprise social tools reach organizational networks and encourage open updates; specific limitation: Confidential approvals still need controlled audiences.

D:

Email is intended to send attributable written updates and attachments without requiring simultaneous attendance, not to meet the network equipment lifecycle program requirement to discuss a design visually with dispersed staff who need live interaction; functional evidence: Email supports durable asynchronous correspondence to a defined audience; qualification to consider: High urgency may require a more immediate escalation channel.

Question 717

In the field technician scheduling rollout, the team proposes the practice Extreme programming (XP) to improve code quality with pair programming, continuous integration, and test-first engineering. 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. This approach emphasizes continued business justification, roles, stage controls, and exceptions.
  3. Extreme programming applies disciplined engineering practices and rapid developer feedback.
  4. This approach commonly completes planned stages in sequence with formal stage outputs.
  5. This approach uses a visible workflow and work-in-progress limits to expose queues and bottlenecks.

Explanation

Correct Answer

C:

This is observable evidence of Extreme programming (XP) for the field technician scheduling rollout purpose to improve code quality with pair programming, continuous integration, and test-first engineering; the practical reason is: Extreme programming applies disciplined engineering practices and rapid developer feedback; important boundary: It is a software development practice set, not an enterprise portfolio framework.

Incorrect Answers

A:

This behavior would demonstrate Scaled Agile Framework (SAFe) for coordinate several agile teams working on a shared large solution, rather than Extreme programming (XP) for improve code quality with pair programming, continuous integration, and test-first engineering in the field technician scheduling rollout; operational mechanism: SAFe provides planning and coordination patterns for agile delivery across multiple teams; specific limitation: Single-team Scrum alone does not define all enterprise-level synchronization needs.

B:

This behavior would demonstrate PRINCE2 for govern an initiative through defined management stages and business-case justification, rather than Extreme programming (XP) for improve code quality with pair programming, continuous integration, and test-first engineering in the field technician scheduling rollout; the practical reason is: PRINCE2 emphasizes continued business justification, roles, stage controls, and exceptions; important boundary: It is a governance-oriented project method rather than a source-code branching practice.

D:

This behavior would demonstrate Waterfall for deliver a tightly specified integration using planned sequential phase approvals, rather than Extreme programming (XP) for improve code quality with pair programming, continuous integration, and test-first engineering in the field technician scheduling rollout; operational mechanism: Waterfall commonly completes planned stages in sequence with formal stage outputs; specific limitation: It is less accommodating of major late requirement changes than iterative approaches.

E:

This behavior would demonstrate Kanban for visualize incoming tickets and limit work in progress to improve continuous flow, rather than Extreme programming (XP) for improve code quality with pair programming, continuous integration, and test-first engineering in the field technician scheduling rollout; functional evidence: Kanban uses a visible workflow and work-in-progress limits to expose queues and bottlenecks; qualification to consider: It does not require fixed-length iterations or a prescribed sprint role set.

Question 718

The procurement automation team already uses Responsibility assignment matrix to make ownership and consultation relationships explicit for important deliverables. A new workstream must also establish high-level boundaries before detailed decomposition into tasks. Which additional practice should be paired with the existing one to address the second, distinct need?

  1. Stakeholder register
  2. Preliminary scope statement
  3. Project charter
  4. Responsibility assignment matrix

Explanation

Correct Answer

B:

Adding Preliminary scope statement addresses the new procurement automation need to establish high-level boundaries before detailed decomposition into tasks; Responsibility assignment matrix already serves the separate need to make ownership and consultation relationships explicit for important deliverables; operational mechanism: Preliminary scope identifies intended inclusions and exclusions at initiation; specific limitation: A detailed WBS belongs later in planning.

Incorrect Answers

A:

Stakeholder register would instead address identify interested parties and their influence before engagement begins; the procurement automation still needs to establish high-level boundaries before detailed decomposition into tasks, in addition to its existing Responsibility assignment matrix; the practical reason is: A stakeholder register records people and groups affected by the project; important boundary: The communication plan can then tailor updates to their needs.

C:

Project charter would instead address formally authorize a project with objectives, high-level scope, and a named leader; the procurement automation still needs to establish high-level boundaries before detailed decomposition into tasks, in addition to its existing Responsibility assignment matrix; functional evidence: The charter establishes project legitimacy and overarching direction; qualification to consider: Detailed work packages and full schedules are developed subsequently.

D:

Responsibility assignment matrix is already present in the procurement automation to make ownership and consultation relationships explicit for important deliverables; repeating it does not fulfill the distinct requirement to establish high-level boundaries before detailed decomposition into tasks; functional evidence: A RAM maps activities to roles and their responsibilities; qualification to consider: It avoids gaps and overlapping claims of authority.

Question 719

In the supplier onboarding portal, the team proposes the practice Milestone baseline approval to define key completion checkpoints as reference dates agreed by authorized stakeholders. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?

  1. Training improves team readiness to use unfamiliar methods and platforms.
  2. Milestone baselines identify significant control dates for delivery monitoring.
  3. Cadence creates a predictable rhythm for coordination and feedback.
  4. A baseline records the formally approved target for monitoring progress.

Explanation

Correct Answer

B:

This is observable evidence of Milestone baseline approval for the supplier onboarding portal purpose to define key completion checkpoints as reference dates agreed by authorized stakeholders; functional evidence: Milestone baselines identify significant control dates for delivery monitoring; qualification to consider: A forecast change alone does not authorize silently moving them.

Incorrect Answers

A:

This behavior would demonstrate Train the project team for close tool or workflow knowledge gaps before work depends on new skills, rather than Milestone baseline approval for define key completion checkpoints as reference dates agreed by authorized stakeholders in the supplier onboarding portal; functional evidence: Training improves team readiness to use unfamiliar methods and platforms; qualification to consider: An untrained assignment creates quality and schedule risk.

C:

This behavior would demonstrate Establish iteration cadence for agree how often planning, review, and delivery synchronization will occur, rather than Milestone baseline approval for define key completion checkpoints as reference dates agreed by authorized stakeholders in the supplier onboarding portal; functional evidence: Cadence creates a predictable rhythm for coordination and feedback; qualification to consider: It should match work characteristics rather than a random calendar interval.

D:

This behavior would demonstrate Establish control baselines for approve reference scope, schedule, and cost values for future variance measurement, rather than Milestone baseline approval for define key completion checkpoints as reference dates agreed by authorized stakeholders in the supplier onboarding portal; operational mechanism: A baseline records the formally approved target for monitoring progress; specific limitation: Forecasts may change without automatically rewriting it.

Question 720

During the enterprise VPN modernization, the project manager has three distinct obligations: (1) assign named participants and deadlines to decisions from a delivery coordination meeting; (2) direct work according to the authorized project plan and agreed deliverables; (3) compare current performance with an agreed target and quantify the remaining difference. Which THREE complementary practices satisfy the three different obligations? Choose THREE.

  1. Execute gap analysis
  2. Communicate adoption benefits
  3. Monitor vendor performance
  4. Record meeting action owners
  5. Report a risk trigger
  6. Execute baseline-approved tasks

Explanation

Correct Answers

A:

Gap analysis identifies missing capabilities or performance against a defined target state; in the enterprise VPN modernization, this fulfills requirement (3) to compare current performance with an agreed target and quantify the remaining difference. For the enterprise VPN modernization, a routine status note may describe progress without measuring that difference.

D:

Action ownership makes execution follow-up possible after the conversation ends; in the enterprise VPN modernization, this fulfills requirement (1) to assign named participants and deadlines to decisions from a delivery coordination meeting. For the enterprise VPN modernization, meeting attendance by itself does not ensure actions are completed.

F:

Execution converts planned work into products through assigned activities; in the enterprise VPN modernization, this fulfills requirement (2) to direct work according to the authorized project plan and agreed deliverables. For the enterprise VPN modernization, material deviations still require appropriate change control.

Incorrect Answers

B:

Change communication builds understanding and reduces uncertainty about adoption; this differs from the listed needs for the enterprise VPN modernization, which are assign named participants and deadlines to decisions from a delivery coordination meeting and direct work according to the authorized project plan and agreed deliverables and compare current performance with an agreed target and quantify the remaining difference. In the enterprise VPN modernization, announcing a launch date without context can increase resistance.

C:

Vendor monitoring uses contractual deliverables and measures to detect slippage; this differs from the listed needs for the enterprise VPN modernization, which are assign named participants and deadlines to decisions from a delivery coordination meeting and direct work according to the authorized project plan and agreed deliverables and compare current performance with an agreed target and quantify the remaining difference. In the enterprise VPN modernization, paying an invoice without validation does not establish performance.

E:

Risk reporting highlights evolving exposure and response triggers; this differs from the listed needs for the enterprise VPN modernization, which are assign named participants and deadlines to decisions from a delivery coordination meeting and direct work according to the authorized project plan and agreed deliverables and compare current performance with an agreed target and quantify the remaining difference. In the enterprise VPN modernization, it is forward-looking unless the event already became an active issue.

CompTIA Project+ (PK0-005) Practice Tests