Identify three options that describe the new Oracle Solaris 11 zone features.

Question

Options

• AThere are boot environments for zones.
• BAdministrators can delegate common administration tasks by using RBAC.
• COracle Solaris 11 supports Solaris 8, 9, and 10 branded zones.
• DYou can migrate a physical Solaris 10 system and its non-global zones to a solaris10 branded zone
• EIt is possible to change the host ID of a zone.

• A
  95% (60)
• C
  3% (2)
• E
  2% (1)

Explanation

A is correct because Oracle Solaris 11 introduced boot environments (BEs) for non-global zones, mirroring the global zone's ability to snapshot and roll back the OS state - a significant new capability for zone lifecycle management.

B is correct because Solaris 11 enhanced RBAC delegation, allowing administrators to grant granular zone administration rights (create, boot, halt, etc.) to non-root users without granting full superuser access.

D is correct because Solaris 11 introduced the solaris10 branded zone as a Physical-to-Virtual (P2V) migration path, enabling a Solaris 10 physical system - including its non-global zones - to be encapsulated and run inside a Solaris 11 global zone.

C is wrong because Solaris 8 and 9 branded zones were a Solaris 10 feature and are not carried forward into Solaris 11. Only the solaris10 branded zone is supported in S11.

E is wrong because non-global zones inherit the global zone's host ID; there is no supported mechanism to independently change a zone's host ID.

Memory tip: Think "A, B, D = Always Boot, Delegate, and Deploy (migrate)" - the three big zone management wins in Solaris 11. The wrong answers both involve things Solaris 11 removed or never had (S8/S9 zones, independent hostid).

No community discussion yet for this question.