HPE2-W09 Online Practice Questions and Answers

Correct Answer: A

A data center network is a network that connects servers, storage devices, and other devices within a data center. A campus network is a network that connects buildings and users within a campus area, such as a university or an enterprise. Data center network traffic flows are typically east-west, which means they are between servers or devices within the data center. This is because data center applications often require high-speed communication and data exchange between servers for processing, analysis, or backup. Campus network traffic flows are typically north-south, which means they are between users or devices and external networks, such as the Internet or a wide area network (WAN). This is because campus users often access online services or resources that are hosted outside the campus network12. Therefore, this is a valid difference between a typical data center network's requirements and a typical campus network's requirements.

Correct Answer: B

Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. VSX Inter-Switch Link (ISL) is a link between the two VSX switches that is used for both data plane and control plane traffic. It is not recommended to reserve the ISL for control plane traffic only, as this would limit the benefits of VSX and create suboptimal traffic forwarding1. Therefore, this is not a valid guideline for establishing a VSX ISL between two ArubaOS-CX switches.

Correct Answer: A

Automated provisioning of LAGs between AHV and VSX is an operation supported when Aruba Fabric Composer (AFC) is integrated with Nutanix. AFC is a tool that provides automation and orchestration for managing data center networks composed of ArubaOS-CX switches. AFC can integrate with various data center software such as VMware vSphere, Nutanix AHV, Microsoft Hyper-V, etc. AFC can discover, monitor, and configure Nutanix AHV clusters and hosts using REST APIs. AFC can also automate the provisioning of LAGs between AHV and VSX by creating VSX LAGs or MC-LAGs on the ArubaOS-CX switches and configuring the corresponding LAGs on the AHV hosts1.

Correct Answer: B

The ArubaOS-CX portfolio for data center networks consists of different switches for different roles. The Aruba 8400 switches are designed for the core and aggregation layers, while the Aruba CX 6300 and CX 6400 switches are designed for the leaf layer1. Therefore, deploying Aruba 8400 switches as data center leaf switches is not how you should position switches in the ArubaOS-CX portfolio for data center networks. Reference: https://www.arubanetworks.com/solutions/datacenter-modernization/

Correct Answer: B

Creating two configuration plans, one with the standard config and one with the device-specific settings, is not what you should do. NetEdit is a tool that allows you to manage and monitor multiple switches from a single interface1. It also provides a plan feature that lets you create containers to group devices and execute operations on them, such as deploying, committing, or rolling back device configuration or firmware1. However, you do not need to create two configuration plans for your scenario. You can create one configuration plan with the standard config and use variables to define the device-specific settings1. Variables are placeholders that can be replaced with different values for different devices1. This way, you can deploy a standard config with device-specific settings using one configuration plan1.

Correct Answer: B

Ring 1, instance 1: control VLAN: 1000protected VLANs: 51-135 Ring 1,Instance2: control VLAN: 1001 protected VLANs: 136-220 Ring 2, Instance 1: control VLAN: 1000 protected VLANs: 181 -200 Ring 2, Instance 2: control VLAN: 1003 protected VLANs: 201 -220 is not a valid design for the control and protected VLANs on the VSX fabric 1 switches for an Ethernet Ring Protection Switching (ERPS) solution. The control VLANs must be unique for each ring instance and must not overlap with any protected VLANs. In this design, the control VLAN 1000 is used for both ring 1 instance 1 and ring 2 instance 1, which can cause conflicts and errors. Also, the protected VLANs 181-220 are used for both ring instances on ring 2, which can cause loops and traffic duplication2.

Correct Answer: B

Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. VSX link-up delay is a feature that delays bringing downstream VSX links up, following a VSX device reboot or an ISL flap. This prevents traffic blackholing or loops due to transient conditions. The link-up delay timer is not only required when split-recovery is disabled. Split-recovery is another feature that prevents traffic blackholing or loops when the ISL link fails and then recovers. Split-recovery works by disabling the secondary VSX member's downstream links until it synchronizes with the primary member. However, split-recovery does not cover all scenarios where traffic blackholing or loops can occur, such as when both VSX members reboot simultaneously or when the ISL flaps rapidly. Therefore, it is recommended to configure the link-up delay timer even when split-recovery is enabled1. Therefore, this is not a valid guideline for configuring the switches' link-up delay settings.

Correct Answer: A

Split-recovery mode is a feature of ArubaOS-CX that prevents traffic loss when the ISL goes out-of-sync and keepalive subsequently fails12. This can happen if the ISL is restored after a failure but the VSX nodes are not synchronized. Split-recovery mode enables the secondary switch to restore its VSX LAGs after 10 keepalive packets are missed, approximately 10 seconds after keepalive goes down2. This avoids a split brain situation where both switches act as primary and forward traffic independently, causing loops and duplicate packets1. Therefore, disabling split-recovery mode is not a use case for preventing split brain situations, and the correct answer is yes. For more information on split-recovery mode and VSX, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet3 and the Virtual Switching Extension (VSX) Guide for your switch model2.

Correct Answer: B

Omit the device-specific settings from the configuration plan and include them in command scripts instead is not what you should do if you want to use NetEdit to manage ArubaOS-CX switches and deploy a standard config to the switches, but need the config to include a few device-specific settings such as hostname and IP address. This approach would require you to create separate command scripts for each switch, which can be tedious and error-prone. A better approach would be to use an auto config plan that uses scripts to customize the configuration for each switch based on variables such as serial number, MAC address, or user-defined parameters1.

Correct Answer: A

The ISL and keepalive goes down, and after a few seconds, the keepalive link restores. Switch-1 and Switch-2 remains up. The Split-recovery mode is enabled. In this case the secondary switch shutdowns SVIs when keepalive is restored is a correct description of how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios. VSX is a feature that provides active-active forwarding and redundancy for ArubaOS-CX switches. The ISL is the inter-switch link that connects two VSX nodes and carries data traffic. The keepalive link is a separate link that carries control traffic between two VSX nodes. The split-recovery mode is a feature that prevents split- brain scenarios when both VSX nodes lose connectivity with each other but remain up. When the ISL and keepalive goes down, both VSX nodes continue to forward traffic independently. When the keepalive link restores, the secondary switch detects that it has lost synchronization with the primary switch and shuts down its SVIs to prevent traffic loops 1.