View Full CompTIA Project+ PK0-005 Exam Dumps and Practice Test Dumps

 

Question 321. Which project artifact identifies stakeholders and records information about their interests, influence, and communication needs?

1. Stakeholder register
2. Risk register
3. Cost baseline
4. WBS dictionary

Correct Answer: 1. Stakeholder register.

Explanation:

The stakeholder register identifies individuals, groups, or organizations that can affect or be affected by the project. It can contain information such as stakeholder roles, interests, influence, expectations, communication needs, and engagement considerations. The register helps the project manager understand who needs information, who may make decisions, and who may require focused engagement throughout the project. A risk register records uncertainty, a cost baseline provides a financial performance reference, and a WBS dictionary describes work components. The stakeholder register should be maintained as the project evolves because stakeholder roles, influence, expectations, and communication requirements can change during execution.

Question 322. A stakeholder has high influence but limited interest in the project. What engagement approach is generally appropriate?

1. Keep the stakeholder satisfied
2. Ignore the stakeholder completely
3. Provide every project detail daily
4. Remove the stakeholder from the register

Correct Answer: 1. Keep the stakeholder satisfied.

Explanation:

A stakeholder with high influence and relatively low interest can significantly affect the project even if that person does not require detailed involvement in every activity. The project manager should generally keep this stakeholder satisfied by providing relevant information, monitoring expectations, and ensuring that significant decisions or changes are communicated appropriately. Providing every project detail may create unnecessary communication overhead, while ignoring a powerful stakeholder can create avoidable problems. Stakeholder engagement should be tailored to the individual’s influence, interest, needs, and role. The stakeholder register and engagement strategy should be updated when the stakeholder’s level of influence or interest changes.

Question 323. Which communication method is most appropriate for resolving a complex disagreement between two important stakeholders?

1. Interactive discussion
2. Automated status report only
3. One-way announcement
4. Silent observation

Correct Answer: 1. Interactive discussion.

Explanation:

Interactive communication allows participants to exchange information, ask questions, clarify misunderstandings, and respond to each other’s concerns in real time. It is particularly useful when a disagreement is complex and requires discussion rather than simply distributing information. Depending on the circumstances, the project manager may facilitate a meeting, video conference, workshop, or other structured discussion. One-way announcements and automated reports are better suited to transmitting established information rather than resolving complex disagreements. The project manager should remain objective, encourage participants to explain their concerns, focus on documented project requirements and objectives, and work toward a mutually understood resolution.

Question 324. What should a project manager do when two stakeholders have conflicting expectations about the project scope?

1. Facilitate clarification using approved requirements and project objectives
2. Automatically accept the request from the most senior person
3. Ignore both stakeholders
4. Expand the scope to satisfy everyone without approval

Correct Answer: 1. Facilitate clarification using approved requirements and project objectives.

Explanation:

Conflicting stakeholder expectations should be addressed by reviewing approved requirements, project objectives, scope documentation, acceptance criteria, and governance procedures. The project manager can facilitate discussion so stakeholders understand the project’s agreed boundaries and identify where expectations differ. If a stakeholder proposes work outside the approved scope, the request should be evaluated through the appropriate change-control process rather than being added informally. Automatically accepting a request based only on seniority can undermine governance, while expanding scope without approval can create scope creep. Clear documentation and structured communication help the team distinguish between an existing requirement and a proposed change.

Question 325. Which conflict-resolution approach attempts to find a solution that satisfies the important concerns of all parties?

1. Collaborate
2. Avoid
3. Force
4. Withdraw

Correct Answer: 1. Collaborate.

Explanation:

Collaboration involves working with the parties involved to understand their underlying concerns and develop a solution that addresses the important interests of everyone as much as practical. It typically requires open communication, active listening, problem analysis, and a willingness to work toward a mutually acceptable outcome. Collaboration can be especially useful when the issue is significant and maintaining a strong working relationship is important. Avoidance postpones or sidesteps the conflict, while forcing imposes a decision through authority. The appropriate approach depends on urgency, importance, organizational context, and the nature of the disagreement, but collaboration is fundamentally focused on jointly solving the underlying problem.

