Question 90
Original unofficial HPE0-J83 storage practice case R183-CASE-023 — Enterprise wants SAN boot for clustered hosts. Observed evidence: Boot LUN is masked to every host, creating conflicting boot identities. After the scoped corrective action, which observation most directly demonstrates that this issue is resolved?
Explanation
Correct Answer
The acceptance result Each node boots from only its assigned LUN after a path failover directly tests recovery for this situation: Boot-from-SAN presentation lacks unique per-host mapping and ordering. The prior signal was: Boot LUN is masked to every host, creating conflicting boot identities. The planned intervention was: Map each boot volume to its intended host and verify supported firmware boot order. This targeted evidence is more useful than merely reporting that an array is online.
Incorrect Answers
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Raw media capacity omits parity, metadata, and reserve overhead, signaled by: The capacity estimate uses raw drive labels rather than post-protection usable capacity. The current symptom is: Boot LUN is masked to every host, creating conflicting boot identities. Verify this incident by checking: Each node boots from only its assigned LUN after a path failover.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Redundancy during failure and resilver or reconstruction exposure are misunderstood, signaled by: Operations assumes parity RAID has no degraded rebuild window. The current symptom is: Boot LUN is masked to every host, creating conflicting boot identities. Verify this incident by checking: Each node boots from only its assigned LUN after a path failover.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Metadata access pattern and small-I/O behavior were omitted from performance sizing, signaled by: The cache plan considers only sequential throughput while directory lookups stall. The current symptom is: Boot LUN is masked to every host, creating conflicting boot identities. Verify this incident by checking: Each node boots from only its assigned LUN after a path failover.