HPE6-A47 Exam Dumps : Designing Aruba Solutions

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)

the new 802.11ac deployment should have a capacity-based design for the best performance, but the existing deployment sounds like a coverage-based design. This is because a capacity-based design takes into account the number and type of clients, the applications they use, and the bandwidth they require. A coverage-based design only considers the signal strength and the absence of coverage holes. A site survey is desirable to determine the optimal locations for the new APs because it can help the architect to assess the current and future capacity needs, identify the sources of interference and noise, and optimize the channel and power settings for the new APs.

Option A is incorrect because an 802.11ac deployment does not necessarily work better with side-mounted APs. The mounting location of the APs depends on the antenna type, the ceiling height, and the RF environment.

Option C is incorrect because 802.11ac AP radios are not more sensitive to 2.4 GHz interference than 802.11n APs. In fact, 802.11ac APs operate in the 5 GHz band, which is less crowded and prone to interference than the 2.4 GHz band.

Option D is incorrect because 802.11ac APs cannot support a higher density of clients by being deployed farther apart. On the contrary, 802.11ac APs need to be deployed closer together to provide the higher data rates and throughput that 802.11ac clients expect.

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 4: Wireless LAN Design, where the capacity-based design and site survey methods are discussed. Designing Aruba Solutions Official Certification Study Guide Aruba Mobility Fundamentals Guide

 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