According to the PMP Exam Study Guide, a subject matter expert (SME) is a person who has specialized knowledge or skills in a particular domain or area. A SME can provide valuable input and guidance on technical, functional, or business aspects of a project. In this scenario, the project manager should consult with a SME to see if the proposed change is acceptable, as it may affect the quality, performance, or functionality of the product or service. The SME can help the project manager to assess the impact of the change, evaluate the alternatives, and make an informed decision. The project manager should not accept, insist, or instruct the vendor without consulting with a SME, as this may lead to poor quality, customer dissatisfaction, or contractual issues. References:
* PMP Exam Study Guide, Chapter 9: Project Resource Management, Section 9.1: Plan Resource Management, p. 443
* PMP Exam Study Guide, Chapter 12: Project Procurement Management, Section 12.2: Conduct Procurements, p. 535-536
* PMP Exam Study Guide, Chapter 13: Project Stakeholder Management, Section 13.3: Manage Stakeholder Engagement, p. 573-574

In the absence of an existing knowledge management system, the project manager should coordinate with the team and stakeholders to collect the necessary knowledge. This approach ensures that all relevant information is captured and made available for the project's needs. It aligns with the principles of knowledge management in project management, which emphasize the importance of gathering, organizing, sharing, and analyzing knowledge to support project success1.
References:
Managing Project Management Knowledge - Project Management Institute1.

A change request is a formal document that proposes a modification to some aspect of the project, such as the user requirements, the deliverables, the schedule, the budget, or the quality standards123. Change requests can originate from various sources, such as the stakeholders, the project team, the customer, or the environment12. Change requests need to be evaluated and approved before they can be implemented, as they may have significant impacts on the project performance, scope, cost, time, quality, and risk123.
The project scope statement is a document that defines and documents the project objectives, deliverables, requirements, assumptions, constraints, and acceptance criteria12. The project scope statement is the basis for making project decisions and controlling changes12. Therefore, the project manager should evaluate the change request against the project scope statement to determine if the change is necessary, feasible, and beneficial for the project123. The project manager should also consider the impact of the change on the other project components, such as the schedule, the budget, the quality, and the risk123.
The other options are not the best actions for the project manager to take next. Discussing approval of the change request in the next project meeting (A) may delay the decision-making process and cause confusion among the project team and stakeholders. Performing a risk assessment on the required change request (B) is an important step, but it should be done after evaluating the change request against the project scope statement, as the risk assessment may depend on the scope implications of the change. Asking the sponsor for more funds to cover the change request (D) is not appropriate, as the project manager should first determine if the change is justified and aligned with the project scope statement, and then explore alternative ways to accommodate the change within the existing budget or negotiate a trade-off with the sponsor. References: 123

Explanation:

Effective management of change requests involves evaluating the effects they have on the project scope, timeline, and finances. By recording these changes in the risk register, the project manager can make informed decisions and ensure the project's overall success. This approach allows for a structured process to assess the impact of each change and to determine the appropriate response, whether it be acceptance, modification, or rejection of the request.
References: = The PMBOK Guide highlights the importance of integrating risk management processes with change management activities. It recommends using tools like the risk register to document and monitor changes, ensuring they are aligned with the project objectives and managed effectively12. Additionally, the guide from Project Management Academy outlines the steps for managing change requests, which include recording them in the risk register34.