NS0-157 · Question #415
You create a 150 GB thick-provisioned volume. In that volume, you create a 50 GB LUN with space-reserve enabled. You create another 50 GB LUN with space-reserve disabled. Before any data is written to
The correct answer is B. 100 GB. A space-reserve enabled LUN on a thick-provisioned volume immediately allocates its full size, while a space-reserve disabled LUN reserves no space until data is written.
Question
You create a 150 GB thick-provisioned volume. In that volume, you create a 50 GB LUN with space-reserve enabled. You create another 50 GB LUN with space-reserve disabled. Before any data is written to either LUN or a Snapshot is taken, how much space will be available in the volume for additional LUNs?
Options
- A150 GB
- B100 GB
- C75 GB
- D50 GB
How the community answered
(25 responses)- A12% (3)
- B64% (16)
- C4% (1)
- D20% (5)
Why each option
A space-reserve enabled LUN on a thick-provisioned volume immediately allocates its full size, while a space-reserve disabled LUN reserves no space until data is written.
150 GB would only remain available if neither LUN reserved any space, but the space-reserve enabled LUN immediately claims its full 50 GB allocation upon creation.
With a 150 GB thick-provisioned volume, the 50 GB space-reserve enabled LUN immediately claims 50 GB of volume space at creation. The 50 GB space-reserve disabled LUN has no data written and no snapshot exists, so it occupies 0 GB. This leaves exactly 100 GB available for additional LUNs.
75 GB is incorrect because the space-reserve disabled LUN does not consume any volume space before data is written or a snapshot is taken, so only 50 GB is consumed - not 75 GB.
50 GB would be the remaining space only if both LUNs reserved their full 50 GB upfront, but space-reserve disabled means no space is pre-allocated for that LUN.
Concept tested: ONTAP LUN space reservation on thick-provisioned volumes
Source: https://docs.netapp.com/us-en/ontap/san-admin/space-reservation-concept.html
Topics
Community Discussion
No community discussion yet for this question.