HPE7-A01 Aruba Certified Campus Access Professional Exam Question and Answers

The statements that are true regarding Aruba NAE agents are A and C.

A. A single NAE script can be used by multiple NAE agents. This means that you can create different instances of the same script with different parameters or settings. For example, you can use the same script to monitor different VLANs or interfaces on the switch 1 .

C. NAE agents will never consume more than 10% of switch processor resources. This is a built-in safeguard that prevents the agents from affecting the switch performance or stability. If an agent exceeds the 10% limit, it will be automatically disabled and an alert will be generated 2 .

The other options are incorrect because:

B. NAE agents are not active at all times. They can be enabled or disabled by the user, either manually or based on a schedule. They can also be disabled automatically if they encounter an error or exceed the resource limit 1 .

D. NAE scripts do not need to be reviewed and signed by Aruba before being used. You can create your own custom scripts using Python and upload them to the switch or Aruba Central. You can also use the scripts provided by Aruba or other sources, as long as they are compatible with the switch firmware version 1 .

E. A single NAE agent cannot be used by multiple NAE scripts. An agent is an instance of a script that runs on the switch. Each agent can only run one script at a time 1 .

This is the appropriate solution for this scenario where wireless 802.1X authentication will be against a RADIUS server in the cloud and the security team is concerned that the traffic between the AP and the RADIUS server will be exposed. RadSec, also known as RADIUS over TLS, is a protocol that provides encryption and authentication for RADIUS traffic over TCP and TLS. RadSec can be configured on both the AP and the RADIUS server to establish a secure tunnel for exchanging RADIUS packets. The other options are incorrect because they either do not provide encryption or authentication for RADIUS traffic or do not involve RadSec. References: https://www.securew2.com/blog/what-is-radsec/ https://www.cloudradius.com/radsec-vs-radius/

The Equivalent Isotropic Radiated Power (EIRP) is the measured radiated power of an antenna in a specific direction. It is also called Equivalent Isotropic Radiated Power. It is the output power when a signal is concentrated into a smaller area by the Antenna. The EIRP can take into account the losses in transmission line, connectors and includes the gain of the antenna. It is represented in dB 2 . The formula for EIRP is:

EIRP = PT − Lc + Ga

where PT is the output power of the transmitter in dBm, Lc is the cable and connector loss in dB, and Ga is the antenna gain in dBi.

For AP1, the EIRP can be calculated as:

EIRP = 16 − 4 + 8 = 20 dBm

Therefore, the answer B is correct.

PAPI is the protocol that is used to establish tunnels between the CX switch and the Aruba Gateway for Dynamic Segmentation 1 .  By default, PAPI uses a simple checksum to verify the integrity of the messages, but it does not encrypt the payload 2 . This could expose the network to spoofing or replay attacks by malicious actors.  To address this situation, the administrator must enable Enhanced PAPI security, which uses AES-256 encryption and HMAC-SHA1 authentication to protect the tunnel traffic 2 .  Enhanced PAPI security can be enabled on the CX switch by using the command  system papi enhanced-security enable 3 . This will ensure that the tunnels built between the CX switch and the Aruba Gateway are encrypted and authenticated.

The correct answer is B. An event log message is created.

The do-not-disable parameter is used to prevent the switch from disabling the port when a loop is detected by the loop-protect feature. Instead, the switch will generate an event log message that indicates the port number and the VLAN ID where the loop was detected. The switch will also send a trap to the SNMP manager, if configured 1 .

The other options are incorrect because:

A. Port status will not be validated once status is cleared. The port will remain enabled even if a loop is detected, unless the loop-protect action is changed to tx-disable or tx-rx-disable 1 .

C. The network analytics engine will not be triggered by a loop detection. The network analytics engine is a feature that allows users to monitor and troubleshoot network issues using scripts and agents 2 .

D. Port status LED will not blink in amber with 100Hz. The port status LED will indicate the normal port status, such as link speed and activity, regardless of the loop detection 3 .

