Oracle 1z0-822 Oracle Solaris 11 Advanced System Administration Exam Practice Test

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.

Set the default scheduler for the system to be the FSS.

# dispadmin -d FSS

Network drivers that support link-based failure detection monitor the interface's link state and notify the networking subsystem when that link state changes.

Incorrect:

Not B: GLDv2 is a multi-threaded, clonable, loadable kernel module that provides support to device drivers for local area networks. Local area network (LAN) device drivers in the Solaris OS are STREAMS-based drivers that use the Data Link Provider Interface (DLPI) to communicate with network protocol stacks.

Not D: Link-based failure detection is always enabled, provided that the interface supports this type of failure detection.

You cannot disable link-based failure detection if this method is supported by the NIC driver.

Note:

* To write a network driver for the Oracle Solaris OS, use the Solaris Generic LAN Driver (GLD) framework.

/ For new Ethernet drivers, use the GLDv3 framework.

/ To maintain older Ethernet, Token Ring, or FDDI drivers, use the GLDv2 framework.

* To ensure continuous availability of the network to send or receive traffic, IPMP performs failure detection on the IPMP group's underlying IP interfaces. Failed interfaces remain unusable until they are repaired. Remaining active interfaces continue to function while any existing standby interfaces are deployed as needed.

The in.mpathd daemon handles the following types of failure detection:

/ Probe-based failure detection, of two types:

No test addresses are configured (transitive probing).

Test addresses are configured.

/ Link-based failure detection, if supported by the NIC driver

Service Dependency. This element identifies a group of FMRIs upon which the service is in some sense dependent.

ATTRIBUTE: Grouping:

Possible values:

'require_all',

'require_any',

'exclude_all',

‘optional_all'

Note:

* Example 1:

name='network'

grouping='require_all'

restart_on='none'

type='service'>

* In this example, let's choose the svc:/system/zones:default service instance. We can use the -l option and the service name to get more information, as shown in Listing 3.

# svcs -l svc:/system/zones:default

fmri svc:/system/zones:default

name Zones autoboot and graceful shutdown

enabled true

state online

next_state none

state_time June 14, 2012 08:30:31 PM NZST

logfile /var/svc/log/system-zones:default.log

restarter svc:/system/svc/restarter:default

manifest /etc/svc/profile/generic.xml

manifest /lib/svc/manifest/system/zones.xml

manifest /lib/svc/manifest/system/zonestat.xml

dependency require_all/none svc:/milestone/multi-user-server (online)

dependency optional_all/none svc:/system/pools:default (disabled)

dependency optional_all/none svc:/system/pools/dynamic:default (disabled)

dependency optional_all/none svc:/system/zones-monitoring (online)

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

* zone.max-processes

Maximum number of process table slots

simultaneously available to this zone.

Because both normal processes and

zombie processes take up process table

slots, the max-processes control thus

protects against zombies exhausting the

process table. Because zombie processes

do not have any LWPs by definition, the

max-lwps control cannot protect against

this possibility

Note:

* prctl - operations on a process

Use the prctl command to make runtime interrogations of and modifications to the resource controls associated with an active process, task, or project on the system.

Example: Displaying Information About the System Administrator Rights Profile

Use the profiles command to display information about a specific rights profile. In the following example, information about the System Administrator rights profile is displayed:

$ profiles -p "System Administrator" info

name=System Administrator

desc=Can perform most non-security administrative tasks

profiles=Install Service Management,Audit Review,Extended Accounting Flow

Etc.

Dump Parameter: minimum free space

Minimum amount of free space required in the savecoredirectory after

saving crash dump files. If no minimum free space has been configured, the

default is one Mbyte.

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

A: IPS package manifests can be signed, with the signatures becoming part of the manifest.

Signatures are represented as actions just as all other manifest content is represented as actions.

C: A manifest can have multiple independent signatures.

* Set the default scheduler for the system to be the FSS.

# dispadmin -d FSS

* Scheduling Class on a System with Zones Installed

Non-global zones use the default scheduling class for the system. If the system is updated with a new default scheduling class setting, non-global zones obtain the new setting when booted or rebooted.

The preferred way to use FSS in this case is to set FSS to be the system default scheduling class with the dispadmin command.

See % below.

coredump parameter: -m mink | minm | min%

Create a minfree file in the current savecore directory indicating that savecore should maintain at least the specified amount of free space in the file system where the savecore directory is located. The min argument can be one of the following:

k

A positive integer suffixed with the unit k specifying kilobytes.

m

A positive integer suffixed with the unit m specifying megabytes.

%

A % symbol, indicating that the minfree value should be computed as the specified percentage of the total current size of the file system containing the savecore directory.

