Oracle 1z0-580 Oracle Solaris 11 Installation and Configuration Essentials Exam Practice Test

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.

• Halt the zone whose configuration you want to change.

# zoneadm -z zone-name halt

• 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.

• 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:

NotE:

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

A:ZFS is the default root file system.

UFS is a supported legacy file system, but it is not supported as a bootable root file system.

E:

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:

*Starting with the Solaris 10 10/08 release for a SPARC based system, you can boot a ZFS root file system in a ZFS pool. For ZFS root pools, you can list the available boot environments withthe boot command with the -L option. You can then choose a boot environment and use the OBP boot command with the -Z option to boot that boot environment.

*Starting with the Solaris 10 1/06 release for x86 based systems, a GRUB boot menu provides the interface for booting between different boot environments.

Note:

*The name originally stood for "Zettabyte File System"but today does not stand for anything.

Incorrect:

Not C: Mirroring is not enabled by default.

Not D:Alternate bootenvironments

If you want to create a backup of an existing boot environment, for example, prior to modifying the original boot environment, you can use the beadm command to create and mount a new boot environment that is a clone of your active boot environment. This clone is listed as an alternate boot environment in the GRUB menu for x86 systems or in the boot menu for SPARC systems.

Incorrect:

not A:IPS relies on network-accessible or locally available software repositories as a delivery

mechanism, which is similar to how other operating systems (notably Oracle Linux) supply

software updates.

not D: can be done with the pkg command.

Note:

*Image Packaging System (IPS) is a new network based package management system included in Oracle Solaris 11. It provides a framework for complete software lifecycle management such as installation, upgrade and removal of software packages.

Safe system upgrades with ZFS boot environments

Network package repositories of software

Efficient downloads and automatic dependency checking

Support for disconnected data center environments

Extensive package publishing tools

The Live Media provides administrators with an opportunity to explore the Oracle Solaris 11.1 environment without installing it on a system. The system boots off the media directly allowing administrators to start the installer should they choose to install it to a system.

Note:

*You have several alternatives for where to install Oracle Solaris 11:

Inside a virtual machine on top of your existing operating system

On the bare metal as a standalone operating system

On the bare metal alongside your existing operating system(s) (multiboot scenario)

To patch a Solaris system or install a command you use pkg command.

auto_reboot – Optional. Omitting the auto_reboot attribute is equivalent to setting the value of the attribute to false. By default, AI does not automatically reboot the client after installation. To request automatic reboot of the client after successful installation, specify auto_reboot="true".

Note:

*Example 1 Set the auto_reboot Attribute

$ aimanifest set /auto_install/ai_instance@auto_reboot false

Interfaces that are on the IP layer (Layer 3) are configured by using the ipadm command.

B(not C):A zone is a virtualized operating system environment that is created within a single instance of the Oracle Solaris operating system. Oracle Solaris Zones are a partitioning technology that provides an isolated, secure environment for applications.

Note:

*When you create a zone, you produce an application execution environment in which processes are isolated from the rest of the system. This isolation prevents a process that is running in one zone from monitoring or affecting processes that are running in other zones. Even a process running with root credentials cannot view or affect activity in other zones. A zone also provides an abstract layer that separates applications from the physical attributes of the machine on which the zone is deployed. Examples of these attributes include physical device paths and network interface names. The default non-global zone brand in the Oracle Solaris 11.1 release is the solariszone.

By default, all systems have a global zone. The global zone has a global view of the Oracle Solaris environment that is similar to the superuser (root) model. All other zones are referred to as non-global zones. A non-global zone is analogous to an unprivileged user in the superuser model. Processes in non-global zones can control only the processes and files within that zone. Typically, system administration work is mainly performed in the global zone. In rare cases where a system administrator needs to be isolated, privileged applications can be used in a non-global zone. In general, though, resource management activities take place in the global zone.

To display information about software packages, refer to the following examples. No special privileges are required to display information about packages.

List the packages that are currently installed on your system:

$ pkg list -H entire

Determine whether a specific package is installed in the current image and whether an update is available.

$ pkg list amp

pkg list: no packages matching 'amp' installed