These are two correct statements regarding OSPFv2 route redistribution for Aruba OS CX switches. Route redistribution is a process that allows routes from one routing protocol or source to be injected into another routing protocol or destination. OSPFv2 is a link-state routing protocol that supports route redistribution from various sources, such as connected, static, BGP, etc. The “redistribute connected” command will redistribute all connected routes for the switch, including local loopback addresses, into OSPFv2. The “redistribute static route-map connected-routes” command will redistribute all static routes that have a matching permit statement in the route map named “connected-routes” into OSPFv2. The other statements are incorrect because they either do not reflect the correct behavior of route redistribution commands or do not exist as valid commands. References: https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/bk01-ch02.html https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/bk01-ch03.html

The built-in auditors role is specifically designed for restricted access to AOS-CX auditing and logging functions. HPE Aruba Networking documents that users assigned to the auditors group have Web UI access only to the System > Log page . For REST API access, auditors are authorized to use GET only against the audit log (/logs/audit) and event log (/logs/event) resources , apart from the POST operations required for login and logout. Aruba Networking

This matches the scenario directly. The requested administrator must be able to inspect event-log information without receiving broader switch management or configuration privileges. The auditors role is therefore an application of least privilege : it provides precisely the logging visibility needed without exposing configuration-changing capabilities.

AOS-CX assigns the auditors role privilege level 19 and restricts CLI access to the auditor context. By comparison, administrators receive privilege level 15 and broad read/write access to switch resources, which would exceed this requirement substantially. Aruba Networking

The AOS-CX REST API documentation also confirms that a GET request against /logs/event retrieves event-log entries, exactly matching the resource specified in the question. Aruba Networking

Therefore, D. auditors is the appropriate default AOS-CX management role.

Study Guide Topics: AOS-CX RBAC, Built-In User Groups, Auditors Role, Web UI Permissions, REST API Authorization, Event and Audit Logs.

The required optimization is to use IEEE 802.3az Energy Efficient Ethernet (EEE) across the AP deployment. Aruba documentation states that 802.3az allows supported APs to consume less power during periods of low data activity , which directly matches the scenario of reducing nighttime energy consumption. Aruba Networking

However, Aruba explicitly documents that 802.3az is not supported on the AP-315 or the 330 Series , which includes the AP-335. Aruba Networking Consequently, those older AP-315 and AP-335 units must be replaced with models supporting EEE. The AP-515 belongs to a newer generation and does not fall within Aruba ' s documented EEE exclusions, so replacing the AP-515 is unnecessary.

After installing EEE-capable replacements, 802.3az should be enabled across the AP environment , allowing Ethernet links to reduce power usage during low-traffic periods.

IPM is not the primary mechanism for this requirement. Aruba describes Intelligent Power Monitoring as dynamically restricting AP functions when AP consumption approaches or exceeds its available power budget . It is primarily concerned with operating an AP within available PoE resources, rather than automatically exploiting nighttime Ethernet inactivity. Aruba Networking

Study Guide Topics: Energy Efficient Ethernet (802.3az), AP Ethernet Link Profiles, AP Power Optimization, Intelligent Power Monitoring (IPM), Campus WLAN Sustainability.

The correct answers are C and D.

MPSK (Multi Pre-Shared Key) is a feature that allows multiple PSKs to be used on a single SSID, providing device-specific or group-specific passphrases for enhanced security and deployment flexibility for headless IoT devices 1 . MPSK requires MAC authentication against a ClearPass Policy Manager server, which returns the encrypted passphrase for the device in a RADIUS VSA 2 . ClearPass Policy Manager is a platform that provides role- and device-based network access control for any user across any wired, wireless and VPN infrastructure 3 . ClearPass Policy Manager can also use device profiling and posture assessment to assign roles based on device fingerprint information 4 .

MPSK Local is a variant of MPSK that allows the user to configure up to 24 PSKs per SSID locally on the device, without requiring ClearPass Policy Manager 5 . MPSK Local can be combined with EAP-TLS (Extensible Authentication Protocol-Transport Layer Security), which is a secure authentication method that uses certificates to encrypt the wireless traffic between the IoT devices and the access points 6 . EAP-TLS can also use device certificates to perform role-based access control 6 .

Therefore, both ClearPass Policy Manager and MPSK Local with EAP-TLS can meet the customer’s requirements for wireless authentication, encryption, unique passphrase, and role-based access for their IoT devices.

