HP HPE6-A47 Designing Aruba Solutions Exam Practice Test

DSCP (Differentiated Services Code Point) is a method of marking network packets with different priorities based on the type of traffic they carry. DSCP values range from 0 to 63, with higher values indicating higher priority. DSCP values are typically mapped to one of the four WMM (Wi-Fi Multimedia) queues, which are used to prioritize wireless traffic on the access points and controllers. WMM queues are: voice, video, best effort, and background12.

The default QoS settings for Aruba APs and controllers map the DSCP values to the WMM queues as follows3:

Table

DSCP Value

WMM Queue

0-7

Background

8-23

Best Effort

24-39

Video

40-63

Voice

According to these settings, the DSCP values 46 and 34, which are assigned to voice and video traffic by Windows policies, will both be mapped to the video WMM queue. This means that both types of traffic will receive the same priority, and voice traffic will not receive the highest priority that it should. This can result in poor voice quality, increased latency, jitter, or packet loss, especially when the network is congested or bandwidth is limited. Voice traffic is more sensitive to these factors than video traffic, and requires strict QoS to ensure optimal performance and user experience4.

To avoid this potential issue, the architect should explain to the customer that they need to modify the QoS settings on the Aruba APs and controllers to match the DSCP values assigned by Windows policies. This can be done by using the following commands on the Aruba controller3:

(config) #wmm traffic-management-profile voice

(config) #dscp 46

(config) #wmm traffic-management-profile video

(config) #dscp 34

These commands will map the DSCP value 46 to the voice WMM queue, and the DSCP value 34 to the video WMM queue, ensuring that voice traffic receives the highest priority and video traffic receives the second highest priority. This will improve the QoS for the Skype for Business UC solution and enhance the end-user experience.

References:

• 1: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/qos.htm
• 2: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/wmm.htm
• 3: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/qos-mapping.htm
• 4: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/qos-voice.htm

In the event of an MM outage, MCs continue to use their existing licenses for 30 days, and the network remains up. However, you cannot change the configuration items in the controller network. In addition, the MM manages many of the higher level functions that can cause issues in the network if the MM fails. Aruba recommends a backup MM for these situations. From an economic point of view, a backup MM for a VMM is free. If a customer has a hardware MM, the customer must purchase a backup hardware MM.

https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/vrrp/conf-stby-mm-l3red.htm

 This answer is correct because it meets the customer’s requirements for wired authentication and traffic forwarding. By assigning wired users to different VLANs from wireless users, the architect can ensure that the wired traffic is not tunneled to the MCs, but forwarded locally on the access layer switches. This reduces the load on the MCs and the network bandwidth. By using port or role assignments on the access layer switches, the architect can also implement 802.1X authentication without tunnelled node, which enables user access control and dynamic VLAN assignment based on user identity and device type. By extending the VLANs to the core, the architect can ensure that the wired users can reach the data center and other network resources through the Layer 3 switch connected to the firewall. References:

• Aruba 2930M Switch Series - Data sheet)
• Aruba ClearPass Policy Manager - Data sheet)
• ArubaOS-Switch Wired Access with ClearPass - Configuration guide)

The switch needs to support PoE+ for this deployment. PoE+ stands for Power over Ethernet Plus, and it is a technology that allows the switch to provide both data and power to the connected devices over a single Ethernet cable. This eliminates the need for separate power sources or adapters for the devices, and simplifies the installation and management of the network. PoE+ can provide up to 30 watts of power per port,which is sufficient for the Aruba 320 Series APs, which have a maximum power consumption of 20 watts. PoE+ also supports 1 GbE connectivity, which meets the customer’s requirement.

The other options are not relevant for this deployment:

• Option B is incorrect because LACP is not a feature that the switch needs to support for this deployment. LACP stands for Link Aggregation Control Protocol, and it is a protocol that allows multiple physical links to be combined into a single logical link, providing higher bandwidth and redundancy. However, the architect plans to connect each AP with one Ethernet port to the switch, so there is no need for link aggregation in this scenario.
• Option C is incorrect because port channel is not a feature that the switch needs to support for this deployment. Port channel is another term for link aggregation, which is not required for this scenario, as explained above.
• Option D is incorrect because Smart Rate is not a feature that the switch needs to support for this deployment. Smart Rate is a technology that allows the switch to provide multi-gigabit Ethernet speeds (up to 10 GbE) and PoE+ to the connected devices, depending on the cable type and length. However, the customer only wants to support at least 1 GbE connectivity, which can be achieved with PoE+ and CAT6 cable, without the need for Smart Rate.

