When using Aruba Central what can identify recommended steps to resolve network health issues and allows you to share detailed information with support personnel?

1. A. Overview Dashboard
2. B. OAlOps
3. C. Alerts and Events
4. D. Audit Trail

Correct Answer: B
OAlOps is a feature of Aruba Central that uses artificial intelligence and machine learning to identify recommended steps to resolve network health issues and allows you to share detailed information with support personnel. OAlOps provides insights into network performance, root cause analysis, anomaly detection, proactive alerts, and automated remediation actions.OAlOps also integrates with Aruba User Experience Insight (UXI) sensors to measure and improve user experience across wired and wireless networks. References:https://www.arubanetworks.com/assets/ds/DS_ArubaCentral.pdf

DRAG DROP
List the WPA 4-Way Handshake functions in the correct order.

Solution:
✑ Proves knowledge of the PMK
✑ Exchanges messages for generating PTK
✑ Distributes an encrypted GTK to the client
✑ Sets first initialization vector (IV)

Does this meet the goal?

1. A. Yes
2. B. No

Correct Answer: A

The noise floor measures 000000001 milliwatts, and the receiver's signal strength is - 65dBm. What is the Signal to Noise Ratio?

1. A. 35 dBm
2. B. 15 dBm
3. C. 45 dBm
4. D. 25 dBm

Correct Answer: D
The signal to noise ratio (SNR) is a measure that compares the level of a desired signal to the level of background noise. SNR is defined as the ratio of signal power to the noise power, often expressed in decibels (dB). A high SNR means that the signal is clear and easy to detect or interpret, while a low SNR means that the signal is corrupted or obscured by noise and may be difficult to distinguish or recover3. To calculate the SNR in dB, we can use the following formula:
SNR (dB) = Signal power (dBm) - Noise power (dBm)
In this question, we are given that the noise floor measures -90 dBm (0.000000001 milliwatts) and the receiver??s signal strength is -65 dBm (0.000316 milliwatts). Therefore, we can plug these values into the formula and get:
SNR (dB) = -65 dBm - (-90 dBm) SNR (dB) = -65 dBm + 90 dBm SNR (dB) = 25 dBm
Therefore, the correct answer is that the SNR is 25 dBm. References: 3 https://en.wikipedia.org/wiki/Signal-to-noise_ratio

The customer has a requirement to create authorization policies for their users with Windows 10 clients, with a requirement Tor authorizing both device and user credentials within one Radius session.
What would be the correct solution for the requirement?

1. A. ClearPass 6.9 with EAP-TTLS
2. B. ClearPass 6.9 with EAP-TLS
3. C. ClearPass 6.9 with PEAP
4. D. ClearPass 6.9 with EAP-TEAP

Correct Answer: D
EAP-TEAP is a tunnel-based authentication method that supports both device and user authentication within a single RADIUS session. ClearPass 6.9 supports EAP-TEAP as anauthentication method for Windows 10 clients. References: https://www.arubanetworks.com/techdocs/ClearPass/6.9/Guest/Content/CPPM_UserGuide
/EAP-TEAP/EAP-TEAP.htm

After having configured the edge switch uplink as requested your colleague says that they have failed to ping the core You ask your colleague to verify the connection is plugged in and the switch is powered on They confirm that both are correct You attempt to ping the core switch and confirm that the ping is failing.
Knowing the nature of this deployment, what commands might you use to troubleshoot this issued

1. A. Ping 10.11 1 - ping the core to attempt to verify connectivity Show trunk - to verify if the LAG interface was correctly added to the switch Show spanning tree - to check for spanning-tree blocked states Show port-access clients interface all - to view any port- access blocking states or failed authentication attempts on all interfaces Show run interface vlan20 - to double check the layer 3 svi configuration is correct for l_3 connectivity Show lldp neighors - to verify whether you are able to see the Core as an L2 neighbor to verify if the correct links are plugged in to the correct ports
2. B. diagnostic diag cable-diag 1/1/51 diag cable-diag 1/1/52 - to view diagnostic information for the physical link to get a status on any interruptions to Layer 1 connectivity, show ip route - to verify that the default gateway is present in the routing table show ip ospf - to check whether there is a layer 3 routing protocol enabled show ip dns - to view whether there is a valid dns source
3. C. Ping 10.1.1.1 - ping the core to attempt to verify connectivity show lacp agg - to verify which link aggregations are currently configured using which physical ports show lacp int - to verify the LACP status and whether any links are blocking in your topology show lldp neighors - to verify whether you are able to see the Core as an L2 neighbor to verify if the correct links are plugged in to the correct ports show run interface 1/1/51.1/1/52-to ensure the physical interfaces are no-shut and members of the lag show run interface lag 1 - to ensure the correct vlan trunking configuration is applied to the logical interface show run int vlan 20 - to ensure you have the L3 SVI no shut and configured in the correct subnet
4. D. Show run - to view the running configuration of the switch Show run | begin 20 "vlan 20"- to ensure VLAN 20 was correctly added to the database show run | begin 20 'interface vlan 20' - to view the L3 SVI configuration Show run interface 1/1/51.1/1/52 - to ensure the physical interfaces are no shut and were added as members of LAG 1 Show run int lag 1 - to verify LACP mode active was configured to eliminate LACP blocking states

Correct Answer: C
These commands might help troubleshoot this issue as they check various aspects of the connectivity between the edge switch and the core switch, such as Layer 3 reachability, Layer 2 adjacency, LACP configuration and status, VLAN trunking configuration, and interface status. References:https://www.arubanetworks.com/techdocs/AOS-CX_10_04/CLI/GUID- 8F0E7E8B-0F4B-4A3C-AE7F-0F1B5A7F9C5D.html