HP HP Certifications HPE2-W09 Questions & Answers

• Question 41:

  Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric?

  Solution: You want an admin to manually fail traffic over to the secondary member if the primary member fails.

  A. Yes

  B. No

  Correct Answer: A

  Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. Split-recovery mode is a feature that prevents traffic loss when the Inter-Switch Link (ISL) goes outof-sync and keepalive subsequently fails. When split-recovery mode is enabled, the secondary VSX member disables its downstream links until it synchronizes with the primary member. When split-recovery mode is disabled, the secondary VSX member keeps its downstream links up even when it is out-of-sync with the primary member1. Disabling split-recovery mode is a use case for situations where you want an admin to manually fail traffic over to the secondary member if the primary member fails. This can be useful for planned maintenance or testing purposes, where you want to avoid automatic failover and failback of traffic. To manually fail traffic over to the secondary member, you need to shut down the ISL on both VSX members1. Therefore, this is a valid use case for disabling split-recovery mode on ArubaOS-CX switches in a VSX fabric.

• Question 42:

  Is this part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) solution?

  Solution: Implement Virtual Switching Extension (VSX) on pairs of ERPS switches at the same site.

  A. Yes

  B. No

  Correct Answer: A

  Implementing Virtual Switching Extension (VSX) on pairs of ERPS switches at the same site is part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) solution. VSX allows two switches to act as a single logical device and provide active-active forwarding across both switches. This way, traffic can be load balanced across all links in the ERPS ring without creating loops1.

• Question 43:

  Is this a requirement for implementing Priority Flow Control (PFC) on an ArubaOS-CX switch interface?

  Solution: configuring a DCBX application priority on the interface

  A. Yes

  B. No

  Correct Answer: A

  Priority Flow Control (PFC) is a feature of ArubaOS-CX that eliminates packet loss due to congestion on a network link1. PFC uses IEEE 802.1Qbb standard to pause traffic on a per-priority basis1. PFC can be configured to operate in symmetric or asymmetric mode1. Symmetric mode applies PFC to both the receiving and sending of pause frames1. Asymmetric mode applies PFC to either the receiving or sending of pause frames1. To configure PFC on an interface, you need to enable flow control with a priority value and configure a DCBX application priority on the interface1. A DCBX application priority maps a traffic class to a priority group and enables the switch to negotiate PFC parameters with the peer device1. Therefore, this is a requirement for implementing PFC on an ArubaOS-CX switch interface, and the correct answer is yes. For more information on PFC and DCBX, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet2 and the QoS Guide for your switch model1.

• Question 44:

  Is this a rule for configuring schedule profiles on an ArubaOS-CX switch?

  Solution: If the profile mixes strict priority scheduling with another scheduling algorithm, the strict priority queue must be the highest numbered queue.

  A. Yes

  B. No

  Correct Answer: A

  A schedule profile is a feature of ArubaOS-CX that determines the order and service of queues for transmission123. A schedule profile must be configured on every interface at all times23. The switch supports three scheduling algorithms: Guaranteed Minimum Bandwidth (GMB), Strict, and Strict EQS23. Strict scheduling gives absolute priority to a queue over other queues, regardless of the bandwidth allocation23. If the profile mixes strict priority scheduling with another scheduling algorithm, the strict priority queue must be the highest numbered queue23. Therefore, this is a rule for configuring schedule profiles on an ArubaOS-CX switch, and the correct answer is yes. For more information on schedule profiles and QoS, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet1 and the QoS Guide for your switch model23.

• Question 45:

  An ArubaOS-CX is \ssmq DCBX on Interface 1/1/1. You enter this command:

  show dcbx interface 1/1/1

  Is this where you can see whether the connected converged network adapter (CNA) has accepted the application priorities advertised with DCBX?

  Solution: in the Enhanced Transmission Selection (ETS) Local advertisement section

  A. Yes

  B. No

  Correct Answer: B

  In the Enhanced Transmission Selection (ETS) Local advertisement section is not where you can see whether the connected converged network adapter (CNA) has accepted the application priorities advertised with DCBX on an ArubaOS-CX switch interface. The ETS Local advertisement section shows the priority groups and bandwidth allocation that the switch advertises to the CNA, but it does not show whether the CNA has accepted them or not. To see whether the CNA has accepted the application priorities advertised with DCBX, you need to look at the Application Priority Local advertisement section, which shows the application protocol identifier (APPID) and priority values that the switch advertises to the CNA, and compare them with the Application Priority Remote advertisement section, which shows the APPID and priority values that the CNA advertises to the switch1.