Question 326. Which action is most appropriate when a project team disagreement is caused by unclear responsibilities?

1. Clarify roles and responsibilities
2. Increase the project budget immediately
3. Close the project
4. Delete the project schedule

Correct Answer: 1. Clarify roles and responsibilities.

Explanation:

Unclear responsibilities can cause duplicated work, missed activities, delays, conflict, and uncertainty about decision ownership. The project manager should review the relevant responsibility assignments and clarify who is responsible, accountable, consulted, and informed for the affected work. Tools such as a responsibility assignment matrix or RACI matrix can help establish these relationships. The team charter may also contain agreed working practices and decision-making expectations. Increasing the budget or deleting project documents does not address the underlying problem. Once responsibilities are clarified, the project manager should communicate the decisions to affected team members and update appropriate project documentation so that the same ambiguity does not recur.

Question 327. Which matrix is commonly used to show who is responsible, accountable, consulted, and informed for project activities?

1. RACI matrix
2. Probability-impact matrix
3. Risk heat map
4. Cost variance matrix

Correct Answer: 1. RACI matrix.

Explanation:

A RACI matrix assigns roles to project activities or deliverables using four common categories: Responsible, Accountable, Consulted, and Informed. Responsible identifies who performs the work, accountable identifies who ultimately owns the outcome or decision, consulted identifies parties whose input is required, and informed identifies those who need to receive information. The matrix helps prevent gaps and overlaps in responsibility. A probability-impact matrix is used for risk analysis, while a risk heat map visually represents risk exposure. A RACI matrix should be developed with the appropriate stakeholders and reviewed when project responsibilities, organizational structures, or deliverables change.

Question 328. Which project-management activity determines how frequently stakeholders should receive status information?

1. Communication planning
2. Cost estimating
3. Scope decomposition
4. Procurement closeout

Correct Answer: 1. Communication planning.

Explanation:

Communication planning determines what information stakeholders need, when they need it, how it should be delivered, who is responsible for communicating it, and how frequently communication should occur. Different stakeholders may require different levels of detail and different communication channels. For example, a sponsor may need a periodic executive summary, while a technical team may require more frequent detailed updates. Communication planning helps prevent both information shortages and unnecessary communication. Cost estimating develops financial estimates, scope decomposition breaks work into smaller components, and procurement closeout completes supplier activities. The communication approach should be adjusted when stakeholder needs or project conditions change.

Question 329. What is a communication barrier in a project environment?

1. Anything that interferes with accurate understanding or transmission of information
2. A completed milestone
3. An approved budget baseline
4. A supplier invoice

Correct Answer: 1. Anything that interferes with accurate understanding or transmission of information.

Explanation:

A communication barrier is a factor that prevents information from being understood, transmitted, received, or interpreted accurately. Examples include language differences, technical jargon, cultural differences, poor timing, excessive information, unclear terminology, inappropriate communication channels, distractions, and assumptions about what the recipient already knows. Project managers should identify potential barriers and adapt communication methods accordingly. For example, complex technical information may require a structured discussion rather than a brief message. Communication barriers can contribute to errors, stakeholder dissatisfaction, rework, and delays, so effective project communication involves not only sending information but also confirming that the intended meaning has been understood.

Question 330. Which document is most useful for recording project decisions, assigned action items, and meeting outcomes?

1. Meeting minutes
2. Risk register
3. Cost estimate
4. Procurement bid

Correct Answer: 1. Meeting minutes.

Explanation:

