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

 

Question 161. What is the primary purpose of a project charter?

1. To formally authorize the project and establish high-level direction
2. To document every project task in detail
3. To replace the project schedule
4. To record completed invoices

Correct Answer: 1. To formally authorize the project and establish high-level direction

Explanation:

The project charter formally authorizes a project and gives the project manager authority to use organizational resources for project activities. It normally contains high-level information such as the project’s purpose, objectives, major deliverables, key stakeholders, assumptions, constraints, risks, and summary-level milestones or budget information. The charter is created early in the project and provides an overall direction rather than detailed task instructions. Detailed activities belong in planning documents such as the schedule and work breakdown structure. By establishing formal authorization and high-level expectations, the charter provides a foundation for subsequent project planning and execution.

Question 162. Which document defines how project performance will be measured against approved expectations?

1. Project management plan
2. Contact directory
3. Procurement invoice
4. Meeting invitation

Correct Answer: 1. Project management plan

Explanation:

The project management plan describes how the project will be executed, monitored, controlled, and closed. It can define the approaches, procedures, baselines, performance measurements, communication methods, risk management activities, quality practices, and other processes used to manage the project. Comparing actual performance with approved baselines allows the project manager to identify variances and determine whether corrective or preventive action may be necessary. A contact directory is primarily used for communication information, while an invoice supports financial administration and a meeting invitation schedules an event. The project management plan therefore provides the broader framework for measuring and managing project performance.

Question 163. A project has a fixed maximum budget that cannot be exceeded. What does this represent?

1. Assumption
2. Constraint
3. Milestone
4. Deliverable

Correct Answer: 2. Constraint

Explanation:

A fixed maximum budget is a project constraint because it places a definite limitation on how the project can be planned and executed. Other common constraints include fixed deadlines, limited resources, contractual requirements, and required quality standards. Constraints must be considered when developing the project schedule, resource assignments, procurement strategy, and other plans. An assumption is something believed to be true for planning purposes but may later prove incorrect. A milestone is a significant point or event in the schedule, while a deliverable is a tangible or verifiable project output. Recognizing constraints early helps the project team develop realistic plans and manage trade-offs.

Question 164. What is the purpose of a work breakdown structure (WBS)?

1. To decompose project scope into manageable components
2. To calculate employee salaries
3. To approve vendor invoices
4. To replace the risk register

Correct Answer: 1. To decompose project scope into manageable components

Explanation:

A work breakdown structure decomposes the project’s scope into smaller, more manageable components. It organizes the total work required to produce the project’s deliverables and helps the project team understand what work must be completed. Lower-level WBS components can be further broken down until the appropriate level of detail is reached for planning and control. The WBS is not primarily a financial payroll document or procurement approval record. It also does not replace the risk register because risks are managed through a separate process. A well-structured WBS helps establish the scope baseline and provides a foundation for scheduling, estimating, assigning responsibilities, and monitoring project work.

Question 165. Which project document identifies stakeholders and records information about their involvement?

1. Stakeholder register
2. Cost baseline
3. Issue log
4. Configuration record

Correct Answer: 1. Stakeholder register

Explanation:

The stakeholder register identifies individuals, groups, departments, customers, sponsors, vendors, and other parties that can affect or be affected by the project. It may contain information such as stakeholder roles, interests, influence, expectations, communication needs, and engagement considerations. This information helps the project manager develop appropriate engagement and communication approaches. A cost baseline represents approved project costs over time, while an issue log records current problems requiring attention. A configuration record focuses on controlled project components and versions. Maintaining an accurate stakeholder register is important because stakeholder involvement and influence can change as the project progresses.

Question 166. A project manager notices that the project team is repeatedly performing work that is not included in the approved scope. What is this situation called?

1. Scope creep
2. Resource leveling
3. Risk transfer
4. Schedule compression

Correct Answer: 1. Scope creep

Explanation:

Scope creep occurs when additional work or requirements are added to a project without following the appropriate formal change control process. Even relatively small additions can accumulate and affect the project’s schedule, cost, resources, quality, and ability to meet approved objectives. The project manager should identify unauthorized scope changes, determine their source, and ensure that legitimate changes are evaluated through the established change process. Resource leveling addresses resource conflicts, risk transfer changes responsibility for a risk to another party, and schedule compression attempts to shorten the project duration. Controlling scope throughout execution helps prevent uncontrolled expansion of project commitments.

Question 167. Which action best supports effective project cost control?

1. Compare actual costs with the approved cost baseline
2. Ignore small cost differences
3. Remove cost information from status reports
4. Approve every requested purchase automatically

Correct Answer: 1. Compare actual costs with the approved cost baseline

Explanation:

Effective cost control requires monitoring actual project spending against the approved cost baseline. The project manager can analyze differences between planned and actual costs to identify unfavorable or favorable variances and determine whether corrective action is appropriate. Significant deviations may require investigation, forecasting, or formal change control depending on the situation. Automatically approving purchases can increase financial risk, while ignoring variances can allow small problems to become larger budget issues. Removing financial information from status reporting also reduces transparency. Regular cost monitoring provides stakeholders with useful information about financial performance and helps the project remain within its authorized budget.

