A company with 465 employees wants to deploy an open WLAN for guests. The company wants the experience to be as follows: Guests select the WLAN and connect without having to enter a password. Guests are redirected to a welcome web page and log in. The company also wants to provide encryption for the network for devices that are capable. Which security options should you implement for the WLAN?
Correct Answer: D
The company wants to deploy an open WLAN for guests with the following requirements: Guests connect without entering a password (open authentication). Guests are redirected to a welcome web page and log in (captive portal). Encryption is provided for devices that support it. Open WLAN with Captive Portal: An open WLAN means no pre-shared key (PSK) or 802.1X authentication is required to connect. A captive portal can be used to redirect users to a web page where they must log in (e.g., with guest credentials). This meets the requirement for guests to connect without a password and then log in via a web page. Encryption for Capable Devices: The company wants to provide encryption for devices that support it, even on an open WLAN. Opportunistic Wireless Encryption (OWE) is a WPA3 feature designed for open networks. OWE provides encryption without requiring a password by negotiating unique encryption keys for each client using a Diffie-Hellman key exchange. OWE in transition mode allows both OWE-capable devices (which use encryption) and non-OWE devices (which connect without encryption) to join the same SSID, ensuring compatibility. Option A, "Opportunistic Wireless Encryption (OWE) and WPA3-Personal," is incorrect. WPA3-Personal requires a pre-shared key (password), which conflicts with the requirement for guests to connect without entering a password. Option B, "Captive portal and WPA3-Personal," is incorrect for the same reason. WPA3-Personal requires a password, which does not meet the open WLAN requirement. Option C, "WPA3-Personal and MAC-Auth," is incorrect. WPA3-Personal requires a password, and MAC authentication (MAC-Auth) does not provide the web-based login experience (captive portal) specified in the requirements. Option D, "Captive portal and Opportunistic Wireless Encryption (OWE) in transition mode," is correct. An open WLAN with OWE in transition mode allows guests to connect without a password, provides encryption for OWE-capable devices (e.g., WPA3 devices), and supports non-OWE devices without encryption. The captive portal ensures that guests are redirected to a welcome web page to log in, meeting all requirements. The HPE Aruba Networking AOS-8 8.11 User Guide states: "Opportunistic Wireless Encryption (OWE) is a WPA3 feature that provides encryption for open WLANs without requiring a password. In OWE transition mode, the WLAN supports both OWE-capable devices (which use encryption) and non-OWE devices (which connect without encryption) on the same SSID. This is ideal for guest networks where encryption is desired for capable devices, but compatibility with all devices is required. A captive portal can be configured on an open WLAN to redirect users to a login page, such as captive-portal guest-login, ensuring a seamless guest experience." (Page 290, OWE and Captive Portal Section) Additionally, the HPE Aruba Networking Wireless Security Guide notes: "OWE in transition mode is recommended for open guest WLANs where encryption is desired for devices that support it. Combined with a captive portal, this setup allows guests to connect without a password, get redirected to a login page, and benefit from encryption if their device supports OWE." (Page 35, Guest Network Security Section) : HPE Aruba Networking AOS-8 8.11 User Guide, OWE and Captive Portal Section, Page 290. HPE Aruba Networking Wireless Security Guide, Guest Network Security Section, Page 35.
Question 62
The first exhibit shows roles on the MC, listed in alphabetic order. The second and third exhibits show the configuration for a WLAN to which a client connects. Which description of the role assigned to a user under various circumstances is correct?
Correct Answer: D
In a WLAN setup that uses 802.1X for authentication, the role assigned to a user is determined by the result of the authentication process. When a user successfully authenticates via 802.1X, the RADIUS server may include a Vendor-Specific Attribute (VSA), such as the Aruba-User-Role, in the Access-Accept message. This attribute specifies the role that should be assigned to the user. If the RADIUS Access-Accept message includes an Aruba-User-Role VSA set to "employee1", the client should be assigned the "employee1" role, as per the VSA, and not the default "guest" role. The "guest" role would typically be a fallback if no other role is specified or if the authentication fails.
Question 63
What is a guideline for managing local certificates on an ArubaOS-Switch?
Correct Answer: A
When managing local certificates on an ArubaOS-Switch, a recommended guideline is to create a trust anchor (TA) profile with the root CA certificate before installing the local certificate. This step ensures that the switch can verify the authenticity of the certificate chain during SSL/TLS communications. The trust anchor profile establishes a basis of trust by containing the root CA certificate, which helps validate the authenticity of any subordinate certificates, including the local certificate installed on the switch. This process is essential for enhancing security on the network, as it ensures that encrypted communications involving the switch are based on a verified certificate hierarchy. References: ArubaOS-Switch security configuration guides that detail the process of certificate management, including the creation of trust anchor profiles. Security best practices and SSL/TLS implementation guidelines that emphasize the importance of establishing trusted certificate chains for secure communications.
Question 64
What is one method for HPE Aruba Networking ClearPass Policy Manager (CPPM) to use DHCP to classify an endpoint?
Correct Answer: A
HPE Aruba Networking ClearPass Policy Manager (CPPM) uses device profiling to classify endpoints, and one of its passive profiling methods involves analyzing DHCP traffic. DHCP fingerprinting is a technique where ClearPass examines the DHCP packets sent by a client, particularly the DHCP Discover packet, to identify the device's operating system or type based on specific attributes. Option A, "It can determine information such as the endpoint OS from the order of options listed in Option 55 of a DHCP Discover packet," is correct. DHCP Option 55 (Parameter Request List) is a field in the DHCP Discover packet where the client specifies the list of DHCP options it requests from the server. The order and combination of these options are often unique to specific operating systems or device types (e.g., Windows, Linux, macOS, or IoT devices). ClearPass maintains a database of DHCP fingerprints and matches the Option 55 data against this database to classify the endpoint. Option B, "It can respond to a client's DHCP Discover with different DHCP Offers and then analyze the responses," is incorrect because ClearPass does not act as a DHCP server or send DHCP Offers. It passively snoops DHCP traffic rather than actively responding to DHCP requests. Option C, "It can snoop DHCP traffic to register the clients' IP addresses," is partially correct in that ClearPass does snoop DHCP traffic, but the purpose is not just to register IP addresses for HTTP probing. While ClearPass can use IP addresses for active probing (e.g., HTTP or SNMP), the question specifically asks about using DHCP to classify, which is done via fingerprinting, not IP registration. Option D, "It can alter the DHCP Offer to insert itself as a proxy gateway," is incorrect because ClearPass does not modify DHCP packets or act as a proxy gateway. This is not a function of ClearPass in the context of DHCP-based profiling. The HPE Aruba Networking ClearPass Policy Manager 6.11 User Guide states: "ClearPass can profile devices using DHCP fingerprinting, a passive profiling method. When a device sends a DHCP Discover packet, ClearPass examines the packet's attributes, including the order of options in DHCP Option 55 (Parameter Request List). The combination and order of these options are often unique to specific operating systems or device types. ClearPass matches these attributes against its DHCP fingerprint database to classify the device (e.g., identifying a device as a Windows 10 laptop or an Android phone)." (Page 247, DHCP Fingerprinting Section) Additionally, the ClearPass Device Insight Data Sheet notes: "DHCP fingerprinting allows ClearPass to passively collect device information without interfering with network traffic. By analyzing DHCP Option 55, ClearPass can accurately determine the device's operating system and type, enabling precise policy enforcement." (Page 3) : HPE Aruba Networking ClearPass Policy Manager 6.11 User Guide, DHCP Fingerprinting Section, Page 247. ClearPass Device Insight Data Sheet, Page 3.
Question 65
You configure an ArubaOS-Switch to enforce 802.1X authentication with ClearPass Policy Manager (CPPM) denned as the RADIUS server Clients cannot authenticate You check Aruba ClearPass Access Tracker and cannot find a record of the authentication attempt. What are two possible problems that have this symptom? (Select two)
