Question 490
Original unofficial HPE0-J83 storage practice case R183-CASE-123 — National retailer installs remote-array TLS. Observed evidence: Clients reject management certificate because SAN names do not include the configured FQDN. After the scoped corrective action, which observation most directly demonstrates that this issue is resolved?
Explanation
Correct Answer
The acceptance result Browser and API clients validate the hostname without bypassing TLS directly tests recovery for this situation: Certificate identity is inconsistent with management hostname. The prior signal was: Clients reject management certificate because SAN names do not include the configured FQDN. The planned intervention was: Install an appropriately trusted certificate covering the actual management FQDN. 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: Volume export identifies the wrong initiator, signaled by: Host HBA WWPN is entered with transposed digits. The current symptom is: Clients reject management certificate because SAN names do not include the configured FQDN. Verify this incident by checking: Browser and API clients validate the hostname without bypassing TLS.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Boot configuration has no tested resilient path selection, signaled by: Firmware boot target is the secondary HBA path that disappears during planned maintenance. The current symptom is: Clients reject management certificate because SAN names do not include the configured FQDN. Verify this incident by checking: Browser and API clients validate the hostname without bypassing TLS.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Provisioning order skips host connectivity prerequisites, signaled by: The automated deployment creates a volume before defining initiator groups and host policies. The current symptom is: Clients reject management certificate because SAN names do not include the configured FQDN. Verify this incident by checking: Browser and API clients validate the hostname without bypassing TLS.