This question belongs to the People domain because it centers on customer engagement, feedback, and adaptive teamwork. PMI's communication and stakeholder guidance emphasizes that project communication must create understanding and support action, not just produce frequent reports. Since the customer remains dissatisfied despite regular communication, the problem is likely not the volume of communication but the project's responsiveness to customer needs. The best action is to review the situation directly with the customer and then make the necessary adjustments with the team.
Option A is weak because explaining that the team is new to agile does not solve the customer's problem.
Option C reduces communication and focuses on formatting, which misses the root issue. Option D may be helpful later, but changing sprint review frequency alone is less effective than understanding dissatisfaction and adapting accordingly. PMP-style thinking in agile environments favors feedback loops, collaboration, and adjustment based on stakeholder input. Therefore, the strongest answer is to work with the customer to understand the concern and then align the team's actions to improve customer satisfaction.

The project manager should determine the appropriate approach for evaluating employee performance1. This involves establishing a framework for performance measurement that is tailored to the unique characteristics of project management1. This could include metrics such as task accountability, team member influence, and decision-making authority1. However, it's important to note that these metrics should be used in conjunction with other forms of feedback, such as input from the project team and stakeholders21. This comprehensive approach ensures a more accurate and holistic assessment of employee performance1. References:
https://www.coursera.org/articles/project-management-lifecycle

In project management, especially in complex projects with a high number of artifacts, it's crucial to ensure that all stakeholders have access to the necessary information. If some stakeholders are having issues accessing the artifacts, the project manager should ensure that the project artifacts are kept up-to-date and shared with the stakeholders. This approach ensures transparency and keeps everyone on the same page, which is essential for the success of the project. References: PMBOK Guide - Sixth Edition, Project Management Institute, Inc., 2017, p. 139. Available at: PMI

The stakeholder register is a project document that identifies and classifies the project stakeholders, their roles, interests, expectations, and influence levels. It is an output of the Identify Stakeholders process, which is the first process in the Project Stakeholder Management knowledge area. The stakeholder register should be updated whenever there are changes in the project environment or stakeholder information, such as a promotion, a change of role, or a change of contact details. Updating the stakeholder register will help the project manager and the project team to communicate effectively and appropriately with the stakeholders, and to manage their expectations and engagement levels throughout the project life cycle.
The project management plan is a comprehensive document that describes how the project will be executed, monitored, and controlled. It integrates and consolidates the subsidiary plans and baselines from the different knowledge areas, such as scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder management. The project management plan is an output of the Develop Project Management Plan process, which is the second process in the Project Integration Management knowledge area. The project management plan should be updated only when there are changes in the project scope, objectives, deliverables, or approach, and when these changes are approved through the Perform Integrated Change Control process. Updating the project management plan for a stakeholder promotion is not necessary, unless it affects the project scope or other aspects of the project.
The stakeholder engagement plan is a subsidiary plan of the project management plan that describes the strategies and actions to increase the support and minimize the resistance of the stakeholders throughout the project. It is an output of the Plan Stakeholder Engagement process, which is the second process in the Project Stakeholder Management knowledge area. The stakeholder engagement plan should be updated when there are changes in the stakeholder engagement levels, needs, or expectations, and when these changes are approved through the Perform Integrated Change Control process. Updating the stakeholder engagement plan for a stakeholder promotion may be required, depending on how it affects the stakeholder's interest, influence, or power over the project.
The communications management plan is a subsidiary plan of the project management plan that describes the communication methods, formats, frequency, and responsibilities for the project. It is an output of the Plan Communications Management process, which is the first process in the Project Communications Management knowledge area. The communications management plan should be updated when there are changes in the communication requirements, preferences, or channels of the project stakeholders, and when these changes are approved through the Perform Integrated Change Control process. Updating the communications management plan for a stakeholder promotion may be necessary, depending on how it affects the stakeholder' s communication needs or preferences.
Therefore, the correct answer is C. Stakeholder register, as it is the most relevant and appropriate document to update for a stakeholder promotion.
References:
PMBOK Guide, 6th edition, pages 513-515, 520-521, 538-539, 563-564, 717-718.
PMP Exam Content Outline, June 2019, pages 6-7, 10-11, 14-15, 18-19.

The project manager should explain that more features can be planned in upcoming iterations and begin building the product12. This approach aligns with the principles of Agile project management, which emphasizes iterative development and the delivery of incremental value12. By starting the build phase, the team can start delivering value and receiving feedback, which can inform the planning and development of additional features in future iterations12. This approach also helps to prevent scope creep, which can delay the project and increase costs3. References:
https://www.projectpractical.com/12-steps-to-initiate-and-plan-a-successful-project/ https://asana.com
/resources/project-initiation