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)

ClearPass OnConnect is a feature of the ClearPass Policy Manager that allows wired authentication on switches that do not support 802.1X or RADIUS protocols. ClearPass OnConnect uses SNMP to monitor and control the switch ports based on the device profiles and policies defined in ClearPass12. ClearPass OnConnect can provide the following benefits for the customer:

• It can enable wired authentication without requiring any changes to the existing switch infrastructure or the end-user devices. This can save the customer’s budget and time, as well as minimize the network disruption and user impact.
• It can provide visibility and control over the wired devices, such as printers, IoT devices, and laptops, that connect to the network. ClearPass OnConnect can identify the device type, user role, and location, and apply the appropriate access policies based on the customer’s security and compliance requirements. For example, ClearPass OnConnect can allow only authorized devices and users to access certain network resources, or quarantine or block any unknown or non-compliant devices.
• It can integrate with the other components of the Aruba solution, such as the MCs, MMs, APs, AirWave, and ClearPass Guest, to provide a consistent and unified network management and security solution across the wired and wireless networks. For example, ClearPass OnConnect can leverage the device profiles and policies from ClearPass Guest, or share the network health and performance data with AirWave.

Therefore, by explaining this feature, the architect can justify the proposed solution and show how it can meet the customer’s needs and expectations for wired authentication, as well as wireless authentication.

References:

• 1: https://www.arubanetworks.com/techdocs/ClearPass/6.7/PolicyManager/index.htm#CPPM_UserGuide/Admin/OnConnect.htm
• 2: https://www.arubanetworks.com/assets/tg/TB_ClearPass_OnConnect.pdf

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))