1z0-822 Practice Test

 Attempts to destroy the snapshot using zfs destroy pool12/data@nov will fail.

The defer_destroy property is set to on for the pool12/data@nov data set.

Explanation: * Use the zfs holds command to display a list of held snapshots.
* Holding a snapshot prevents it from being destroyed (B). In addition, this feature allows a
snapshot with clones to be deleted pending the removal of the last clone by using the zfs
destroy -d command. Each snapshot has an associated user-reference count, which is
initialized to zero. This count increases by one whenever a hold is put on a snapshot and
decreases by one whenever a hold is released.
Note:
* Example:
# zfs holds tank/home@now
NAME TAG TIMESTAMP
tank/home@now keep Thu Jul 15 11:25:39 2010
* You can use the zfs release command to release a hold on a snapshot or set of
snapshots.
If the snapshot is released, the snapshot can be destroyed by using the zfs destroy
command.
* Two new properties identify snapshot hold information:
The defer_destroy property is on if the snapshot has been marked for deferred destruction
by using the zfs destroy -d command. Otherwise, the property is off.
The userrefs property is set to the number of holds on this snapshot, also referred to as the
user-reference count.

transient

Explanation: Example:
The default service model is contract, but may be modified. For this example, we are going
to start the service with svc.startd. As a transient service, it will be started once and not
restarted by adding the following lines to the manifest:
<property_group name='startd' type='framework'>
<propval name='duration' type='astring' value='transient'
/>
</property_group>
Note:
svc.startd provides three models of service, which are
* Transient services—These are often configuration services, which require no longrunning
processes to provide service. Common transient services take care of boot-time
cleanup or load configuration properties into the kernel. Transient services are also
sometimes used to overcome difficulties in conforming to the method requirements for
contract or wait services. This is not recommended and should be considered a stopgap
measure.
* Contract services—These are the standard system daemons. They require processes
which run forever once started to provide service. Death of all processes in a contract
service is considered a service error, which will cause the service to restart.
* Wait services—These services run for the lifetime of the child process, and are restarted
when that process exits.

the location of the dump device

the location of the savecore directory

the reserved file system space that a core dump may not use

the compression of the crash dump file

Explanation: dumpadm - configure operating system crash dump
SYNOPSIS
/usr/sbin/dumpadm [-nuy] [-c content-type] [-d dump-device]
[-m mink | minm | min%] [-s savecore-dir]
[-r root-dir] [-z on | off]
The options include:
A: -d dump-device
Modify the dump configuration to use the specified dump device.

B: -s savecore-dir
Modify the dump configuration to use the specified directory to
save files written by savecore.
D: -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.
E: -z on | off
Modify the dump configuration to control the operation of savecore on reboot. The options
are on, to enable saving core files in a compressed format, and off, to automatically
uncompress the crash dump file. The default is on, because crash dump files can be very
large and require less file system space if saved in a compressed format.

 Add the IP address to the /etc/defaultrouter file and run route add default 172.31.10.1.

Explanation: * AI Server Software Requirements include:
Default router
Ensure that your AI server has a default route set by using the netstat command to show
network status. If your AI server does not have a default route set, you can set a static
default route by populating the /etc/defaultrouter file with the IP address of a static default
route for your server's network.
* For any currently active NCP (fixed or reactive), use the route command with the -p option
to persistently add a route:
# route -p add default ip-address

Because this command applies the specified route to the currently active NCP, the default
route is removed and potentially replaced, if the active NCP changes.

Incorrect:
Not A, Not B: The svccfg command manipulates data in the service configuration
repository. svccfg can be invoked interactively, with an individual subcommand, or by
specifying a command file that contains a series of subcommands.

The distribution constructor will not use checkpoints without the correct CLI option
added to the command.

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