File write permissions are permissions that control who can modify or delete files in a directory or system. Restricting the file write permissions to the development group only can help minimize the risk of having systems administrators in an IaaS compute instance perform application code changes, as it can prevent anyone other than the development group from altering or removing any files in the directory where the application code is stored. Restricting the file write permissions can also help maintain consistency and integrity, as it can ensure that only authorized and qualified users can make changes to the application code. Reference: CompTIA Cloud+ Certification Exam Objectives, page 14, section 2.7

Explanation
An active-active site is a type of disaster recovery (DR) site that runs simultaneously with the primary site and handles part of the normal workload or traffic. An active-active site can help maintain maximum availability for a SaaS service, as it can provide load balancing, redundancy, and failover capabilities for the SaaS service in case of an outage or disruption at the primary site. An active-active site can also improve performance and scalability, as it can distribute the workload or traffic across multiple sites and handle increased demand or peak periods. References: CompTIA Cloud+ Certification Exam Objectives, page 10, section 1.5

Explanation
The wrong gateway is the most likely cause of the connectivity issue for the new VM that cannot access the Internet or the VMs on any other subnet. A gateway is a device or software that connects two or more networks and routes traffic between them. A gateway is usually configured as the default route for a network device, which means that any traffic that is not destined for the local network will be sent to the gateway. If the gateway is configured incorrectly, the network device will not be able to communicate with other networks or the Internet. In this case, the new VM has an IP address of 172.16.31.40/24, which means that its subnet mask is 255.255.255.0 and its network ID is 172.16.31.0. However, its gateway is configured as 172.16.30.1, which belongs to a different network (172.16.30.0/24). This means that the new VM will not be able to reach its gateway or any other network through it. The administrator should change the gateway to an IP address that belongs to the same network as the new VM, such as 172.16.31.1 or 172.16.31.254.