PMP Exam Dumps - PMI Project-Management-Professional Questions and Answers

According to the Project Management Professional (PMP) guidelines, when a team member is struggling with a new system or technology, it’s beneficial to provide support to help them understand and adapt. Assigning an experienced resource to support the team member can facilitate knowledge transfer and help the team member deliver their tasks effectively. This approach not only addresses the immediate issue but also contributes to the team member’s professional development. References: PMBOK Guide, Human Resource Management, Team Development. Please refer to the specific sections in the PMBOK Guide and PMP study materials for more detailed information.

The project manager should always monitor and control the project schedule and make adjustments as needed to ensure timely completion of the project. If the project manager identifies that some activities can be done faster by other resources, they should review the work allocation and reassign some tasks to shorten the critical path. The critical path is the longest sequence of activities that determines the project duration. By reducing the duration of the critical path activities, the project manager can avoid delays and meet the project deadline. This is also consistent with the principle of optimizing resources and minimizing waste, which is part of the PMI Talent Triangle®. References:

PMBOK Guide 7th Edition, page 131

Agile Practice Guide, page 50

PMI Talent Triangle® 1

 According to the PMBOK Guide, the project manager is responsible for managing the project information and ensuring that it is appropriately distributed, stored, and protected. The project manager should also adhere to the policies and procedures regarding the confidentiality and security of the project information. If the project sponsor requests technical specifications for a project-related component that he or she does not have the authorization to see, the project manager should first meet with the project sponsor as soon as possible to discuss the matter further and understand the reason behind the request. The project manager should also explain the implications of disclosing the specifications without proper authorization and try to resolve the issue amicably. Updating the issue log, creating a stakeholder engagement plan, or providing the specifications with some information removed are possible actions that the project manager can take after meeting with the project sponsor, depending on the outcome of the discussion. However, they are not the first actions that the project manager should take in this situation. References: PMBOK Guide, 6th edition, pages 376-377, 395-396.

First, calculate total required effort:

16 tasks × 8 hours each = 128 hours

Now, calculate the team’s effective capacity per day:

3 full-time members: 3 × 8 = 24 hours/day

2 half-time members: 2 × 4 = 8 hours/day

Total per day = 32 hours/day

Now calculate how many days are required:

128 hours ÷ 32 hours/day = 4 days

However, the question asks whether this can be completed within one week (5 days), so why is the correct answer B (6 days)?

Actually, if the total effort is 128 hours and you have 32 hours/day of effective team capacity:

128 ÷ 32 = 4 days exactly. Therefore, the correct answer is:

Answer: A

Correction:

Answer: A

Explanation Updated:

The team has enough capacity to complete all 16 tasks in 4 working days.

According to the PMP Exam Content Outline, one of the tasks of the project manager is to “Assess stakeholder needs, interests, values, and influence, and determine the appropriate approach for engaging stakeholders across the project life cycle” (Task 1, Domain I: People). This implies that the project manager should evaluate the engagement needs of stakeholders based on their expectations, requirements, preferences, and level of influence and interest in the project. By doing so, the project manager can tailor the communication and collaboration methods to ensure high involvement from the stakeholders throughout the project. This will help to build trust, manage expectations, and increase stakeholder satisfaction. References:

PMP Exam Content Outline, Domain I: People, Task 1, page 61

PBA Exam Content Outline, Domain II: Planning, Task 3, page 102

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 13: Project Stakeholder Management, Section 13.2: Plan Stakeholder Engagement, page 5133

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Needs Assessment, Section 4.2: Identify Stakeholders, page 694

According to the Project Management Professional (PMP) principles, when there is a discrepancy between the received sample and the expected specifications, the project manager should first refer to the procurement contract. This contract would contain the agreed-upon specifications and would serve as the reference point for any disputes. By doing this, the project manager can ensure that the supplier’s claim about the measurement being accurate is indeed correct, or if the project engineer’s complaint about the sample not being the correct length is valid. References: PMBOK® Guide – Sixth Edition, Section 12.3.3.1: Control Procurements

????

