When a quality issue that requires a change to the quality standard is encountered in a project, and there is currently no budget available for the required changes, the project manager should check the change management plan. The change management plan is a part of the project management plan and it documents how changes will be monitored and controlled throughout the lifecycle of the project. It provides a process for managing changes and their impact on the project's objectives. In this case, the change management plan would provide guidance on how to handle a situation where a change to the quality standard is required but there is no budget available for the changes. References: Project Management

According to the PMBOK Guide, 6th edition, page 141, the project manager should engage with stakeholders throughout the project life cycle to ensure that their needs and expectations are met. When there are changes in the stakeholder environment, such as new or replaced stakeholders, the project manager should identify them and assess their impact on the project. The project manager should also review and prioritize the new requirements with the stakeholders and analyze how they affect the project scope, schedule, cost, quality, and risk. The project manager should then follow the change control process to submit, evaluate, approve, and implement the change requests that are needed to accommodate the new requirements. This approach ensures that the project manager maintains effective communication, collaboration, and alignment with the stakeholders, and delivers a product, service, or result that meets their needs and expectations.
The other options are not the best choices because they do not address the new requirements in a proactive and collaborative manner. Option B is not the best choice because it implies that the project manager is trying to avoid the new requirements and resist the change, which could create conflict and dissatisfaction among the stakeholders. Option C is not the best choice because it implies that the project manager is accepting all the new requirements without analyzing their impact and feasibility, which could lead to scope creep, unrealistic expectations, and poor quality. Option D is not the best choice because it implies that the project manager is imposing a rigid and inflexible approach to the project, which could alienate the new stakeholders and jeopardize their support and engagement.
References:
PMBOK Guide, 6th edition, pages 141-142, 161-162, 171-172
PMP Exam Questions - Part 17 (Q 161-170), YouTube video by Certify Me Now
[PMP Exam Prep: 100% Coverage for PMP Exam Success], Udemy course by Joseph Phillips

According to the PMP Exam Content Outline, one of the tasks under the domain of Business Environment is to plan and manage project compliance, which includes confirming project compliance requirements and classifying compliance categories. Compliance requirements are the rules and regulations that the project must follow to meet the standards of quality, safety, security, and legality. Compliance categories are the types of compliance requirements that apply to the project, such as security, health and safety, regulatory, environmental, etc. Compliance requirements and categories may vary depending on the industry, country, and organization of the project. Therefore, the project manager should not assume that there are no compliance requirements for the project based on the sponsor's knowledge, but should seek expert advice from the compliance leader, who is the person responsible for ensuring that the project meets the compliance standards and requirements. The compliance leader can help the project manager confirm if there are any compliance requirements for the project, and if so, what they are and how to comply with them. This will help the project manager avoid the risks and consequences of non-compliance, such as fines, penalties, lawsuits, reputation damage, or project failure. The other options are not correct because they do not involve consulting the compliance leader, who is the best source of information and guidance on compliance matters. Checking with the national compliance agency may not be sufficient, as there may be other compliance requirements at the regional, local, or organizational level. Trusting in the expertise of the sponsor may be risky, as the sponsor may not be aware of all the compliance requirements or changes that may affect the project.
Conducting independent research may be helpful, but it may not be comprehensive, accurate, or up-to-date, and it may not address the specific needs and context of the project. References:
* PMP Exam Content Outline
* How compliance in project management works1
* 3.1 Plan and Manage Project Compliance2

According to the PMBOK Guide, 7th edition, a joint requirements session is a technique used to elicit and prioritize requirements from multiple stakeholders in a collaborative and interactive way. It can also be called a workshop, a focus group, or a brainstorming session. To ensure that the session is effective and efficient, the project manager should organize a formal session led by a skilled facilitator who can guide the discussion, manage conflicts, and ensure participation from all attendees. The facilitator should also establish and communicate the rules for how the participants will interact with one another, such as respecting different opinions, using constructive feedback, and following an agenda. This will help to avoid chaos and confusion, and to achieve the desired outcomes of the session. References:
* PMBOK Guide, 7th edition, page 149, section 5.2.3.1, Joint Requirements Session
* PMBOK Guide, 7th edition, page 150, section 5.2.3.2, Facilitation