2V0-622D · Question #43
An administrator wants to ensure that all datastores defined on an ALUA-based storage array have load balancing enabled by default. The storage configuration is: - Storage Array Type =…
The correct answer is A. Change the Storage Array Type Policy to = VMW_SATP_ALUA and the Path Selection Policy =. ALUA storage arrays expose active-optimized and active-non-optimized target port groups that require an ALUA-aware SATP for correct path state handling, and a Round Robin PSP for load balancing. Both components must be changed together to satisfy the stated requirements.
Question
An administrator wants to ensure that all datastores defined on an ALUA-based storage array have load balancing enabled by default. The storage configuration is:
- Storage Array Type = VMW_SATP_DEFAULT_AA
- Path Selection Policy = VMW_PSP_FIXED
Which configuration would support the stated requirements?
Options
- AChange the Storage Array Type Policy to = VMW_SATP_ALUA and the Path Selection Policy =
- BChange the Path Selection Policy = VMW_PSP_RR and leave the Storage Array Type Policy as
- CChange the Storage Array Type Policy to = VMW_SATP_ALUA and leave the Path Selection
- DChange the Path Selection Policy = NMP and leave the Storage Array Type Policy as is.
How the community answered
(20 responses)- A45% (9)
- B15% (3)
- C30% (6)
- D10% (2)
Why each option
ALUA storage arrays expose active-optimized and active-non-optimized target port groups that require an ALUA-aware SATP for correct path state handling, and a Round Robin PSP for load balancing. Both components must be changed together to satisfy the stated requirements.
VMW_SATP_ALUA is the only SATP plugin that understands ALUA target port group state transitions - it correctly identifies active-optimized paths and avoids routing I/O through active-non-optimized paths under normal conditions. Pairing it with VMW_PSP_RR enables round-robin load distribution across the optimized paths, satisfying both ALUA compatibility and the load balancing requirement in a single configuration change.
Changing only the PSP to VMW_PSP_RR while retaining VMW_SATP_DEFAULT_AA does not provide ALUA support - DEFAULT_AA does not parse ALUA target port group attributes, so it cannot distinguish optimized from non-optimized paths and may route I/O suboptimally.
Changing the SATP to VMW_SATP_ALUA while leaving the PSP as VMW_PSP_FIXED does not enable load balancing - FIXED routes all I/O through a single preferred path and uses other paths only for failover, not for distributing load.
NMP (Native Multipathing Plugin) is the top-level multipathing framework that hosts all SATPs and PSPs - it is not itself a valid Path Selection Policy value, and specifying it as a PSP is an unsupported configuration that would not enable load balancing.
Concept tested: ALUA array SATP and PSP selection for load balancing
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.storage.doc/GUID-EF2DF7C7-8AB0-44A2-BE03-39E1E7690A3D.html
Topics
Community Discussion
No community discussion yet for this question.