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
  4% (1)
• B
  15% (4)
• C
  74% (20)
• D
  7% (2)

Explanation

Option C is correct because when installing a Solaris 10 branded zone from a flash archive, the -u flag on zoneadm install triggers an unconfigure operation - it strips the source system's identity (hostname, naming service config) from the archive so the zone prompts for new values on first boot, which is exactly what you need when re-deploying sysA's image with a new identity.

Option B is wrong because attach is used to reattach an already-installed zone directory to a zone configuration (typically when moving zones between hosts), not for laying down a flash archive - it's the wrong subcommand for this workflow. Option A is wrong because changing the zonename in zonecfg only renames the zone administratively within the zone framework; it has no effect on the system identity (hostname, NIS/LDAP config) stored inside the zone's root filesystem. Option D is wrong because manually removing sysidcfg from the zone path does not reliably trigger the reconfiguration process in a Solaris 10 branded zone - the proper mechanism is the install-time -u flag, not manual file removal.

Memory tip: Associate -u with "un-brand" - you're taking a flash archive branded with sysA's identity and using -u at install time to wipe that identity clean, forcing the zone to introduce itself on first boot.

No community discussion yet for this question.