Free 1Z0-820 Practice Test

To update the OS image from a new publisher repository, you must change the origin URI of the existing publisher using the pkg set-publisher command. By specifying the new URL for the 'solaris' publisher (e.g., using the -G and -g flags to remove the old URI and add the new one), the system will correctly pull packages from the updated repository when the pkg update command is subsequently executed.

A. Copying the repository locally and using svccfg is unnecessary and overly complex for simply changing a publisher's origin URI.
B. The svccfg command is used for SMF service configuration, not for directly managing IPS publisher URIs on a client system.
D. Adding a new publisher and setting search orders is not required or best practice when you can simply update the URI of the existing 'solaris' publisher.

1. Oracle Corporation. (2012). Adding and Updating Software in Oracle Solaris 11.1. Part No: E28042. Chapter 3: "Configuring Publishers".

2. Oracle Corporation. (2012). Oracle Solaris 11.1 Information Library. Part No: E28030. Section: "pkg(1) Man Page".

The zonecfg command uses the -f option to specify a command file containing configuration instructions. Running zonecfg -z testzone2 -f testzone.cfg reads the exported configuration from testzone.cfg and applies it to create or configure the new zone named testzone2. This is the officially documented method for non-interactive zone configuration using an exported configuration file.

A: While shell redirection (<) might pass input to interactive commands, -f is the officially supported and documented flag for zonecfg to process a file. B: The import subcommand is not a valid zonecfg subcommand for reading a configuration file in this manner. C: The zoneadm clone command is used to clone an installed zone's file system, not to apply a zonecfg configuration file.

1. Oracle Solaris 11.3 Information Library, "System Administration: Oracle Solaris Zones", Section: "How to Configure the Zone".

2. Oracle Solaris 11.3 zonecfg(1M) man page, Options section detailing the -f flag.

Setting up an Automated Installer (AI) server in Oracle Solaris 11 requires several prerequisite tasks. The server must have a static IP address configured (B). A DHCP server must be available on the network to provide IP addresses and boot parameters to clients, though it does not need to reside on the AI server itself (D). You must install the AI tools via the installadm package (G) and download the appropriate AI boot image (ISO) (E). Finally, you must create the AI install service using installadm create-service, which unpacks the ISO to a specified directory (H).

- Option A: A local IPS repository is not mandatory; clients can install packages directly from the remote Oracle repository (pkg.oracle.com) if they have internet access.
- Option C: The DHCP server is required on the network but does not strictly need to be enabled on the AI install server itself.
- Option F: The text install image is used for interactive manual installations, not for setting up an AI server or IPS repository.
- Option I: The installadm create-service command does not specify the path to the IPS repository; the repository location is defined within the AI manifest XML file.

- Oracle Solaris 11.1 Installing Oracle Solaris 11.1 Systems, Chapter 8: Setting Up an Install Server, Section: "Requirements for an AI Install Server".

- Oracle Solaris 11 Documentation: installadm(1M) man page.

Oracle Solaris 11 introduced several major ZFS enhancements not present in the original baseline of Oracle Solaris 10. These include native ZFS dataset encryption for secure data at rest, ZFS deduplication to detect and remove redundant data blocks synchronously, and Shadow Migration for seamless background data migration from legacy file systems to local ZFS datasets. While some features (like deduplication) were later backported to late Solaris 10 updates, these three are officially classified as key Solaris 11 ZFS architectural advantages in upgrade scenarios.

D. The ability to split a mirrored ZFS storage pool (zpool split) was introduced earlier and is available in Oracle Solaris 10 9/10 (Update 9).
E. Booting from a ZFS root file system was introduced in Oracle Solaris 10 10/08 (Update 6), so it is not exclusive to Solaris 11.
F. Solaris 11 does not eliminate the swap file system; it utilizes ZFS volumes (zvol) to provide swap and dump devices.

1. Oracle Solaris 11.1 Administration: ZFS File Systems, Chapter 1: "Oracle Solaris ZFS File System (Introduction)", Section: "What's New in ZFS?".

2. Oracle Solaris 11 Feature FAQ, Section: "Data Management - ZFS Enhancements".

To connect to the console of a non-global zone before or during boot, Oracle Solaris uses the zlogin command with the -C option followed by the zone name. Therefore, the correct command is zlogin -C testzone. The zoneadm command administers zone state, such as install, boot, halt, and verify, but it does not provide console login access.

A. zoneadm has no -C option for console access.
B. zoneadm -console is not valid Solaris zone syntax.
C. zlogin does not use -z; console is not a trailing subcommand here.
D. Invalid syntax; zlogin uses -C zonename, not -z.
F. Invalid zoneadm syntax and wrong command for console login.

- Oracle Solaris zlogin(8) man page, Options: -C connects to the zone console.

- Oracle Solaris Zones Administration Guide, “How to Log In to the Zone Console,” command format zlogin -C zonename.

- Oracle Solaris zoneadm(8) man page, Subcommands: zone lifecycle administration, not console login.

An etherstub is a pseudo-ethernet Network Interface Card (NIC) configured at the data link layer (L2) in Oracle Solaris 11. It acts as a virtual switch that is completely isolated from the physical network interfaces of the system. By creating an etherstub and configuring Virtual Network Interfaces (VNICs) over it for specific local zones, administrators can establish a dedicated, isolated virtual network for inter-zone communication. This ensures that the network traffic between these zones is not exposed to the external network or to other zones on the system.