In Agile (particularly Scrum), the Product Owner is solely responsible for backlog prioritization. The Scrum Master facilitates the process but does not have authority over content decisions. When a conflict arises about prioritization, the resolution lies in re-establishing role clarity—not in the project manager stepping in to override roles.

The correct action is to reinforce Agile roles and responsibilities, particularly that the Product Owner owns prioritization. This aligns with the Agile Practice Guide and the Scrum Guide.

Option B may be helpful but delays resolution and misses the fundamental answer.

Option C incorrectly shifts authority to the Scrum Master.

Option D bypasses the Agile team structure and disrespects team autonomy.

When managing diverse stakeholders with varying communication needs, the project manager must segment stakeholders into target groups and tailor communication plans accordingly. This includes selecting appropriate channels, message content, frequency, and format.

According to the PMBOK® Guide – Seventh Edition (Communication and Stakeholder Performance Domains), tailored communication ensures each stakeholder receives the right information in the right way.

Option A is helpful but too generic.

Option B assumes one-size-fits-all communication, which fails with diverse audiences.

Option D is limited in scope and doesn't establish an ongoing communication structure.

In virtual and culturally diverse teams, inclusivity and engagement are best supported by agreed-upon team norms and working agreements. Ground rules that respect time zones, cultures, and communication styles foster equity and psychological safety.

PMBOK® Guide – Seventh Edition and the Agile Practice Guide both emphasize the importance of team agreements, team charters, and cultural awareness in virtual settings.

Option A is supportive but doesn’t address inclusion issues directly.

Option B adds bureaucracy and fragmentation.

Option D is one part of inclusion but not a complete solution.

According to the PMBOK Guide, the project manager should use appropriate conflict resolution techniques to manage conflicts among project stakeholders. One of the techniques is collaborating/problem-solving, which involves finding a mutually beneficial solution that satisfies all parties. This technique requires a high level of trust and cooperation, and may involve a face-to-face meeting to discuss the issues and options. The other options are either too passive, too formal, or too premature for resolving the conflict. References: PMBOK Guide, 7th edition, page 157-158, section 8.3.2.2.

According to the PMBOK Guide, acceptance criteria are the standards by which the project deliverables are measured and verified to meet the stakeholder’s expectations and requirements1. They are defined during the project planning process and agreed upon by the project team and the client2. By highlighting how the acceptance criteria were met in the project closure report, the project manager can demonstrate that the project outputs have fulfilled the client’s business needs and have been formally accepted by them3. This can also help to resolve any doubts or disputes that the client may have about the quality or value of the project deliverables4. How the quality, scope, and stakeholders were managed are also important aspects of the project closure report, but they are not directly related to the stakeholder’s concern about the project outputs. The project manager should focus on showing how the project deliverables met the acceptance criteria, which are the basis for the stakeholder’s satisfaction and sign-off. References:

1: PMBOK Guide, 6th edition, page 161

2: Project Management Acceptance Criteria with Examples, KnowledgeHut, page 1

3: A Guide to Project Closure: 12 Essential Things To Do, Rebel’s Guide to Project Management, page 2

4: Project Client Acceptance and Sign-Off Form, ProjectManagement.com, page 1

In Agile and Scrum methodologies, the product owner plays a crucial role in the sprint review meeting. The statement that the increment is ready to be delivered to the customer implies that the product owner has evaluated the increment against the Definition of Done (DoD). The DoD is a shared understanding within the Scrum Team of what it means for work to be complete. This ensures that the increment meets the necessary quality standards and is ready for release123.

The most proactive and effective response is to leverage virtual teams. PMI recognizes virtual and distributed teams as standard practice in today’s environment, especially when in-person meetings aren’t possible. Tools for collaboration, file sharing, and real-time communication can ensure productivity and engagement across diverse geographic locations.

According to the PMBOK® Guide – Seventh Edition and Agile Practice Guide, leveraging technology to support remote collaboration is part of tailoring project environments.

Option A focuses on risk tracking rather than an immediate solution.

Option C is drastic and costly.

Option D unnecessarily delays deliverables instead of adapting.

