A zone won't boot. Identify the five causes.

A zone boot process can fail for several reasons related to resource allocation, the zone's current state, or the integrity of its configuration and file system. The boot will fail if dedicated CPU resources are unavailable in the system pool. It will also fail if an exclusive-IP network interface is already configured and active in the global zone, preventing the zone from acquiring it. Similarly, if a configured file system resource cannot be mounted due to conflicts, such as it already being mounted elsewhere, the boot will not succeed. A boot attempt will also be rejected if the zone is already in a running or shutting-down state. Finally, if the zone has been uninstalled, its root file system is destroyed, making a boot impossible.

F. The SYSTIME privilege allows a process to manipulate the system clock. Booting a zone requires the solaris.zone.boot authorization, not privileges related to time management.

1. For A (CPU Resources): Oracle® Solaris 11.4 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management, Chapter 10, "dedicated-cpu Resource". The documentation states that if the system does not have the number of available CPUs specified by the ncpus property, the zone will fail to transition to the ready state, which is a prerequisite for booting.

2. For B (Network Resources): Oracle® Solaris 11.4 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management, Chapter 13, "Administering Network Configuration in Oracle Solaris Zones". This chapter explains that for an exclusive-IP zone, the network data-link is assigned to the non-global zone. If the data-link is already in use (e.g., plumbed with an IP address in the global zone), the zone boot will fail.

3. For C (Filesystem Resources): Oracle Solaris 11.4 man pages section 8: System Administration Commands, zoneadm(8). The man page notes that during a boot, all specified file systems are mounted. If a mount fails for any reason (e.g., the source is unavailable or already mounted incompatibly), the boot process is halted.

4. For D (Zone State): Oracle Solaris 11.4 man pages section 8: System Administration Commands, zoneadm(8). Under the boot subcommand description, it states: "This action is only available for zones in the installed state." Attempting to boot a zone in the running or shutting-down state will result in an error.

5. For E (Uninstalled Zone): Oracle Solaris 11.4 man pages section 8: System Administration Commands, zoneadm(8). The uninstall subcommand description clarifies that it "uninstalls all of the files under the zone's root file system." A subsequent boot attempt will fail because the necessary OS files within the zonepath are missing.