1z0-822 Questions and Answers

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.

set-publisher --sticky

With --sticky, specify that updates to packages that were installed from this publisher must also come from this publisher. This is the default behavior.

A: The audit_remote plugin is loaded by auditd if the plugin is configured as an active via auditconfig. Use the auditconfig -setplugin option to change all the plugin related configuration parameters

B: The solaris-audit service port assigned by IANA is 16162.

Incorrect:

Not D: audit_remote authenticates itself to the remote audit service by way of GSS-API (libgss(3LIB)). Default gss credentials are used as provided by the gss implementation mechanism, such as Kerberos.

Note: audit_remote

- send Solaris audit logs to a remote server

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.

svcs -x: Explains why a service is not available.

Incorrect:

not A: svcs -l FMRI: Provides a long listing of information about FMRI; includes dependency information

not B, not C: svcs -d FMRI: Lists dependencies for FMRI.

not e: svcadm clear FMRI: Clear faults for FMRI.

B: Link aggregations provide high availability and higher throughput by aggregating multiple interfaces at the MAC layer. IP Multipathing (IPMP) provides features such as higher availability at the IP layer. Both IPMP and Link Aggregation are based on the grouping of network interfaces, and some of their features overlap, such as higher availability. These technologies are however implemented at different layers of the stack, and have different strengths and weaknesses.

E: Internet Protocol Network Multipathing (IPMP) provides fault-tolerance and load balancing across multiple network interface cards. By using IPMP, you can configure one or more interfaces into an IP multipathing group. After configuring IPMP, the system automatically monitors the interfaces in the IPMP group for failure. If an interface in the group fails or is removed for maintenance, IPMP automatically migrates, or fails over, the failed interface's IP addresses

Incorrect:

Not A: The same (non-null) character string IPMP group name identifies all interfaces in the group. You can place interfaces from NICs of different speeds within the same IPMP group, as long as the NICs are of the same type.

Not C:If LACP (Link Aggregation Control Protocol) cannot aggregate all the ports that are compatible (for example, the remote system might have more restrictive hardware limitations), then all the ports that cannot be actively included in the channel are put in hot standby state and are used only if one of the channeled ports fails.

Not D: MP is built into Oracle Solaris and does not require any special hardware. Any interface that is supported by Oracle Solaris can be used with IPMP. However, IPMP does impose the following requirements on your network configuration and topology:

/All interfaces in an IPMP group must have unique MAC addresses.

/ All interfaces in an IPMP group must be of the same media type.

/ All interfaces in an IPMP group must be on the same IP link

Profiles are, in many ways, similar to manifests in that they use the same XML DTD. However, instead of providing information about a service, its dependencies, and methods, a profile is used to provide customization of a service or an instance of a service. Customizations include whether an instance of a service should be enabled or disabled and any modifications to service configuration properties.

Incorrect:

Not A: Manifests (not profiles) are used to describe services and instances of a service, including any property groups and properties they might have.

How to Manually Specify Target Systems for Probe-Based Failure Detection

1. Add a route to a particular host to be used as a target in probe-based failure detection.

$ route -p add -host destination-IP gateway-IP -static

where destination-IP and gateway-IP are IPv4 addresses of the host to be used as a target. For example, you would type the following to specify the target system 192.168.10.137, which is on the same subnet as the interfaces in IPMP group itops0:

$ route -p add -host 192.168.10.137 192.168.10.137 -static

This new route will be automatically configured every time the system is restarted. If you want to define only a temporary route to a target system for probe-based failure detection, then do not use the -p option.

2.Add routes to additional hosts on the network to be used as target systems.

* Example:

root@solaris:~# zonecfg -z zd1

Use 'create' to begin configuring a new zone.

zonecfg:zd1> create

create: Using system default template 'SYSdefault'

zonecfg:zd1> exit

zonepath cannot be empty.

Zone zd1 failed to verify

zd1: Required resource missing

Configuration not saved; really quit (y/[n])? n

zonecfg:zd1> verify

zonepath cannot be empty.

zd1: Required resource missing

zonecfg:zd1> set zonepath=/zones/zd1

zonecfg:zd1> exit

Note:

* anet

Automatic network interface.

The anet resource represents the automatic creation of a network resource for an exclusive-IP zone.

See steps 7 and 8 below.

How to Re-create a ZFS Root Pool and Restore Root Pool Snapshots

1. Boot from an installation DVD or the network.

2. Mount the remote snapshot file system if you have sent the root pool snapshots as a file to the remote system.

3. If the root pool disk is replaced and does not contain a disk label that is usable by ZFS, you must relabel the disk.

4. Re-create the root pool.

5. Restore the root pool snapshots.

6. Verify that the root pool datasets are restored.

7. Set the bootfs property on the root pool BE.

8. Install the boot blocks on the new disk.

9. Reboot the system.

The beadm utility enables you to create a new boot environment based on an existing snapshot.

Note:

* You can manage the boot environments on your system either by using the beadm command or by using the Package Manager.

* A boot environment is a bootable instance of the Oracle Solaris operating system image plus any other application software packages installed into that image. System administrators can maintain multiple boot environments on their systems, and each boot environment can have different software versions installed.