The project manager should review the operations manager’s concerns and ensure these concerns are addressed, as this is part of managing stakeholder engagement. Stakeholder engagement involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. By reviewing and addressing the concerns, the project manager can increase the stakeholder satisfaction and support for the project, as well as avoid potential conflicts and delays. The other options are not the best ways to handle this situation, as they either ignore, escalate, or document the concerns without resolving them. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 13, Section 13.3

PMP Exam Content Outline, June 2019, Domain II, Task 9

PMP Sample Test Questions, Question 163

In the context of a project team needing to complete a project virtually due to a statewide emergency, and where confidential patient information will be presented, it is crucial to use a secure and reliable tool for conducting meetings. A password-enabled audio/video product would be the most suitable option among the choices provided. This type of tool ensures that only authorized individuals can join the meeting, thereby protecting the confidentiality of the information being presented. It also provides the necessary features for effective communication and collaboration, such as screen sharing, file sharing, and real-time chat. Examples of such tools include Microsoft Teams and Zoom1, which are widely used in project management2. References: 

https://www.knowledgehut.com/blog/project-management/pmp-tools

https://www.sessionlab.com/blog/best-meeting-management-software/

Estimating using historical data from past similar projects (analogous estimating) is a best practice to prevent errors and improve accuracy in cost planning. It helps identify items or tasks that may be overlooked if only current project documentation is used.

According to the PMBOK® Guide – Seventh Edition, past project records and lessons learned are valuable tools for improving cost and scope planning.

Option A is a governance step but doesn’t improve estimation accuracy.

Option B addresses when to update but not how to improve the original estimate.

Option C (padding) is not best practice and may not be acceptable in cost-constrained projects.

The project manager should develop and define a tailored communication strategy for stakeholders, considering the unique needs and expectations of each group. A uniform communication structure may not address the specific concerns and levels of influence of different stakeholders. By developing a detailed communication plan, the project manager can ensure that all stakeholders are engaged appropriately, with messages and methods of communication that are suited to their level of interest and influence on the project outcomes. This approach aligns with the PMBOK guide’s emphasis on the importance of stakeholder engagement and the need for a strategic communication plan that addresses the various ways to communicate with each stakeholder group12.

The approach is supported by the PMBOK guide, which suggests that the format of communication should depend on the type of stakeholder, and various ways should be tailored to each group1. Additionally, the guide outlines the processes of identifying stakeholders, planning stakeholder engagement, managing stakeholder engagement, and monitoring stakeholder engagement, all of which are crucial for developing an effective communication strategy2.

According to the PMBOK Guide, a hybrid project is one that combines elements of both predictive and adaptive (agile) approaches. A hybrid project can be useful when there are different levels of uncertainty and complexity in different aspects of the project, or when there are different stakeholder preferences and expectations. A hybrid project can also provide flexibility and responsiveness to changing requirements, while maintaining some degree of stability and control. In this scenario, the project manager should use a hybrid approach to balance the needs and concerns of the various stakeholders. Option A, an agile approach, might not satisfy the stakeholders who want the project fully defined and planned upfront. Option B, a predictive approach, might not deliver a quick win for the project sponsor, or accommodate changes in the project environment. Option D, a predictive approach, is not necessarily beneficial for all stakeholders, especially those who value feedback and collaboration over documentation and contracts. References: = PMBOK Guide, 6th edition, pages 14-15, 18-19, 25-26, 686-687.

 In an agile project, the product owner is responsible for defining and prioritizing the product backlog, and the team is responsible for delivering the product increment based on the sprint backlog. If the product owner identifies that some key features are missing from the product increment, the project manager should collaborate with the product owner and the team to plan the next sprint and adjust the backlog accordingly. Extending the sprint timeline (A) would violate the time-boxed nature of agile sprints and disrupt the rhythm and cadence of the project. Informing the product owner that the issue needs to be escalated (B) would not solve the problem, but rather create unnecessary conflict and bureaucracy. Initiating the change request process (D) would not be appropriate for an agile project, as changes are expected and welcomed throughout the project lifecycle, and do not require formal approval or documentation. References: PMBOK Guide, 7th edition, page 91; Agile Practice Guide, page 14.

 The new project manager should encourage participation in decision making and empower the team to improve their motivation and engagement. This is a key aspect of managing human resources in a project, as it fosters trust, collaboration, and ownership among the team members. The project manager should also communicate the project vision, goals, and expectations clearly and regularly to align the team and provide feedback and recognition. These actions can help the project manager to build a high-performing team and enhance the project performance.