MPSK and an internal RADIUS server is not a valid solution, because MPSK does not support internal RADIUS servers and requires ClearPass Policy Manager 7 8 9 . MPSK Local with MAC Authentication is not a valid solution, because MAC Authentication does not encrypt the wireless traffic or use fingerprint information for role-based access 2 . Local User Derivation Rules are not a valid solution, because they do not provide unique passphrase per device or use fingerprint information for role-based access 10 11 12 .

The correct answers are A and D.

According to the web search results, VSX LAG is a feature that allows multiple PSKs to be used on a single SSID, providing device-specific or group-specific passphrases for enhanced security and deployment flexibility for headless IoT devices 1 . VSX LAGs span both aggregation switches and appear as one device to partner downstream or upstream devices or both when forming a LAG with the VSX pair 2 .

One of the statements that is true about VSX LAG is that the total number of configured links may not exceed 8 for the pair or 4 per switch 1 . This means that a VSX LAG across a downstream switch can have at most a total of eight member links, and a switch can have a maximum of four member links. When creating a VSX LAG, it is recommended to select an equal number of member links in each segment for load balancing 1 .

Another statement that is true about VSX LAG is that outgoing traffic is preferentially switched to local members of the LAG 2 . This means that when active forwarding and active gateway are enabled, north-south and south-north traffic bypasses the ISL link and uses the local ports on the switch. This optimizes the traffic path and reduces the load on the ISL link 2 .

The other statements are false or not relevant for VSX LAG. Outgoing traffic is not switched to a port based on a hashing algorithm, which may be either switch in the pair. This is a characteristic of MLAG (Multi-Chassis Link Aggregation), which is a different feature from VSX LAG. LAG traffic is not passed over VSX ISL links only while upgrading firmware on the switch pair. This is a scenario that may occur when performing hitless upgrades, which is a feature that allows software updates without impacting network availability. The number of VSX lags that can be configured on all 83xx and 84xx model switches is not 255, but depends on the switch model and firmware version. For example, the AOS-CX 10.04 supports up to 64 VSX lags for 8320 switches and up to 128 VSX lags for 8325 and 8400 switches.

a) Support up to 10 devices per stack - >   VSF  

b) Support two devices per stack - >   VSX  

c) Individual ISL links up to 400G are supported - >   VSX  

d) individual ISL links up to 50G are supported - >   VSF  

e) A maximum aggregate ISL bandwidth of 200G is supported - >   VSF

The reason is that PBR allows you to route packets based on policies that match certain criteria, such as source or destination IP addresses, ports, protocols, etc. PBR can also be used to set metrics, next-hop addresses, or tag traffic for different routes.

QoS stands for Quality of Service and is a mechanism that allows network devices to prioritize and differentiate traffic based on certain criteria, such as application type, source, destination, etc 3 .  QoS involves identifying specific traffic for special treatment and applying policies and actions to improve its performance or meet certain service level agreements (SLAs) 3 .  QoS can help network devices to manage congestion, delay, jitter, packet loss, bandwidth allocation, etc., for different types of traffic 3 .  QoS can be implemented at various layers of the network stack and across different network domains. References:  3   https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos/configuration/15-mt/qos-15-mt-book/qos-overview.html

The correct action to fix the issue is C. Change the SSID to WPA3-Enhanced Open.

WPA3-OWE is not a valid SSID type in Central. OWE stands for Opportunistic Wireless Encryption, and it is a feature that provides encryption for open networks without requiring authentication. OWE is also known as Enhanced Open, and it is one of the options for WPA3 SSIDs in Central 1 .

According to the Aruba document Configuring WLAN Settings for an SSID Profile , one of the steps to configure a WPA3 SSID is:

Select the Security Level from the drop-down list. The following options are available:

WPA3-Personal: This option uses Simultaneous Authentication of Equals (SAE) to provide stronger password-based authentication and key exchange than WPA2-Personal.

WPA3-Enterprise: This option uses 192-bit cryptographic strength for authentication and encryption, as defined by the Commercial National Security Algorithm (CNSA) suite.

