View Full PMI CAPM Exam Dumps and Practice Test Dumps

 

Question 221. A project manager is initiating a project and needs formal authorization to begin the project and use organizational resources. Which document provides this authorization?

1. Project management plan
2. Project charter
3. Stakeholder register
4. Business case

Correct Answer: 2. Project charter

Explanation:
The project charter formally authorizes the existence of a project and gives the project manager authority to apply organizational resources to project activities. It typically includes high-level information such as project purpose, objectives, requirements, assumptions, constraints, high-level risks, milestones, budget information, and the assigned project manager’s authority. The business case provides justification for undertaking the project but does not itself formally authorize the project. The project management plan explains how the project will be executed, monitored, controlled, and closed after authorization.

Question 222. A project sponsor asks the project manager to explain why the organization should invest in the proposed project. Which document provides the justification for making this investment?

1. Business case
2. Team charter
3. Issue log
4. Requirements traceability matrix

Correct Answer: 1. Business case

Explanation:
The business case provides the justification for undertaking a project by describing the business need, expected benefits, costs, risks, strategic alignment, and other factors supporting the investment decision. It helps organizational leaders determine whether the proposed project is worthwhile and aligned with organizational objectives. The project charter subsequently authorizes the project and provides high-level direction. A team charter establishes team working agreements, an issue log records current problems, and a requirements traceability matrix connects requirements to related deliverables and project work. Therefore, the business case is the primary document used to justify the proposed investment.

Question 223. A project manager is clarifying the difference between the product being created and the work required to create it. Which statement correctly distinguishes product scope from project scope?

1. Product scope describes the project schedule, while project scope describes product quality
2. Product scope describes the features and functions of the product, while project scope describes the work required to deliver it
3. Product scope applies only to predictive projects, while project scope applies only to adaptive projects
4. Product scope and project scope always mean exactly the same thing

Correct Answer: 2. Product scope describes the features and functions of the product, while project scope describes the work required to deliver it

Explanation:
Product scope refers to the features, functions, characteristics, and capabilities that define a product, service, or result. Project scope refers to the work that must be performed to deliver that product, service, or result with the specified features and functions. Understanding this distinction helps prevent confusion between what is being delivered and the work necessary to produce it. Product scope can be described through requirements and product specifications, while project scope is represented through the project work and related scope documentation. The two concepts are closely related but are not identical.

Question 224. A project team needs to discover detailed requirements directly from several users who have different experiences with the proposed product. Which technique is most appropriate for obtaining individual perspectives?

1. Interviews
2. Procurement audit
3. Trend analysis
4. Reserve analysis

Correct Answer: 1. Interviews

Explanation:
Interviews are a requirements elicitation technique used to obtain information directly from stakeholders or subject matter experts. They are particularly useful when the project team needs detailed individual perspectives, clarification of specific needs, or information that may not emerge effectively in a larger group setting. Interviews can be structured, semi-structured, or informal depending on the project context. Focus groups are more appropriate when gathering perspectives from a selected group at the same time. Workshops can also be useful for collaborative requirements development. The choice of elicitation technique should reflect the information needed and the characteristics of the stakeholders involved.

Question 225. A product owner has a long list of requested features and asks the team to identify which requirements provide the most value and should be addressed first. What should the team do?

1. Prioritize the requirements
2. Archive the requirements
3. Remove all low-cost requirements
4. Delay all requirements until project closure

Correct Answer: 1. Prioritize the requirements

Explanation:
Requirements prioritization involves determining the relative importance of requirements so that the team can focus effort on the items that provide the greatest value or satisfy the most important needs. In adaptive environments, prioritization is especially important because work is often delivered incrementally and the team may not be able to implement every requirement immediately. Factors such as business value, risk, dependencies, urgency, regulatory needs, and stakeholder expectations can influence priority. Prioritization does not necessarily mean permanently removing lower-priority requirements; those requirements may remain in the backlog for future consideration.

Question 226. An adaptive team is deciding which product features are essential, desirable, or optional before planning upcoming work. Which prioritization approach could help categorize the requirements?

