You have Solaris 11 system with a host name of sysA and it uses LDAP as a naming service. You have created a flash archive of sysA and you want to migrate this system to an Oracle Solaris11 server, Solaris10 branded zone. The zone Status on the Oracle Solaris 11 server is: -zone10incomplete /zone/zone1 solaris10 exc1 Select the option that will force the non-global zone to prompt you for a host name and name service the first time it is booted. 

Answer options:

A. Use zonecfg to change the zonename before booting the system for the first time
B. Use the - u option with the zoneadm - z zone10 attach command.
C. Use the -u option with the zoneadn -z zone10 install command.
D. Remove the sysidcfg file from the <zonepath>/root directory before booting the non-global zone.

C

Oracle Solaris 10 branded zonesOracle Solaris 10 Zones provide an Oracle Solaris 10 environment on Oracle Solaris 11. You can migrate an Oracle Solaris 10 system or zone to a solaris10 zone on an Oracle Solaris 11 system in the following ways: * Create a zone archive and use the archive to create an s10zone on the Oracle Solaris 11 system. This option applies in the current scenario. Example of command to Install the Oracle Solaris 10 non-global zone. s11sysB# zoneadm -z s10zone install -u -a /pond/s10archive/s10.flar * Detach the zone from the Oracle Solaris 10 system and attach the zone on the Oracle Solaris 11 zone. The zone is halted and detached from its current host. The zonepath is moved to the target host, where it is attached. Note: install [-x nodataset] [brand-specific options] A subcommand of the zoneadm. Install the specified zone on the system. This subcommand automatically attempts to verify first. It refuses to install if the verify step fails. -u uuid-match Unique identifier for a zone, as assigned by libuuid(3LIB) . If this option is present and the argument is a non-empty string, then the zone matching the UUID is selected instead of the one named by the -z option, if such a zone is present. Incorrect answers: B: The attach subcommand takes a zone that has been detached from one system and attaches the zone onto a new system. Therefore, it is advised (though not required) that the detach subcommand should be run before the "attach" takes place. Once you have the new zone in the configured state, use the attach subcommand to set up the zone root instead of installing the zone as a new zone. Reference: Oracle Solaris 11 Information Library, Transitioning an Oracle Solaris 10 Instance to an Oracle Solaris 11 System