1z0-580 Sample Questions Answers

How to Install Oracle Solaris From the Live Media If Your System Boots in Console Mode

For this procedure, two networked systems are required: the system on which the Live Media was booted (target system) and a remote system from which the installation will be performed. Both systems must have network access. The two systems are not required to be on the same subnet. However, the target system must be reachable from the remote system. Also, the remote system must be running an OS that supports a graphical desktop.

Note:

*If your system's graphics card is not supported by the Live Media or your system does not have a graphics card, the system boots in console mode when you insert the Live Media. In this case, you cannot perform a GUI installation.

Your two alternatives are as follows:

• Use the text installer image instead of the Live Media ISO image.

You can run the text installer on the local console without network access.

• Perform a remote installation

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

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

You can display information about snapshots, boot environments, and datasets that were created by the beadm command by using the beadm list subcommand. The beadm list command output also displays boot environments that are created by the pkg command.

Viewing Boot Environment Specifications

The values for the Active column are as follows:

• R – Active on reboot.
• N – Active now.
• NR – Active now and active on reboot.
• “-” – Inactive.
• “!” – Unbootable boot environments in a non-global zone are represented by an exclamation point.

The following example displays full information for the BE5 boot environment.

Note:

*virtual local area networks (VLANs), link aggregations, and IP tunnels can be assigned administratively-chosen names and then configured by referring to those names.

*VNICs are pseudo interfaces that you create on top of datalinks. A VNIC has an automatically generated MAC address. Depending on the network interface in use, you can explicitly assign to a VNIC a MAC address other than the default address, as described in the dladm(1M) man page. You can create as many VNICs over a datalink as you require.

*Etherstubs are pseudo ethernet NICs which are managed by the system administrator. You can create VNICs over etherstubs instead of over physical links. VNICs over an etherstub becomeindependent of the physical NICs in the system. With etherstubs, you can construct a private virtual network that is isolated both from the other virtual networks in the system and from the external network. For example, you want to create a network environment whose access is limited only to your company developers than to the network at large. Etherstubs can be used to create such an environment.

*The basic link aggregation topology involves a single aggregation that contains a set of physical interfaces. You might use the basic link aggregation in the following situations:

For systems that run an application with distributed heavy traffic, you can dedicate an aggregation to that application's traffic.

For sites with limited IP address space that nevertheless require large amounts of bandwidth, you need only one IP address for a large aggregation of interfaces.

For sites that need to hide the existence of internal interfaces, the IP address of the aggregation hides its interfaces from external applications.

Note:

*Oracle Solaris 11 adds transparent data encryption functionality to ZFS. All data and file system metadata (such as ownership, access control lists, quota information, and so on) are encrypted when stored persistently in the ZFS pool.

*A ZFS pool can support a mix of encrypted and unencrypted ZFS data sets (file systems and ZVOLs). Data encryption is completely transparent to applications and other Oracle Solaris file services, such as NFS or CIFS. Since encryption is a first-class feature of ZFS, we are able to support compression, encryption, and deduplication together. Encryption key management for encrypted data sets can be delegated to users, Oracle Solaris Zones, or both. Oracle Solaris with ZFS encryption provides a very flexible system for securing data at rest, and it doesn't require any application changes or qualification.

ZFS makes it easy to encrypt data and manage data encryption. You can have both encrypted and unencrypted file systems in the same storage pool. You can also use different encryption keys for different systems, and you can manage encryption either locally or remotely.

A:

*Oracle Solaris 11 adds transparent data encryption functionality to ZFS. All data and file system metadata (such as ownership, access control lists, quota information, and so on) are encrypted when stored persistently in the ZFS pool.

*A very simple example of using ZFS encryption is as follows:

#zfs create -o encryption=on rpool/export/project

Enter passphrase for 'rpool/export/project':

Enter again:

#zfs create rpool/export/project/A

#zfs create rpool/export/project/A/design

#zfs create rpool/export/project/B

D:compression=onreduces storate footprint

E:If you want to allow the filesystem to be managed inside the zone, use the zfs zoned=on option when creating or modifying the filesystem.

Note:

*Modern computing environments have to provide a flexible response to the varying workloads that are generated by different applications on a system. A workload is an aggregation of all processes of an application or group of applications. If resource management features are not used, the Oracle Solaris operating system responds to workload demands by adapting to new application requests dynamically. This default response generally means that all activity on the system is given equal access to resources.

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.

