According to the PMBOKGuide, the Plan Risk Management process is the process of defining how to conduct risk management activities for a project. Because risk management requires resources and impacts the project ' s finances, it must be integrated with other management plans.
* Cost Management Plan: This is a key input to Plan Risk Management. It provides processes and controls that can be used to help define how the risk budget will be allocated, how contingency reserves will be established, and how financial risks will be reported.
* Other Key Inputs to Plan Risk Management:
* Project Charter: Provides high-level boundaries and risks.
* Project Management Plan: Includes other subsidiary plans like the Schedule Management Plan and Communications Management Plan.
* Stakeholder Register: Identifies who the stakeholders are, which helps in determining their risk appetite and thresholds.
* Enterprise Environmental Factors (EEFs): Such as the organization ' s risk attitudes and thresholds.
* Organizational Process Assets (OPAs): Risk categories, templates, and lessons learned from past projects.
Analysis of Other Options:
* B. risk management plan: This is the output of the Plan Risk Management process, not an input. It is the document that describes how risk management will be structured and performed.
* C. activity list: This is an input to processes like Identify Risks, but it is too granular for the high-level Plan Risk Management process, which focuses on the methodology rather than individual tasks.
* D. risk register: This is an output of the Identify Risks process. Since Plan Risk Management happens before you start identifying specific risks, the register does not yet exist.

According to the PMBOKGuide, the Close Procurements process (often integrated into Control Procurements in the most recent editions) is the process of finishing each project procurement. A critical component of closing out any contract is the capture of knowledge for future use.
* Organizational Process Assets (OPA) Updates: During the formal closure of a contract, the project manager and the procurement team update the organization ' s knowledge base. Lessons learned documentation is a primary OPA update. This includes documenting what went well during the procurement, what challenges were faced, and how the seller performed.
* Purpose of Lessons Learned: Capturing this information helps the organization improve its future procurement processes, refine its " Preferred Seller " lists, and avoid repeating the same mistakes in subsequent projects.
* Other OPA Updates: These may include the Procurement File, which is a complete set of indexed contract documentation (including the closed contract), and Final Acceptance notices.
Comparison with other options:
* A. Procurement audit: This is a Tool and Technique used to identify successes and failures that warrant recognition in the preparation or administration of other procurement contracts. It is the action taken to generate the lessons learned, not the update itself.
* C. Performance reporting: This is a tool and technique (or part of the Monitor and Control Project Work process) used during the execution and monitoring phases of the project to communicate progress, not a final OPA update during procurement closure.
* D. Payment requests: These are typical activities or Inputs within the Control Procurements process throughout the project life cycle as work is completed. By the time you reach " Close Procurements, " final payments are typically being processed or confirmed rather than " requested. "

According to the PMBOKGuide, specifically within the Plan Risk Responses process, risk response strategies are divided into two categories: those for threats (negative risks) and those for opportunities (positive risks).
Exploit: This strategy is used for high-priority opportunities where the organization wants to ensure that the opportunity is realized. By " exploiting " the risk, the project manager seeks to eliminate the uncertainty associated with a particular positive risk by ensuring the opportunity definitely happens (e.g., assigning the organization ' s most talented resources to a project to shorten the time to completion).
* Other Opportunity Strategies:
* Share: Allocating some or all of the ownership of the opportunity to a third party who is best able to capture the benefit for the project (e.g., a joint venture).
* Enhance: Increasing the probability and/or the positive impacts of an opportunity.
* Accept: Being willing to take advantage of the opportunity if it arises, but not actively pursuing it.
Analysis of Other Options:
A). Mitigate: This is a strategy for threats. It involves seeking to reduce the probability of occurrence or impact of a negative risk.
* B. Transfer: This is a strategy for threats. It involves shifting the impact of a threat to a third party, together with ownership of the response (e.g., insurance or warranties).
* D. Avoid: This is a strategy for threats. It involves changing the project management plan to eliminate the threat entirely, isolating project objectives from the risk ' s impact, or relaxing the objective that is in jeopardy.

According to the PMBOKGuide, there is a distinct and critical difference between Management and Leadership, though a successful project manager must balance both. The description in the question highlights the dual nature of these two roles:
Management: This relates to directing another person to get from one point to another using a known set of expected behaviors. It focuses on systems, structures, administration, and results. Management is about doing things right, maintaining the status quo, and following the established plan (the " how " and " when " ).
* Leadership: This relates to the ability to lead a team and inspire them to do their jobs well. It involves working with others through discussion or debate to guide them from one point to another. Leadership is about doing the right things, innovating, focusing on relationships, and inspiring trust (the " what " and " why " ).
Key Differences according to PMI:

Analysis of other options:
A). Influence and challenge: These are components or skills of leadership, but they do not capture the administrative " known set of expected behaviors " described in the first half of the question.
* B. Innovation and administration: While " Innovation " is often a trait of leadership and " Administration " a trait of management, these are individual qualities rather than the core disciplines themselves.
* D. Engagement and guidance: These are general terms used in stakeholder management and coaching, but they do not represent the formal PMI distinction between the two primary roles of a project manager.
Per PMI standards, the PMI Talent Triangle emphasizes that a project manager must be competent in technical project management (Management) while also possessing the soft skills required to guide and motivate a team (Leadership).

According to the PMBOKGuide, specifically within the Plan Procurement Management process, Source Selection Criteria are developed and used to rate or score seller proposals. When an organization evaluates a vendor, they use specific criteria to ensure the selected seller can fulfill the requirements.
* Technical Approach: This specific criterion focuses on the " how. " It analyzes whether the seller's proposed methodologies, techniques, solutions, and services align with the requirements defined in the procurement documents (such as the Statement of Work). It evaluates the feasibility and effectiveness of the vendor ' s planned delivery process.
* Source Selection Criteria (General): These are often included as part of the procurement documents to give sellers an understanding of how they will be evaluated. They can be objective (e.g., " The seller must have 10 years of experience " ) or subjective (e.g., " The proposed technical approach must be innovative " ).
Comparison with other options:
* B. Technical capability: This refers to the seller ' s ability or expertise (e.g., does the staff have the required skills or certifications?) rather than the specific methodology proposed for the current project.
* C. Business size and type: This is a non-technical criterion used to see if the seller meets specific categories, such as being a small business or a disadvantaged enterprise, as required by some government or corporate policies.
* D. Production capacity and interest: This evaluates whether the seller has the available resources (manpower, equipment, or facility space) to take on the work and whether they have expressed a genuine interest in the contract.