References:

• Aruba 320 Series Access Points Data Sheet)
• ArubaOS-Switch and ArubaOS-CX Transceiver Guide)
• Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47))

A wide sector directional antenna is a type of antenna that radiates or receives radio waves in a sector-shaped pattern, covering a wide angle of a circle. The width of the sector is determined by the horizontal beamwidth (H-plane) of the antenna, while the height of the sector is determined by the vertical beamwidth (E-plane) of the antenna12. A wide sector directional antenna is usually used to provide regional coverage for wireless networks, such as Wireless Internet Service Providers (WISP) or similar applications2.

According to the antenna specifications given, Antenna 3 has the widest horizontal beamwidth of 100 degrees, which means it can cover a large sector of a circle. Antenna 4 has a narrower horizontal beamwidth of 60 degrees, which means it can cover a smaller sector of a circle. Antenna 1 and Antenna 2 have a horizontal beamwidth of 360 degrees, which means they are omnidirectional antennas, not directional antennas. Therefore, Antenna 3 is the best choice for the plan that specifies wide sector directional antennas.

References:

• 1: https://en.wikipedia.org/wiki/Sector_antenna
• 2: https://lcantennas.com/directional-antennas/

Jitter is the variation in the delay of packets arriving at the destination. It is caused by network congestion, routing changes, or other factors that affect the transmission quality. Jitter can affect the quality of VoIP calls, as it can cause gaps, distortion, or echo in the audio. According to the Aruba Validated Reference Design for Voice and Video over Wi-Fi, the recommended maximum jitter for VoIP calls is 30 ms. Therefore, a jitter of 100 ms would typically cause a poor experience for users.

The other options are incorrect because:

• A. The packet loss is the percentage of packets that are lost or discarded during transmission. Packet loss can affect the quality of VoIP calls, as it can cause missing or corrupted audio. However, according to the Aruba Validated Reference Design for Voice and Video over Wi-Fi, the recommended maximum packet loss for VoIP calls is 1 percent. Therefore, a packet loss of 0.3 percent would not typically cause a poor experience for users.
• B. The throughput is the amount of data that can be transferred per unit of time. Throughput can affect the quality of VoIP calls, as it determines the bandwidth available for the audio. However, according to the Aruba Validated Reference Design for Voice and Video over Wi-Fi, the typical throughput for VoIP calls is 64 Kbps. Therefore, a throughput of 67 Kbps would not typically cause a poor experience for users.
• C. The latency is the delay between the sender and the receiver of packets. Latency can affect the quality of VoIP calls, as it can cause delays or out-of-sync audio. However, according to the Aruba Validated Reference Design for Voice and Video over Wi-Fi, the recommended maximum latency for VoIP calls is 150 ms. Therefore, a latency of 100 ms would not typically cause a poor experience for users.

References:

• Aruba Validated Reference Design: Voice and Video over Wi-Fi - Chapter 2)
• Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47) - Chapter 7)

 Aruba Instant APs are a simple, easy to deploy, and cost-effective solution for small office buildings that need wireless access. Aruba Instant APs can form a self-organizing and self-healing mesh network that supports basic rogue AP detection and provides a stateful firewall with role-based policies. Aruba Instant APs do not require a separate controller or license, and can be managed from the cloud or a mobile app. Aruba remote APs are designed for branch or home offices that need to connect to a central controller over a WAN link. Aruba campus APs and a Virtual Mobility Controller are suitable for larger or more complex deployments that need more scalability and flexibility. Aruba campus APs and an Aruba 7005 Mobility Controller are also more expensive and require additional hardware and licensing. References: Aruba Instant Access Points), Aruba Validated Design: Campus Wireless LAN)

For a VHD wireless network at a large events venue, the architect should ensure that the DHCP and DNS servers are carrier-grade and support a low transaction time. This is because the DHCP and DNS servers are responsible for providing IP addresses and name resolution for the wireless devices, and they need to handle a high volume of requests and responses in a short time. A low transaction time reduces the latency and improves the user experience. A carrier-grade server is a server that meets the high standards of reliability, availability, and scalability required by telecom operators and service providers. A carrier-grade server can handle a large number of concurrent connections, provide redundancy and fault tolerance, and offer high performance and security.

