Explanation
The project manager should use a change control log to document the effects of the hurricane delay on the project. A change control log is a tool that records and tracks any changes that occur during the project lifecycle. It usually includes information such as change ID, description, impact, status, approval, and resolution. A change control log can help to monitor and manage the changes that affect the project scope, schedule, cost, quality, or resources and ensure that they are aligned with the project objectives and stakeholder expectations.

Explanation
The project manager should communicate the change deployment next after updating the project plan with the newest project end date as a result of an approved change. Communicating the change deployment involves informing all relevant parties about when and how the change will be implemented and what are the expected outcomes and benefits.Communicating the change deployment can help to ensure alignment, readiness, and support for the change and avoid any confusion or resistance.

Explanation
The project manager should distribute an agenda before a call to ensure all meeting items are addressed and the correct participants attend. An agenda is a document that outlines the purpose, topics, and objectives of a meeting. It also includes information such as date, time, duration, location, attendees, and roles. Distributing an agenda can help to prepare the participants for the meeting, set clear expectations, and facilitate a productive and focused discussion12

Explanation
Customer notification should be added to the issue log after receiving an escalation from an executive about the extension of the downtime after the scheduled window. Customer notification is a communication activity that informs the customers about any issues or changes that may affect their satisfaction or expectations.
Customer notification can help to maintain trust, transparency, and goodwill with the customers and prevent any negative impacts on their business operations or experience.

Explanation
The dependency between software installation and desktop installation is a mandatory dependency. A mandatory dependency is a type of dependency that is inherent in the nature or logic of the work and cannot be avoided or changed. It is also known as a hard dependency or a hard logic dependency. A mandatory dependency means that one task must be completed before another task can start or finish. For example, software installation can only start after desktop installation is finished5 The dependency between desktop installation and software installation represents a mandatory dependency. A mandatory dependency is a type of task dependency that is inherent in the nature of the work being performed.
In this case, software installation cannot begin until desktops are installed and powered on, and therefore, the dependency is mandatory. References: CompTIA Project+ Study Guide, Chapter 3: Project Integration Management, Objective 3.1: Identify the project management processes and the interactions between them.