Question 168. What is a milestone in a project schedule?

1. A significant point or event with no substantial duration
2. A detailed list of every project expense
3. A project risk response
4. A vendor contract amendment

Correct Answer: 1. A significant point or event with no substantial duration

Explanation:

A milestone represents a significant point or event in the project schedule. Examples include completion of a major phase, formal approval, contract signing, delivery of a major component, or customer acceptance. Milestones generally have no substantial duration themselves; they mark an important event that helps stakeholders understand project progress. Milestones are useful for reporting and monitoring because they provide clear checkpoints against which progress can be assessed. They are different from activities, which require time and resources to complete. They are also different from risks, contracts, and cost records, which serve separate project management purposes.

Question 169. Which approach should a project manager use when a stakeholder has high influence and high interest in the project?

1. Manage the stakeholder closely
2. Provide no communication
3. Monitor only occasionally
4. Remove the stakeholder from project decisions

Correct Answer: 1. Manage the stakeholder closely

Explanation:

Stakeholders with high influence and high interest generally require close management because they can significantly affect project decisions and are strongly affected by project outcomes. The project manager should maintain appropriate communication, understand their expectations, provide relevant information, involve them in decisions when appropriate, and monitor their engagement. A stakeholder power-interest analysis can help categorize stakeholders and determine suitable engagement approaches. Low-involvement strategies may not provide enough attention for stakeholders with substantial influence. Effective engagement does not mean allowing one stakeholder to control every decision; rather, it means maintaining a productive relationship while following established governance and decision-making processes.

Question 170. What should a project manager do when a project risk has a clearly defined trigger?

1. Monitor for the trigger and prepare the planned response
2. Ignore the trigger until project closure
3. Automatically cancel the project
4. Delete the risk from the risk register

Correct Answer: 1. Monitor for the trigger and prepare the planned response

Explanation:

A risk trigger is a condition or event that indicates a risk may be occurring or is becoming more likely. When a trigger is identified, the project team should monitor for it and be prepared to implement the planned risk response. For example, a supplier warning about a potential delivery delay could trigger a previously planned contingency response. The risk should remain appropriately documented and monitored until it is resolved, accepted, or otherwise managed according to the project’s risk process. Ignoring a trigger can reduce response time and increase potential impact. Effective risk management relies on recognizing early warning signs.

Question 171. Which document is used to track problems that have already occurred?

1. Issue log
2. Risk register
3. Stakeholder register
4. Assumption log

Correct Answer: 1. Issue log

Explanation:

An issue log records problems or concerns that have already occurred and require action or resolution. Issues may involve schedule delays, technical failures, resource shortages, vendor problems, quality defects, or stakeholder conflicts. The log can include the issue description, owner, priority, status, target resolution date, and actions taken. A risk register is different because it records uncertain events that may occur in the future. A stakeholder register focuses on project stakeholders, while an assumption log records assumptions and constraints relevant to planning. Keeping an issue log current helps the project manager track accountability and ensure that unresolved problems receive appropriate attention.

Question 172. What is the main purpose of a requirements traceability matrix?

1. To connect requirements with their sources, deliverables, and validation activities
2. To calculate project profitability
3. To schedule employee vacations
4. To replace the project charter

Correct Answer: 1. To connect requirements with their sources, deliverables, and validation activities

Explanation:

A requirements traceability matrix provides a structured way to connect project requirements with their sources, related deliverables, design or development activities, and validation or acceptance activities. It helps the project team confirm that requirements are addressed throughout the project and reduces the possibility of important requirements being forgotten. The matrix can also help identify the impact of requirement changes and support testing or acceptance activities. It does not calculate profitability or manage employee vacations. It also does not replace the project charter. Traceability is particularly valuable when a project contains many requirements or when demonstrating that contractual or customer expectations have been addressed.

Question 173. A customer requests an additional feature after the scope baseline has been approved. What should happen next?

1. Evaluate the request through the formal change control process
2. Add the feature immediately
3. Reject every customer request automatically
4. Hide the request from the project sponsor

Correct Answer: 1. Evaluate the request through the formal change control process

Explanation:

Once the scope baseline has been approved, a request for additional work should normally be evaluated through the project’s formal change control process. The project team should determine how the requested feature could affect scope, schedule, cost, quality, resources, risks, and other project commitments. Appropriate authority then decides whether the change should be approved, rejected, deferred, or returned for additional information. Implementing the feature immediately without evaluation can create uncontrolled scope changes and may cause the project to exceed its approved budget or deadline. Formal change control provides a consistent and traceable way to manage modifications to approved project plans.

Question 174. Which procurement document describes the goods or services a buyer expects a supplier to provide?

1. Statement of work
2. Risk register
3. Lessons learned register
4. Stakeholder engagement assessment

Correct Answer: 1. Statement of work

Explanation:

