HP HPE6-A85 Aruba Certified Campus Access Associate Exam Online Training

Question #31

You need to drop excessive broadcast traffic on ingress to an ArubaOS-CX switch.

What is the best technology to use for this task?

A . Rate limiting
B . DWRR queuing
C . QoS shaping
D . Strict queuing

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

The best technology to use for dropping excessive broadcast traffic on ingress to an ArubaOS-CX switch is rate limiting. Rate limiting is a feature that allows network administrators to control the amount of traffic that enters or leaves a port or a VLAN on a switch by setting bandwidth thresholds or limits. Rate limiting can be used to prevent network congestion, improve network performance, enforce service level agreements(SLAs), or mitigate denial-of-service (DoS) attacks. Rate limiting can be applied to broadcast traffic on ingress to an ArubaOS-CX switch by using the storm-control command in interface configuration mode. This command allows network administrators to specify the percentage of bandwidth or packets per second that can be used by broadcast traffic on an ingress port. If the broadcast traffic exceeds the specified threshold, the switch will drop the excess packets.

The other options are not technologies for dropping excessive broadcast traffic on ingress because:

– DWRR queuing: DWRR stands for Deficit Weighted Round Robin, which is a queuing algorithm that assigns different weights or priorities to different traffic classes or queues on an egress port. DWRR ensures that each queue gets its fair share of bandwidth based on its weight while avoiding starvation of lower priority queues. DWRR does not drop excessive broadcast traffic on ingress, but rather schedules outgoing traffic on egress.

– QoS shaping: QoS stands for Quality of Service, which is a set of techniques that manage network resources and provide different levels of service to different types of traffic based on their requirements. QoS shaping is a technique that delays or buffers outgoing traffic on an egress port to match the available bandwidth or rate limit. QoS shaping does not drop excessive broadcast traffic on ingress, but rather smooths outgoing traffic on egress.

– Strict queuing: Strict queuing is another queuing algorithm that assigns different priorities to different traffic classes or queues on an egress port. Strict queuing ensures that higher priority queues are always served before lower priority queues regardless of their bandwidth requirements or weights. Strict queuing does not drop excessive broadcast traffic on ingress, but rather schedules outgoing traffic on egress.

References:

https://en.wikipedia.org/wiki/Rate_limiting

https://www.arubanetworks.com/techdocs/AOS-CX_10_08/NOSCG/Content/cx-noscg/qos/storm-control .htm

https://www.arubanetworks.com/techdocs/AOS-CX_10_08/NOSCG/Content/cx-noscg/qos/dwrr.htm

https://www.arubanetworks.com/techdocs/AOS-CX_10_08/NOSCG/Content/cx-noscg/qos/shaping.htm

https://www.arubanetworks.com/techdocs/AOS-CX_10_08/NOSCG/Content/cx-noscg/qos/strict.htm

Question #32

Which authentication does Aruba’s Captive Portal use?

A . Layer 3 authentication
B . MAC authentication
C . 802.1x authentication
D . Layer 2 authentication

Reveal Solution Hide Solution

Question #33

Where are wireless client roaming decisions made?

A . Client device
B . Virtual Controller
C . Joint decision made by the origination and destination APs
D . Aruba Central

Reveal Solution Hide Solution

Question #34

Which feature can network administrators use to centralized RF planning and optimization service when using an Aruba mobility master architecture?

A . Airwave
B . Client Match
C . AirMatch
D . Client Wave

Reveal Solution Hide Solution

Question #35

Match the feature to the Aruba OS version (Matches may be used more than once.)

Reveal Solution Hide Solution

Correct Answer:

Explanation:

Features: 1) Clustered Instant Access Points Aruba OS version: a) Aruba OS 8

Features: 2) Dynamic Radius Proxy Aruba OS version: a) Aruba OS 8

Features: 3) Scales to more than 10,000 devices Aruba OS version: b) Aruba OS 10

Features: 4) Unifies wired and wireless management Aruba OS version: a) Aruba OS 8

Features: 5) Wireless controllers Aruba OS version: a) Aruba OS 8

ArubaOS is the operating system for all Aruba Mobility Controllers (MCs) and controller-managed wireless access points (APs). ArubaOS 8 delivers unified wired and wireless access, seamless roaming, enterprise grade security, and a highly available network with the required reliability to support high density environments1.

Some of the features of ArubaOS 8 are:

– Clustered Instant Access Points: This feature allows multiple Instant APs to form a cluster and share configuration and state information. This enables seamless roaming, load balancing, and fast failover for clients2.

– Dynamic Radius Proxy: This feature allows an MC to act as a proxy for RADIUS authentication requests from clients or APs. This simplifies the configuration and management of RADIUS servers and reduces the network traffic between MCs and RADIUS servers3.

– Wireless controllers: Aruba wireless controllers are devices that centrally manage and control the wireless network. They provide functions such as AP provisioning, configuration, security, policy enforcement, and network optimization.

ArubaOS 10 is the next-generation operating system that works with Aruba Central, a cloud-based network management platform. ArubaOS 10 delivers greater scalability, security, and AI-powered optimization across large campuses, branches, and remote work environments. Some of the features of ArubaOS 10 are:

– Scales to more than 10,000 devices: ArubaOS 10 can support up to 10,000 devices per cluster, which is ten times more than ArubaOS 8. This enables customers to scale their networks without compromising performance or reliability.

– Unifies wired and wireless management: ArubaOS 10 provides a single platform for managing both wired and wireless devices across the network. Customers can use Aruba Central to configure, monitor, troubleshoot, and update their devices from anywhere.

Both ArubaOS 8 and ArubaOS 10 share some common features, such as:

– Unifies wired and wireless management: Both operating systems provide unified wired and wireless