Meeting minutes provide a documented record of important meeting discussions, decisions, action items, assigned owners, and follow-up dates. They help participants confirm what was agreed and provide stakeholders with a reliable reference after the meeting. Effective minutes should focus on meaningful project information rather than attempting to capture every spoken statement. They are particularly useful when meetings result in decisions that affect scope, schedule, cost, risks, responsibilities, or stakeholder commitments. A risk register focuses on uncertainty, a cost estimate focuses on expected expenditures, and a procurement bid is part of supplier selection. Meeting records should be stored according to the project’s document-management practices.

Question 331. Which project artifact defines how project documents will be controlled, versioned, and maintained?

1. Configuration management plan
2. Stakeholder register
3. Risk trigger list
4. Issue escalation chart

Correct Answer: 1. Configuration management plan.

Explanation:

A configuration management plan defines how project and product configurations, documents, versions, changes, and related information will be identified and controlled. It helps ensure that team members are working from the correct versions of important artifacts and that changes are properly authorized and traceable. Configuration management can be particularly important when multiple teams are producing interconnected deliverables. A stakeholder register identifies stakeholders, a risk trigger list identifies warning conditions associated with risks, and an escalation chart defines how problems may be elevated. Effective configuration management reduces confusion caused by outdated documents and supports controlled changes throughout the project lifecycle.

Question 332. Which practice helps prevent team members from using an outdated version of an important project document?

1. Version control
2. Resource leveling
3. Scope reduction
4. Risk avoidance

Correct Answer: 1. Version control.

Explanation:

Version control provides a structured method for identifying, maintaining, and managing different versions of project documents or other controlled artifacts. It helps team members determine which version is current and provides traceability regarding when changes were made and, depending on the system, who made them. Version control is especially important for requirements, designs, schedules, procedures, contracts, and other documents that may change during the project. Without it, teams can accidentally work from obsolete information, creating inconsistencies or rework. Version control is typically part of broader configuration or document-management practices and should follow organizational policies.

Question 333. Which project activity is most directly associated with identifying whether a requested change affects the project’s approved baseline?

1. Change impact analysis
2. Team onboarding
3. Resource release
4. Procurement archival

Correct Answer: 1. Change impact analysis.

Explanation:

Change impact analysis examines how a proposed change could affect approved project baselines and other project elements. The assessment may consider scope, schedule, cost, quality, resources, risks, procurement, security, compliance, and stakeholder expectations. If the change affects a baseline, the project manager should follow the formal change-control process rather than modifying the baseline informally. This approach maintains control over approved project commitments and allows decision-makers to understand potential consequences before approving the change. Team onboarding concerns bringing people into the project, resource release occurs as resources leave assignments, and procurement archival occurs during documentation closeout.

Question 334. Which project control helps maintain an auditable record of changes from request through approval and implementation?

1. Change log
2. Team charter
3. Resource calendar
4. Product description

Correct Answer: 1. Change log.

Explanation:

A change log provides a structured record of proposed and approved changes throughout the project. It can capture the request description, requester, date, impact assessment, approval status, implementation status, and closure information. Maintaining this history improves transparency and supports traceability when stakeholders need to understand why project plans or baselines changed. It can also support audits and lessons learned after project completion. A team charter establishes team norms, a resource calendar records availability, and a product description explains characteristics of the deliverable. The change log should be maintained consistently and linked to related approvals or project documentation when appropriate.

Question 335. Which activity is most appropriate when a project manager needs to determine whether a project is still aligned with organizational strategy?

1. Strategic alignment review
2. Daily task assignment only
3. Resource release
4. Document deletion

Correct Answer: 1. Strategic alignment review.

Explanation:

A strategic alignment review examines whether the project’s objectives, expected outcomes, and benefits continue to support organizational priorities. Organizational strategies can change because of market conditions, regulatory developments, financial constraints, leadership decisions, or other factors. A project that was justified under earlier conditions may need reassessment if its business context changes significantly. The review can consider the business case, benefits, costs, risks, current performance, and organizational priorities. It does not automatically mean that the project should be changed or stopped; instead, it provides decision-makers with relevant information for determining appropriate action under the organization’s governance process.