Option A is incorrect because the DHCP server can support a high number of scopes with a /24 size, but this does not guarantee a low transaction time or a carrier-grade service. A scope is a range of IP addresses that the DHCP server can assign to the clients. A /24 size means that each scope can have up to 254 hosts. However, the number of scopes does not affect the speed or quality of the DHCP service. Option B is incorrect because a third-party firewall integrates with ClearPass to filter the guest user traffic, but this does not affect the DHCP and DNS services. A firewall is a device that monitors and controls the network traffic based on predefined rules. ClearPass is a network access control solution that provides secure authentication and policy enforcement. A firewall integration with ClearPass can enhance the security and visibility of the guest user traffic, but it does not improve the performance or reliability of the DHCP and DNS servers. Option C is incorrect because a domain CA is set up to deploy certificates to a high volume of guest devices, but this does not affect the DHCP and DNS services. A certificate authority (CA) is an entity that issues digital certificates that verify the identity and authenticity of the devices. A domain CA is a CA that is part of a domain and can issue certificates to the domain members. A certificate deployment is a process of distributing and installing the certificates to the devices. A certificate deployment can improve the security and trust of the wireless network, but it does not improve the speed or quality of the DHCP and DNS servers. References: Aruba Validated Design: Very High Density 802.11ac Networks), Aruba Validated Design: Campus Wired LAN), Aruba Validated Design: Guest Access)

 The correct answer is option C, voice. Voice applications have the greatest potential impact on RF design because they are sensitive to latency, jitter, and packet loss. Voice applications also require a minimum signal strength and signal-to-noise ratio to ensure good voice quality. Therefore, an architect needs to consider the number of voice devices, the codec used, the roaming behavior, and the call admission control when planning the RF coverage for voice applications. References: The information can be referenced from the official HPE documents and learning materials available on HPE Press and Aruba Networks. Specifically, it aligns with the objectives outlined in Chapter 3: Wireless LAN Technologies and Standards, where the RF design considerations for voice applications are discussed. Designing Aruba Solutions Official Certification Study Guide Aruba Mobility Fundamentals Guide

This answer is correct because it matches the scenario for which the Aruba backplane stacking technology is designed. Aruba backplane stacking technology allows up to 10 switches to be interconnected using high-speed backplane cables, creating a single logical device with a single IP address and configuration. This simplifies the management and operation of the network, as well as the redundancy design, as the stack can operate in ring or chain topology and provide fast failover in case of link or switch failure. This technology is suitable for customers who need to deploy a pair of aggregation switches in the same closet, as it reduces the number of devices and links to manage, and provides high availability and scalability for the network.

The other options are incorrect because:

• B. The customer needs to simplify the deployment of core switches which are located in different closets for redundancy purposes. This scenario is not suitable for Aruba backplane stacking technology, as it requires the switches to be physically close to each other and connected with backplane cables. A better option for this scenario would be to use Aruba Virtual Switching Framework (VSF) technology, which allows up to twoswitches to be interconnected using standard Ethernet links, creating a virtual switch that can span across different closets or racks.
• C. The customer needs to expand the network and make it possible for the current core switches to support more MAC forwarding and ARP entries. This scenario is not suitable for Aruba backplane stacking technology, as it does not increase the MAC or ARP table size of the switches. The MAC and ARP table size is determined by the hardware specifications of each switch model, and stacking them together does not change that. A better option for this scenario would be to upgrade the core switches to a higher-end model that supports more MAC and ARP entries, or to segment the network into smaller subnets to reduce the MAC and ARP traffic.
• D. The customer needs to deploy a switch at a branch office and have the switch automatically discover and join the network stack at the main office. This scenario is not suitable for Aruba backplane stacking technology, as it requires the switches to be on the same LAN and connected with backplane cables. A better option for this scenario would be to use Aruba Central, which is a cloud-based management platform that allows remote provisioning and monitoring of Aruba switches and other devices. Aruba Central can automatically discover and join the switch to the network, and apply the configuration and policies from the main office.

References:

