2V0-21.20 · Question #139
Why is it necessary to select the policy structure type before creating a storage policy?
The correct answer is C. defines rule categories available for storage policy use. The storage policy structure type must be selected first because it determines which rule categories and capabilities are available when defining the policy's placement rules.
Question
Why is it necessary to select the policy structure type before creating a storage policy?
Options
- Adefines if the storage policy is thick or thin provisioned
- Bdefines the VM virtual hardware version
- Cdefines rule categories available for storage policy use
- Ddefines if SIOC will be used
How the community answered
(43 responses)- A2% (1)
- B5% (2)
- C93% (40)
Why each option
The storage policy structure type must be selected first because it determines which rule categories and capabilities are available when defining the policy's placement rules.
Thick or thin provisioning is a disk format setting configured at VM or datastore level and is not determined by the storage policy structure type.
VM virtual hardware version is a compatibility setting tied to the ESXi host version and is completely unrelated to storage policy configuration.
The policy structure type - such as tag-based placement, datastore-specific rules, or vSAN rules - controls which rule categories appear in the policy editor. For example, selecting a vSAN structure type exposes vSAN-specific capabilities like failures to tolerate and stripe width, while a tag-based type exposes tag categories. Without selecting the structure type first, the appropriate rule categories cannot be surfaced for configuration.
Storage I/O Control (SIOC) is a datastore-level feature configured separately in vCenter and is not what the storage policy structure type controls.
Concept tested: VM storage policy structure type and rule categories
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-521A39EA-E9D2-4E59-8003-4D8A84DC9963.html
Topics
Community Discussion
No community discussion yet for this question.