Free 1Z0-820 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

shadowd is a daemon that provides background worker threads to migrate data for a shadow

migration. A shadow migration gradually moves data from a source file system into a new “shadow”

file system. Users can access and change their data within the shadow file system while migration is

occurring.

The shadowd service is managed by the service management facility, smf(5). Administrative actions

on this service, such as enabling, disabling, or requesting restart, can be performed using

svcadm(1M). The service's status can be queried using the svcs(1) command.

The svccfg(1M) command can be used to manage the following parameter related to shadowd:

config_params/shadow_threads

Note: Oracle Solaris 11: In this release, you can migrate data from an old file system to a new file

system while simultaneously allowing access and modification of the new file system during the

migration process.

Setting the shadow property on a new ZFS file system triggers the migration of the older data. The

shadow property can be set to migrate data from the local system or a remote system with either of

the following values:

file:///path

nfs://host:path

Reference: man shadowd

There is no data-link named vswitch192.168.

We need to create an etherstub first.

See Note and example below for details.

Note: Create a VNIC in the system's global zone.

# dladm create-vnic -l data-link vnic-name

data-link is the name of the interface where the VNIC is to be configured.

-l link, --link=link

link can be a physical link or an etherstub.

vnic-name is the name that you want to give the VNIC.

For example, to create a VNIC named vnic0 on interface e1000g0, you would type the following:

# dladm create-vnic -l e1000g0 vnic0

Example: Creating a Virtual Network Without a Physical NIC

First, create an etherstub with name stub1:

# dladm create-etherstub stub1

Create two VNICs with names hello0 and test1 on the etherstub. This

operation implicitly creates a virtual switch connecting hello0 and

test1.

# dladm create-vnic -l stub1 hello0

# dladm create-vnic -l stub1 test1

Reference: man dladm

D: According to line /etc/security

F: According to line /export/home

Not E: According to line IGNORE dirmtime

Note: In default mode, the bart compare command, as shown in the following example, checks all

the files installed on the system, with the exception of modified directory timestamps (dirmtime):

CHECK all

IGNORE

dirmtime

Note 2: The Basic Audit Reporting Tool (BART) feature of Oracle Solaris enables you to

comprehensively validate systems by performing file-level checks of a system over time. By creating

BART manifests, you can easily and reliably gather information about the components of the

software stack that is installed on deployed systems.

BART is a useful tool for integrity management on one system or on a network of systems.

Reference: Oracle Solaris Administration: Security Services, BART Manifests, Rules Files, and Reports

(Reference)

rctladm - display and/or modify global state of system

resource controls

The following command activates system logging of all viola-

tions of task.max-lwps.

# rctladm -e syslog task.max-lwps

#

Reference: man rctladm

Migrating Data With ZFS Shadow Migration

ZFS shadow migration is a tool you can use to migrate data from an existing file system to a new file

system. A shadow file system is created that pulls data from the original source as necessary.

You can use the shadow migration feature to migrate file systems as follows:

* A local or remote ZFS file system to a target ZFS file system

* A local or remote UFS file system to a target ZFS file system

Shadow migration is a process that pulls the data to be migrated:

* Create an empty ZFS file system.

* Set the shadow property on an empty ZFS file system, which is the target (or shadow) file system,

to point to the file system to be migrated.

For example:

# zfs create -o shadow=nfs://system/export/home/ufsdata users/home/shadow2

* Data from file system to be migrated is copied over to the shadow file system.

Incorrect answers:

B: lucreate– create a new boot environment

Note: ZFS is the default root file system.

UFS is a supported legacy file system, but it is not supported as a bootable root file system.

Reference: Transitioning From Oracle Solaris 10 to Oracle Solaris 11, Migrating Data With ZFS Shadow

Migration

Check DNS

* (A) Check whether DNS is configured on your client by verifying that a non-empty /etc/resolv.conf

file exists.

* (F) If /etc/resolv.conf does not exist or is empty, check that your DHCP server is providing DNS

server information to the client:

# /sbin/dhcpinfo DNSserv

If this command returns nothing, the DHCP server is not set up to provide DNS server information to

the client. Contact your DHCP administrator to correct this problem.

* (B) If an /etc/resolv.conf file exists and is properly configured, check for the following possible

problems and contact your system administrator for resolution:

** The DNS server might not be resolving your IPS repository server name.

** No default route to reach the DNS server exists.

Reference: Installing Oracle Solaris 11 Systems, Client Installation Fails

Example (assuming there exists a snapshot ‘tank/test@1).

Full backup

Now let’s do a full initial backup from the ‘tank/test@1 snapshot:

# zfs send tank/test@1 | zfs receive tank/testback

B: Set the correct permissions. Serving a Local Repository Using SMF First, create a ZFS file system to hold the repository. Next, make a local copy of the IPS repository file. Make the contents of the repository file available to the pkg.depotd(1M) server, using the lofiadm command to mount the ISO image. 4. (A) Copy the repository files to the ZFS file system you created. This will increase the performance of repository accesses and avoid the need to remount the .iso image each time the system restarts. (Be sure to use /mnt/repo, not /mnt/repo/, so that you copy the repo directory and not just the files and subdirectories in the repo directory.) # rsync -aP /mnt/repo /export/repo2010_11 You can use the df command to confirm the copy: 5. Once the files are copied, unmount the image and deallocate the block device. 6. Now that your local copy is ready, use the svccfg command to configure the repository server service, specifying the location of your local repository and setting readonly to true: (D)# svccfg -s application/pkg/server setprop pkg/inst_root=/export/repo2010_11/repo (E)# svccfg -s application/pkg/server setprop pkg/readonly=true 7. Start the pkg.depotd repository service: (G) # svcadm refresh application/pkg/server (I) # svcadm enable application/pkg/server Reference: How I Created Local Package Repositories http://www.oracle.com/technetwork/articles/servers-storage-admin/localrepositories1377242.html

