Limiting access to members of the project team is a way to minimize the risk of compromising the project details if a cloud service is used. This means that only authorized and trusted individuals can access, view, modify, or share the project information stored in the cloud. Limiting access can prevent unauthorized access, data leakage, cyberattacks, or espionage from external parties who might want to steal or sabotage the new technology. Limiting access can also reduce the risk of human error, negligence, or misconduct from internal parties who might accidentally or intentionally expose or misuse the project information123. Reference = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Communications, p. 143; Cloud Security Risks and How to Mitigate Them | Cloud Academy; Cloud Security: How to Secure Your Data in the Cloud | Kaspersky; Cloud Security: Best Practices for Securing Cloud Computing | Cloud Security Alliance

The rules of engagement are the guidelines and expectations that define the relationship between the contractor
and the company. They may include topics such as communication, confidentiality, access, security,
performance, and compliance. The project manager should reinforce the rules of engagement with the
contractor to ensure that they understand and respect the boundaries and protocols of the company. This will
help to avoid any potential conflicts, misunderstandings, or breaches of contract. References = CompTIA
Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Project Stakeholder Management, p. 239;
Contractor Rules of Engagement - Cox Enterprises, p. 1; Legal Considerations for Engaging Contractors |
LegalVision

An Ishikawa diagram is a tool that the project team should use to find the cause of the defects associated with
project deliverables. An Ishikawa diagram, also known as a fishbone diagram or a cause-and-effect diagram, is
a graphical tool that shows the possible causes of a problem or effect using a fishbone-like structure. An
Ishikawa diagram can help to identify and analyze the root causes of defects or issues and find solutions to
prevent or eliminate them.

Informal communication is a type of communication that is casual, spontaneous, and unstructured. It does not follow any predefined rules, protocols, or formats. Examples of informal communication include email, phone calls, conversations in the hallway, and impromptu meetings12. The sponsor is using informal communication to communicate with the team, as these methods are convenient, flexible, and personal. However, informal communication may also have some drawbacks, such as lack of documentation, inconsistency, and potential for misunderstanding3. Therefore, the sponsor should also use formal communication when necessary, such as for official reports, contracts, and presentations4.

The execution phase is when the project manager and the team execute the project plan, deliver the project
outputs, and monitor and control the project performance. This includes tracking and managing the project
budget, scope, schedule, quality, and risks. Making adjustments to the budget based on the actual project
expenditures is part of the monitoring and controlling process in the execution phase. References = CompTIA
Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Executing and Closing Projects, p. 263.