• Aruba 2930M Switch Series - Data sheet)
• ArubaOS-Switch Virtual Switching Framework - Configuration guide)
• Aruba Central - Data sheet)

The maximum bandwidth possible between the aggregation and core layers using 8 strands of OM4 Multi-Mode fiber can be up to 200 Gbps1. This is because each strand of OM4 fiber can support up to 25 Gbps of bandwidth, and with 8 strands, the total bandwidth can reach up to 200 Gbps1. However, the actual bandwidth can be influenced by various factors such as the quality of the fiber, the type of transceivers used, and the distance between the aggregation and core layers1.

References:

• What is IP and Ethernet aggregation? - Ciena
• Aruba 5400R zl2 Switch Series Data Sheet
• Aruba 5400R zl2 Switch Series Installation and Getting Started Guide
• ArubaOS-Switch and ArubaOS-CX Transceiver Guide

ClearPass Access licenses are required for each unique endpoint that authenticates to ClearPass using any supported protocol, such as 802.1X, MAC authentication, web authentication, or VPN authentication1. ClearPass Onboard licenses are required for each unique endpoint that is provisioned with a certificate using the ClearPass Onboard service2. In this scenario, the customer has 900 employees and up to 30 guests a day, which means there are at most 930 users who need to authenticate to the network. Assuming each user has about two or three devices, the maximum number of devices that need Access licenses is 930 x 3 = 2790, which can be rounded up to 3000. The customer also wants to use certificates to authenticate user devices, which means they need Onboard licenses as well. However, the customer only issues laptops to the employees, which means only 900 devices need Onboard licenses. Therefore, the architect should include 3000 Access licenses and 1000 Onboard licenses in the proposal. References:

• 1: ClearPass Licensing Guide - Aruba
• 2: ClearPass Onboard Data Sheet - Aruba

 The number of devices used by each user is an important factor for creating the RF plan, as it affects the network capacity, bandwidth demand, and interference level. The architect should estimate the average number of devices per user and the types of applications they use, such as voice, video, or data. This will help the architect to determine the optimal number and placement of access points, the channel width and selection, the transmit power and data rates, and the radio resource management settings.

The OS used on wireless devices, whether BLE wayfinding is required, and the software version on MCs are not directly relevant for creating the RF plan, as they do not affectthe physical layer characteristics of the wireless network. However, they may have implications for other aspects of the network design, such as security, compatibility, and features.

References:

• RF Design | Validated Solution Guide - Aruba
• Enterprise Mobility 8.5 Design Guide - WLAN RF Design Considerations [Cisco 5500 Series Wireless Controllers] - Cisco

The customer needs a solution that can terminate VPN tunnels for Aruba RAPs, which are remote access points that connect to the corporate network over the Internet. The customer has only one public IP address, which means that they need to use NAT to forward the IPsec traffic to the device that will terminate the VPN tunnel. The customer also wants N+1 redundancy, which means that they need at least two devices that can act as backup for each other in case of failure.

The solution that meets the customer requirements is to use two Aruba MCs on the same subnet that use VRRP without clustering. VRRP stands for Virtual Router Redundancy Protocol, and it is a protocol that allows multiple devices to share a virtual IP address and act as a single gateway for the network. This way, the customer can use the virtual IP address as the public IP address for the NAT, and the IPsec traffic will be forwarded to the device that is the VRRP master. If the master device fails, the backup device will take over the role of the master and continue to terminate the VPN tunnels. This provides N+1 redundancy for the customer.

The other options are not suitable for the customer requirements:

• Option B is not suitable because a Layer 3 cluster requires two public IP addresses, one for each MC. The customer only has one public IP address, so they cannot use this option.
• Option C is not suitable because VRRP does not work across different subnets. The customer needs to have the MCs on the same subnet to use VRRP.
• Option D is not suitable because a Layer 2 cluster does not support NAT. The customer needs to use NAT to forward the IPsec traffic to the MCs.

References:

• Aruba Remote Access Point (RAP) Networks Validated Reference Design)
• Aruba Mobility Controller Virtual IP Configuration Guide)
• ArubaOS 8.5 User Guide)