B:

Note: You can create custom AI manifests for particular clients.

Create a custom XML AI manifest file. This method is best suited to an environment where few

systems require custom provisioning. Most systems to be installed have identical or similar hardware

and will be provisioned identically.

Write a script that dynamically creates an AI manifest for each client at installation time. Use this

method to create a custom installation for each client, based on client characteristics discovered at

installation time.

E: AI Server Software Requirements include

Software package repository

Ensure that the install server can access an IPS software package repository. AI requires the

install/installadm package.

F: Install Server Requirements

Any system that meets these requirements can be used as an AI install server, including laptops,

desktops, virtual machines, and enterprise servers. The install server can be either an x86 machine or

a SPARC machine. An x86 install server can install both SPARC and x86 clients, and a SPARC install

server can install both SPARC and x86 clients.

Note: To install clients over the network, AI requires a separate system to be an install server. On the

install server, create an AI install service to provide a net image and instructions for installing the

Oracle Solaris 11 OS on different clients.

pkg/image_root

(astring) The path to the image whose file information will be used as a cache for file data.

Incorrect answers:

A: pkg.depotd is the depot server for the image packaging system. It provides network access to the

data contained within a package repository. Clients that do not support direct access to a repository

through the file system, or for which network access is the only available or preferred method of

transport, typically use the package depot.

B: pkg/readonly(boolean)

Sets whether modifying operations, such as those initiated by pkgsend(1), are disabled. Retrieval

operations are still available. This property cannot be true when the pkg/mirror property is true. The

default value is true.

C: pkg/writable_root

(astring) The file system path to a directory to which the program has write access. This is used with

the -readonly option to enable the depot server to create files, such as search indexes, without

needing write access to the package information.

Reference: man pkg.depotd

B: The Network Status notification icon is only displayed on the desktop if you are using NWAM to

automatically configure your network.

C: All online (Wireless)

Indicates all manually enabled connections in the enabled network profile are online and that the

required number of connections in the enabled profile group (if such a group exists) are online. The

required number is the same as those described for the All online (Wired) status.

Note that at least one online connection is wireless.

Reference: Oracle Solaris Administration: Network Interfaces and Network Virtualization , Checking

the Status of Your Network Connection

How to Create an iSCSI LUN The following steps are completed on the system that is providing the storage device. 1.Create a ZFS storage pool. Example: target# zpool create sanpool mirror c2t3d0 c2t4d0 (C)2. Create a ZFS volume to be used as a SCSI LUN. (D)3. Create a LUN for the ZFS volume. Example: target# stmfadm create-lu /dev/zvol/rdsk/sanpool/vol1 Logical unit created: 600144F0B5418B0000004DDAC7C10001 4. Confirm that the LUN has been created. Example target# stmfadm list-lu LU Name: 600144F0B5418B0000004DDAC7C10001 (F) 5. Add the LUN view. This command makes the LUN accessible to all systems. target# stmfadm add-view 600144F0B5418B0000004DDAC7C10001 How to Create the iSCSI Target This procedure assumes that you are logged in to the local system will contains the iSCSI target. Note: The stmfadm command manages SCSI LUNs. Rather than setting a special iSCSI property on the ZFS volume, create the volume and use stmfadm to create the LUN. (H) 1. Enable the iSCSI target service. target# svcadm enable -r svc:/network/iscsi/target:default (I) 2. Create the iSCSI target. target# itadm create-target Reference: Oracle Solaris Administration: Devices and File Systems, Configuring iSCSI Devices With COMSTAR

The framework enables providers of cryptographic services to have their services used by many

consumers in the Oracle Solaris operating system. Another name for providers is plugins. The

framework allows three types of plugins:

* User-level plugins - Shared objects that provide services by using PKCS #11 libraries, such as

pkcs11_softtoken.so.1.

* Kernel-level plugins - Kernel modules that provide implementations of cryptographic algorithms in

software, such as AES.

Many of the algorithms in the framework are optimized for x86 with the SSE2 instruction set and for

SPARC hardware.

* Hardware plugins - Device drivers and their associated hardware accelerators. The Niagara chips,

the ncp and n2cp device drivers, are one example. A hardware accelerator offloads expensive

cryptographic functions from the operating system. The Sun Crypto Accelerator 6000 board is one

example.

Reference: Oracle Solaris Cryptographic Framework

http://docs.oracle.com/cd/E19963-01/html/821-1456/scf-10.html

B: Binary Signatures for Third-Party Software

The elfsign command provides a means to sign providers to be used with the Oracle Solaris

Cryptographic Framework. Typically, this command is run by the developer of a provider.

The elfsign command has subcommands to request a certificate from Sun and to sign binaries.

Another subcommand verifies the signature. Unsigned binaries cannot be used by the Oracle Solaris

Cryptographic Framework. To sign one or more providers requires the certificate from Sun and the

private key that was used to request the certificate.

C: Export law in the United States requires that the use of open cryptographic interfaces be

restricted. The Oracle Solaris Cryptographic Framework satisfies the current law by requiring that

kernel cryptographic providers and PKCS #11 cryptographic providers be signed.

Reference: System Administration Guide: Security Services, Oracle Solaris Cryptographic Framework