Which five steps (dealing with first boot script creation) can be omitted when working with provisioning Oracle Solaris 11 Zones and services with…

The five steps describe the standard and complete procedure for creating and deploying a custom first-boot script in an Oracle Solaris 11 environment. This process is equally applicable to both Global and non-global Zones. A Zone is a virtualized operating system environment with its own file system, SMF repository, and package database. To ensure a script runs on a Zone's first boot, it must be packaged (IPS), delivered via a repository, and installed into the Zone. Omitting any of these fundamental steps would prevent the script from being correctly deployed and executed within the Zone's distinct lifecycle.

A. A script in the Global Zone is not automatically inherited or executed by a non-global Zone during its first boot. The script must be installed into the Zone's own root file system.
B. Oracle Solaris 11 exclusively uses the Image Packaging System (IPS) for software management. While conversion tools exist, SVR4 is a legacy format and not the standard method for deploying software.
D. The Oracle Solaris 11 Automated Installer (AI) fully supports the configuration and installation of non-global Zones via the AI manifest, making this statement factually incorrect.
E. Each Zone has its own SMF instance and a lifecycle distinct from the Global Zone, including its own "first boot" sequence where first-boot services are executed.

1. Oracle Solaris 11.4 Documentation, Customizing an Oracle Solaris 11.4 Installation, Chapter 4, "Running a Custom Script During First Boot." This chapter details the entire five-step process as the standard method. It outlines creating the script, the SMF manifest, the IPS package, publishing it, and installing it via an AI manifest. The process is presented as the canonical way to perform this task, with no exceptions mentioned for Zones.

2. Oracle Solaris 11.4 Documentation, Creating and Administering Oracle Solaris 11.4 Zones, Chapter 2, "Configuring, Installing, and Booting a Zone." This section explains that software is added to a zone by installing packages. The zonecfg command includes subcommands like add-pkg to specify packages to be installed when the zone is installed, confirming that the packaging steps (3, 4, 5) are necessary.

3. Oracle Solaris 11.4 Documentation, Installing Oracle Solaris 11.4 Systems, Chapter 10, "Provisioning the Client System." The section "Adding Zones to an AI Manifest File" explicitly describes the element and its attributes, which are used to define and install a zone during an AI installation. This directly refutes the claim in option D.

4. Oracle Solaris 11.4 Documentation, Developing and Administering Oracle Solaris 11.4 Services, Chapter 1, "Introduction to the Service Management Facility." The section "SMF and Booting" explains that each zone runs its own instance of the svc.startd daemon, which manages the zone's services independently of the global zone. This confirms that a Zone has its own boot process and SMF context, refuting option E.