According to the PMBOK Guide, 7th edition, one of the principles of project management is to collaborate with stakeholders. This means that the project manager should identify, analyze, and engage the project stakeholders throughout the project life cycle, using various communication methods and tools. The level and frequency of stakeholder engagement may vary depending on the stakeholder's interest, influence, expectations, and needs. A member of the board of directors who is the sponsor of a project that is important to the organization but has many other priorities and is not currently engaged in the project activities should be kept informed and consulted with based on their needs. This will help to ensure that the sponsor is aware of the project status, issues, risks, and changes, and can provide support and guidance when needed. The project manager should also consult with the sponsor to understand their expectations, preferences, and feedback, and to involve them in governance and decision making as appropriate. Keeping the stakeholder informed and consulted with based on their needs will help to maintain a positive and trusting relationship with the sponsor and increase the likelihood of project success. References: PMBOK Guide, 7th edition, page 9, Principle 2:
Collaborate with Stakeholders; page 31, Section 2.3.1, Project Stakeholders; page 41, Section 2.5.1.1, Stakeholder Analysis; page 42, Section 2.5.2.2, Stakeholder Engagement Plan.

According to the PMBOK Guide, 7th edition, one of the principles of project management is to support team performance. This means that the project manager should foster a collaborative project team environment, build team competencies, and address and remove impediments, obstacles, and blockers for the team. In this scenario, the project manager should provide appropriate training to the team members who lack the necessary skills or knowledge to perform their tasks, rather than emphasizing deadlines, updating the schedule, or accepting the risk. Providing training will help the team improve their performance, deliver value, and meet the expectations of the steering committee and other stakeholders. References: PMBOK Guide, 7th edition, page 9, Principle 8: Support team performance.

When a project requires a significant resource, such as the installation of a call center, it's important for the project manager to conduct an alternative analysis. This analysis will help determine the most effective and efficient approach, whether that's hiring people directly or contracting with a company. The decision should be based on various factors such as cost, time, quality, and the specific needs of the project. References:
Project Management Professional (PMP) Reference Materials, Professional in Business Analysis Reference Materials study guide. Please note that the exact documents and page numbers are not provided as the information is based on general project management principles. For more detailed information, please refer to the specific guides and documents mentioned.

According to the PMI, a hybrid approach is a combination of two or more project methodologies, such as waterfall and agile, to suit the needs of the project. A hybrid approach can offer flexibility, adaptability, and customer focus, while also maintaining some level of predictability, structure, and control. However, a hybrid approach can also pose some challenges, such as stakeholder resistance, misalignment, or confusion.
Therefore, the project manager needs to address and remove any obstacles and blockers that may prevent the team from achieving their goals. Obstacles and blockers are issues or impediments that hinder or stop the team's progress, such as lack of resources, unclear requirements, technical debt, conflicts, communication gaps, etc. The project manager should follow these steps to address and remove obstacles and blockers for the team:
Identify the obstacles and blockers by using various techniques, such as daily stand-up meetings, retrospectives, feedback sessions, surveys, etc.
Analyze the impact, root cause, and priority of the obstacles and blockers by using tools, such as issue logs, risk registers, impact analysis, root cause analysis, prioritization matrix, etc.
Develop and implement solutions to remove the obstacles and blockers by using methods, such as problem- solving, negotiation, escalation, delegation, collaboration, etc.
Monitor and evaluate the effectiveness of the solutions by using measures, such as team velocity, customer satisfaction, quality metrics, etc.
Communicate and report the status and results of the solutions to the relevant stakeholders, such as the team, the sponsor, the customer, etc.
By addressing and removing obstacles and blockers for the team, the project manager can improve the project performance, as well as the team's productivity, quality, morale, and collaboration.
The other options are not the best choices, because:
Asking stakeholders to communicate with the project manager and not directly with the team would create a communication bottleneck, reduce transparency, and increase the risk of misunderstanding or miscommunication.
Empowering the team members to remove obstacles and blockers would be a good practice, but it would not be sufficient without the project manager's support, guidance, and intervention, especially if the obstacles and blockers are beyond the team's authority or capability.
Adding blockers to the issue log and risk management plan would be a necessary step, but it would not be enough without taking action to resolve them. Simply documenting the blockers would not help the team to overcome them or improve their performance. References:
Hybrid Project Management: What is it, Methodology & Software - Teamhood Agile, Traditional, and Hybrid Approaches to Project Success Impediments, Obstacles, and Blockers: How to Address and Remove Them
1.7. Address and remove impediments, obstacles, and blockers for the team - KnowledgeMap
1.7 Address and Remove Impediments, Obstacles, and Blockers ... - BrainBOK

This question belongs to the Process domain because it focuses on assessing and managing risks, which is explicitly listed in the PMP Examination Content Outline. PMI states that project leaders should determine risk management options and iteratively assess and prioritize risks. In this case, the audit reveals a capability gap: the team is struggling with qualitative and quantitative risk assessment itself, not simply lacking one isolated data point or one additional opinion. That means the most effective corrective action is to strengthen the team's competence through risk management training.
Option B may help temporarily, but relying on one SME does not build the team's long-term ability to identify, qualify, and quantify risks. Option A can improve participation, and Option C may increase sponsorship support, but neither directly fixes the root problem. PMI risk references consistently describe project risk management as a disciplined process that includes qualitative and quantitative analysis, so the project manager should ensure the team is properly equipped to perform that work. Training addresses the underlying skill deficiency and improves future risk assessment quality across the project.