WPA3-Enterprise (CCM): This option uses 128-bit cryptographic strength for authentication and encryption, as defined by the Counter with CBC-MAC (CCM) mode.

WPA3-Enhanced Open: This option uses Opportunistic Wireless Encryption (OWE) to provide encryption for open networks without requiring authentication.

The other options are incorrect because:

A. WPA3-Enterprise (CNSA) is a valid SSID type, but it requires 802.1X authentication with a RADIUS server, which may not be suitable for the company’s use case.

B. WPA3-Personal is a valid SSID type, but it requires a passphrase to join the network, which may not be suitable for the company’s use case.

D. WPA3-Enterprise (CCM) is a valid SSID type, but it requires 802.1X authentication with a RADIUS server, which may not be suitable for the company’s use case.

This is because Best Effort traffic is all other kinds of non-detrimental traffic that are not sensitive to Quality of Service metrics (jitter, packet loss, latency).  A typical example would be peer-to-peer and email applications 2 .  Background traffic is a type of traffic that is used for system maintenance or backup purposes and does not affect the performance or availability of the network 3 .

Therefore, Best Effort traffic has a higher priority than Background traffic in terms of network resources allocation and management.

1 : https://www.arubanetworks.com/techdocs/ArubaDocPortal/content/docportal.htm  2 : https://stackoverflow.com/questions/33854306/best-effort-traffic-and-real-time-traffic-difference  3 : https://www.informit.com/articles/article.aspx?p=25315 & seqNum=4

The reason is that AOS 10.x does not support clustering gateways with different versions in the same cluster profile. A cluster profile defines the configuration settings for a group of gateways that are managed by Aruba Central.

According to the Aruba documentation 2 , “You can combine 7200 Series and 7000 Series gateways in the same cluster with a maximum size of four devices with reduced AP client capacity on 7000 Series gateways.”

Two parts of the solution for these requirements are Option C and Option E.

Option C is a part of the solution because it defines a policy-based routing action list named route_test, which specifies the next hop IP address as 10.1.1.253 for the matching traffic. This is the new default route that the user wants to use for the subnet 10.2.250.0/24. The interface null parameter indicates that the traffic will be routed to the next hop without using a specific interface 1 .

Option E is a part of the solution because it applies the policy-based routing action list route_test to the VLAN interface 250, which has an IP address of 10.2.250.1/24. This is the subnet that the user wants to test the new default route for. The apply policy command enables policy-based routing on the interface and associates it with the action list 2 .

Option A is not a part of the solution because it defines a policy-based routing action list named route_test, but does not specify the next hop IP address as 10.1.1.253, which is the new default route that the user wants to use. Instead, it specifies a next hop IP address of 10.1.1.254, which is different from the requirement.

Option B is not a part of the solution because it defines a policy-based routing action list named route_test, but does not specify any next hop IP address at all, which is necessary for policy-based routing to work. Instead, it specifies an interface null parameter without any IP address, which is invalid.

Option D is not a part of the solution because it applies the policy-based routing action list route_test to the VLAN interface 200, which has an IP address of 10.2.200.1/24. This is not the subnet that the user wants to test the new default route for, but a different subnet that should not be affected by this change.

To establish a keepalive connection between two Aruba CX 8325 switches for VSX configuration, you need to use a routed port in custom VRF. A routed port is a physical port that acts as a layer 3 interface and does not belong to any VLAN. A custom VRF is a virtual routing and forwarding instance that provides logical separation of routing tables. By using a routed port in custom VRF, you can isolate the keepalive traffic from other traffic and prevent routing loops or conflicts. The other options are incorrect because they either do not use a routed port or do not use a custom VRF. References: https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/bk01-ch07.html https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/bk01-ch02.html

The correct built-in AOS-CX management role is administrators . HPE Aruba Networking defines the administrators group as the default role with full management privileges and explicitly assigns it privilege level 15 . Members of this group can perform firmware upgrades, modify switch configuration, view sensitive configuration information, add or remove local user accounts, change passwords, and use all supported REST API methods. Aruba Networking

The existing auditors assignment does not satisfy the requirement. The auditors group is intentionally restricted to audit-related operations and is assigned privilege level 19 , not 15. Its CLI access is limited to the auditor context, and its Web UI and REST API permissions are similarly restricted to logging and auditing resources. Aruba Networking

