1z0-822 Practice Test

ipadm set-ifprop –p forwarding=on net0

routeadm –ue ipv4-routing

Explanation:
URL: http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-118-s11-
script-zones-524499.html

  after the commit command

Explanation:
* The netcfg command manipulates system network configuration profiles. The netcfg
command can be invoked interactively, with an individual subcommand, or by specifying a
command file that contains a series of subcommands.
* subcommand: netcfg commit
Commits the current profile specification to persistent storage. A configuration must be
correct to be committed. Therefore, this operation automatically performs a verify operation
on the profile or object as well. The commit operation is attempted automatically upon
exiting the current scope by using either the end or exit subcommand.
Note:

* from the netadm list output we see the line
ncp Automatic disabled
* Oracle Solaris 11 uses profile-based network configuration, which is comprised of two
network configuration modes: manual (fixed) and automatic (reactive). Depending on which
network configuration mode you choose during an installation, either the DefaultFixed
network configuration profile (NCP) or the Automatic NCP is activated on the system. If the
DefaultFixed NCP is active, the network is manually configured by using the dladm and
ipadm commands . If the Automatic NCP or a user-defined NCP that you previously
created is active, the netcfg and netadm commands (formerly nwamcfg and nwamadm) are
used to create and manage network configuration.

re

Explanation: re
page reclaims.
The information is given in units per second.
Note:
* vmstat reports virtual memory statistics regarding kernel thread, virtual memory, disk,
trap, and CPU activity.
Incorrect:
Not B: sr, pages scanned by clock algorithm
Not C: free
size of the free list (Kbytes)
Not D: fr
kilobytes freed

 Both technologies can increase outbound bandwidth.

 IPMP supports load spreading across all interfaces for inbound traffic

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

Fixed-priority (FX)

Explanation: The FX scheduler provides a scheduling policy for processes that require
user or application control of scheduling priorities. The priorities of processes that run
under FX are fixed.
The FX class provides a fixed-priority preemptive scheduling policy. This policy is used by
processes that require user or application control of scheduling priorities but are not
dynamically adjusted by the system. By default, the FX class has the same priority range
as the TS, IA, and FSS classes. The FX class allows user or application control of
scheduling priorities through user priority values assigned to processes within the class.
These user priority values determine the scheduling priority of a fixed-priority process
relative to other processes within its class.
Incorrect:
Not A: The fair share scheduling class enables you to allocate CPU time based on shares
instead of the priority scheme of the timesharing (TS) scheduling class.
Not D: The goal of the time-sharing policy is to provide good response time to interactive
processes and good throughput to CPU-bound processes. The scheduler switches CPU
allocation often enough to provide good response time, but not so often that the system
spends too much time on switching. Time slices are typically a few hundred milliseconds.
The time-sharing policy changes priorities dynamically and assigns time slices of different
lengths.