A zone won't boot. Identify the five causes.

Question

Options

• AThe zone is configured to have its own CPUs, and there aren't enough.
• BThe zone is configured to have exclusive access to an NIC, and the NIC is already up.
• CThe zone is configured to mount a file system, which is already mounted.
• DThe zone is currently running or shutting down.
• EThe zone has been uninstalled.
• FYour terminal session is missing the SYS_TIME privilege.

• A
  77% (46)
• F
  23% (14)

Explanation

A: dedicated-cpu Resource The dedicated-cpu resource specifies that a subset of the system's processors should be dedicated to a non-global zone while it is running. When the zone boots, the system will dynamically create a temporary pool for use while the zone is running. C: s the global administrator in the global zone, you can import raw and block devices into a non- global zone. After the devices are imported, the zone administrator has access to the disk. The zone administrator can then create a new file system on the disk and perform one of the following Mount the file system manually Place the file system in /etc/vfstab so that it will be mounted on zone boot D, E: Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state. Not F: Sys_time not related to booting a zone.

No community discussion yet for this question.