How should you permanently restrict the non-global zone testzone so that it does not use more than 20 CPU shares while it is running?

Question

Options

• AWhile configuring the zone, add this entry:
• BWhile configuring the zone, add this entry:
• CFrom the command line enter:
• DFrom the command line, enter:

• A
  9% (4)
• B
  70% (33)
• C
  4% (2)
• D
  17% (8)

Explanation

Option B is correct because permanently restricting CPU shares requires using zonecfg to set cpu-shares=20 directly as a zone property (e.g., set cpu-shares=20 within the zonecfg interactive session), which persists across reboots and zone restarts. Option A is wrong because it likely shows an incorrect zonecfg syntax - perhaps using an rctl block entry instead of the simpler direct set cpu-shares=20 property, which is the proper method for this resource. Options C and D are wrong because command-line approaches (typically prctl) only apply temporarily for the current running session - they are lost when the zone halts or reboots, failing the "permanently" requirement in the question.

Memory tip: Think "P for Permanent = zonecfg" - any time an exam question says "permanently," the answer involves zonecfg, not runtime commands like prctl. The zonecfg tool writes to the zone's persistent configuration store, while command-line tools modify only live kernel state.

No community discussion yet for this question.