1. Critical path analysis
2. MoSCoW prioritization
3. Earned value analysis
4. Monte Carlo analysis

Correct Answer: 2. MoSCoW prioritization

Explanation:
MoSCoW is a prioritization technique that categorizes requirements into Must have, Should have, Could have, and Won’t have at this time. It helps stakeholders and teams communicate relative priority and establish realistic expectations about what should be addressed first. Must-have requirements are considered essential for the solution to meet its objectives, while lower categories represent progressively less immediate needs. Critical path analysis focuses on schedule activities, earned value analysis evaluates project performance, and Monte Carlo analysis can model uncertainty. MoSCoW is therefore appropriate when a team needs to classify requirements according to importance and urgency.

Question 227. A project team wants to release a simple version of a product containing only enough functionality to test whether the proposed solution provides value to users. What concept does this describe?

1. Minimum viable product
2. Scope baseline
3. Work package
4. Configuration item

Correct Answer: 1. Minimum viable product

Explanation:
A minimum viable product (MVP) is a version of a product that contains enough functionality to provide value and enable learning or validation with users. The purpose is not to deliver every planned feature but to obtain meaningful feedback and evidence before investing in additional functionality. MVPs can help teams validate assumptions, learn about user needs, and reduce uncertainty. An MVP should still meet the agreed quality and usability expectations appropriate to its intended purpose. A work package is a component of the WBS, while a scope baseline defines approved project scope and a configuration item is a controlled product or project element.

Question 228. During an adaptive project, stakeholders review a completed increment at the end of an iteration and provide feedback about the product. Which activity is taking place?

1. Iteration retrospective
2. Iteration review
3. Risk reassessment
4. Procurement audit

Correct Answer: 2. Iteration review

Explanation:
An iteration review focuses on examining the product increment created during an iteration and obtaining feedback from stakeholders. The team demonstrates completed functionality and uses stakeholder feedback to help guide future priorities and adjustments. This differs from a retrospective, which focuses primarily on the team’s process, collaboration, and opportunities for improvement. The review is therefore product-focused, while the retrospective is process-focused. Regular stakeholder feedback during adaptive delivery helps ensure that future work remains aligned with evolving needs and provides opportunities to identify changes in priorities or requirements.

Question 229. An adaptive team wants to examine how its collaboration and working practices can improve after completing an iteration. Which activity should the team conduct?

1. Product acceptance
2. Procurement negotiation
3. Retrospective
4. Requirements validation

Correct Answer: 3. Retrospective

Explanation:
A retrospective provides an opportunity for the team to reflect on its recent work and identify ways to improve collaboration, communication, processes, and working practices. Team members may discuss what went well, what did not go well, and what changes could improve future iterations. The purpose is continuous improvement rather than formal acceptance of the product. A product review focuses on the increment and stakeholder feedback, while a retrospective focuses on the team’s process and performance. Regular retrospectives can help adaptive teams identify practical improvements and incorporate those improvements into subsequent iterations.

Question 230. A project manager uses active listening, coaching, and facilitation to help team members solve problems independently rather than simply giving them instructions. Which leadership approach is being demonstrated?

1. Servant leadership
2. Directive management
3. Command-and-control leadership
4. Transactional procurement management

Correct Answer: 1. Servant leadership

Explanation:
Servant leadership emphasizes supporting and enabling team members rather than relying primarily on authority or directive control. A servant leader helps remove obstacles, facilitates collaboration, coaches team members, encourages autonomy, and creates an environment where the team can perform effectively. This approach is particularly relevant in adaptive environments where self-organizing teams are expected to make many day-to-day decisions. Directive management may involve giving explicit instructions, while command-and-control approaches rely heavily on centralized authority. Servant leadership focuses on enabling the team to achieve objectives by providing support, guidance, and facilitation.

Question 231. A project manager notices that a stakeholder frequently misunderstands technical information presented in written reports. What should the project manager do first?

