According to the PMBOKGuide, specifically within the Control Procurements process of the Project Procurement Management knowledge area, Claims Administration is the formal tool and technique used to handle contested changes and potential constructive changes.
* Definition of Claims: A claim is a request, demand, or assertion of rights by a seller against a buyer, or vice versa, for consideration, compensation, or payment under the terms of a legally binding contract.
* Alternative Dispute Resolution (ADR): When the buyer and seller cannot reach an agreement on a claim (a " disputed change " ), it is handled through the claims administration process. The preferred method of settling all claims is through negotiation. If negotiation fails, the parties may use Alternative Dispute Resolution (ADR), such as mediation or arbitration, as defined in the contract ' s terms and conditions.
* Hierarchy of Resolution: The PMBOKemphasizes a specific order: 1. Negotiation (Preferred), 2.
ADR (Mediation/Arbitration), and 3. Litigation (Legal action in court, the least desirable).
Why the other options are incorrect:
* A. Interactive communication: This is a Communication Method used in Project Communications Management. While it involves multidirectional exchange of information, it is not the formal legal
/contractual framework used for settling procurement disputes.
* C. Conflict management: This is a Tool and Technique used in Manage Team and Manage Stakeholder Engagement. While ADR is a form of resolving conflict, " Conflict Management " in PMI terms refers to the general interpersonal skills (e.g., Withdraw/Avoid, Smooth/Accommodate, Collaborate/Problem Solve) used with team members and stakeholders, not the specific contractual administration of claims.
* D. Performance reporting: This is a process (or part of Manage Communications) that involves collecting and distributing performance information. It provides the data that might lead to a claim, but it is not the technique used to resolve the dispute.

According to the PMBOKGuide, specifically within the Plan Risk Responses process, there are distinct strategies for dealing with negative risks (threats) versus positive risks (opportunities).
* Negative Risk Strategies (Threats):
* Avoid: Changing the project management plan to eliminate the threat entirely (e.g., extending the schedule, changing the strategy, or reducing scope).
* Mitigate: Taking action to reduce the probability of occurrence or the impact of a risk (e.g., using less complex processes, performing more tests, or choosing a more stable supplier).
* Transfer: Shifting the impact of a threat to a third party, together with ownership of the response (e.g., insurance, performance bonds, or warranties). This usually involves paying a risk premium.
* Accept: Acknowledging the risk but not taking any proactive action. Passive acceptance requires no action except documenting the strategy, while active acceptance usually involves establishing a contingency reserve.
Analysis of Other Options:
* A. Share, Accept, Transfer, or Mitigate: " Share " is a strategy for positive risks (opportunities), not threats.
* B. Exploit, Enhance, Share, or Accept: Exploit, Enhance, and Share are all strategies specifically for positive risks.
* C. Mitigate, Share, Avoid, or Accept: Again, " Share " is an opportunity strategy, making this combination incorrect for a list of purely negative risk responses.

According to the PMBOKGuide, specifically the Develop Project Charter process, the project charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
* Content of the Project Charter: The charter contains high-level information because it is created during the Initiating phase when detailed data is not yet available. Key components include:
* Project purpose or justification.
* Measurable project objectives and related success criteria.
* High-level requirements.
* High-level risks.
* Summary milestone schedule and summary budget.
* Purpose of High-Level Risks: Identifying risks at this stage helps the sponsor and the project manager understand the major threats or opportunities that could affect the project ' s feasibility before a significant investment is made. These are later refined into detailed risks during the Identify Risks process in the Planning phase.
Comparison with other options:
* A. Business case: While it provides the economic justification and may mention very high-level constraints, the formal project document that lists " high-level risks " as a required element is the project charter.
* B. Risk breakdown structure (RBS): This is a tool/representation used to categorize risks by their sources (e.g., Technical, External, Organizational). it is a framework for identification, not a document that lists the risks themselves.
* D. Risk register: This document is the primary output of the Identify Risks process. It contains detailed individual project risks, their root causes, and potential responses. It is much more granular than the high-level risks found in the charter.

According to the PMBOKGuide, specifically within the Project Resource Management knowledge area (formerly focused specifically on Human Resources), the Human Resource Management Plan (or Resource Management Plan in the 6th and 7th editions) is the primary document that provides guidance on how project resources should be categorized, allocated, managed, and released.
* Roles and Responsibilities: This section of the plan identifies the functions assumed by or assigned to persons on the project, including their authority, responsibility, and competency levels.
* Project Organization Charts: This is a graphic display of project team members and their reporting relationships.
* Staffing Management Plan: A component of the resource management plan that describes when and how team members will be acquired and how long they will be needed (staffing management).
Analysis of Distractors:
* B. Activity resource requirements: This is an output of the Estimate Activity Resources process. It identifies the types and quantities of resources required for each activity in a work package, but it does not define reporting structures or management strategies.
* C. Personnel assessment tools: These are tools (such as attitude surveys or focus groups) used to give the project management team insight into the strengths and weaknesses of the team. They are a tool
/technique, not a descriptive plan.
* D. Multi-criteria decision analysis: This is a technique used during the Acquire Resources process to rate or score potential team members based on criteria like availability, cost, or experience. It is not a document that describes the project structure.

According to the PMBOKGuide, the Ishikawa diagram is a fundamental tool used in the Plan Quality Management and Control Quality processes. It is most commonly referred to by two other names:
* Cause and Effect Diagram: Because it maps out various factors (causes) that contribute to a specific problem or quality defect (the effect).
* Fishbone Diagram: Because the completed diagram resembles the skeleton of a fish, with the " head " representing the problem statement and the " bones " representing the categories of potential causes.

Analysis of Other Options:
* B. Control chart: A graphic display of process data over time and against established control limits, used to determine if a process is stable.
* C. Flowchart: A graphical representation of a process showing the relationship between steps. It is used to identify where quality problems might occur.
* D. Histogram: A vertical bar chart showing the frequency of occurrence of data points, used to illustrate the central tendency and dispersion of a data set.