VCP-DCV Configure and Manage vSphere Storage Practice Question
Network Topology
Refer to the exhibit. An administrator configures a claim rule to use VMW_SATP_ALUA with VMW_PSP_RR and TPGS enabled. After applying the rule, the device shows one active and one standby path. However, the administrator notices that I/O is only sent to the active path. What is the most likely reason?
⚠ Common exam trap
VCP-DCV often tests the misconception that VMW_PSP_RR always load-balances across all visible paths; in reality, with ALUA and TPGS, RR only uses paths the array marks Active/Optimized, so array-side TPG configuration is the deciding factor.
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
✓
The array is not properly configured to present both paths as active/optimized.
VMW_PSP_RR (Round Robin) with TPGS (Target Port Group Support) enabled only distributes I/O across paths that the array reports as Active/Optimized. If the array presents one path as Active/Optimized and the other as Standby, RR will still send I/O only to the optimized path because ALUA state dictates path usage. The array's target port group configuration must mark both paths as Active/Optimized for RR to load-balance across them.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The PSP should be changed to VMW_PSP_MRU to use both paths.
Why it's wrong here
Round Robin with ALUA and TPGS already balances I/O across active/optimised paths; MRU sends I/O down one path until failover, so it cannot activate a standby path. MRU suits active-passive arrays lacking ALUA support, where only one controller owns the LUN at a time.
- ✓
The array is not properly configured to present both paths as active/optimized.
Why this is correct
Round robin only distributes I/O across paths the array reports as active/optimised. If the array presents one path as standby rather than both active/optimised, the PSP sends I/O solely to the active path, matching the observed behaviour.
- ✗
The claim rule should have used VMW_SATP_DEFAULT_AA instead.
Why it's wrong here
DEFAULT_AA treats all paths as active regardless of array target port state, so it cannot explain a standby path receiving no I/O. It suits legacy active-active arrays that expose no ALUA target port groups, where the array itself handles path selection without host-side state awareness.
- ✗
The TPGS option should be disabled to force both paths active.
Why it's wrong here
Disabling TPGS removes the host's ability to read target port group states, which would not make a standby path active; the array still reports it as standby. TPGS is correctly enabled for ALUA arrays, and disabling it suits arrays that do not expose target port group information.
Go deeper
Related to this question
About these practice questions
This VCP-DCV question is part of Courseiva's 281-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.