The Stop rights profile is the simplest way to create a restricted shell. The authorizations and rights profiles that are assigned in the policy.conf file are not consulted. In the default configuration, the role or user is not assigned the Basic Solaris User rights profile, the Console User rights profile, or the solaris.device.cdrw authorization.

Example:

Assign the Desktop Applets rights profile and the Stop rights profile to the user.

# usermod -P "Desktop Applets,Stop" username

This user does not have the Basic Solaris User rights profile or the Console User rights profile. Therefore, no commands other than the commands in the Desktop Applets rights profile can be run by this user.

Note:

*The usermod utility modifies a user's login definition on the system. It changes the definition of the specified login and makes the appropriate login-related system file and file system changes.

*Synopsis

usermod [-u uid [-o]] [-g group] [-G group [, group...]]

[-d dir [-m]] [-s shell] [-c comment] [-l new_name]

[-f inactive] [-e expire]

[-A authorization [, authorization]]

[-P profile [, profile]] [-R role [, role]]

[-K key=value] login

*-P profile

One or more comma-separated rightsprofiles defined in prof_attr.

*prof_attr

- profile description database

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.

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.

*Use the configuration element in the AI manifest for the client system to specify non-global zones.

Use the name attribute of the configuration element to specify the name of the zone.

Use the source attribute to specify the location of the config file for the zone.

The source location can be any http:// or file:// location that the client can access during installation.

*The following sample AI manifest specifies two Non-Global Zones: zone1 and zone2

You should replace the server_ip with the ip address of the NFS server.

name="http://pkg.oracle.com/solaris/release"/ >

pkg:/entire@latest

pkg:/group/system/solaris-large-server

A:Joint innovations, co-engineered projects, and specific optimizations make Oracle Solaris 11 the best UNIX for your Oracle Database, Oracle Fusion Middleware, and Oracle Applications.

C:Oracle Solaris and SPARC with Oracle Database, Oracle Fusion Middleware, Java, and Oracle Applications hold many world-record benchmarks

Not D: Solaris 11 is available for x86 as well.

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.

Storage

ZFS is the root file system on Oracle Solaris 11 offering a superior experience in terms of

manageability, scalability and data integrity. ZFS presents a pooled storage model that

completely eliminates the concept of volumes and the associated problems of partitions,

provisioning, wasted bandwidth and stranded storage. Thousands of file systems can draw

from a common storage pool, each one consuming only as much space as it actually needs. All

operations are copy-on-write transactions ensuring that the on-disk state is always valid.

Incorrect:

Not A:Network Auto-Magic(NWAM)is a project to simplify and automate network configuration on Solaris. Network Auto-Magic generally refers to Network Profiles, which allow users to specify various network configurations to be created depending on the current network conditions. The Service Discovery project, which incorporates Multicast DNS into Solaris, also fell under the Network Auto-Magic umbrella.

Not B:Pre-Flight Checker tool which can be used to check whether apps will work without modification on Solaris 11

Not C:Network Auto-Magic is a project to simplify and automate network configuration on Solaris. Network Auto-Magic generally refers to Network Profiles, which allow users to specify various network configurations to be created depending on the current network conditions. The Service Discovery project, which incorporates Multicast DNS into Solaris, also fell under the Network Auto-Magic umbrella.

Tasks such as installing and updating IPS packages, setting publishers, and modifying images require more privilege.

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.

You can display information about snapshots, boot environments, and datasets that were created by the beadm command by using the beadm list subcommand. The beadm list command output also displays boot environments that are created by the pkg command.

The beadm list command syntax is:

Syntax: beadm list [-a | [-ds] [-H] [BeName]

The command lists information about the existing boot environment. To view information for a specific boot environment, replace BeName with a boot environment name. If a specific boot environment is not specified, the command lists information about all boot environments. The default is to list boot environments without additional information.

-a – Lists all available information about the boot environment. This information includes subordinate datasets and snapshots.

-d – Lists information about all subordinate datasets that belong to the boot environment.

-s – Lists information about the snapshots of the boot environment.

-H – Prevents listing header information. Each field in the output is separated by a semicolon.