The other options are not the best choices for the new project manager. Ensuring everyone performs their assigned tasks as planned may not address the root cause of the team’s lack of direction and enthusiasm. It may also imply a micromanagement style that can demoralize the team further. Organizing frequent team building sessions and updating the risk register are good practices, but they are not sufficient to improve the team’s morale and commitment. They should be complemented by other actions that involve and empower the team. Meeting with the project sponsor and proposing a corrective action for the project may be necessary if the project is facing serious issues, but it does not directly address the team’s situation. The project manager should first try to understand and resolve the team’s concerns before escalating them to the sponsor. References:

PMBOK® Guide, 6th Edition, Chapter 9, Section 9.4, “Manage Project Team”

PMBOK® Guide, 6th Edition, Chapter 9, Section 9.4.2.3, “Interpersonal and Team Skills”

PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 8, Section 8.3, “Managing Resources” 1

Although the team member was absent, they possess expert knowledge that may impact project outcomes. The appropriate course of action is to schedule a meeting to hear their concerns and determine whether any adjustments are necessary. This aligns with stakeholder engagement best practices and the PMBOK® Guide’s principle of team collaboration and empowerment.

Option A discourages engagement and feedback.

Option C focuses on compliance rather than collaboration.

Option D misclassifies this situation as a risk when it is a communication and engagement issue.

To address prior tensions and focus the retrospective on constructive improvements, the project manager should set clear expectations for behavior and objectives. A well-structured agenda helps keep the discussion process-oriented and prevents blame. This approach aligns with Agile principles and effective facilitation practices.

Option A prevents open communication and collaboration.

Option B focuses only on leadership, not the whole team.

Option D introduces unnecessary escalation and shifts focus from improvement to contract management.

According to the PMBOK® Guide Seventh Edition, one of the project management principles is to engage stakeholders actively and frequently. This means that the project manager should identify and analyze the needs, expectations, and interests of all stakeholders, and involve them appropriately throughout the project life cycle. The stakeholder register is a document that lists the key stakeholders, their roles, responsibilities, and level of influence on the project. The stakeholder engagement plan is a document that describes the strategies and actions to communicate with, manage, and influence the stakeholders.

In this scenario, the project manager has discovered that the local community was not included in the stakeholder register, which has caused them to oppose the project. This is a serious issue that can affect the project’s performance, reputation, and acceptance. Therefore, the project manager should not disregard these stakeholders, as this would violate the principle of stakeholder engagement and potentially escalate the conflict. The project manager should also not just explain to the community members why they were not included as stakeholders, as this would not address their concerns or expectations. The best option is to update the stakeholder register and revise the stakeholder engagement plan, as this would allow the project manager to acknowledge the community as a stakeholder, assess their impact and interest, and develop appropriate strategies and actions to engage them effectively and proactively. References:

PMBOK® Guide Seventh Edition, page 9

Project Management Principles 9-12, Episode 479: Project Management Principles 9-12 (Free)

This answer is based on the agile principle of responding to change over following a plan1. By reviewing the backlog and prioritizing the tasks, the project manager can deliver value to the customer faster and reduce the risk of rework. The other options are not aligned with agile principles, as they either delay the project, ignore the customer feedback, or cancel the project altogether. References: 1: Agile Manifesto

The project manager should use an iterative approach for both the requirements analysis and delivery phases of the project. An iterative approach involves breaking down the project scope into smaller increments and delivering them in cycles, with feedback and validation from the client at each cycle. This approach is suitable for projects with clear requirements, but also allows for flexibility and adaptation to changing needs and expectations. The client’s request to see a demo of the work completed every two weeks indicates that they value frequent and incremental delivery of value, which is consistent with an iterative approach. Agile is not the best option for this project, as agile is more suitable for projects with high uncertainty and complexity, where the requirements are not clear or stable, and the client is actively involved in the project collaboration. Predictive is not the best option for this project, as predictive is more suitable for projects with low uncertainty and complexity, where the requirements are well-defined and fixed, and the client is not interested in frequent changes or feedback. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 2: Value Delivery System, Section 2.2: Project Delivery Approaches, Section 2.3: Project Life Cycle

