HP HPE2-W09 Practice Test - Questions Answers, Page 3

List of questions
Question 21

Refer to the exhibits.
Is this how the switch-1 handles the traffic?
Solution: A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN10. except the incoming interface. It replicates the broadcast, encapsulates each broadcast with VXLAN. and sends the VXLAN traffic to 192.168.1.2 and 192.168.1.3.
A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN10, except the incoming interface. It replicates the broadcast, encapsulates each broadcast with VXLAN, and sends the VXLAN traffic to 192.168.1.2 and 192.168.1.3 is a correct explanation of how the switch handles the traffic. Switch-1, Switch-2, and Switch-3 are ArubaOS-CX switches that use VXLAN and EVPN to provide Layer 2 extension over Layer 3 networks. VXLAN is a feature that uses UDP encapsulation to tunnel Layer 2 frames over Layer 3 networks using VNIs. EVPN is a feature that uses BGP to advertise multicast information for VXLAN networks using IMET routes. Switch-1 receives a broadcast in VLAN 10, which belongs to VNI 5010. Switch-1 forwards the frame on all interfaces assigned to VLAN 10, except the incoming interface, as per normal Layer 2 switching behavior. Switch-1 replicates the broadcast, encapsulates each broadcast with VXLAN, and sends the VXLAN traffic to both 192.168.1.2 and 192.168.1.3, which are Switch-3's and Switch-2's loopback interfaces respectively.
Question 22

Refer to the exhibits.
Is this how the switch-1 handles the traffic?
Solution: A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN 10, except the incoming interface. It encapsulates the broadcast with VXIAN and sends it to 192.168.1.3, out not 192.168.1.2.
A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN 10, except the incoming interface. It encapsulates the broadcast with VXLAN and sends it to 192.168.1.3, but not 192.168.1.2 is not a correct explanation of how the switch handles the traffic. Switch-1, Switch-2, and Switch-3 are ArubaOS-CX switches that use VXLAN and EVPN to provide Layer 2 extension over Layer 3 networks. VXLAN is a feature that uses UDP encapsulation to tunnel Layer 2 frames over Layer 3 networks using VNIs. EVPN is a feature that uses BGP to advertise multicast information for VXLAN networks using IMET routes. Switch-1 receives a broadcast in VLAN 10, which belongs to VNI 5010. Switch-1 forwards the frame on all interfaces assigned to VLAN 10, except the incoming interface, as per normal Layer 2 switching behavior. However, Switch-1 does not encapsulate the broadcast with VXLAN and send it only to 192.168.1.3, which is Switch-2's loopback interface, but rather replicates the broadcast, encapsulates each broadcast with VXLAN, and sends the VXLAN traffic to both 192.168.1.2 and 192.168.1.3, which are Switch-3's and Switch-2's loopback interfaces respectively.
Question 23

Is this part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) ring?
Solution: Combine multiple links between two data centers into link aggregations (but not multichassis ones).
Combine multiple links between two data centers into link aggregations (but not multi-chassis ones) is part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) ring. ERPS is a feature that provides loop prevention and fast convergence for Layer 2 networks that use ring topologies. ERPS can support link aggregation groups (LAGs) between two nodes in a ring as long as they are not multi-chassis LAGs (MC-LAGs). MC-LAGs are not supported by ERPS because they can create loops in the ring topology.
Question 24

Is this part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection
Switching (ERPS) ring?
Solution: Implement Virtual Switching Extension (VSX) on pairs of ERPS switches at the same site.
Then combine multiple links between two data centers into VSX LAGs (M-LAGs).
Implement Virtual Switching Extension (VSX) on pairs of ERPS switches at the same site. Then combine multiple links between two data centers into VSX LAGs (MC-LAGs) is not part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) ring. ERPS is a feature that provides loop prevention and fast convergence for Layer 2 networks that use ring topologies. VSX is a feature that provides active-active forwarding and redundancy for ArubaOSCX switches. VSX LAGs or MC-LAGs are LAGs that span across two VSX nodes and provide load balancing and resiliency. However, VSX LAGs or MC-LAGs are not supported by ERPS because they can create loops in the ring topology. A better way to load share traffic across the links in an ERPS ring would be to use link aggregation groups (LAGs) between two nodes in a ring as long as they are not multi-chassis LAGs (MC-LAGs)1.
Question 25

Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios?
Solution: The ISL and keepalive goes down, and after a few seconds, the keepalive link restores.
Switch-l and Switch-2 remains up. The Split-recovery mode is enabled. In this case the secondary switch shutdowns SVls when keepalive is restored.
Question 26

Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios?
Solution: The keepalive goes down, ISL link remains up. Switch-1 and Switch-2 remains up. The Splitrecovery mode is disabled. In this case the secondary switch shutdowns Svls.
Question 27

Refer to the exhibit.
You need to set up an ArubaOS-CX switch to implement Virtual Extensible LAN (VXLAN) WITHOUT Ethernet VPN (EVPN). The exhibit Indicates which servers should be part of the same VXLANs and the desired VNls for the VXLANs. Assume that the network is already configured to permit each ArubaOS-CX switch to reach each other switch's loopback interface.
Is this part of the process for setting up VXLAN to meet the requirements?
Solution: On Switch-1, set 192.168.1.3 as a peer IP address in the VNI 5020 context.
Question 28

Is this a use case for implementing Enhanced Transmission Selection (ETS) on an ArubaOS-CX switch?
Solution: to help the switch to look inside tunneled traffic and apply different quality of service (QoS) settings to different types of traffic
Question 29

Is this a use case for implementing Enhanced Transmission Selection (ETS) on an ArubaOS-CX switch?
Solution: ensures a minimum bandwidth guarantee between two endpoints traffic with various 802.1 p values.
Question 30

You are configuring Ethernet Ring Protection Switching (ERPS) on an ArubaOS-CX switch. Is this a guideline for configuring timers?
Solution: The wait to restore timer (WTR) Is set in units of minutes; you can set it to prevent frequent topology changes due to a link going up and down.
Question