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…

Question

Options

• AUse zonecfg to change the zonename before booting the system for the first time
• BUse the - u option with the zoneadm - z zone10 attach command.
• CUse the -u option with the zoneadn -z zone10 install command.
• DRemove the sysidcfg file from the <zonepath>/root directory before booting the non-global zone.

• A
  2% (1)
• B
  12% (5)
• C
  81% (34)
• D
  5% (2)

Explanation

Using the -u (unconfigure) flag with zoneadm -z zone10 install strips the imported flash archive of its original system identity - hostname, naming service config, etc. - so that sysidtool runs on first boot and prompts for new values. This is the correct mechanism when installing a Solaris 10 branded zone from a flash archive (-a archive.flar -u), because the archived system (sysA with LDAP) would otherwise silently retain its old identity inside the new zone.

Why the distractors are wrong:

• A - zonecfg changes the zone's container name in the global zone, not the internal OS identity; the zone still boots with sysA's hostname and LDAP config untouched.
• B - zoneadm attach is for re-attaching a previously detached zone (moving between servers); the zone here is incomplete and needs install, not attach.
• D - Removing sysidcfg is a valid trick for native Solaris zones, but the proper, supported method for branded zones installed from a flash archive is the -u flag at install time; relying on file removal is fragile and not the exam-expected path.

Memory tip: Think of -u as "un-identity" - it wipes who the zone thinks it is so it must introduce itself on first boot.

No community discussion yet for this question.