whether the MC needs to support advanced 8.x features. This is because the Aruba 7000 Series MCs are based on the older hardware platform and can only run up to ArubaOS 6.5.x, while the Aruba 7200 Series MCs are based on the newer hardware platform and can run ArubaOS 8.x and above. ArubaOS 8.x introduces many advanced features, such as clustering, MultiZone, AirMatch, and dynamic segmentation, that are not supported by the Aruba 7000 Series MCs. Therefore, if the architect needs to design a solution that leverages these features, the Aruba 7200 Series MCs are the better choice.

Option A is incorrect because the number of wireless devices that the MC needs to support is not a key criteria to choose between the Aruba 7000 Series or 7200 Series MCs.Both series can support a similar number of devices, depending on the model and license.

Option B is incorrect because whether the MC needs to terminate VPN tunnels is not a key criteria to choose between the Aruba 7000 Series or 7200 Series MCs. Both series can terminate VPN tunnels, such as IPSec, GRE, and RAP, depending on the model and license.

Option C is incorrect because the need to deploy controllers in a cluster is not a key criteria to choose between the Aruba 7000 Series or 7200 Series MCs. Both series can participate in a cluster, as long as they run the same ArubaOS version and have the same license.

References: The information can be referenced from the official HPE documents and learning materials available on HPE Press and Aruba Networks. Specifically, it aligns with the objectives outlined in Chapter 6: Wireless Network Design, where the MC selection and ArubaOS 8.x features are discussed. Designing Aruba Solutions Official Certification Study Guide Aruba Mobility Controller Data Sheet ArubaOS 8.7 User Guide

According to the Aruba Validated Design: Campus Wireless LAN1, MCs that are in different subnets cannot form a cluster, which is a logical group of MCs that share the same configuration and provide redundancy and load balancing for each other. However, MCs that are in different subnets can still provide backup LMS (local mobility switch) functionality for each other’s APs. This means that if the primary MC that controls an AP fails, the AP can fail over to the backup MC that is in a different subnet. However, this failover is not stateful, meaning that the user sessions and firewall states are not preserved. Therefore, option D is the correct answer.

Option A is incorrect because the MCs can provide some level of redundancy for each other without being in the same subnet, as explained above. Option B is incorrect because VRRP is not required to provide redundancy for MCs that are in different subnets. VRRP is a protocol that provides redundancy for routers by creating a virtual router with a shared IP address. However, MCs do not act as routers, and they do not need a shared IP address to provide backup LMS functionality. Option C is incorrect because the MCs cannot be in a cluster if they are in different subnets, as explained above. Therefore, the cluster will not support any features, such as stateful failover, load balancing, or centralized configuration. References: Aruba Validated Design: Campus Wireless LAN)

it meets the customer’s requirements for wired network upgrade. By combining the switches in each Building 2 closet as a Virtual Switching Framework (VSF) fabric, the architect can reduce the number of logical devices within the network, simplifying management and reducing complexity, aligning with the goal of flattening architecture. Establishing two 10 GbE connections to the core per fabric ensures redundancy and resilience, maintaining connectivity even if one link fails, without necessitating additional cabling. This also provides sufficient bandwidth and scalability for the network traffic.

The other options are incorrect because:

• A. Using two additional 2930F switches to act as an aggregation layer for Building 2 adds another layer of devices and complexity to the network, contradicting the goal of flattening architecture. It also requires additional cabling and ports to connect the switches to the core and the access layer.
• B. Connecting each Building 2 switch directly to the core on a single fiber strand through the use of SFP±SR transceivers does not provide redundancy and resilience, as one link failure would disconnect the switch from the core. It also limits the bandwidth and scalability of the network, as each switch would have only one 10 GbE connection to the core.
• D. Extending additional fiber between the buildings so that each Building 2 switch can have a direct 10 GbE connection to the core requires recabling, which the customer wants to avoid. It also increases the cost and complexity of the network, as more fiber strands and ports would be needed.

References:

• Aruba 2930M Switch Series - Data sheet)
• Aruba Validated Reference Design: Campus Wired LAN - Chapter 3)
• ArubaOS-Switch Virtual Switching Framework - Configuration guide)

The Aruba SDN Controller is a software component that runs on the Mobility Master (MM) and provides centralized control and management of the network devices and applications that support the SDN services. The SDN Controller communicates with the network devices through the southbound interface (SBI) and exposes the northbound API (NBAPI) for the SDN applications to access the network resources and services1.