AOS-CX also documents the mapping used with TACACS+: privilege level 15 maps to administrators , privilege level 1 maps to operators, and privilege level 19 maps to auditors. Aruba Networking

Therefore, because this user needs both firmware-upgrade capability and privilege level 15 , the appropriate default management role is administrators .

Study Guide Topics: AOS-CX Management Users, Built-in User Groups, RBAC, Privilege Levels, Administrators vs. Auditors, Firmware Management, TACACS+ Authorization.

This is because option C shows how to create a single group in Central with different configuration methods defined for each device type. For example, you can create a group with the name Group1, and within this group, you can enable template-based configuration method for switches and UI-based configuration method for Instant APs and Gateways. Aruba Central identifies both these groups under a single name (Group1). If a device type in the group is marked for template-based configuration method, the group name is prefixed with TG (TG Group1).  You can use Group1 as the group ID for workflows such as user management, monitoring, reports, and audit trail 2 .

https://www.arubanetworks.com/techdocs/central/latest/content/nms/groups/abt-groups.htm  2 : https://www.arubanetworks.com/techdocs/central/latest/content/nms/groups/groups.htm

Multicast Transmission Optimization (MTO) improves wireless multicast efficiency by allowing an Aruba AP to transmit broadcast and multicast frames at a higher data rate than the normally configured basic multicast rate. In Aruba Instant and Aruba Central WLAN configuration, the AP determines the optimized rate using the lowest unicast rate among all associated clients , ensuring that every associated client can still receive the multicast transmission reliably. Aruba Networking

Critically, Aruba documentation states that when this feature is enabled, multicast traffic can be transmitted at up to 24 Mbps . Therefore, B is the correct answer . In the documented Instant implementation, the normal default multicast transmission rates are typically much lower—1 Mbps on 2.4 GHz and 6 Mbps on 5 GHz—so MTO can substantially reduce airtime consumed by multicast traffic. Aruba Networking

Option A is incorrect because Aruba uses the lowest , not highest, unicast rate of associated clients. Option C incorrectly specifies 48 Mbps. Option D is also incorrect because MTO ' s rate-selection mechanism is based on client unicast data rates , not client latency. Aruba Networking

Study Guide Topics: WLAN Optimization, Multicast Transmission Optimization, Broadcast/Multicast Traffic, Wireless Data Rates, Aruba Instant/Central WLAN Profiles.

This is the most likely cause of the issue where the access points in a Microbranch group are online in Aruba Central, but no VPN tunnels are forming. A Microbranch group is a group that contains both APs and Gateways and allows them to form VPN tunnels for secure communication. The VPN tunnels use GRE (Generic Routing Encapsulation) as the encapsulation protocol and IPSec as the encryption protocol. If there is a firewall blocking GRE traffic between the AP and the gateway, the VPN tunnels cannot be established. The other options are incorrect because they either do not affect the VPN tunnel formation or do not apply to a Microbranch group. References: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/gateways/microbranch.htm https://www.arubanetworks.com/assets/tg/TB_ArubaGateway.pdf

The reason is that the Inter-Switch Link Protocol (ISLP) is a protocol that enables VSX stack join and synchronization between two VSX peer switches. ISLP uses a hello interval to exchange control messages between the switches.

The hello interval is a parameter that specifies the time interval between sending hello messages. The default value of the hello interval is 1 second. The hello interval can be configured from 1 second to 10 seconds.

https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/index.html

Strict queuing is the best scheduling technology to use for voice traffic on an AOS-CX switch. Scheduling is a mechanism that determines how packets are transmitted from different queues on an egress port. Strict queuing is a scheduling method that gives the highest priority queue absolute preference over all other queues, regardless of their size or utilization. Voice traffic should be assigned to the highest priority queue and scheduled with strict queuing to ensure minimal latency and jitter. The other options are incorrect because they are either not scheduling methods or not optimal for voice traffic. References: https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/bk01-ch02.html https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6728/bk01-ch03.html

