Oracle 1z0-822 - Oracle Solaris 11 Advanced System Administration

Signature Policy: verify

Verify that all manifests with signatures are validly signed, but do not require all installed packages to be signed.

This is the default value.

Incorrect:

Not B: You cannot activate an unbootable BE in a nested BE.

Not D: The zone is named ozone (not ozone2).

Note:

* beadm supports the concept of a nested BE, specifically, as it pertains to BEs for non-global zones.

* beadm list [-a | -ds] [-H] [beName]

Lists information about the existing boot environment named beName, or lists information for all boot environments if beName is not provided. The Active field indicates whether the boot environment is active now, represented by N; active on reboot, represented by R; or both, represented by NR. Unbootable BEs inside of a nested BE are represented by an exclamation point (!)

An interface that has been created cannot become a member of an aggregation.

A: Oracle Solaris Image Types include:

x86 or SPARC ISO Image for Automated Installations – The Oracle Solaris release includes the automated installer tool. The automated installer (AI) is used to automate the installation of the Oracle Solaris OS on one or more SPARC and x86 systems over a network.

D:

* You can also create custom scripts to modify your installation image. Then, you can add checkpoints to the manifest file to run these custom scripts.

* You can use the options provided in the distro_const command to stop and restart the build process at various stages in the image-generation process, in order to check and debug the image that is being built. This process of stopping and restarting during the build process is called checkpointing. Checkpointing is optional. Default checkpoints are specified in each manifest file.

Incorrect:

Not B: Only for x86, not for SPARC-

Oracle Solaris x86 LiveCD – You can create an x86 ISO image that is comparable to the LiveCD image that's distributed as an Oracle Solaris release. You can also modify the content of this ISO image by adding or removing packages. You can revise the default settings for the resulting booted environment to create a custom ISO image or USB image.

Note: The distribution constructor creates images based on settings specified in XML files, called manifest files. The manifest files contain specifications for the contents and parameters for the ISO images that you create using the distribution constructor. The distribution-constructor package provides sample manifests that can be used to create a custom x86 Live Media ISO, an x86 or SPARC Automated Install ISO image, or an x86 or SPARC text installation ISO image.

The elements in each manifest file provide preset, default values that will create the type of ISO image you need. You can manually edit these preset elements in a manifest file to customize the resulting image. In addition, you can create custom scripts to further modify your image. Then, reference the new scripts in the manifest file.

Note:

* In Oracle Solaris 11, etherstubs and VNICs are the basic components of network virtualization.

* The VNIC connects the virtual network to the external network. The VNIC also enables the zones to communicate with one another through the virtual switch that is automatically created with the VNIC. For a virtual network to host traffic internally between zones and with the external LAN and the Internet, each zone must have its own interface. Therefore, you must repeat this procedure as many times as the number of zones that will belong to the virtual network.

* Create the etherstub.

# dladm create-etherstub etherstub

Perform this step only if you are creating a private virtual network which you want to restrict from being accessed by external systems.

Example. Displaying Administratively Customized Properties (here only admin layer is displayed with –l)

The following command uses SMF layers to display administratively customized properties.

example% svcprop -p config -l admin svc:/network/dns/client

(A) config/domain astring admin my.domain.com

(D) config/nameserver net_address admin 10.22.33.44 10.44.33.11

Note:

* config/nameserver refers to the Solaris DNS server.

/ The nameserver keyword specifies DNS servers to query using IP address.

Example:

The /etc/resolv.conf file contains configuration directives for the DNS resolver. The following resolv.conf example shows two name servers and three search suffixes:

domain nj.bigcorporation.com

nameserver 192.168.10.11

nameserver 192.168.20.88

* The svcprop utility prints values of properties in the service configuration repository. Properties are selected by -p options and the operands

* Simulation:

* Creating a New Pool By Splitting a Mirrored ZFS Storage Pool

A mirrored ZFS storage pool can be quickly cloned as a backup pool by using the zpool split command.

Currently, this feature cannot be used to split a mirrored root pool.

You can use the zpool split command to detach disks from a mirrored ZFS storage pool to create a new pool with one of the detached disks. The new pool will have identical contents to the original mirrored ZFS storage pool.

By default, a zpool split operation on a mirrored pool detaches the last disk for the newly created pool. After the split operation, import the new pool. For example::

# zpool status tank

pool: tank

state: ONLINE

scrub: none requested

config:

NAME STATE READ WRITE CKSUM

tank ONLINE 0 0 0

mirror-0 ONLINE 0 0 0

c1t0d0 ONLINE 0 0 0

c1t2d0 ONLINE 0 0 0

errors: No known data errors

# zpool split tank tank2

# zpool import tank2

# zpool status tank tank2

pool: tank

state: ONLINE

scrub: none requested

config:

NAME STATE READ WRITE CKSUM

tank ONLINE 0 0 0

c1t0d0 ONLINE 0 0 0

errors: No known data errors

pool: tank2

state: ONLINE

scrub: none requested

config:

NAME STATE READ WRITE CKSUM

tank2 ONLINE 0 0 0

c1t2d0 ONLINE 0 0 0

errors: No known data errors

Example:

List all configuration changes that have been made in the SMF configuration repository to the name-service/switch service:

# svccfg -s name-service/switch listcust –L

AD: Manifests from the standard directory trees /lib/svc/manifest and /var/svc/manifest are processed during system boot and anytime an administrator or program runs:

$ svcadm restart manifest-import

C: svccfg

apply subcommand

If the argument is a service profile or manifest, apply the configuration to the admin layer of the SMF repository. Services, instances, property groups, and properties will be created as necessary.

E: import [-V] [file | directory]

svccfg import on a file in a system-managed filesystem location (subdirectories of /lib/svc/manifest and /var/svc/manifest) invokes: svcadm restart manifest-import.

Placing your manifests in a system-managed location and invoking svcadm restart manifest-import to import them is the recommended practice.

svccfg import on files in other locations imports their properties as administrative customization into the admin layer. It is equivalent to:

svccfg apply [file | directory]

Incorrect:

not B: Manifests are processed in two different phases during boot.

The service svc:/system/early-manifest-import:default, a pseudo service, is responsible for the first manifest processing. This service processes only manifests from the /lib/svc/manifest directory tree before svc.startd(1M) initializes any services thus enabling services delivered in /lib/svc/manifest to always start with their most updated definition. Since this is a pseudo service, svcadm(1M) commands are ignored though svcs(1) can be used to observe status and get log file information.

The svc:/system/manifest-import:default service handles the second manifest processing and imports manifest files from both /lib/svc/manifest and /var/svc/manifest directory trees, in that respective order.