HPE6-A47 Exam Dumps : Designing Aruba Solutions

 To ensure that wireless voice traffic is properly prioritized for Microsoft Skype for Business, the architect should set up firewall policies and SDN to mark voice on the MCs or MM. Firewall policies are used to classify and prioritize traffic based on the application, user role, device type, and location. SDN is used to integrate with the Skype for Business SDN API, which provides real-time information about voice and video sessions, such as source and destination IP addresses, ports, codecs, and quality metrics. By using firewall policies and SDN, the MCs or MM can dynamically mark voice traffic with the appropriate DSCP values and queue them in the highest priority queue on the wireless and wired network12.

The other options are not sufficient or relevant for ensuring wireless voice traffic prioritization for Skype for Business. Broadcast suppression combined with AirGroup is used to reduce the network overhead and improve the user experience for wireless devices that use multicast or broadcast protocols, such as Apple Bonjour or Microsoft UPnP3. Airtime Fairness set to fair-access is used to balance the airtime usage among clients with different capabilities and data rates, such as 802.11ac and 802.11n4. Voice-aware Layer 3 roaming is used to enable seamless handoff of voice sessions across different subnets without dropping the call5. While these features may enhance the overall wireless performance and reliability, they do not directly prioritize voice traffic for Skype for Business.

References:

• Aruba Validated Reference Design: 802.11ac Networks
• Aruba Validated Reference Design: Skype for Business
• Aruba Validated Reference Design: AirGroup
• Aruba Validated Reference Design: Adaptive Radio Management
• Aruba Validated Reference Design: Voice over Wireless LAN

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 customer needs to upgrade their wireless network, which has a single large building with four floors. The customer requires 30 APs on each floor, totaling 120 APs for the whole building. The customer also wants to use a MM-based architecture, and deployone Aruba 7030 MC on each floor, with the MCs combined in a cluster for seamless client failover and roaming. However, the proposed solution does not meet the customer’s requirements, because the Aruba 7030 MC does not support enough APs for the customer’s needs. Each Aruba 7030 MC can only support up to 64 APs, which means that deploying one on each floor would not be enough to support all the required APs. The architect should explain this limitation to the customer, and suggest a different solution that can support more APs, such as using a higher-capacity MC model, or deploying more MCs per floor.

References:

• Aruba 7000 Series Mobility Controllers Data Sheet)
• ArubaOS 8.5 User Guide)
• Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47))