The correct mechanism is RADIUS Change of Authorization (CoA) . ClearPass Policy Manager can dynamically alter or terminate an already authenticated network session by sending a RADIUS dynamic-authorization message to the network access device. Aruba defines dynamic authorization as the capability to modify a user ' s authorization while the session is active, including disconnecting the session . Aruba Networking

For guest accounts, ClearPass can associate an expiration time or permitted access duration with the account. When the configured expiration condition requires the guest to be logged out, ClearPass can issue a RADIUS Disconnect-Request to the NAS, such as an Aruba wireless controller or access infrastructure. Aruba ' s ClearPass Guest documentation specifically describes the Disable and logout behavior as disabling further authorization and using a RADIUS Disconnect-Request for matching active sessions. Aruba Networking Once disconnected, the client must go through the applicable authentication and authorization process again before network access can resume.

An Authorization Profile defines what access should be granted but does not itself provide the dynamic session-disconnect mechanism. Active Directory session timeout and Wi-Fi Sense do not fulfill this ClearPass enforcement function.

Study Guide Topics: ClearPass Policy Manager, AAA, Guest Access, RADIUS Dynamic Authorization, Change of Authorization (CoA), Disconnect-Request, Session Enforcement.

When a UXI sensor must be deployed into an environment protected by 802.1X but lacks cellular connectivity, the appropriate bootstrap mechanism is the UXI Onboarding application using Bluetooth . The sensor initially cannot authenticate to the protected network because it has not yet obtained the required 802.1X credentials, certificates, or other connectivity configuration. Bluetooth provides an out-of-band path for supplying that initial configuration.

HPE Aruba Networking ' s UXI onboarding documentation states that when Ethernet connectivity or cellular onboarding is unavailable, the UXI onboarding app can send the sensor ' s initial configuration over Bluetooth . The application supports configuring network parameters including 802.1X credentials and certificates . Cape Networks Help Center

HPE ' s UXI QuickSpecs likewise confirms that UXI sensors include a Bluetooth 5.0 radio specifically enabling setup through the UXI mobile application. Hewlett Packard Enterprise

Therefore, D is correct. Barcode scanning alone does not solve the sensor ' s protected-network connectivity requirement. Sensors are not onboarded by daisy-chaining configuration from another UXI, and UXI deployment is not based on serial-CLI provisioning.

Study Guide Topics: UXI Sensor Deployment, UXI Onboarding, Bluetooth Provisioning, 802.1X Authentication, Sensor Bootstrap Connectivity.

CoA (Change of Authorization) is a feature that allows ClearPass to dynamically change the authorization and access privileges of a device after it has been authenticated 1 .  CoA uses RADIUS messages to communicate with the network device and instruct it to perform an action, such as reauthenticating the device, applying a new VLAN or user role, or disconnecting the device 2 .

To enable CoA on a CX switch, the network engineer needs to configure dynamic authorization on the switch, which is a global command that allows the switch to accept RADIUS messages from ClearPass and execute the requested actions 3 .  The network engineer also needs to specify the IP address and shared secret of ClearPass as a dynamic authorization client on the switch 3 .

To trigger CoA for a specific wired device, the network engineer needs to bounce the switchport, which is an action that temporarily disables and re-enables the port where the device is connected. This forces the device to reauthenticate and receive the new policy from ClearPass. Bouncing the switchport can be done manually by using the interface shutdown and no shutdown commands, or automatically by using ClearPass as a CoA server and sending a RADIUS message with the Port-Bounce-Host AVP (Attribute-Value Pair).

Spectrum Monitor is an Aruba AP mode that is sending captured RF data to Aruba Central for waterfall plot. Spectrum Monitor is a mode that allows an AP to scan all channels in both 2.4 GHz and 5 GHz bands and collect information about the RF environment, such as interference sources, noise floor, channel utilization, etc. The AP then sends this data to Aruba Central, which is a cloud-based network management platform that can display the data in various formats, including waterfall plot. Waterfall plot is a graphical representation of the RF spectrum over time, showing the frequency, amplitude, and duration of RF signals. The other options are incorrect because they are either not AP modes or not sending RF data to Aruba Central. References: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/spectrum_monitor.htm https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/waterfall_plot.htm https://www.arubanetworks.com/products/network-management-operations/aruba-central/

