You create a flash archive of the Solaris 10 global zone on the serves named sysA. The archive name is s10-system.flar, and it is stored on a remote server named backup_server. On sysA, you create a…

Question

Options

• Azoneadm -z s10 -zone install - a /net/backup_server/s10-system.flar -u
• Bzonecfg -z s10 -zone install - a /net/backup_server/s10-system.flar -u
• Czoneadm - z s10 -zone clone - s /net/backup_server/s10-system.flar
• Dzone cfg - a s10-zone create - t SUNWsolaris10\
• Ezonecfg -z s10-zone install -f /net/backup/backup_server/s10-system.flar

• A
  83% (33)
• B
  10% (4)
• C
  3% (1)
• D
  5% (2)

Explanation

zoneadm is the correct command for zone administration tasks like installation - option A uses zoneadm -z s10-zone install -a <archive> -u, where -a specifies the flash archive source and -u unconfigures the archive (strips host-specific identity so the new zone gets its own), which is exactly what's needed when installing from a global zone's flash archive into a branded zone.

Why the distractors fail:

• B and E use zonecfg, which handles zone configuration (creating/modifying zone definitions), not zone installation - it has no install subcommand for deploying an OS.
• C uses clone, which copies from an already-installed zone, not from a .flar file; the -s flag is also incorrect syntax for this operation.
• D is a zonecfg create command used to define a new zone's brand type (SUNWsolaris10), a step that happens before installation, not during it.

Memory tip: Split the two commands by their first syllable - zoneadm does actions (install, boot, halt, clone), while zonecfg does configuration (create, set, add properties). When you see "install from archive," reach for zoneadm with -a (archive) and -u (unconfigure).

No community discussion yet for this question.