A statement of work, or SOW, describes the products, services, or results that a supplier is expected to provide. It can define the scope of procurement work, deliverables, requirements, performance expectations, standards, assumptions, constraints, and acceptance conditions. A clear SOW helps potential suppliers understand what the organization needs and provides a basis for evaluating proposals and later assessing vendor performance. A risk register documents project risks, a lessons learned register captures knowledge gained during the project, and a stakeholder engagement assessment focuses on stakeholder relationships. Procurement documentation should be sufficiently clear to reduce ambiguity and support consistent supplier expectations.

Question 175. What is the purpose of acceptance criteria?

1. To define the conditions a deliverable must meet to be accepted
2. To assign employee salaries
3. To identify every project risk
4. To calculate resource utilization

Correct Answer: 1. To define the conditions a deliverable must meet to be accepted

Explanation:

Acceptance criteria define the specific conditions or standards that a deliverable must satisfy before the customer, sponsor, or authorized stakeholder can formally accept it. Criteria should be clear enough to support objective evaluation and may address functionality, quality, performance, compliance, completeness, or other requirements. Well-defined acceptance criteria reduce disagreements because stakeholders understand what constitutes an acceptable result before evaluation occurs. They are different from the risk register, which addresses uncertainty, and from resource metrics, which measure resource usage. Acceptance criteria also support validation and formal acceptance activities during project execution and closure.

Question 176. A project team member is unavailable unexpectedly, causing an important activity to be delayed. What should the project manager review?

1. Resource availability and the project schedule
2. Only the project title
3. The organization logo
4. Archived meeting invitations

Correct Answer: 1. Resource availability and the project schedule

Explanation:

When a key team member becomes unavailable, the project manager should review resource availability and the project schedule to determine the effect on planned work. The manager may need to identify another qualified resource, adjust task sequencing, revise assignments, or evaluate schedule impacts. The appropriate response depends on the activity’s importance, dependencies, available alternatives, and project constraints. Reviewing only unrelated administrative information would not address the underlying scheduling problem. Resource availability should be considered together with dependencies and the critical path where applicable. Early assessment helps the project manager respond before the resource shortage causes additional delays or downstream impacts.

Question 177. What is the primary purpose of project status reporting?

1. To communicate current project performance, progress, risks, issues, and decisions
2. To replace all project documentation
3. To approve employee promotions
4. To eliminate stakeholder meetings permanently

Correct Answer: 1. To communicate current project performance, progress, risks, issues, and decisions

Explanation:

Project status reports provide stakeholders with a structured summary of the project’s current condition. Depending on the organization, a status report may include progress against milestones, schedule and cost information, completed and upcoming work, risks, issues, changes, decisions required, and areas requiring attention. Consistent reporting helps stakeholders understand whether the project remains aligned with approved expectations and whether escalation or corrective action is needed. Status reporting does not replace detailed project records or eliminate the need for appropriate meetings. The level of detail and frequency should be based on stakeholder needs, governance requirements, project complexity, and organizational practices.

Question 178. Which action is most appropriate when a project deliverable fails an agreed quality test?

1. Document the nonconformance and determine corrective action
2. Accept the deliverable without review
3. Delete the test results
4. Close the project immediately

Correct Answer: 1. Document the nonconformance and determine corrective action

Explanation:

When a deliverable fails an agreed quality test, the project team should document the nonconformance and determine the appropriate corrective action. The response may involve fixing the defect, retesting the deliverable, investigating the cause, or escalating the problem according to project procedures. Accepting a failed deliverable without review could result in an outcome that does not satisfy requirements or acceptance criteria. Test results should be retained because they provide evidence of quality performance and may be useful for analysis and audit purposes. Quality control focuses on evaluating deliverables and identifying defects so that problems can be addressed before formal acceptance.

Question 179. What is the purpose of a communication management approach?

1. To determine what information stakeholders need, when they need it, and how it should be delivered
2. To prevent all communication with stakeholders
3. To assign project costs
4. To replace the risk management process

Correct Answer: 1. To determine what information stakeholders need, when they need it, and how it should be delivered

Explanation:

A communication management approach establishes how project information will be collected, created, distributed, stored, and communicated to stakeholders. Different stakeholders may require different levels of detail, communication frequency, formats, and channels. For example, an executive sponsor may need concise performance summaries, while technical team members may require detailed implementation information. Effective communication also considers confidentiality, organizational procedures, time zones, language, technology availability, and stakeholder preferences when appropriate. The purpose is not to communicate everything to everyone, but to provide relevant information to the appropriate people at the appropriate time through suitable methods.

Question 180. Which activity helps ensure that project records remain available for future reference after closure?

1. Archiving project documentation
2. Deleting all project files
3. Removing approved baselines
4. Destroying acceptance records

Correct Answer: 1. Archiving project documentation

Explanation:

Archiving project documentation preserves important records after a project has been formally completed. Archived materials may include approved plans, requirements, contracts, change records, acceptance documentation, financial information, schedules, status reports, lessons learned, quality records, and final reports. Proper archival supports organizational knowledge, future projects, audits, contractual requirements, and historical reference. The exact retention period and storage method depend on organizational policies, legal requirements, contractual obligations, and information classification. Deleting project files or destroying acceptance records can remove important evidence and reduce the organization’s ability to understand how the project was managed and completed.