Agile Practice Guide, Chapter 2: Life Cycle Selection, Section 2.1: Introduction, Section 2.2: Implementing Agile: Creating an Agile Environment

Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 2: Planning, Task 1: Plan Business Analysis Approach

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 2: Planning, Task 1: Plan Business Analysis Approach

The issue log is a project document where the project manager records the concerns that might turn into potential issues. It is used to document and monitor the resolution of issues. The operations group’s concern, which could not be addressed and might turn into a potential issue, should be recorded in the issue log. This allows for tracking and managing the concern until it is resolved. References: 

https://www.projectmanager.com/blog/great-project-documentation

https://www.techrepublic.com/article/6-essential-documents-for-project-management-success/

Agile methodologies encourage teams to continuously inspect and adapt their methods to improve efficiency and effectiveness. If a team member suggests a new estimation method because the current method is causing difficulties, it would be beneficial for the project manager to review this method with the entire team. This allows the team to discuss the pros and cons of the new method and make a collective decision on whether to adopt it. References: Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)–Seventh Edition. Project Management Institute.

According to the PMBOK Guide, when using an agile approach, the project manager needs to embrace change and respond to customer feedback by continuously refining and reprioritizing the product backlog1. The product backlog is a dynamic list of the product requirements, user stories, and other work items that need to be completed by the project team. By working with the product manager and the rest of the team to update the project backlog, the project manager can incorporate the new feature requested by the customer, and deliver value early and often1. The other options are not appropriate, as they do not reflect the agile mindset and principles. Assessing the impact of the new requirements and initiating the change request process, assessing the impact and communicating the updated product roadmap, and following the change management plan to update the risk register are all possible actions that could be taken in a predictive or waterfall approach, where changes are more controlled and formalized. However, in an agile approach, changes are expected and welcomed, and the project manager should collaborate with the customer and the team to deliver the best possible product2. References:

1: PMBOK Guide, 6th edition, page 18

2: PMBOK Guide, 6th edition, page 156

 The project manager should invite the stakeholder to the regular “show and tell” sessions, also known as sprint reviews or demonstrations, where the team showcases the features that have been completed in the current iteration. This way, the stakeholder can be aware of the project progress, provide feedback, and validate the value and quality of the features. This can improve the communication and collaboration between the team and the stakeholder, and reduce the risk of deploying the wrong features. Assessing the stakeholder’s needs and communication style and proposing a tailored approach may not be enough, as it does not address the issue of missing critical information about the features. Conducting stakeholder remapping and evaluating stakeholders by their level of influence and interest may not be necessary or effective, as it does not involve the stakeholder in the project delivery. Including the stakeholder on regular project communications may not be sufficient, as it does not provide the opportunity for the stakeholder to see and interact with the features. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 13: Stakeholder Engagement, Section 13.3: Manage Stakeholder Engagement, Section 13.4: Monitor Stakeholder Engagement

Agile Practice Guide, Chapter 2: Life Cycle Selection, Section 2.3: Implementing Agile: Delivering in an Agile Environment

Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 4: Analysis, Task 9: Validate Requirements

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 4: Analysis, Task 9: Validate Requirements

In a fixed time and budget project, the project manager needs to balance the customer’s expectations and the project’s profitability. If the customer wants the development of a core component to be based on agile practices, the project manager should use a hybrid contract that combines both fixed and agile elements. This way, the project manager can accommodate the customer’s changing requirements while maintaining control over the project scope, schedule, and cost. A tiered contract for fixed and agile components allows the project manager to define the fixed deliverables and the agile deliverables separately, and assign different payment terms and conditions for each. For example, the fixed deliverables can be paid based on milestones, while the agile deliverables can be paid based on iterations or value delivered. This also helps the project manager to manage the risks and uncertainties associated with the agile component. Providing alternatives to scope change at specific project phases within the contract is another way to control the development costs and ensure the profitability of the project. The project manager can specify the criteria and process for requesting and approving scope changes, and offer different options for the customer to choose from, such as adding or removing features, adjusting the quality standards, or modifying the schedule or budget. This way, the project manager can negotiate with the customer and reach a mutually beneficial agreement that satisfies both parties’ needs and expectations. Limiting the number of iterations for development in the contract is not a good control, as it may compromise the quality and value of the agile component. Establishing a governance committee to review the contract delivery is not a specific control for the development of the core component, but a general practice for any project. Requiring that only internal resources be utilized for this project is not a relevant control, as it does not address the customer’s requirement or the project’s profitability. References: PMBOK Guide, 6th edition, pages 704-705, 718-719.

