1Z0-580 Practice Questions

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.

Reference: How to Manage ZFS Data Encryption

The beadm create command has the following options, where BeName specifies the name of the

boot environment to be created.

Syntax: beadm create [-a] [-d description] [-e non-activeBeName | BeName@snapshot] [-o

property=value]...[-p zpool] BeName

-a – Activate the newly created boot environment upon creation. The default is to not activate the

newly created boot environment.

Reference: Creating and Administering Oracle Solaris 11 Boot Environments

pkgrecv

- Image Packaging System content retrieval utility

Options include:

-c cache_dir

The path to a directory that will be used to cache downloaded content. If this directory is not

supplied, the client automatically selects a cache directory. In the case where a download is

interrupted, and a cache directory was automatically chosen, use this option to resume the

download. See the “Environment Variables” section below for details about how to set the location

used for temporary data storage.

Reference: Image Packaging System Man Pages

:

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.

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.

Reference: Oracle Solaris 11 Express Automated Installer Guide,

Boot the Install Environment

Without Starting an Installation

B: The disk intended for the root pool must have an SMI label. Otherwise, the installation will fail.

D: The default target location for the installation is the first disk found on each client that meets the

size requirement. If the size of a disk is greater than or equal to the recommended size, the installer

selects that disk as the installation target. If the size of the disk is less than the recommended size,

the installer checks the next disk. If no disk is found that meets the size requirement, the automated

installation fails for that client.

Note:

* If you do not specify a target location on a client for installing the Oracle Solaris OS, AI selects a

default target.

Incorrect:

not A: and – Optional. You can use AI to configure swap and dump during the

automated install.

Not C: A mirrored dataset for the root pool is not required.

Reference: Oracle Solaris ZFS Administration Guide, Installing a ZFS Root Pool

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.

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

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

Reference: Oracle Solaris 11 Information Library, Transitioning Your Oracle Solaris 10 System to

Oracle Solaris 11

Boot Load Failed

If the AI client starts downloading the boot_archive, but then fails with the error, “Boot load failed,”

that indicates that the client DHCP information is configured incorrectly.

Rebooting with command: boot net:dhcp - install

Boot device: /pci@7c0/pci@0/network@4:dhcp File and args:

1000 Mbps FDX Link up

HTTP: Bad Response: 500 Internal Server Error

Evaluating:

Boot load failed

This error could happen if another DHCP server is responding to the client. Check the DHCP

configuration for this client. If the configuration appears to be correct, determine whether there is

another DHCP server in the subnet.

Reference: Installing Oracle Solaris 11 Systems, Boot Load Failed