You are creating a non-global zone on your system. Which option assigns a zpool to a non-global zone, and gives the zone administrator permission to create zfs file system in that zpool?

Question

Options

• AWhile creating the non-global zone, make the following entry:
• BIn the global zone, create the zpool:
• CIn the global zone, create the zpool:
• DIn the global zone, create the zpool and the ZFS file systems that you want to use in the non- global zone:
• ECreate the zpool in the global zone:

• A
  3% (1)
• B
  3% (1)
• C
  85% (28)
• E
  9% (3)

Explanation

Option C is correct because it uses zonecfg's add dataset resource type to delegate the entire zpool to the non-global zone, which is the only method that both assigns the pool and grants the zone administrator privileges to create child ZFS file systems within it. This leverages ZFS's built-in delegation model, where assigning a pool-level dataset transfers administrative capabilities down to the zone.

Why the distractors fail:

• Option A (entry during zone creation) likely uses add fs, which creates a loopback/lofs mount - this shares a filesystem but does not grant the zone admin ZFS management permissions.
• Option B uses a global-zone-side configuration that probably mounts the storage without delegating ZFS administrative rights to the zone admin.
• Option D pre-creates the ZFS file systems in the global zone before assigning them - this gives the zone access to existing filesystems but explicitly takes away the zone admin's ability to create new ones.
• Option E creates the zpool but likely uses add fs or another method that stops short of full ZFS delegation.

Memory tip: Think "Dataset = Delegation" - add dataset in zonecfg is the magic phrase. If the question mentions a zone admin needing to create ZFS filesystems (not just use them), you need add dataset, not add fs.

No community discussion yet for this question.