HPE6-A47 Exam Dumps : Designing Aruba Solutions

The specifications for the AP models are in the format of Tx:Rx:SU-MIMO:MU-MIMO:MU-MIMO clients, where Tx is the number of transmit antennas, Rx is the number of receive antennas, SU-MIMO is the number of spatial streams supported in single-user MIMO mode, MU-MIMO is the number of spatial streams supported in multi-user MIMO mode, and MU-MIMO clients is the number of MU-MIMO clients that can be served simultaneously.

The customer requirements are:

• Support for MU-MIMO: This means the AP must have a MU-MIMO value greater than 1, as MU-MIMO is a technique that allows multiple spatial streams to be transmitted to different clients at the same time.
• Support for up to four spatial streams, both when MU-MIMO is used and when it is not used: This means the AP must have a SU-MIMO value and a MU-MIMO value of 4, as spatial streams are independent data streams that can be transmitted or received by an antenna.
• Support for transmissions to up to three MU-MIMO clients at the same time: This means the AP must have a MU-MIMO clients value of 3, as this indicates the maximum number of clients that can receive MU-MIMO transmissions from the AP at the same time.

Based on these criteria, only the AP 335 meets the customer requirements, as it has a specification of 4x4:4:4:4:3, which means it has 4 transmit and receive antennas, 4 spatial streams in both SU-MIMO and MU-MIMO modes, and can serve 3 MU-MIMO clients simultaneously. The AP 325 does not meet the customer requirements, as it has a specification of 4x4:4:4:3:3, which means it has only 3 spatial streams in MU-MIMO mode, and can only serve 2 MU-MIMO clients simultaneously.

References:

• Aruba AP-335 Wireless Access Point | Aruba
• Aruba AP-325 Wireless Access Point | Aruba
• Multi-User MIMO in WiFi 6 - Arista Networks

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