Oracle 1Z0-580 Dumps - Pass Solaris 11 Installation and Configuration Essentials Exam in 2026

There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

Oracle Solaris 11 Transition Tools and Features

Note:

* There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

/ JumpStart Migration Utility (js2ai)

Used to convert Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries.

/ ZFS shadow migration feature

Used to migrate data from an existing file system to a new file system.

/ Oracle Solaris 11 support for Oracle Solaris 10 zones

Used to migrate your Oracle Solaris 10 application environments to an Oracle Solaris 11 system.

/ NFS file sharing and pool migration

Used to access shared files from an Oracle Solaris 10 system on an Oracle Solaris 11 system.

Used to import a ZFS storage pool from an Oracle Solaris 10 system into an Oracle Solaris 11 system.

How to Loopback Mount a File That Is Usually Not Visible in a Labeled Zone

This procedure enables a user in a specified labeled zone to view files that are not exported from the global zone by default.

1. Halt the zone whose configuration you want to change.

# zoneadm -z zone-name halt

2. Loopback mount a file or directory.

For example, enable ordinary users to view a file in the /etc directory.

# zonecfg -z zone-name

add filesystem

set special=/etc/filename

set directory=/etc/filename

set type=lofs

add options [ro,nodevices,nosetuid]

end

exit

Note - Certain files are not used by the system, so that loopback mounting them has no effect. For example, the /etc/dfs/dfstab file in a labeled zone is not checked by Trusted Extensions software. For more information, see Sharing Files From a Labeled Zone.

3. Start the zone.

# zoneadm -z zone-name boot

Note:

* In this Solaris release, you create a ZFS file system share and publish the share as follows:

Create the file system share and define the NFS or SMB share properties by using the zfs share command.

* ZFS File Sharing Within a Non-Global Zone

In previous Solaris releases, you could not create and publish NFS or SMB shares in a Oracle Solaris non-global zone. In this Solaris release, you can create and publish NFS shares by using the zfs set share command and the legacy share command with a non-global zone.

* If a ZFS file system is mounted and available in a non-global zone, it can be shared in that zone.

* A file system can be shared in the global zone if it is not mounted in a non-global zone or is not shared to a non-global zone.

* If a ZFS file system's mountpoint property set to legacy, the file system can be shared by using the legacy share command.

A:

* If your system has more than one OS installed on the system or more than one root boot environment in a ZFS root pool, you can boot from these boot environments for both SPARC and x86 platforms.

* GRUB, the open source boot loader, is the default boot loader in the Solaris OS.

C: With GRUB based booting, the kernel is loaded by specifying its file name, and the drive, and the partition where the kernel resides. GRUB based booting replaces the Solaris Device Configuration Assistant and simplifies the booting process with a GRUB menu.

Incorrect:

Not E:

* In this implementation of GRUB, the multiboot module is no longer used.

B:

* With Oracle Solaris 11, the configuration of the system is specified as a set of configuration parameters provided in a file called the System Configuration Profile, which is in the form of an SMF profile.

* Oracle Solaris 11 uses SMF for configuration. SMF uses a database to centralize the configuration information, it uses the SMF framework to carry out configuration tasks, and it uses SMF properties as an API. SMF is also well integrated with Oracle Solaris Zones technology.

* Oracle Solaris 11 uses the Service Management Facility (SMF) to centralize configuration information. The new sysconfig command replaces the older sys-unconfig command and provides a method based upon SMF for unconfiguring an Oracle Solaris 11 instance and reconfiguring it.

D: To use AI to install client systems over the network, you must set up DHCP and set up an AI service on an AI server.

An AI service is associated with a SPARC or x86 AI install image and one or more sets of installation instructions.

Note:

Using the Oracle Solaris Automated Installer (AI) you can create and manage services to install the Oracle Solaris 11 operating system over the network in a hands-off manner.

Three significant steps are performed by various services during the installation process:

Assigning a network identity for the system being installed

Contacting the automated installation service to download over the network a small boot image and a description of how to provision a system

Provisioning the system over the network, including software and system configuration

Each of the steps can be performed by various services residing on the same physical or virtual system, or the services can be on separate systems. In this article, the following services reside on the same system:

DHCP service

Automated Installer service

Image Packaging System (IPS) repository service

A: dedicated-cpu Resource

The dedicated-cpu resource specifies that a subset of the system's processors should be dedicated to a non-global zone while it is running. When the zone boots, the system will dynamically create a temporary pool for use while the zone is running.

C: s the global administrator in the global zone, you can import raw and block devices into a non-global zone. After the devices are imported, the zone administrator has access to the disk. The zone administrator can then create a new file system on the disk and perform one of the following actions:

Mount the file system manually

Place the file system in /etc/vfstab so that it will be mounted on zone boot

D, E: Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state.

Incorrect:

Not F: Sys_time not related to booting a zone.