Incorrect B: Solaris does not use a "virtual router" construct for L2 isolation between zones; routing implies Layer 3 operations, not isolated Layer 2 switching. Incorrect C: While an etherstub functions conceptually like a virtual switch, the specific Solaris administrative object created via dladm create-etherstub is explicitly called an etherstub. Incorrect D: A virtual bridge connects multiple links together but does not inherently create an isolated internal-only network like an etherstub does. Incorrect E: A VNIC connects a zone to a network, but without an etherstub, it would connect to a physical link, lacking the required isolation. Incorrect F: Virtual switches are created implicitly over physical links, but for completely isolated traffic, an etherstub must be explicitly created by the administrator.

1. Oracle Corporation. (2012). Oracle Solaris 11.1 Administration: Network Interfaces and Network Virtualization. Part No: E28989-02. Chapter 3: Network Virtualization and Virtual Networks, Section: "Components of Network Virtualization".

2. Oracle Corporation. (2012). dladm(1M) man page, Oracle Solaris 11.1 Reference Manual.

In Oracle Solaris 11, ZFS shares are managed via ZFS properties rather than legacy configuration files. According to Oracle documentation, renaming a share created with the zfs set share command is not supported; the share must be removed and recreated with the new name. Additionally, a standard NFS restriction dictates that a directory cannot be shared if a subdirectory below it is already shared within the same file system, as this creates overlapping export paths that the NFS server cannot resolve properly.

A: The /etc/dfs/dfstab file is obsolete in Solaris 11. Shares are now managed persistently by SMF services and ZFS dataset properties. D: ZFS fully supports sharing a single dataset simultaneously using both NFS and SMB protocols by setting both sharenfs and sharesmb properties.

- Oracle Solaris 11.1 Administration: ZFS File Systems (Part No: E22481). Chapter 5: Managing Oracle Solaris ZFS File Systems, Section: "Sharing ZFS File Systems".

- Oracle Solaris 11 share(1M) man page.

To perform an incremental ZFS backup of data modified since the Sunday full backup, you must use the zfs send -i command. The correct syntax requires specifying the initial snapshot (Sunday) followed by the latest snapshot (Wednesday). Option A correctly creates the Wednesday snapshot and sends the incremental stream (zfs send -i pool1/data@sunday pool1/data@wednesday) directly to the tape device at /dev/rmt/0.

B: The syntax zfs snapshot -i is invalid; the -i flag is an option for the zfs send command, not for creating snapshots. C: The order of the snapshots in the zfs send -i command is reversed. The older snapshot must precede the newer snapshot. D: The zfs send -i command is missing the first (older) snapshot argument, which is required to calculate the incremental difference. E: Piping the output to zfs recv is used for receiving a stream into a ZFS dataset, not for writing the raw backup stream to a tape device.

- Oracle Corporation. (2012). Oracle Solaris 11.1 Administration: ZFS File Systems (Part No: E28548). Section: "Sending and Receiving Complex ZFS Snapshot Streams".

- Oracle Corporation. (2012). Oracle Solaris 11.1 Administration: ZFS File Systems (Part No: E28548). Section: "Saving ZFS Data to Tape".

To set up a local IPS package repository from an ISO image in Oracle Solaris 11, you must first populate the repository file system by copying the files using rsync (Option A). Next, configure the application/pkg/server SMF service by setting the pkg/instroot property to the repository path (Option D - noting a slight typo in the option's dot notation, but it provides the correct absolute path /export/IPS). Since the repository is a static copy from an ISO, set the pkg/readonly property to true (Option E). After configuring the properties, refresh (Option G) and enable (Option I) the SMF service. Finally, rebuild the repository catalog using pkgrepo rebuild to ensure the search indexes are up to date (Option J).

- B: Changing permissions to 700 restricts access and is not a required or recommended step for an IPS repository server.
- C: The path export/IPS lacks the leading slash, making it a relative path which will fail to resolve correctly.
- F: Setting pkg/readonly to false is incorrect for a static repository copied directly from a release ISO, as it is not meant to receive direct package publications.
- H: pkgrep refresh is not a valid command

- Oracle, Copying and Creating Package Repositories in Oracle Solaris 11.2, “How to Copy a Repository From a File”: documents mounting/copying repository media with rsync and running pkgrepo rebuild -s.

- Oracle, Copying and Creating Package Repositories in Oracle Solaris 11.2, “Serving a Local Repository Using the Package Depot Server”: documents svccfg -s application/pkg/server setprop pkg/instroot=..., pkg/readonly=true, svcadm refresh, and svcadm enable.

- Oracle Solaris 11.4 Reference Manual, pkgrepo(1), “rebuild” subcommand: rebuilds repository catalog/search data.

- Oracle Solaris 11.4 Reference Manual, pkg.depotd(8), SMF properties pkg/instroot and pkg/readonly.

Oracle Solaris crash dumps can be saved in compressed vmdump.N format in /var/crash. To expand or extract the dump into the traditional two crash-dump files, unix.N and vmcore.N, Oracle documents using savecore -f vmdump.N. Therefore, savecore -f vmdump.0 is the correct command to display or make available the two component files from vmdump.0.

B. dumpadm configures crash-dump behavior; uncompressed is not the command to extract existing vmdump.0 files.
C. gunzip only decompresses gzip files; vmdump.0 is processed by savecore, not directly by gunzip.
D. dumpadm -z off changes future dump compression settings; it does not expand an existing compressed crash dump.

- Oracle, Managing System Crash Information in Oracle Solaris 11.4, “Examining Crash Dump Files”: describes vmdump.N, unix.N, and vmcore.N.

- Oracle, Managing System Crash Information in Oracle Solaris 11.4, “How to Manually Extract a Crash Dump”: documents savecore -f vmdump.N.

- Oracle Solaris 11.4 Reference Manual, savecore(8), option -f dumpfile: saves/extracts a crash dump from the named file.

- Oracle Solaris 11.4 Reference Manual, dumpadm(8): configures dump device/content/compression for future dumps.