EVPN-VXLAN is a technology that allows layer-2 communication across layer-3 networks by using Ethernet VPN (EVPN) as a control plane and Virtual Extensible LAN (VXLAN) as a data plane 3 . EVPN-VXLAN can be used to support legacy applications that communicate at layer-2 across different campuses or data centers that are connected via layer-3.  EVPN-VXLAN minimizes flooding by using BGP to distribute MAC addresses and IP addresses of hosts across different VXLAN segments 3 .  EVPN-VXLAN also provides benefits such as loop prevention, load balancing, mobility, and scalability 3 . References:  3   https://www.arubanetworks.com/assets/tg/TG_EVPN_VXLAN.pdf

The best option to enhance security for the new IP cameras and scanners in this environment is C. MPSK provides for each device in the WLAN to have its own unique pre-shared key.

MPSK stands for Multi Pre-Shared Key, and it is a feature that allows different devices to connect to the same SSID with different pre-shared keys. This improves the security and scalability of the network, as each device can have its own key and role without requiring 802.1X authentication or an external policy engine. MPSK can be configured either locally on the AP or centrally on Aruba Central 1 2 .

The other options are incorrect because:

A. MPSK Local is a feature that allows the user to configure 24 PSKs per SSID locally on the device. These local PSKs would serve as an extension of the base MPSK functionality. However, MPSK Local is not suitable for this scenario, as it can only support up to 24 devices per SSID, while the client has 250 devices 1 .

B. Aruba ClearPass is a network access control solution that can perform 802.1X authentication and install certificates for devices. However, this option is not feasible for this scenario, as the new IP cameras and scanners do not support 802.1X authentication 3 .

D. MPSK Local will not allow the cameras to share a key and the scanners to share a different key. MPSK Local will assign a different key to each device, regardless of their type. Moreover, MPSK Local can only support up to 24 devices per SSID, while the client has 250 devices 1 .

The active gateway feature is used to provide active-active layer 3 default gateway for hosts on the same subnet. It allows the switch to convert multicast streams into unicast streams over the wireless link, which improves the quality and reliability of streaming video, while preserving the bandwidth available to the non-video clients. The active gateway feature is unique to VSX configuration because it eliminates the need for VRRP and avoids traffic being pushed over the ISL link, which can cause latency in the network 1 2 .

The correct answer to the question is C. Sixteen different VMACs are supported for each IPv4 and IPv6 stack simultaneously. This means that you can have a maximum of eight VMACs for IPv4, and a maximum of eight VMACs for IPv6, on a VSX pair. Only 15 VMACs are supported on 6400 switch series 2 .

The other options are incorrect because:

A. Sixteen different VMACs are not supported total as shared. They are supported for each IPv4 and IPv6 stack separately.

B. Active gateway can be used without MSTP instances. MSTP is a protocol that allows multiple spanning tree instances to coexist on the same switch, but it does not affect how active gateway works.

D. Active gateway does not copy traffic over the ISL link for an optimized path. It avoids using the ISL link for routed traffic and uses the local switch interface MAC instead of the virtual MAC address (VMAC) for source address 1 .

Option C is the correct configuration to ensure that APs will work properly. It uses the  ap  command to configure a port profile for APs with VLAN 100 as the native VLAN and VLAN 200 and 300 as tagged VLANs. It also enables LLDP on the ports to discover the APs and assign them to the port profile automatically. The other options are incorrect because they either do not use the  ap  command, do not enable LLDP, or do not configure the VLANs correctly. References: https://www.arubanetworks.com/techdocs/AOS-CX_10_08/UG/bk01-ch02.html https://www.arubanetworks.com/techdocs/AOS-CX_10_08/UG/bk01-ch03.html

a) A device with IP address 10.1.3.7 in a network wants to send the traffic stream to a device with IP address 10.13.4.2 in the other network - >   Unicast  

b) One/more senders and one/more recipients participate in data transfer traffic - >   Multicast  

c) Sent to all hosts on a remote network - >   IP Directed Broadcast  

d) Sent to all NICs on the same network segment as the source NIC - >   Broadcast