Which three options are valid methods of installing a Solaris 10 branded zone on a system running Oracle Solaris 11?

Question

Options

• AUse the V2V process to migrate an existing Solaris 8 or 9 non-global zone from a Solaris 10 system
• BUse the V2V process to migrate an existing Solaris 10 non global whole root zone from a Solaris 10
• CInstall a solaris10 branded zone directly from the Oracle Solaris 10 media.
• DMigrate an existing 64-bit Solaris 10 system to a solaris10 branded non-global zone using the P2V process.
• EMigrate an existing 32 bit Solaris10 system to a solaris10 branded non-global zone using the P2V process.
• FUse the V2V process to migrate an existing Solaris 10 non-global sparse root zone from a Solaris 10

• A
  4% (2)
• B
  71% (37)
• C
  10% (5)
• F
  15% (8)

Explanation

B, D, and E represent the three supported pathways because Oracle's solaris10 branded zone accepts: V2V migration from Solaris 10 whole root non-global zones (B), and P2V migration from physical Solaris 10 systems in both 64-bit (D) and 32-bit (E) architectures - all of which produce a self-contained file system that the branded zone can host on Solaris 11.

Why the distractors fail:

• A is wrong because V2V is for Solaris 10 zones only; Solaris 8/9 zones use a different brand (s8/s9) and cannot be migrated into a solaris10 branded zone.
• C is wrong because there is no mechanism to install a solaris10 branded zone directly from Solaris 10 install media; you migrate from an existing system or zone.
• F is wrong because sparse root zones share file system loopback mounts from the global zone and lack a complete, independent root - the branded zone requires a whole root layout to function correctly on Solaris 11.

Memory tip: Think "Whole or Physical, never Sparse or Media." V2V only works with whole root zones (not sparse), P2V works with both bitnesses of physical machines, and there's no direct media install path.

No community discussion yet for this question.