1z0-822 Practice Test

 It does not persist across reboots.

Explanation: To make IPMP groups persists across reboots you would have to do some
work:
To configure an IPMP group that persists across system reboots, you would edit the
hostname configuration file of the IPMP interface to add data addresses.
Note: 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. For example, you can configure the interfaces of
100-megabit Ethernet NICs and the interfaces of one gigabit Ethernet NICs in the same
group. As another example, suppose you have two 100-megabit Ethernet NICs. You can
configure one of the interfaces down to 10 megabits and still place the two interfaces into
the same IPMP group.
Incorrect:
Not A: You cannot place two interfaces of different media types into an IPMP group. For
example, you cannot place an ATM interface in the same group as an Ethernet interface.
Not B: An IP multipathing group, or IPMP group, consists of one or more physical
interfaces on the same system that are configured with the same IPMP group name. All
interfaces in the IPMP group must be connected to the same IP link.

  Yes. Run priocntl –s –c FSS –i all inside the zone.

Explanation: * Syntax:
priocntl -s [-c class] [class-specific options]
[-i idtype] [idlist]
* The priocntl command displays or sets scheduling parameters of the specified process(es). It can also be used to display the current configuration information for the
system's process scheduler or execute a command with specified scheduling parameters.
Processes fall into distinct classes with a separate scheduling policy applied to each class.
The process classes currently supported are the real-time class, time-sharing class,
interactive class, fair-share class, and the fixed priority class.
* priocntl options include:
-c
class
Specifies the class to be set. (The valid class arguments are RT for real-time, TS for timesharing,
IA for inter-active, FSS for fair-share, or FX for fixed-priority.) If the specified class
is not already configured, it is automatically configured.
-s
Sets the scheduling parameters associated with a set of processes.

Modify the privileges in the service configuration.

Explanation: A service can be configured to run within a limited set of privileges, rather
than as the all-powerful root user.

Install the boot blocks on the new disk.

 Set the bootfs property on the root pool.

Explanation: 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.

Option A

Explanation: How to Create a Virtual Network Interface
This procedure shows how to create a virtual network interface card (VNIC).
1. Create a VNIC over a datalink.
# dladm create-vnic -l link vnic
link is the name of the datalink over which the VNIC is configured.
vnic is the VNIC which you can label with a customized name as well.
2. Create a VNIC IP interface over the link.
# ipadm create-ip vnic
3. Configure the VNIC with a valid IP address.
If you are assigning a static IP address, use the following syntax:
# ipadm create-addr -T static -a address addrobj
where addrobj uses the naming format interface/user-defined-string, such as
e1000g0/v4globalz.