Detailed Explanation:
Rationale for Correct Answer:
Option B (All) is correct because in an Active Peer Persistence deployment where both arrays and hosts are in close proximity (metro or campus cluster scenario), the hosts should be configured with Host Proximity = All. This ensures that the host (ESX31) can access both arrays symmetrically and concurrently, enabling active-active paths. This is essential to deliver seamless failover and load balancing across the arrays in an HPE Alletra MP Peer Persistence environment.
Analysis of Incorrect Options (Distractors):
A (Secondary): This is used for hosts located closer to the secondary array, to bias access toward it in asymmetric deployments. Not applicable here since the hosts are near both arrays.
C (Exclusive): This option assigns the host to a single array exclusively, preventing dual-active access. This would defeat the purpose of symmetric Peer Persistence.
D (Primary): Similar to Secondary, this biases access to only the primary array, which is not correct when arrays and hosts are in the same site for active-active.
Key Concept:
This question focuses on Host Proximity parameters in HPE Peer Persistence.
Primary/Secondary = asymmetric designs (hosts closer to one array).
All = symmetric design (hosts equidistant to both arrays, enabling active-active).
Exclusive = restricts access to one array only.
[Reference:, HPE Alletra MP Storage Peer Persistence Best Practices Guide, HPE Primera/Alletra Remote Copy and Peer Persistence Technical White Paper, VMware Metro Storage Cluster with HPE Peer Persistence Implementation Notes, , , , ]
