VCP-DCV Configure and Manage vSphere Storage Practice Question
A vSphere administrator is planning a Storage DRS implementation for a datastore cluster containing multiple VMFS datastores. The VMs have various I/O patterns. Some VMs should always remain together on the same datastore. Which configuration should be used?
⚠ Common exam trap
VCP-DCV often tests the confusion between compute-level DRS rules (host affinity) and storage-level DRS rules (datastore affinity), causing candidates to select host-based options for a storage placement requirement.
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
✓
Create a VM-to-VM affinity rule in the datastore cluster.
Storage DRS supports VM-to-VM affinity rules within a datastore cluster, which ensure that specified VMs are always placed on the same datastore. This is the correct configuration when VMs must remain together, such as for application clusters that require shared storage locality or licensing constraints. The rule is enforced during initial placement and during Storage DRS migrations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a VM-to-VM affinity rule in the datastore cluster.
Why this is correct
VM-to-VM affinity rules keep specified virtual machines together on the same datastore within the datastore cluster. This satisfies the requirement that certain VMs must always remain co-located, which Storage DRS would otherwise separate during automated migrations.
- ✗
Set individual datastore affinity rules on each host.
Why it's wrong here
Host-level datastore affinity rules govern which hosts may access a datastore, not whether VMs stay co-located, so they cannot keep VMs together. They are tempting because they are affinity rules, and would be correct for restricting host-to-datastore access.
- ✗
Apply Storage I/O Control with high shares to the VMs.
Why it's wrong here
Storage I/O Control with high shares prioritises I/O bandwidth during contention; it does not constrain placement, so VMs can still be separated by Storage DRS. It is tempting for addressing varied I/O patterns, and would be correct when the goal is latency-sensitive bandwidth allocation.
- ✗
Create a VM-to-VM anti-affinity rule in the datastore cluster.
Why it's wrong here
VM-to-VM anti-affinity keeps specified VMs apart on separate datastores, the opposite of the stated requirement that they remain together. It is tempting because it is a VM-level Storage DRS rule, and would be correct when VMs must never share a datastore.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VCP-DCV question from scratch — 281 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official VMware exam blueprint
This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.