Explanation
The project's contingency allowance is a provision in the project budget that is intended to cover known risks that may affect the project costs. The risk of increased fuel costs was identified and included in the contingency allowance, so the project manager should use it to process the freight invoices at the actual shipping costs. This is the best way to handle the risk without affecting the project scope, schedule, or quality.
Requesting a formal change order from the customer (option B) is not necessary, as the project budget already has a provision for this risk. Processing the freight invoices for the budgeted amount and hoping the shipping company will forgive the difference (option C) is unethical and unprofessional, as it violates the terms of the contract and the PMI Code of Ethics and Professional Conduct. Asking the project sponsor to cover the additional shipping costs on the company's reserves account (option D) is also not appropriate, as the company's reserves are meant for unknown risks that are beyond the project's control, not for known risks that are already accounted for in the project budget. References: PMI, The Standard for Risk Management in Portfolios, Programs, and Projects, 2019, p. 72; PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 6th ed., 2017, p. 252.
The project manager should use the contingency allowance to cover the additional shipping costs, as it was specifically included in the project budget for such risks. This approach avoids requesting unnecessary changes or relying on external sources to cover the cost overrun.

Explanation
The team is documenting all the checkpoints along the way that might indicate delays on critical deliverables, which is an example of risk triggers. Risk triggers are events or conditions that indicate a risk may be about to occur or has already occurred, helping the project team to monitor and respond to risks effectively.
Risk triggers are indicators or warning signs that a risk event is about to occur or has occurred. They help to monitor the status of risks and initiate risk responses when needed. Documenting risk triggers is part of the Plan Risk Responses process, which aims to develop options and actions to enhance opportunities and reduce threats to project objectives. References: The Standard for Risk Management in Portfolios, Programs, and Projects, page 78; PMBOK Guide, 6th edition, page 402.

Explanation
Legal and regulatory requirements and constraints when assessing a project environment for threats and opportunities may include ensuring the confidentiality of project information, as this is often governed by laws and regulations.
Legal and regulatory requirements and/or constraints are external factors that can affect the project environment and influence the risk management process. They may include laws, regulations, standards, codes, permits, licenses, contracts, or agreements that the project must comply with or adhere to.
Confidentiality of project information is an example of such a requirement or constraint, as it may limit the disclosure, sharing, or access of project data, documents, or reports to authorized parties only. Violating confidentiality may result in legal actions, penalties, or reputational damage for the project and the organization. Therefore, the project manager and the risk management team must identify and comply with the confidentiality requirements and/or constraints when assessing the project environment for threats and opportunities. References: PMI, 2019. Practice Standard for Project Risk Management. Newtown Square, PA:
Project Management Institute, Inc., p. 181

Explanation
The total contingency budget is the sum of the expected values of each risk. The expected value of a risk is the product of its probability and impact. Therefore, the expected value of risk A is 0.4 * 100,000 = US$40,000 and the expected value of risk B is 0.6 * 20,000 = US$12,000. The total contingency budget is 40,000 +
12,000 = US$52,000. However, this answer is not among the options given. The closest option is A.
US$68,000, which might be the result of rounding up the expected values of each risk to the nearest thousand.
This is a common practice in some projects to avoid dealing with small amounts of money. References: PMI.
(2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition. Chapter
11: Project Risk Management, p. 406. 5

Explanation
A SWOT analysis is a risk identification technique that helps to identify high-level and strategic project risks by examining the internal and external factors that may affect the project objectives. A SWOT analysis involves listing the strengths, weaknesses, opportunities, and threats of the project, and then analyzing how they may impact the project positively or negatively. A SWOT analysis can help to uncover potential risks that may not be obvious from other techniques, such as prompt lists, interviews, or brainstorming12 References: 1: PMI Risk Management Professional (PMI-RMP) Handbook, page 10 2: A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, page 11.2.2.1