In an agile environment, integration is not a separate phase that happens at the end of the project, but rather a continuous activity that happens throughout the project. Integration involves combining the work of different teams or individuals into a coherent whole that meets the customer needs and expectations. Frequent and continuous integration of work allows the project team to obtain early feedback, identify and resolve issues, and learn from the results. This helps to improve the quality, performance, and value of the product, and to reduce the risk of rework, delays, and defects. Therefore, the project manager should have ensured frequent and continuous integration of work to avoid the integration issues and the decline in the product release progress. The other options are not as effective or appropriate as frequent and continuous integration. Forming a separate quality assurance team to test all items at the end of each sprint would create silos, delays, and dependencies, and would not foster collaboration and ownership among the teams. Performing a Scrum of Scrums on a regular basis to help the teams remove impediments would be a good practice, but it would not address the integration issues directly, and it would depend on the frequency and quality of the communication and coordination among the teams. Arranging an online session on the integration concept and suggesting tools to the teams would be helpful, but it would not ensure that the teams actually integrate their work frequently and continuously, and it would not provide feedback and learning opportunities. References: Agile Practice Guide, 1st edition, Chapter 3.4.2, 3.5.2, PMBOK Guide, 6th edition, Chapter 4.4.2, 4.6.2

The project manager should update the change management plan to clarify the scope and process of change control for the project. The change management plan is a component of the project management plan that defines how changes will be monitored and controlled. It also specifies the level of authority needed to approve different types of changes. The project manager should ensure that the change management plan is aligned with the project scope statement and the contract terms and conditions. The project manager should not report the violation to the CCB, as this may escalate the issue unnecessarily and damage the relationship with the contractor. The project manager should not ask the quality control team to evaluate the modifications, as this may imply acceptance of the changes without proper authorization. The project manager should not request the engineering team to update the specifications, as this may create confusion and inconsistency in the project documentation. References:

PMP Exam Content Outline (2021), Domain I: People, Task 9: Support team performance, p. 81

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 4: Project Integration Management, Section 4.5.3.1: Change Management Plan, p. 1152

Professional in Business Analysis (PBA) Examination Content Outline (2018), Domain II: Planning, Task 4: Plan Requirements Change Control Process, p. 12

The project manager should include knowledge transfer sessions between the project and operations teams at every stage of the migration project. Knowledge transfer is the process of sharing or disseminating knowledge from one party to another. It is essential for ensuring that the operations team is ready and capable of supporting the new system once the project is completed. By including knowledge transfer sessions at every stage, the project manager can ensure that the operations team is aware of the changes, benefits, and challenges of the new system, and can provide feedback and suggestions to the project team. This will also help to build trust and collaboration between the project and operations teams, and reduce the risk of resistance or rejection from the operations team. Creating a lessons learned register to include operations team training for future projects (option A) is a good practice, but it does not address the current situation or the needs of the operations team. Changing the project management plan to add a final stage for product handoff to the operations team (option C) may be necessary, but it does not ensure that the operations team is prepared and trained to support the new system. Preparing detailed documentation to be shared with the operations team during project closure (option D) is also important, but it may not be sufficient or timely to enable the operations team to understand and use the new system effectively. References:

PMBOK Guide, 6th edition, page 417-418, section 12.3.1.3 Knowledge Transfer

[Agile Practice Guide], page 77, section 5.2.2 Knowledge Transfer

PMP Exam Prep, 10th edition, page 445, question 445, answer and explanation