According to the PMBOK Guide, the communications management plan is a component of the project management plan that describes how, when, and by whom information about the project will be communicated to stakeholders. It also includes the communication methods, formats, frequency, and escalation process for resolving issues. When there is a change in the project stakeholders, the project manager should review and update the communications management plan to ensure that the new stakeholder is informed and engaged in the project. Sending evidence or suggesting a review of the project status may not address the root cause of the communication gap, and may not satisfy the new stakeholder's expectations and needs. Sharing the existing communications management plan without discussing the project requirements may not reflect the current situation and may not be effective for the new stakeholder. References: : PMBOK Guide, 6th edition, page 377 : PMBOK Guide, 6th edition, page 386 : How To Find The Correct Answer On PMP Exam Questions

According to the PMBOK Guide, an agile project is an adaptive life cycle project that follows an iterative and incremental approach. In an agile project, the project manager facilitates collaboration and empowers the team to deliver value. When an unidentified risk becomes an issue, the project manager should help the team review the project approach and initiate the corrective actions to address the issue and prevent recurrence.
Asking the sponsor to approve an additional iteration or money is not agile, as it implies that the project scope or budget is fixed and cannot accommodate changes. Asking the team to include the contingency plan in the iteration backlog is not appropriate, as the contingency plan should have been developed before the risk occurred and should be executed as soon as possible. References: PMBOK Guide, 6th edition, pages 18-19,
456-457, 686-687.

The best action for a project manager to control scope creep in a global project with resources spread out in different locations is to ensure that any changes to the project scope are formally controlled. This is typically done through a change control board (CCB), which is a formal group responsible for reviewing, evaluating, and approving or rejecting changes to a project. The CCB ensures that any changes made to the project are carefully considered, evaluated for their impact, and aligned with the project's objectives and constraints12.
By having a CCB, the project manager can manage scope changes in a controlled manner, preventing scope creep and ensuring that the project remains on track.
References:
Control Scope Process3
Change Control Board: Roles, Responsibilities & Processes1
Change Control Board: What is It in Project Management?2

Transitioning from a predictive to an agile approach requires a cultural shift and an organizational commitment1. Engaging operation teams in retrospectives and demo sessions allows for direct feedback on the product, which can lead to improvements in the transition to operations and minimize support issues2. This engagement is crucial as it fosters a collaborative environment where operational insights can directly influence the development process, ensuring that the product is aligned with operational needs and reducing the likelihood of issues post-deployment3. References:
* Transitioning to agile - Project Management Institute1.
* How to Handle Production Support When Using Scrum2.
* Engaging Your Team to Greater Project Performance3.

When there is a conflict between the project team and organizational standards (represented by the PMO), the project manager should initiate a discussion among relevant subject matter experts to resolve the disagreement collaboratively. This approach ensures alignment between technical validity and compliance with organizational processes.
Option A escalates prematurely.
Option B bypasses the PMO's input.
Option C assumes external help is needed before internal resolution attempts.
References:
PMBOK Guide - Seventh Edition, Governance and Stakeholder Engagement Domains PMBOK Guide - Sixth Edition, Section 5.2 and 5.3: Collect and Define Requirements
-