1z0-820 Upgrade to Oracle Solaris 11 System Administrator Questions and Answers

to temporarily bypass IP Filter rules

to specify an IPMP target IP address to in.mpathd

to specify routing to an adjacent network when in.rdisc is not used

to specify routing to an adjacent network when in.routed is not used

to ensure the IP address for serverB is not flushed from the ARP cache

to optimize link aggregation using a direct connection between two systems

zoneadm -C testzone

zoneadm -console testzone

zlogin -z testzone console C

zlogin -z testzone -C

zlogin -C testzone

F zoneadm -z testzone -C

terminal=xterms

name_service=NIS+

timezone=US/Pacific

system_locale=en_US

network_interface=PRIMARY

root_password=rJmv5LUXM10cU

There are boot environments for zones.

Administrators can delegate common administration tasks by using RBAC.

Oracle Solaris 11 supports Solaris 8, 9, and 10 branded zones.

You can migrate a physical Solaris 10 system and its non-global zones to a solaris10 branded zone running on an Oracle Solaris 11 system.

It is possible to change the host ID of a zone.

Use the pkg remove command with the -require-backup-be option

Use the beadm create command to create a new boot environment

Use the pkg remove command to remove the gzip package from the current boot environment.

Use the luucreate command to create a new boot environment.

Use the pkgrm command to remove the gzip package from the current boot environment

Use the pkg unmstall command with the -backup-be-name option

AJ: manifest files

JumpStart: begin script

Al:installadmcreate-client

JumpStart: setup_install_sen/er

Al SMF system configuration profile files JumpStart: profile files

Al: SMF system configuration profile files JumpStart: finish scripts and sysidcfg files

forwarding=on has not been configured for SystemA and SystemB.

forwarding=on has not been configured for the global zone of SystemA.

There are missing entries for SystemA and SystemB in /etc/inet/hosts.

forwarding=on has not been configured for zonel and zone2 of SystemA.

ARP table entries on SystemA and SystemB are incomplete for vnid and vnic2.

SystemB and SystemC require a static route to the 172.16.0.x network via 192.168.1.20.

an Al SC profile for non-global zones

the default Al config file for non-global zones

the default Al manifest for non-global zones

a custom Al manifest

Jumpstart

LiveCD

A text Installation over the network

An Automated Installation performed on an x86 client

An Automated Installation using media from a local DVD or USB drive

An Automated Installation using a networked repository

ISO images for use with the Automated Installer (AI) can be created.

Bootable USB images can be created for SPARC and x86 architectures.

A single installation server can be used to create ISO images for SPARC and x86 architectures.

Checkpoints can be used to pause the build, allowing scripts to run that modify the resulting ISO Image.

A single Installation server can be used to create ISO images for Solaris 10 and Solaris11 operating systems.

pktool genkey keystone=file outkey=/mykey keytype=aes keylen=256

genkey pktool keystore=file outkey=/mykey keytype=aes keylen=256

zfs create -o encryption=aes-256-ccm -o keysource=raw,file://mykey pooll/encrypt

zfs create -o encryption=aes-256-ccm -o keysource=raw,file:///mykey pooM/encrypt

zfs create -o encryption=aes-256-ccm -o keysource=raw,file:///mykey source=local pooll/encrypt

IP address of the Al server

passwords for user accounts

target disk slice for installation

NWAM active network configuration profile (NCP)

IP address of the IPS (Image Packaging System) repository

SI_MANIFEST_SCRIPT, which defines the URL of the manifest script

If the AI client does not match any criteria to use a custom manifest or script, the default manifest is used.

If the AI client does not match any criteria to use a custom manifest or script, the automated installation aborts.

Any manifest or script in a service can be designated to be the default for that service.

Only the default.xml file is used as the default AT client manifest.

If a client system does not use any SC profile, then an interactive tool opens on that client at first boot after that client installation to complete the configuration of that client.

If a client system does not use any SC profile, then the install server will use the default SC profile.

sent, prior to VLAN tag modifications

received, after VLAN tag modifications

received, prior to VLAN tag modifications

sent and received, after VLAN tag modifications

zonecfg -z s 10-zone create-tSYSsolarislO

zonecfg -z s 10-zone

create setbrand=solaris10

zonecfg -z solarisl 0 -t SYSsolarislO

zonecfg -z s10-zone install -f/net/backup_setver/s1O-system.flar

NWAM is disabled.

NWAM is automatically configuring the network.

The wireless network card is manually configured and operational.

The wireless network card is manually configured but not operational.

The wireless network card is automatically configured and operational.

The wireless network card is automatically configured but not operational.