Question 336. Which event is an example of a project constraint?

1. A legally mandated completion date
2. A possible future defect
3. A stakeholder preference
4. An unverified assumption

Correct Answer: 1. A legally mandated completion date.

Explanation:

A project constraint is a limitation that restricts the project’s options or ability to operate freely. A legally mandated completion date is an example because the project must meet an externally imposed deadline. Other constraints may involve budget, resources, technology, scope, quality, procurement, or regulatory requirements. A possible future defect is more appropriately treated as a risk, while an assumption represents something believed to be true for planning purposes. A stakeholder preference may influence project decisions but is not automatically a constraint unless it is formally established as a binding limitation. Identifying constraints early helps the team develop realistic plans and manage trade-offs.

Question 337. Which statement best describes a project assumption?

1. A condition believed to be true for planning purposes
2. A confirmed project defect
3. A mandatory contractual penalty
4. A completed deliverable

Correct Answer: 1. A condition believed to be true for planning purposes.

Explanation:

A project assumption is a condition, circumstance, or factor that the project team accepts as true for planning purposes without necessarily having complete confirmation. Examples might include assuming that a key resource will remain available, that required data will be supplied by a certain date, or that a facility will be accessible during a planned activity. Assumptions should be documented because an assumption that proves false can affect scope, schedule, cost, resources, or risks. A confirmed defect is an issue, a contractual penalty is a contractual condition, and a completed deliverable represents achieved work. Assumption monitoring helps the project team respond when planning conditions change.

Question 338. What should the project team do when a critical assumption is proven to be false?

1. Assess the impact and update relevant project plans and risks
2. Continue using the assumption without review
3. Delete the assumption from all records
4. Automatically close the project

Correct Answer: 1. Assess the impact and update relevant project plans and risks.

Explanation:

When a critical assumption is proven false, the project team should evaluate how the change affects the project. The assessment may reveal impacts to scope, schedule, cost, resources, quality, procurement, risks, or stakeholder expectations. Relevant assumptions, plans, risk records, schedules, and other project artifacts should then be updated according to established procedures. The team may also need to create corrective actions or submit a formal change request if approved baselines are affected. Continuing to rely on a known-invalid assumption can produce unrealistic plans and poor decisions. Proper assumption management helps maintain an accurate understanding of the conditions under which the project is being executed.

Question 339. Which activity ensures that project records are retained according to organizational, contractual, or regulatory requirements after project completion?

1. Project archival
2. Scope decomposition
3. Resource leveling
4. Activity sequencing

Correct Answer: 1. Project archival.

Explanation:

Project archival involves organizing and retaining project records according to applicable organizational, contractual, legal, regulatory, and information-management requirements. Records may include approved plans, requirements, contracts, change records, acceptance documentation, financial information, lessons learned, meeting records, and final reports. Proper archival ensures that authorized personnel can retrieve important historical information when needed and supports organizational learning, audits, contractual obligations, and future projects. Archival should also consider appropriate access controls and retention periods, particularly when records contain confidential or personal information. Scope decomposition, resource leveling, and activity sequencing are planning activities and do not address long-term record retention.

Question 340. Which activity provides an opportunity for the project team to evaluate what worked well, what did not, and what should be improved on future projects?

1. Lessons learned review
2. Resource assignment
3. Initial procurement
4. Activity sequencing

Correct Answer: 1. Lessons learned review.

Explanation:

A lessons learned review provides a structured opportunity for the project team and relevant stakeholders to identify practices that were effective, problems that occurred, causes of those problems, and improvements that could benefit future projects. Lessons can address planning, communication, stakeholder engagement, procurement, risk management, quality, scheduling, resource management, governance, and technical practices. Lessons learned should ideally be captured throughout the project rather than waiting until the final day, because important information can be forgotten over time. At closure, the team can consolidate the information into an appropriate repository so that future project teams can access and apply organizational knowledge.