Pass the Oracle Oracle Solaris 1z0-580 Questions and answers with CertsForce

Note:

* second line in exhibit (minor typo):

boot-device = disk net

*The line starting with net is:

/pci@780/pci@0/pci@1/network@0

Note:

*In many cases, one software package depends on another package. For example, one package might require functionality that is in a second package in order to function or install correctly. These relationships, or dependencies, between packages are important for automating package installation operations and for upgrading system software to known and well-tested states. IPS supports a number of different relationships between packages.

Incorrect:

Not B:IPS relies on network-accessible or locally available software repositories as a delivery mechanism.

Not D:

Table,SVR4 and IPS Package Command Equivalents

SVR4 Package Command

IPS Package Command Equivalent

pkgadd

pkg install

patchadd

pkg update

pkgrm

pkg uninstall

pkgadm addcert, pkgadm removecert

pkg set-publisher -k, -c, --approve-ca-cert, --revoke-ca-cert, unset-ca-cert

pkginfo, pkgchk -l

pkg info, pkg list, pkg contents, pkg search

pkgchk

pkg verify, pkg fix, pkg revert

A: project.cpu-shares

Number of CPU shares granted to this project for use with the fair share scheduler

B:project.cpu-cap

Absolute limit on the amount of CPU resources that can be consumed by a project. A value of 100 means 100% of one CPU as the project.cpu-cap setting. A value of 125 is 125%, because 100% corresponds to one full CPU on the system when using CPU caps.

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.

To ensure the system boots without starting the installation, make sure the entry you choose to boot does not have the install=true boot property specified in its kernel line.

Running a Custom Script During First Boot

To perform any additional installation or configuration that cannot be done in the AI manifest or in a system configuration profile, you can create a script that is executed at first boot by a run-once SMF service.

Create the first-boot script.

Create the manifest for an SMF service that runs once at first boot and executes the script.

Create an IPS package that contains the service manifest and the script.

Add the package to an IPS package repository.

Install that package during the AI installation by specifying that package in the AI manifest.

The service runs and executes the script at first reboot after the AI installation.

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.

Note:

*The services started by svc.startd are referred to as milestones. The milestone concept replaces the traditional run levels that were used in previous versions of Solaris. A milestone is a special type of service that represents a group of services. A milestone is made up of several SMF services. For example, the services that instituted run levels S, 2, and 3 in previous version of Solaris are now represented by milestone services named:

milestone/single-user (equivalent to run level S)

milestone/multi-user (equivalent to run level 2)

milestone/multi-user-server (equivalent to run level 3)

*Shut down the system.

# shutdown -iinit-state -ggrace-period -y

-iinit-state

Brings the system to an init state that is different from the default of S. The choices are 0, 1, 2, 5, and 6.

Run levels 0 and 5 are states reserved for shutting the system down. Run level 6 reboots the system. Run level 2 is available as a multiuser operating state.

Through the zonecfg utility, the file-mac-profile can be set to one of the following values (see note below). All of the profiles except none will cause the /var/pkg directory and its contents to be read-only from inside the zone.

*none

Standard, read-write, non-global zone, with no additional protection beyond the existing zones boundaries. Setting the value to none is equivalent to not setting file-mac-profile property.

* strict

*fixed-configuration

Permits updates to /var/* directories, with the exception of directories that contain system configuration components.

IPS packages, including new packages, cannot be installed.

Persistently enabled SMF services are fixed.

SMF manifests cannot be added from the default locations.

Logging and auditing configuration files can be local. syslog and audit configuration are fixed.

* flexible-configuration

Note:

zonecfg file-mac-profile Property

By default, the zonecfg file-mac-profile property is not set in a non-global zone. A zone is configured to have a writable root dataset.

In a solaris read-only zone, the file-mac-profile property is used to configure a read-only zone root. A read—only root restricts access to the runtime environment from inside the zone.

If an error occurs when booting the new BE, activate and boot to the previous BE.

Example:

# beadm activate solaris

# init 6