The savecore command will consult the minfree file, if present, prior to writing the dump files. If the size of these files would decrease the amount of free disk space below the minfree threshold, no dump files are written and an error message is logged. The administrator should immediately clean up the savecore directory to provide adequate free space, and re-execute the savecore command manually. The administrator can also specify an alternate directory on the savecore command-line.

Incorrect:

Not C: Separate ZFS volumes must be used for the swap area and dump devices.

* The following directives cause audit_binfile.so to be loaded, specify the directories for writing audit logs, and specify the percentage of required free space per directory.

auditconfig -setplugin audit_binfile active \

"p_dir=/var/audit/jedgar/eggplant,/var/audit/jedgar.aux/eggplant,

/var/audit/global/eggplant;p_minfree=20;p_fsize=4.5GB"

* The attributes specifying the configuration of audit_binfile plugin include:

p_dir

dir1[,dir2],.. [,dirn]

A list of directories, where the audit files will be created. Any valid writable directory can be specified.

p_fsize

The p_fsize attribute defines the maximum size that an audit file can become before it is automatically closed and a new audit file is opened. This is equivalent to an administrator issuing an audit -ncommand when the audit file size equals the value specified by the administrator. The default size is zero (0), which allows the file to grow without bound.

Only verbose mode is selected (-v) not checkpoints options.

* 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.

Note:

* 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 your selection of files, packages, and scripts for the image that is being built. This process uses the checkpointing options that are available in the distro_const command.

* distro_const Command Options

/ distro_const build manifest

Builds an image in one step using specified manifest file

/ distro_const build -v

Verbose mode

/ distro_const build -l manifest

Lists all valid checkpoints at which you can pause and resume building an image

/ distro_const build -p checkpoint_name manifest

Pauses building an image at a specified checkpoint

/ distro_const build -r checkpoint_name manifest

Resumes building an image from a specified checkpoint

/ distro_const build -h

Displays help for the command

* After you have set up the manifest file that you plan to use and, if desired, customized the finalizer scripts, you are ready to build an image by running the distro_const command.

You can use the distro_const command to build an image in either of the following:

In one step

Pausing and restarting the build as needed to examine the content of the image and debug the scripts during the build process

Note:

* (not A, not B, not D) The privs key contains a comma-separated list of privilege numbers that will be effective when the command or action is run.

* euid and uid contain a single user name or a numeric user ID. Commands designated with euid run with the effective UID indicated, which is similar to setting the setuid bit on an executable file. Commands designated with uid run with both the real and effective UIDs. Setting uid may be more appropriate than setting the euid on privileged shell scripts.

* egid and gid contain a single group name or a numeric group ID. Commands designated with egid run with the effective GID indicated, which is similar to setting the setgid bit on a file. Commands designated with gid run with both the real and effective GIDs. Setting gid may be more appropriate than setting guid on privileged shell scripts.

* /etc/security/exec_attr is a local database that specifies the execution attributes associated with profiles.

/etc/security/exec_attr

Locally added entries. Make sure that the shipped header remains intact.

/etc/security/exec_attr.d/*

Entries added by package installation.

Global Actions on Resource Control Values

Global actions apply to resource control values for every resource control on the system. You can use the rctladm command to perform the following actions:

* Display the global state of active system resource controls

* Set global logging actions

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.

* DiffServ uses the 6-bit Differentiated services Field (DS field) in the IP header for packet classification purposes.

* In the Diffserv model, the marker marks a packet with a value that reflects a forwarding behavior. Marking is the process of placing a value in the packet's header to indicate how to forward the packet to the network. IPQoS contains two marker modules:

/ dscpmk – Marks the DS field in an IP packet header with a numeric value that is called the Differentiated Services codepoint, or DSCP. A Diffserv-aware router can then use the DS codepoint to apply the appropriate forwarding behavior to the packet.

/ dlcosmk – Marks the virtual local area network (VLAN) tag of an Ethernet frame header with a numeric value that is called the user priority. The user priority indicates the class of service (CoS), which defines the appropriate forwarding behavior to be applied to the datagram.

Note:

* Differentiated services or DiffServ is a computer networking architecture that specifies a simple, scalable and coarse-grained mechanism for classifying and managing network traffic and providing quality of service (QoS) on modern IP networks. DiffServ can, for example, be used to provide low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as web traffic or file transfers.

* IPQoS, included in Solaris, includes the following modules, which are part of the Differentiated Services (Diffserv) architecture that is defined in RFC 2475:

Classifier

Meter

Marker

IPQoS adds the following enhancements to the Diffserv model:

Flow-accounting module

802.1D datagram marker

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