1. Continue using the same communication method to maintain consistency
2. Analyze the stakeholder’s communication needs and adapt the communication approach
3. Remove the stakeholder from the distribution list
4. Stop providing project information until requested

Correct Answer: 2. Analyze the stakeholder’s communication needs and adapt the communication approach

Explanation:
Effective communication requires the project manager to consider the information needs, preferences, context, and capabilities of the intended audience. If a stakeholder repeatedly misunderstands technical written reports, the project manager should assess the communication requirements and consider alternatives such as visual summaries, demonstrations, simplified language, meetings, or tailored reports. Maintaining an ineffective communication method simply for consistency does not improve understanding. Removing the stakeholder or withholding information could create additional engagement problems. Communication should be adapted so that the right information reaches the right stakeholder in a form that supports understanding and appropriate decision-making.

Question 232. A project manager displays key project information on a visible board so that team members and stakeholders can quickly see progress, work status, and emerging issues. What is this an example of?

1. Information radiator
2. Procurement register
3. Cost baseline
4. Configuration audit

Correct Answer: 1. Information radiator

Explanation:
An information radiator is a highly visible display that communicates important project information in a way that can be quickly understood by the intended audience. Examples can include task boards, burn charts, progress indicators, and other visual displays. Information radiators are particularly common in adaptive environments because they promote transparency and reduce the need for people to request status information individually. The displayed information should be current and relevant to the team’s needs. A cost baseline represents approved cost information, while procurement registers and configuration audits serve different project management purposes.

Question 233. A project manager is evaluating a newly identified threat by considering both its likelihood of occurring and its potential impact on project objectives. Which risk analysis approach is being used?

1. Qualitative risk analysis
2. Procurement analysis
3. Configuration management
4. Product decomposition

Correct Answer: 1. Qualitative risk analysis

Explanation:
Qualitative risk analysis assesses risks using characteristics such as probability and impact to determine their relative significance and priority. A probability-impact matrix is commonly used to categorize threats and opportunities according to their likelihood and potential effect on project objectives. This analysis helps the project team determine which risks may require more detailed assessment or response planning. Quantitative risk analysis, in contrast, uses numerical analysis to evaluate the potential effects of identified risks on project objectives. Qualitative analysis is often used first to prioritize risks and determine where additional analysis or response effort should be focused.

Question 234. A project team identifies an opportunity that could increase project benefits, but the team does not have the capability to realize the full opportunity internally. The project manager assigns a capable external partner to pursue it. Which opportunity response is being used?

1. Avoid
2. Mitigate
3. Share
4. Accept

Correct Answer: 3. Share

Explanation:
Share is an opportunity response used when responsibility for realizing a positive risk or opportunity is allocated to a third party that is better positioned to capture the benefit. This can involve partnerships, joint ventures, special-purpose companies, or other collaborative arrangements. The goal is to increase the likelihood or potential benefit of the opportunity by involving a party with appropriate expertise or resources. Avoid is generally a threat response, while mitigate reduces the probability or impact of a threat. Accepting an opportunity means taking advantage of it if it occurs without proactively assigning ownership to another party.

Question 235. A project manager needs to purchase a specialized component, and the seller will be paid a predetermined amount for completing the agreed work regardless of the seller’s actual costs. Which contract type is most appropriate?

1. Cost-reimbursable contract
2. Time and materials contract
3. Fixed-price contract
4. Cost-plus-incentive-fee contract

Correct Answer: 3. Fixed-price contract

Explanation:
A fixed-price contract establishes a predetermined price for the agreed scope of work. Under this arrangement, the seller generally bears greater risk if the actual cost of performing the work exceeds the agreed price, assuming the scope and contractual conditions remain unchanged. Fixed-price contracts are appropriate when requirements and scope can be defined with reasonable clarity. Cost-reimbursable contracts reimburse allowable seller costs and generally place more cost risk on the buyer. Time and materials contracts combine elements of fixed rates and variable quantities. The project manager should select the contract type based on scope clarity, risk allocation, market conditions, and procurement objectives.

