Huawei RAID 2.0+ Extent Properties in Storage Pools
Short answer
ABCD In Huawei RAID 2.0+, an extent is the per-pool configurable allocation unit that belongs exclusively to one LUN and is the minimum space a thick LUN requests, so all four statements hold.
Question
Key Takeaways
The question tests the extent’s role as the exclusive pool-level allocation unit, and the main trap is treating the 64 MB default as an immutable size or confusing extents with chunks.
Huawei RAID 2.0+ extents are the storage pool’s allocation units, and this page confirms that exclusive LUN ownership, configurable pool-level size, thick-LUN granularity, and per-pool size differences are all correct.
Common mistake: A common wrong selection is AB, assuming extent size is fixed and thick-LUN allocation uses a smaller unit; however, extent size is set per storage pool, so D also follows, and a thick LUN’s capacity is allocated in whole extents, making C correct.
Expert Analysis
Reading the selection rule. The stem asks which statements “about extents in Huawei RAID 2.0+” are correct and explicitly says “Choose all that apply,” so there is no fixed count and no EXCEPT-style inversion. Each option must stand or fall on the extent’s role in a RAID 2.0+ storage pool, not on the more familiar chunk or RAID stripe.
Exclusive ownership (A). A storage pool is divided into extents, and LUNs are provisioned from those extents. Once an extent is assigned to a volume/LUN, it is not shared with another LUN; it stays with that logical space until released or relocated. The community note makes the same point: an extent allocated to a LUN belongs exclusively to that LUN. A is correct.
Pool-level size (B and D). Extent size is a property chosen when the storage pool is created; 64 MB is a common default, not the only possible value. Because the setting is made per pool, one pool can use a different extent size than another, so D follows from B. The wording “can be set” and “vary” does not require every pool to differ—it only permits the difference. B and D are correct.
Thick-LUN granularity (C). A thick LUN reserves its full capacity at creation, but the storage pool satisfies that reservation in whole extents. The extent is therefore the minimum unit of space that a thick LUN applies for from the pool. C is correct.
Verdict. No option introduces a foreign concept such as a chunk being the allocation unit or extent size being immutable. All four statements are consistent with RAID 2.0+ extent behaviour: A, B, C, and D.
Exam Strategy
For Huawei multi-select items, do not stop at the first two familiar statements. Define the term’s layer—extent for pool allocation, chunk or stripe for RAID—and test each option against that layer. Treat defaults such as 64 MB as defaults, not fixed constraints, unless the wording says “cannot be changed.”
Frequently Asked Questions
Can one extent in Huawei RAID 2.0+ be shared by multiple LUNs?
Is the Huawei RAID 2.0+ extent size always 64 MB?
What is the minimum allocation unit for a thick LUN from a Huawei storage pool?
Community Votes
50% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
10c5cfe 👍 1A should also be selected as : While an extent (typically 64 MB by default) is carved out of a CKG (Chunk Group), once it is allocated to a specific LUN, it belongs exclusively to that LUN's logical space until it is released or relocated.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.