HP HPE6-A86 Practice Test Questions Answers

The correct answer is A. Disable SSH and HTTPS in the data plane. After connecting the out-of-band management, or OOBM, interface, management access should be restricted to the management plane rather than left available through user/data-plane interfaces. HPE Aruba Networking AOS-CX hardening guidance explains that the default VRF is associated with non-management interfaces, while the management VRF is associated with the dedicated management interface. It also lists SSH on TCP 22 and HTTPS/Web UI on TCP 443 as management services enabled by default. For hardening, if OOBM is being used, management services such as SSH and HTTPS should be disabled or restricted from the default/data VRF so users cannot manage the switch through production-facing ports. Option B is incorrect because disabling SSH and HTTPS in the management plane would remove the secure OOBM management path. Option C is incorrect because Telnet and HTTP are insecure protocols. Option D is incorrect because enabling SSH and HTTPS in the data plane increases the exposed management surface.

The correct answer is D. Allowed VLANs between access switches. The diagram shows Server-1 connected to Access-2 in VLAN 20 and PC-1 connected to Access-1. The inter-switch link between Access-1 and Access-2 is shown as a trunk carrying VLANs 1, 10, and 20. If users on Access-1 cannot reach Server-1 in VLAN 20 after a recent change, while devices directly connected to Access-2 are not affected, the most likely issue is that VLAN 20 is not being correctly carried across the trunk between the access switches. HPE Aruba Networking AOS-CX documentation states that vlan trunk allowed defines which VLAN traffic is allowed across a trunk interface. It also explains that allowed VLANs are the VLANs that can be transported by the trunk; if a required VLAN is missing from the allowed list, that VLAN’s traffic will not traverse the trunk. Option A is less likely because devices directly connected to Access-2 can access Server-1, indicating Server-1’s local VLAN placement is probably correct. Option B is unlikely because a down trunk would affect more VLANs than just access to VLAN 20. Option C is not supported by the symptom pattern.

The correct matches are based on the high-availability technologies supported by each CX switch family in the answer list. HPE Aruba Networking AOS-CX VSF documentation states that VSF supports up to 8-member stacks for CX 6200F devices and up to 10-member stacks for CX 6300 devices. That makes CX 6200 match “VSF - 8 members” and CX 6300 match “VSF - 10 members.” HPE Aruba Networking documentation for VSX support lists the CX 8100 as a VSX-supported switch series, so CX 8100 matches “VSX.” The CX 6100 and CX 4100i do not match the listed VSF 8-member, VSF 10-member, or VSX choices. Although AOS-CX VSF documentation lists other VSF limits for some platforms, the choices provided only include VSF-8, VSF-10, VSX, and None; therefore, CX 6100 and CX 4100i map to “None” in this drag-and-drop question.

The correct answer is A. Change the hash algorithm. In a LAG, traffic is not normally split packet-by-packet across every member link. Instead, the switch uses a hashing method to choose which physical interface in the aggregate should transmit each flow. The output shows that the current hash is l3-src-dst, which means the load-balancing calculation uses Layer 3 source and destination IP information. If many flows share the same source and destination IP pair, traffic can be unevenly distributed, causing one link to become congested while another link is lightly used. HPE Aruba Networking AOS-CX documentation states that the lacp hash command controls the selection of an interface in an aggregate group and supports Layer 2, Layer 3, and Layer 4 source/destination hash options. Changing the hash algorithm, for example to include Layer 4 source and destination TCP/UDP ports, can improve distribution when Layer 3 values alone are not diverse enough. Changing LACP mode, configuring static LAG, or changing LACP heartbeat rate would not directly fix uneven traffic distribution.

The correct answer is D. To configure a physical interface as a Layer 3 routed port on an HPE Aruba Networking CX 6300 switch, the interface must be placed in routing mode and assigned an IP address directly. This creates a routed interface rather than a bridged Layer 2 port. HPE Aruba Networking AOS-CX examples show routed physical interfaces configured with routing, followed by an ip address, and then no shutdown. The same examples contrast this with Layer 2 ports, which use no routing and VLAN commands such as vlan access or vlan trunk. Option A is incorrect because no routing makes the interface a Layer 2 interface, so assigning an IP address directly is not the correct routed-port configuration. Options B and C are incorrect because vlan access 1 configures the port as a bridged access port. The requirement specifically says the switch should be configured without a bridged port, so the correct CX configuration is a routed physical interface using routing with the IP address configured directly on the port.