HPE6-A88 practice question 3 of 10

A network engineer is troubleshooting an issue where a factory default Aruba Network device is not redirecting DNS requests correctly. The device is supposed to intercept requests for 'securelogin.hpe.com' but is failing to do so. What is a likely cause of this issue?

Full set: 111 questions

Answer options

A: The device's IP address is not correctly configured in the ClearPass Guest settings.

B: The common name in the HTTPS certificate does not match 'securelogin.hpe.com'. Correct answer

C: The Page Name for the web login page is missing from the URL.

Correct Answer:

B. The common name in the HTTPS certificate does not match 'securelogin.hpe.com'.

Explanation

Factory-default ArubaOS/Instant devices ship with an HTTPS certificate whose Common Name is “securelogin.arubanetworks.com”. If the system is configured (or upgraded image expects) to intercept traffic to “securelogin.hpe.com”, the hostname in the URL no longer matches the certificate’s CN. Browsers therefore reject the TLS session and the controller never receives the HTTP request, appearing as if DNS interception failed.

Why Incorrect

A. ClearPass IP settings are unrelated to the built-in HTTPS server used for DNS intercept.
C. The Page Name affects the redirect URI after TLS is established; the mismatch happens before that stage.

References

1. Aruba Instant 8.8.0.0 User Guide, §24.4 “Default Factory Certificate”, p. 227 – CN = securelogin.arubanetworks.com.

2. ArubaOS 10.3 Release Notes, “Change in captive-portal FQDN to securelogin.hpe.com”, p. 19 – must replace certificate or hostname to match.

3. RFC 2818 “HTTP over TLS”, §3.1 – host name must match certificate CN/SAN.

Keep practicing

Take the free HPE6-A88 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test