• Question 46:

  A data center has a three-tier topology with ArubaOS-CX switches at each layer, is this a use case for implementing Virtual Switching Extension (VSX) at the core?

  Solution: The aggregation layer operates at Layer 2 only, and the core provides Layer 2 and Layer 3 functions.

  A. Yes

  B. No

  Correct Answer: B

  The aggregation layer operates at Layer 2 only, and the core provides Layer 2 and Layer 3 functions is not a use case for implementing Virtual Switching Extension (VSX) at the core for a data center that has a three-tier topology with ArubaOS-CX switches at each layer. VSX is a feature that provides active-active forwarding and redundancy for ArubaOS-CX switches. VSX can be implemented at any layer of the data center network, but it is more common to implement it at the aggregation or leaf layer, where it can provide Layer 2 and Layer 3 functions. The core layer typically operates at Layer 3 only and does not require VSX2.

• Question 47:

  Refer to the exhibit.

  

  You want to enable devices in VRF B and VRF C to reach shared resources in VRF A. is this a valid strategy for meeting this goal?

  Solution: Create a separate OSPF process for each VRF on Switch-1. Then redistribute each process into the other VRFs' processes.

  A. Yes

  B. No

  Correct Answer: B

  Create a separate OSPF process for each VRF on Switch-1. Then redistribute each process into the other VRFs' processes is not a valid strategy for meeting this goal of enabling devices in VRF B and VRF C to reach shared resources in VRF A. This strategy would create unnecessary complexity and overhead on Switch-1, and it would not guarantee optimal routing between the VRFs. A better strategy would be to use inter- VRF routing or route leaking on Switch-1, which allows direct communication between different VRFs without requiring redistribution1.

• Question 48:

  Is this a best practice when positioning ArubaOS-CX switches in data center networks? Solution: Deploy Aruba CX 83xx switches as data center spine switches.

  A. Yes

  B. No

  Correct Answer: A

  Deploy Aruba CX 83xx switches as data center spine switches is a best practice when positioning ArubaOS-CX switches in data center networks. The Aruba CX 83xx switches are designed for data center spine or core roles, and they provide high performance, scalability, and resiliency. They can support various data center network architectures such as leaf-spine, three-tier, or collapsed core1.

• Question 49:

  Is this correct positioning of AtubaOS-CX switches in the data center?

  Solution: Aruba CX 6300 switches are an appropriate choice for leaf switches in a leaf-spine topology that uses Virtual Extensible LAN (VXLAN) with Ethernet VPN (EVPN).

  A. Yes

  B. No

  Correct Answer: A

  Aruba CX 6300 switches are an appropriate choice for leaf switches in a leaf- spine topology that uses Virtual Extensible LAN (VXLAN) with Ethernet VPN (EVPN) is a correct positioning of ArubaOS-CX switches in the data center. The Aruba CX 6300 switches are designed for data center leaf roles, and they support advanced features such as VSX, EVPN, and PFC that enable high performance, scalability, and resiliency for data center networks1

• Question 50:

  Is this something that NetEdit 2.0 does after it discovers a switch? Solution: It enables SNMP on the switch, if disabled.

  A. Yes

  B. No

  Correct Answer: B

  NetEdit 2.0 is a network management tool that allows you to configure, monitor, and troubleshoot ArubaOS-CX switches. NetEdit 2.0 can discover switches using different methods, such as IP range scan, LLDP neighbors, or manual entry. After it discovers a switch, NetEdit 2.0 does not enable SNMP on the switch, if disabled. SNMP is a protocol that allows NetEdit 2.0 to collect information and statistics from the switches, but it is not required for discovery or management. NetEdit 2.0 can use other protocols, such as REST API or SSH, to communicate with the switches1. Therefore, this is not something that NetEdit 2.0 does after it discovers a switch.