access for customers who use Aruba switches and APs. Customers can use a single interface to manage

their entire network infrastructure1.

References:

1 https://www.arubanetworks.com/resource/arubaos-8-fundamental-guide/

2 https://www.arubanetworks.com/techdocs/Instant_86_WebHelp/Content/instant-ug/iap-maintenance/clus

3 https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overvie

https://www.arubanetworks.com/products/networking/controllers/

https://www.arubanetworks.com/products/network-management-operations/arubaos/

https://blogs.arubanetworks.com/solutions/making-the-switch/

https://www.arubanetworks.com/products/network-management-operations/aruba-central/

Question #36

When using an Aruba standalone AP you select "Native VLAN" for the Client VLAN Assignment.

In which subnet will the client IPs reside?

A . The same subnet as the mobility controller
B . The same subnet as the Aruba ESP gateway
C . The same subnet as the mobility conductor
D . The same subnet as the access point

Reveal Solution Hide Solution

Question #37

When performing live firmware upgrades on Aruba APs.

Which technology partitions all the APs based on RF neighborhood data minimizing the impact on clients?

A . Aruba ClientMatch
B . Aruba Ai insights
C . Aruba AirMatch
D . Aruba ESP

Reveal Solution Hide Solution

Question #38

You are configuring a network with a stacked pair of 6300M switches used for distribution and layer 3 services. You create a new VLAN for users that will be used on multiple access stacks of CX6200 switches connected downstream of the distribution stack You will be creating multiple VLANs/subnets similar to this will be utilized in multiple access stacks

What is the correct way to configure the routable interface for the subnet to be associated with this VLAN?

A . Create a physically routed interface in the subnet on the 6300M stack for each downstream switch.
B . Create an SVl in the subnet on each downstream switch
C . Create an SVl in the subnet on the 6300M stack, and assign the management address of each downstream switch stack to a different IP address in the same subnet
D . Create an SVl in the subnet on the 6300M stack.

Reveal Solution Hide Solution

Correct Answer: D
D

Explanation:

The correct way to configure the routable interface for the subnet to be associated with this VLAN is to create an SVI Switched Virtual Interface (SVI) Switched Virtual Interface (SVI) is a virtual interface on a switch that represents a VLAN and provides Layer 3 routing functions for that VLAN. SVIs are used to enable inter-VLAN routing, provide gateway addresses for hosts in VLANs, apply ACLs or QoS policies to VLANs, etc. SVIs have some advantages over physical routed interfaces such as saving interface ports, reducing cable costs, simplifying network design, etc. SVIs are usually numbered according to their VLAN IDs (e.g., vlan 10) and assigned IP addresses within the subnet of their VLANs. SVIs can be created and configured by using commands such as interface vlan, ip address, no shutdown, etc. SVIs can be verified by using commands such as show ip interface brief, show vlan, show ip route, etc. in the subnet on the 6300M stack. An SVI is a virtual interface on a switch that represents a VLAN and provides Layer 3 routing functions for that VLAN. Creating an SVI in the subnet on the 6300M stack allows the switch to act as a gateway for the users in that VLAN and enable inter-VLAN routing between different subnets. Creating an SVI in the subnet on the 6300M stack also simplifies network design and management by reducing the number of physical interfaces and cables required for routing.

The other options are not correct ways to configure the routable interface for the subnet to be associated with this VLAN because:

– Create a physically routed interface in the subnet on the 6300M stack for each downstream switch: This option is incorrect because creating a physically routedinterface in the subnet on the 6300M stack for each downstream switch would require using one physical port and cable per downstream switch, which would consume interface resources and increase cable costs. Creating a physically routed interface in the subnet on the 6300M stack for each downstream switch would also complicate network design and management by requiring separate routing configurations and policies for each interface.

– Create an SVl in the subnet on each downstream switch: This option is incorrect because creating an SVI in the subnet on each downstream switch would not enable inter-VLAN routing between different subnets, as each downstream switch would act as a gateway for its own VLAN only. Creating an SVI in the subnet on each downstream switch would also create duplicate IP addresses in the same subnet, which would cause IP conflicts and routing errors.

– Create an SVl in the subnet on the 6300M stack, and assign the management address of each downstream switch stack to a different IP address in the same subnet: This option is incorrect because creating an SVI in the subnet on the 6300M stack, and assigning the management address of each downstream switch stack to a different IP address in the same subnet would not enable inter-VLAN routing between different subnets, as each downstream switch would still act as a gateway for its own VLAN only. Creating an SVI in the subnet on the 6300M stack, and assigning the management address of each downstream switch stack to a different IP address in the same subnet would also create unnecessary IP addresses in the same subnet, which would waste IP space and complicate network management.

References:

https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/index.html https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/cx-noscg/l3-routing/l3-routing-ov

https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/cx-noscg/l3-routing/l3-routing-co

Question #39

Refer to the exhibit.

In the given topology, a pair of Aruba CX 8325 switches are in a VSX stack using the active gateway.

What is the nature and behavior of the Virtual IP for the VSX pair if clients are connected to the access switch using VSX as the default gateway?

A . Virtual IP is active on the primary VSX switch
B . Virtual floating IP will failover in case of a failure
C . Virtual IP is active on both CX switches
D . Virtual IP uses SVI IP address synced with VSX

Reveal Solution Hide Solution

Question #40

What are two advantages of a UXl? (Select two.)

A . A UXl can be used without any internet connection
B . A UXl helps to calculate the best WiFi channels in a remote location
C . A UXl behaves like a client/user
D . A UXl measures the Wi-Fi coverage of all APs in the given location.
E . A UXl can check different applications, such as HTTP VOIP or Office 365.

Reveal Solution Hide Solution