Pass the Oracle Solaris 1z0-822 Questions and answers with ExamsMirror

Not on compression setting:

compression=on | off | lzjb | gzip | gzip-N

Controls the compression algorithm used for this dataset. The

"lzjb" compression algorithm is optimized for performance while

providing decent data compression. Setting compression to "on" uses

the "lzjb" compression algorithm.

Incorrect:

Not A, Not E: Should not use commas like this.

Not B, Not D: There is no property algorithm named to this command. To specify the use of the lzjb compression command we must use compression=lzjb.

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

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.

* How to Reconfigure a Zone to Use a VNIC

1. Become an administrator.

2. Create the VNIC.

(C) 3. Change the zone's IP type from shared to exclusive.

4.Change the zone's interface to use a VNIC.

5. Verify and commit the changes you have implemented and then exit the zone.

(D) 6. Reboot the zone.

7. Log in to the zone.

8. Configure the VNIC with a valid IP address.

* Example. Reconfiguring a Zone Configuration to Use a VNIC

In this example, zone2 already exists as a shared zone. The zone also uses the primary interface of the system rather than a virtual link. You need to modify zone2 to use vnic2. To use vnic2, zone2's IP type must first be changed to exclusive. Note that some of the output is truncated to focus on the relevant information that relates to virtual networks.

global# dladm create-vnic -l net0 vnic2

global# zonecfg -z zone2

(C) zonecfg:zone1> set ip-type=exclusive

zonecfg:zone1> remove net physical=net0

zonecfg:zone1> add net

zonecfg:zone1:net> set physical=vnic2

zonecfg:zone1:net> end

zonecfg:zone1> verify

zonecfg:zone1> commit

zonecfg:zone1> exit

(D) global# zoneadm -z zone2 reboot

global# zlogin zone2

zone2# ipadm create-ip vnic2

zone2# ipadm create-addr -a 192.168.3.85/24 vnic2

ipadm: vnic2/v4

zone2# exit

global# vi /etc/hosts

#

1 localhost

127.0.0.1 localhost

192.168.3.70 loghost #For net0

192.168.3.80 zone1 #using vnic1

192.168.3.85 zone2 #using vnic2

Required to maintain high availability --> use a mirror.

The same data will be accessed many times throughout the day. Configure the storage for maximum performance. Use caching.

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.

The capped-memory resource sets limits for physical, swap, and locked memory. Each limit is optional, but at least one must be set.

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.

D: /etc/security/auth_attr is a local source for authorization names and descriptions.

An authorization is a right assigned to users that is checked by certain privileged programs to determine whether users can execute restricted functionality.