Question 236. A buyer is uncertain about the exact amount of labor and materials required for a short-term procurement but wants to establish agreed hourly or daily rates. Which contract type may be appropriate?

1. Fixed-price contract
2. Time and materials contract
3. Cost-plus-fixed-fee contract
4. Lump-sum incentive contract

Correct Answer: 2. Time and materials contract

Explanation:
A time and materials (T&M) contract combines characteristics of fixed-price and cost-reimbursable arrangements. The buyer and seller agree on fixed rates for labor categories or units of material, while the final amount depends on the actual quantity of time and materials used. T&M contracts can be useful when the exact scope or duration is not fully defined but the buyer can establish reasonable unit rates. Because the total cost can vary with the amount of work performed, the buyer should use appropriate controls, such as ceilings or approval limits, when suitable.

Question 237. A project manager wants to prevent unauthorized changes to an approved product specification and ensure that the correct version is being used by the team. Which practice is most appropriate?

1. Configuration management
2. Stakeholder analysis
3. Qualitative risk analysis
4. Resource smoothing

Correct Answer: 1. Configuration management

Explanation:
Configuration management establishes processes for identifying, documenting, controlling, and tracking changes to project and product characteristics. It helps ensure that approved versions of specifications, documents, designs, and other controlled items are consistently used. Configuration management can include version identification, change tracking, status accounting, and verification that changes have been properly authorized. This is particularly important when multiple team members work with evolving technical information. Stakeholder analysis, risk analysis, and resource smoothing address different project management concerns and do not directly provide control over product or document versions.

Question 238. A project is divided into formal stages, and management wants to evaluate whether the project should continue at the end of each stage before authorizing the next stage. What is this review commonly called?

1. Phase gate review
2. Daily stand-up
3. Requirements workshop
4. Procurement audit

Correct Answer: 1. Phase gate review

Explanation:
A phase gate review is a decision point at the end of a project phase where stakeholders or governance authorities evaluate project performance, deliverables, risks, business justification, and readiness to proceed. Depending on the organization’s governance approach, the decision may involve continuing, modifying, pausing, or terminating the project or phase. Phase gates provide structured oversight and help ensure that significant investments remain justified as the project progresses. A daily stand-up supports team coordination, a requirements workshop supports elicitation and clarification, and a procurement audit examines procurement processes or results.

Question 239. A project team needs to decide how much work should be completed during each iteration while ensuring that selected work is realistic for the team’s capacity. What should the team consider most directly?

1. Stakeholder influence only
2. Team capacity and prioritized work
3. Historical project cost only
4. Procurement contract value only

Correct Answer: 2. Team capacity and prioritized work

Explanation:
When planning an iteration, an adaptive team should consider the priority of available work along with the team’s realistic capacity. The team needs to select an achievable amount of work rather than committing to more work than can reasonably be completed. Capacity can be affected by team availability, skills, planned absences, technical constraints, and other factors. Prioritized work helps ensure that the team focuses on the most valuable or important items first. Considering both priority and capacity supports sustainable delivery and helps reduce excessive unfinished work or frequent iteration commitments that cannot be met.

Question 240. A project manager is closing a project and confirms that all contractual obligations, deliverables, and closure requirements have been completed. What should the project manager do next?

1. Continue executing project activities until the original team members leave
2. Restart planning to identify additional project work
3. Obtain formal confirmation of closure and complete organizational closure activities
4. Add new features to increase stakeholder satisfaction

Correct Answer: 3. Obtain formal confirmation of closure and complete organizational closure activities

Explanation:
Once project deliverables, contractual obligations, and closure requirements have been satisfied, the project manager should complete formal closure activities according to organizational procedures. This may include obtaining formal acceptance or confirmation of closure, transitioning remaining responsibilities, closing procurements, releasing resources, finalizing documentation, archiving records, and ensuring required organizational processes are completed. Adding new features or continuing project work after closure criteria are met would create unnecessary additional work. Proper closure ensures that the project is formally concluded and that responsibilities and information are appropriately transitioned to the organization or operational stakeholders.