View the Exhibit to inspect the boot environment Information displayed within a non global zone on your system. Which two options describe the solaris-1 boot environment?

Question

Exhibit

Options

• AThe solaris-1 boot environment is not bootable.
• BThe solaris-1 boot environment is incomplete.
• CThe solaris-1 boot environment was created automatically when the non global zone was created.
• DThe solaris-1 boot environment was created in the non-global zone using the beadm create command.
• EThe solaris-1 boot environment is associated with a non active global zone boot environment.

• A
  63% (19)
• B
  3% (1)
• C
  10% (3)
• D
  23% (7)

Explanation

Options A and E are correct because in Oracle Solaris, non-global zone (NGZ) boot environments are automatically created as paired counterparts whenever the global zone administrator runs beadm create - so solaris-1 in the NGZ exists because a solaris-1 BE was created in the global zone (E). Since that global zone BE is not currently active, its NGZ counterpart is also non-bootable; a NGZ cannot independently boot into a BE whose parent global zone BE is inactive (A).

B is wrong because "incomplete" is a distinct, explicit status flag shown in beadm list output when a BE creation was interrupted mid-process - the exhibit shows no such flag for solaris-1.

C is wrong because the original solaris BE (not solaris-1) was created automatically when the zone was provisioned; solaris-1 was created later as a result of a global zone beadm create operation.

D is wrong because if a NGZ administrator had run beadm create solaris-1 locally inside the zone, the resulting BE would be zone-local and not associated with any global zone BE - but the exhibit links it to a global zone BE, revealing its true origin.

Memory tip: Think of NGZ BEs as shadows - for every BE created in the global zone, a shadow BE appears in each NGZ. A shadow whose GZ parent is inactive = not bootable (A) + tied to a non-active GZ BE (E).

No community discussion yet for this question.