Configure and Manage vSphere Storage →hardMultiple ChoiceObjective-mapped

VCP-DCV Configure and Manage vSphere Storage Practice Question

Exhibit

Refer to the exhibit.

VASA Storage Capability JSON from an array:

{
  "capabilities": [
    {
      "id": "capacityByThin",
      "description": "Thin provisioning",
      "properties": {
        "provisioningType": {
          "type": "string",
          "value": "thin"
        }
      }
    },
    {
      "id": "replication",
      "description": "Replication at storage container level",
      "properties": {
        "rpo": {
          "type": "integer",
          "value": 3600
        }
      }
    }
  ]
}

Refer to the exhibit. An administrator creates a storage policy with the rule: "Rule: provisioningType equals thick". When the policy is applied to a VM on this array, what will be the compliance status?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Not compliant - the array does not advertise thick provisioning capability.

The array only advertises thin provisioning and replication capabilities. The policy requires thick provisioning, which is not advertised. Therefore the VM will be marked as uncompliant because the array does not support the required capability. Option B is incorrect because it does not match; the array supports thin only. Option C is incorrect because VVols do not automatically default to thick. Option D is incorrect because the array does not provide thick.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Not compliant - the array does not advertise thick provisioning capability.
Why this is correct
Correct: The array does not have a thick provisioning capability, so the VM is uncompliant.
✗
Not compliant - the replication RPO is too high.
Why it's wrong here
Incorrect: The policy does not involve replication.
✗
Compliant - the storage policy is applied regardless of capabilities.
Why it's wrong here
Incorrect: The policy must match capabilities for compliance.
✗
Compliant - the array supports thin provisioning by default.
Why it's wrong here
Incorrect: The policy requires thick, not thin.

Go deeper

VCP-DCV Configure and Manage vSphere Storage Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question