One of the SDN applications that can integrate with the Aruba SDN Controller is the Aruba UC and Collaboration Solution, which optimizes the performance and quality of Skype for Business traffic over the wireless network. The Aruba UC and Collaboration Solution consists of three components: the Aruba UC and Collaboration SDN Application, the Aruba UC and Collaboration Dashboard, and the Aruba UC and Collaboration Agent2.

The Aruba UC and Collaboration SDN Application is a software module that runs on the Skype for Business Front End Server and communicates with the Aruba SDN Controller through the NBAPI. The Aruba UC and Collaboration SDN Application monitors the Skype for Business sessions and events, and sends the relevant information to the Aruba SDN Controller, such as the user identity, device type, session type, codec, bandwidth, and quality of service (QoS) requirements2.

The Aruba UC and Collaboration Dashboard is a web-based graphical user interface that provides visibility and analytics of the Skype for Business sessions and events over the wireless network. The Aruba UC and Collaboration Dashboard connects to the Aruba SDN Controller through the NBAPI and displays the information collected by the Aruba UC and Collaboration SDN Application, such as the number of active sessions, session types, session quality, bandwidth consumption, and device distribution2.

The Aruba UC and Collaboration Agent is a software module that runs on the Mobility Controller (MC) and communicates with the Aruba SDN Controller through the SBI. The Aruba UC and Collaboration Agent receives the information from the Aruba UC and Collaboration SDN Application through the Aruba SDN Controller, and applies the appropriate QoS policies and actions on the wireless network, such as prioritizing the Skype for Business traffic, marking the DSCP values, reserving the bandwidth, and adjusting the airtime2.

To support high availability for the SDN services, the Aruba SDN Controller must be deployed in a redundant configuration, with a primary MM and a backup MM. The primary MM runs the active instance of the Aruba SDN Controller, while the backup MM runs the standby instance of the Aruba SDN Controller. The backup MM synchronizes the configuration and state information from the primary MM, and takes over the SDN Controller role in case of a failure or switchover of the primary MM1.

The other options do not provide high availability specifically for the SDN services, although they may provide redundancy for other aspects of the wireless network. A redundant master MC does not run the Aruba SDN Controller, and only provides backup for the master MC role, which is responsible for managing the configuration and licensing of the MCs in the network3. Backup controllers defined on the APs do not run the Aruba SDN Controller, and only provide backup for the local MC role, which is responsible for terminating and managing the APs in the network4. A cluster deployment for MCs does not run the Aruba SDN Controller, and only provides load balancing and fast failover for the APs in the network5.

References: 1: ArubaOS 8.7 User Guide - Aruba, Chapter 42: SDN Controller, pages 1049-1050. 2: Aruba UC and Collaboration Solution Guide - Aruba, Chapter 2: Aruba UC and Collaboration Solution Overview, pages 11-15. 3: ArubaOS 8.7 User Guide - Aruba, Chapter 2: ArubaOS Architecture, pages 25-26. 4: ArubaOS 8.7 User Guide - Aruba, Chapter 3: Configuring Controller Redundancy, pages 39-40. 5: ArubaOS 8.7 User Guide - Aruba, Chapter 4: Configuring Controller Clustering, pages 51-52.

The minimum acceptable signal for an active site survey depends on the type of applications and the data rates that the users require. For 802.11ac, which operates in the 5 GHz band, Aruba recommends a signal of -65 dBm or better for high-performance applications such as voice and video, and a signal of -72 dBm or better for basic applications such as Web and email1. These values are based on the receiver sensitivity of typical 802.11ac clients and the expected signal-to-noise ratio (SNR) for different modulation and coding schemes (MCS). A higher SNR means a higher data rate and a better user experience.

Therefore, the architect should look for a signal of -65 dBm in the 5 GHz band to determine the test AP range for 802.11ac, assuming that the users run high-performance applications. A signal of -75 dBm in the 5 GHz band might be too weak to support the desired data rates and quality of service. A signal of -65 dBm or -75 dBm in the 2.4 GHz band is irrelevant for 802.11ac, as it does not operate in that band.

References:

• Aruba Validated Reference Design: 802.11ac Networks
• Best Practices for Monitoring and Troubleshooting 802.11ac Networks