Which of the following descriptions about virtualized storage Thick LUN usage scenarios is wrong?

Question

Options

• AScenarios where storage space utilization is less sensitive
• BScenarios with low cost requirements
• CTrades with high performance requirements
• DScenarios where it is difficult to estimate storage space in practical applications

• A
  3% (1)
• B
  3% (1)
• C
  13% (4)
• D
  80% (24)

Explanation

Option D is the correct answer because Thick LUN is the wrong choice when storage needs are hard to estimate. Thick provisioning pre-allocates the full declared storage capacity upfront, meaning you must know your space requirements in advance - if estimation is difficult, Thin LUN (which allocates dynamically as data is written) is the appropriate solution.

Why the other options are valid Thick LUN scenarios (and therefore wrong answers):

• A is a legitimate use case: since Thick LUN reserves space regardless of actual usage, it's well-suited to environments that aren't trying to maximize storage efficiency.
• B is valid in context: Thick LUN's predictable, pre-allocated model can simplify cost planning, making it acceptable where budget flexibility exists.
• C is arguably the strongest use case: because space is pre-allocated, there's no dynamic allocation overhead at write time, giving Thick LUN a performance edge over Thin LUN in I/O-intensive workloads.

Memory tip: Think of it this way - "Thick = committed upfront." Just like paying in full before using a service, Thick LUN locks in your space immediately. If you don't know how much you'll need, you can't commit upfront - that's Thin LUN territory.

No community discussion yet for this question.