Switch-1 and Switch-2 are AruDaOS-CX switches, which are part of a Virtual Switching Extension (VSX) fabric. Switch-2 is the primary member. Switch-2 experiences a power failure while Switch-1 remains up. Switch-2’s power recovers, and Switch-2 reboots.
Is this one of the things that happens when Switch-2 finishes booting? Solution: Switch-2 wails a period called the link-up delay before it enables Switched Virtual Interfaces (SVls) on its VSX LAGs.
- A . Yes
- B . No
A
Explanation:
Switch-2 waits a period called the link-up delay before it enables Switched Virtual Interfaces (SVIs) on its VSX LAGs is a true statement about what happens when Switch-2 experiences a power failure while Switch-1 remains up and then recovers. Switch-1 and Switch-2 are ArubaOS-CX switches, which are part of a Virtual Switching Extension (VSX) fabric. VSX is a feature that provides active-active forwarding and redundancy for ArubaOS-CX switches. The link-up delay timer defines how long a VSX node waits before advertising link state changes to its peer node. This allows the node to synchronize its MAC forwarding, ARP, and routing tables with its peer node before sending or receiving traffic on the newly activated link1.
Refer to the exhibit.
which shows the topology tot an Ethernet Ring Protection Switching (ERPS) solution.
Is this a valid design for the control and protected VLANs on the VSX fabric 1 switches?
Solution: Ring l, instance 1:
control VLAN: 1000 protected VLANs: 51-135 Ring 1, Instance 2:
control VLAN: 1000 protected VLANs: 136-220 Ring 2, Instance 1: control VLAN:
1001 protected VLANs: 181 -200 Ring 2, Instance 2: control VLAN: 1001 protected
VLANs: 201 -220
- A . Yes
- B . No
A
Explanation:
Ring l, instance 1: control VLAN: 1000 protected VLANs: 51-135 Ring l, Instance2: control VLAN: 1001 protected VLANs: 136-220 Ring 2, Instance l: control VLAN: 1002 protected VLANs: l8l -200 Ring 2, Instance2: control VLAN: l003 protected VLANs:201 -220 is a valid design for the control and protected VLANs on the VSX fabric l switches for an Ethernet Ring Protection Switching (ERPS) solution. The control VLANs are unique for each ring instance and do not overlap with any protected VLANs. The protected VLANs are also unique for each ring instance and do not overlap with any control VLANs2.
Is this a difference between a typical data center network’s requirements and a typical campus network’s requirements? Solution: Data center network traffic flows are typically east-west whereas while campus networks experience more north-south traffic.
- A . Yes
- B . No
A
Explanation:
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.
Refer to the exhibits.
Is this how the switch handles the traffic?
Solution: A frame with destination MAC address, 00:50:56:15:16:28, arrives with a VLAN 10 tag on 1/1/1 on Switch-1. Switch-1 encapsulates the frame with VXLAN and an IP header destined to 192.168.1.2.
- A . Yes
- B . No
A
Explanation:
A frame with destination MAC address, 00:50:56:15:16:28, arrives with a VLAN 10 tag on 1/1/1 on Switch-1. Switch-1 encapsulates the frame with VXLAN and an IP header destined to 192.168.1.2 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 MAC and IP addresses of hosts connected to VTEPs. Switch-1 receives a frame with destination MAC address, 00:50:56:15:16:28, which belongs to VM-2 on Switch-3. Switch-1 learns from EVPN that VM-2 is reachable through VTEP 192.168.1.2, which is Switch-3’s loopback interface. Switch-1 encapsulates the frame with VXLAN and an IP header destined to 192.168.1.2 and sends it over the underlay network1.
Your task is to configure an EVPN solution for a dual-stack IPv4 and IPv6 protocol in the overlay networks. Is this statement about EVPN and IPv6 correct?
Solution: IPv6 protocol can be encapsulated in the underlay network’s IPv4 packets.
- A . Yes
- B . No
B
Explanation:
IPv6 protocol cannot be encapsulated in the underlay network’s IPv4 packets. EVPN is a protocol that provides layer 2 and layer 3 services over an IP network1. It uses VXLAN tunnels to encapsulate Ethernet frames in UDP packets and transport them across the underlay network1. The underlay network can use either IPv4 or IPv6 protocol, but it must match the protocol used by the VXLAN tunnels1. The statement is false because it implies that IPv6 protocol can be encapsulated in IPv4 packets, which is not possible.
Does this correctly describe Network Analytics Engine (NAE) limitations on ArubaOS-CX switches?
Solution: You can run NAE with VSX, but only the primary VSX member will actually run agents during normal operation.
- A . Yes
- B . No
A
Explanation:
Network Analytics Engine (NAE) is a built-in analytics framework for network assurance and remediation on ArubaOS-CX switches. NAE allows monitoring, troubleshooting, and proactive network management using scripts and agents. Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. You can run NAE with VSX, but only the primary VSX member will actually run agents during normal operation. The secondary VSX member will only run agents if the primary member fails or is rebooted1. Therefore, this correctly describes NAE limitations on ArubaOS-CX switches.
AtubaOS-CX switches are acting as Virtual Extensible LAN (VXLAN) Tunnel Endpoints (VTEPs) WITHOUT Ethernet VPN (EVPN).
Does this correctly describe how the VTEPs handle VXLAN traffic forwarding?
Solution: VTEPs that use headend replication forward broadcast as multicast to each VTEP in the same VNI.
- A . Yes
- B . No
A
Explanation:
VXLAN is a tunneling protocol that encapsulates layer 2 traffic over an IP network using VXLAN Network Identifiers (VNIs) to identify different layer 2 segments. VXLAN Tunnel Endpoints (VTEPs) are devices that perform the encapsulation and decapsulation of VXLAN packets. VTEPs can use different methods to handle broadcast, unknown unicast, and multicast (BUM) traffic within a VNI. One of these methods is headend replication, which means that the VTEP that receives a BUM packet replicates it and sends it as a unicast to each remote VTEP in the same VNI1. This method does not require multicast routing in the underlay network, but it can increase the load on the ingress VTEP. Therefore, this correctly describes how the VTEPs handle VXLAN traffic forwarding without EVPN.
Does this correctly describe the ArubaOS-CX architecture?
Solution: The AtubaOS-CX software is based on the ArubaOS-Switch software and adds data center features.
- A . Yes
- B . No
B
Explanation:
The ArubaOS-CX software is based on the ArubaOS-Switch software and adds data center features is not a correct description of the ArubaOS-CX architecture. The ArubaOS-CX software is a new operating system that is designed for data center and campus networks. It is not based on the ArubaOS-Switch software, which is used for legacy campus switches. The ArubaOS-CX software provides advanced features such as VSX, EVPN, NAE, REST APIs, etc1.
Your task is to configure an EVPN solution for a dual-stack IPv4 and IPv6 protocol in the overlay networks. Is this statement about EVPN and IPv6 correct?
Solution: Different virtual MAC must be used for IPv4 and IPv6 Active Gateway.
- A . Yes
- B . No
B
Explanation:
Different virtual MAC must be used for IPv4 and IPv6 Active Gateway is not a true statement about EVPN and IPv6 for configuring an EVPN solution for a dual-stack IPv4 and IPv6 protocol in the overlay networks. Active Gateway is a feature that provides first-hop redundancy for hosts connected to VTEPs using anycast gateway addresses. Active Gateway can use the same virtual MAC address for both IPv4 and IPv6 protocols on the same VNI2.
Is this a guideline for establishing a Virtual Switching Extension (VSX) Inter-Switch Link (ISL) between two ArubaOS-CX switches?
Solution: Reserve the ISL for control plane traffic only.
- A . Yes
- B . No
B
Explanation:
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.
You want to use NetEdit to configure an AtubaOS-CX switch.
Is this a minimum requirement for setting up communications between the switch and NetEdit?
Solution: Enable the REST interface in read-only mode.
- A . Yes
- B . No
B
Explanation:
The solution is incorrect because enabling the REST interface in read-only mode is not a minimum requirement for setting up communications between the switch and NetEdit. NetEdit uses the REST interface to configure the switch, so it needs write access as well as read access. Therefore, enabling the REST interface in read-write mode is a minimum requirement for setting up communications between the switch and NetEdit.
You ate using NetEdit to manage AruDaOS-CX switches. You want to deploy a standard conflg to the switches, but need the config to include a few device-specific settings such as hostname and IP address.
Is this what you should do?
Solution: Instead of using a standard configuration plan to deploy the configuration, create an auto config plan that uses scripts.
- A . Yes
- B . No
A
Explanation:
Instead of using a standard configuration plan to deploy the configuration, create an auto config plan that uses scripts is 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. An auto config plan is a type of plan that allows you to use scripts to customize the configuration for each switch based on variables such as serial number, MAC address, or user-defined parameters1.
Refer to the exhibit.
The company wants AtubaOS-CX switches to provide VXLAN services for several VMs and servers, as shown in the exhibit. Hypervisors will not run VXLAN for this solution.
Is this part of a valid configuration to meet the requirements? Solution: Attach VNIs 5010 and 5020 to interface 1/1/3 on Switch-2.
- A . Yes
- B . No
B
Explanation:
Attach VNIs 5010 and 5020 to interface 1/1/3 on Switch-2 is not part of a valid configuration to meet the requirements for providing VXLAN services for several VMs and servers using ArubaOS-CX switches. VNIs are virtual network identifiers that are used to identify VXLAN segments. A VNI can only be attached to a VLAN interface, not a physical interface, on an ArubaOS-CX switch1.
Refer to the exhibit.
The company wants AtubaOS-CX switches to provide VXLAN services for several VMs and servers, as shown in the exhibit. Hypervisors will not run VXLAN for this solution.
Is this part of a valid configuration to meet the requirements?
Solution: Work with the server admins to assign a consistent VLAN for VMs 1 and 4.
Assign interface 1/1/2 on Switch-1 to the same VLAN.
- A . Yes
- B . No
A
Explanation:
Work with the server admins to assign a consistent VLAN for VMs 1 and 4. Assign interface 1/1/2 on Switch-1 to the same VLAN is part of a valid configuration to meet the requirements for providing VXLAN services for several VMs and servers using ArubaOS-CX switches. VMs 1 and 4 belong to the same VXLAN segment (VNI 5010), so they should be assigned to the same VLAN on their respective hypervisors. Interface 1/1/2 on Switch-1 should also be assigned to the same VLAN as VMs 1 and 4, so that Switch-1 can act as a VTEP for them1.
A customer’s servers use ISCSI, and they send data and storage traffic on the same pair of I OGbE links. Is this a best practice for supporting the ISCSI requirements?
Solution: Use Virtual Routing and Forwarding (VRF) to tunnel iSCSI traffic through the network spine on the same links that data traffic uses.
- A . Yes
- B . No
B
Explanation:
ISCSI is a protocol that allows storage devices to communicate over IP networks. ISCSI traffic has different requirements than data traffic, such as low latency, high throughput, and reliability. Therefore, it is not a best practice to send data and storage traffic on the same pair of 10GbE links, as this can cause congestion and performance degradation. It is also not a best practice to use Virtual Routing and Forwarding (VRF) to tunnel ISCSI traffic through the network spine on the same links that data traffic uses. VRF is a technology that creates multiple isolated Layer 3 domains on a physical network, each with its own routing table. VRF does not provide any benefits for ISCSI traffic, as it does not guarantee bandwidth, priority, or quality of service. VRF also adds overhead and complexity to the network configuration1. Therefore, this is not a valid way to support the ISCSI requirements.
Your customer is using Nutanix AHV and they need a network orchestration tool to simplify network provisioning.
Is this operation supported when Aruba Fabric Composer (AFC) is integrated with Nutanix?
Solution: Automated provisioning of LAGs Between AHV and VSX
- A . Yes
- B . No
A
Explanation:
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.
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 multi-chassis ones).
- A . Yes
- B . No
A
Explanation:
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.
Is this a difference between a typical data center network’s requirements and a typical campus network’s requirements?
Solution: Data center networks are typically less oversubscribed than campus networks.
- A . Yes
- B . No
A
Explanation:
Data center networks are typically less oversubscribed than campus networks is a difference between a typical data center network’s requirements and a typical campus network’s requirements. Oversubscription is the ratio of potential maximum demand to available capacity on a network link or device. Data center networks typically have higher bandwidth and lower latency requirements than campus networks, so they need to minimize oversubscription as much as possible1.
Is this a guideline for establishing a Virtual Switching Extension (VSX) Inter-Switch Link
(ISL) between two ArubaOS-CX switches?
Solution: Use the same speed on every link In the ISL.
- A . Yes
- B . No
A
Explanation:
The solution is correct because using the same speed on every link in the ISL is a guideline for establishing a VSX ISL between two ArubaOS-CX switches. Using the same speed on every link in the ISL ensures consistent performance and avoids potential issues with link aggregation. Therefore, using the same speed on every link in the ISL is a good practice for establishing a VSX ISL.
Refer to the exhibit.
which shows the topology tot an Ethernet Ring Protection Switching (ERPS) solution.
Is this a valid design for the control and protected VLANs on the VSX fabric 1 switches?
Solution: Ring 1, Instance 1:
control VLAN: 51 protected VLANs: 51-100 Ring 1, Instance 2:
control VLAN: 51 protected VLANs: 101-150 Ring 2, Instance 1: control VLAN: 181
protected VLANs: 181-200 Ring 2, Instance 2: control VLAN: 181 protected VLANs:
201-220
- A . Yes
- B . No
B
Explanation:
ERPS is a feature of ArubaOS-CX that prevents loops at layer 2 on ring networks1. ERPS uses a protocol called Ring Auto Protection Switching (RAPS) to detect link failures and perform fast traffic switchover1. ERPS supports multiple rings and multiple instances per ring1. Each instance has a control VLAN and one or more protected VLANs1. The control VLAN carries the RAPS PDUs and must be unique per ring1. The protected VLANs are the user traffic VLANs that are protected by ERPS and must be unique per instance1. Based on the exhibit, the design for the control and protected VLANs on the VSX fabric 1 switches is not valid. The control VLAN 51 is used for both instances 1 and 2 on ring 1, which violates the rule that the control VLAN must be unique per ring1. The protected VLANs 51-100 and 101-150 are also overlapping with the control VLAN 51, which violates the rule that the protected VLANs must be unique per instance1. Therefore, this is not a valid design for the control and protected VLANs on the VSX fabric 1 switches, and the correct Answer is no. For more information on ERPS and VLANs, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet2 and the ERPS Guide for your switch model1.
Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric?
Solution: In situations in which the primary switch fails and then reboots, you want to make the primary switch take over again as the primary switch.
- A . Yes
- B . No
B
Explanation:
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 out-of-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 does not affect how the primary switch takes over again as the primary switch after a failure and reboot. The primary switch always takes over as the primary switch when it comes back online, regardless of the split-recovery mode setting. Therefore, this is not a use case for disabling split-recovery mode on ArubaOS-CX switches in a VSX fabric.
Is this a guideline for establishing a Virtual Switching Extension (VSX) Inter-Switch Link (ISL) between two ArubaOS-CX switches?
Solution: Use a link aggregation with multiple 40GbE links or multiple 100GbE links.
- A . Yes
- B . No
A
Explanation:
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 recommended that the ISL link is a link aggregation with multiple 40GbE links or multiple 100GbE links to provide redundancy and bandwidth1. Therefore, this is a valid guideline for establishing a VSX ISL between two ArubaOS-CX switches.
Is this a use case for deploying Ethernet Ring Protection Switching (ERPS)?
Solution: connecting multiple data centers at Layer 2 while minimizing the number of dark fiber connections required
- A . Yes
- B . No
A
Explanation:
Connecting multiple data centers at Layer 2 while minimizing the number of dark fiber connections required is a use case for deploying Ethernet Ring Protection Switching (ERPS). ERPS is a feature that provides loop prevention and fast convergence for Layer 2 networks that use ring topologies. ERPS can be used to connect multiple data centers at Layer 2 using fewer fiber connections than traditional mesh topologies1.
Does this correctly describe NetEdit’s notification capabilities?
Solution: NetEdlt can send an error link to admins through ServlceNow.
- A . Yes
- B . No
A
Explanation:
NetEdit is a network management tool that allows you to configure, monitor, and troubleshoot ArubaOS-CX switches. NetEdit can send notifications of changes in network conditions to other services, such as ServiceNow, using methods that define the service type and credentials. ServiceNow is a cloud-based platform that provides IT service management and digital workflows. NetEdit can send an error link to admins through ServiceNow, which allows them to view the details of the error and take actions to resolve it 1. Therefore, this correctly describes NetEdit’s notification capabilities.
Does this correctly describe how Network Analytics Engine (NAE) agents work?
Solution: Agents write data to the switch’s current state database.
- A . Yes
- B . No
A
Explanation:
Agents write data to the switch’s current state database is a correct description of how Network Analytics Engine (NAE) agents work. NAE agents are scripts that run on ArubaOS-CX switches and collect data from various sources such as CLI commands, REST APIs, SNMP queries, etc. The agents write the collected data to the switch’s current state database (CSDB), which stores information about the switch’s
configuration, status, and performance1.
Does this correctly describe Network Analytics Engine (NAE) limitations on ArubaOS-CX switches?
Solution: Different switches have different limitations for the number of NAE scripts, monitors, and agents supported.
- A . Yes
- B . No
A
Explanation:
Different switches have different limitations for the number of NAE scripts, monitors, and agents supported is a correct description of Network Analytics Engine (NAE) limitations on ArubaOS-CX switches. NAE is a feature that provides automation and analytics for managing ArubaOS-CX switches. NAE scripts are scripts that run on switches and collect data from various sources. NAE monitors are rules that define conditions and actions for NAE agents. NAE agents are instances of NAE scripts and monitors that run on switches. Different switches have different limitations for the number of NAE scripts, monitors, and agents supported depending on their hardware resources1.
Does this correctly describe NetEdit’s notification capabilities?
Solution: NetEdit notifies admins of errors using Its Internal email server.
- A . Yes
- B . No
B
Explanation:
NetEdit is a network management tool that allows you to configure, monitor, and troubleshoot ArubaOS-CX switches. NetEdit can send notifications of changes in network conditions to other services, such as email, using methods that define the service type and credentials. However, NetEdit does not use its internal email server to send notifications. NetEdit requires an external SMTP server to send email notifications, and the SMTP server address, port, username, and password must be configured in the email method1. Therefore, this does not correctly describe NetEdit’s notification capabilities.
Is this how you should position switches in the ArubaOS-CX portfolio for data center networks?
Solution: Deploy Aruba 8400 switches as data center leaf switches.
- A . Yes
- B . No
B
Explanation:
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/data-center-modernization/
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
B
Explanation:
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.
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
A
Explanation:
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.
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
A
Explanation:
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
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
B
Explanation:
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.
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
B
Explanation:
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.
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
B
Explanation:
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.
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
A
Explanation:
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.
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
A
Explanation:
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.
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
A
Explanation:
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.
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
A
Explanation:
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 out-of-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.
Is this a way that Virtual Switching Extension (VSX) differs from Virtual Switching Framework (VSF)?
Solution: VSX features a dual control plane while VSF features a single control plane.
- A . Yes
- B . No
A
Explanation:
VSX features a dual control plane while VSF features a single control plane. VSX and VSF are both high availability solutions that provide redundancy and load balancing across a pair of switches1. However, VSX features a dual control plane, which means that each switch has its own independent configuration and state information1
. VSF features a single control plane, which means that one switch acts as the commander and synchronizes the configuration and state information to the other switch1. The statement is true because it correctly describes the difference between VSX and VSF control planes.
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, create two VXLAN interfaces, one with ID 5010 and one with 1D 5020; both VXLAN interfaces should use 192.168.1.1 as the source IP address.
- A . Yes
- B . No
A
Explanation:
VXLAN is a feature of ArubaOS-CX that provides layer 2 connectivity between networks across an IP network1. VXLAN uses a 24-bit identifier called VXLAN Network Identifier (VNI) to segment the layer 2 domain1. VXLAN also uses a tunnel endpoint (VTEP) to encapsulate and decapsulate VXLAN packets1. A VXLAN interface is a logical interface that represents a VNI and is associated with a source IP address and a VRF1. To set up VXLAN without EVPN, you need to create VXLAN interfaces on each switch and configure static VTEP peers1. Based on the exhibit, Switch-1 needs to create two VXLAN interfaces, one with ID 5010 and one with ID 5020, to match the VNIs of the servers connected to it. Both VXLAN interfaces should use 192.168.1.1 as the source IP address, which is the loopback interface of Switch-1. Therefore, this is part of the process for setting up VXLAN to meet the requirements, and the correct Answer is yes. For more information on VXLAN and EVPN, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet2 and the EVPN VXLAN Guide for your switch model1.
Is this a requirement for implementing Priority Flow Control (PFC) on an ArubaOS-CX switch interface?
Solution: configuring trust of Cos on the interface
- A . Yes
- B . No
A
Explanation:
Configuring trust of CoS on the interface is a requirement for implementing Priority Flow Control (PFC) on an ArubaOS-CX switch interface. PFC is a feature that allows a switch to pause traffic on a per-class basis using IEEE 802.1Qbb frames. To use PFC, the switch must trust the CoS values in the incoming frames and map them to priority groups and queues1.
You are configuring Ethernet Ring Protection Switching (ERPS) on an ArubaOS-CX switch. Is this a guideline for configuring timers?
Solution: The guard interval is set in units of seconds and is used to prevent frequent topology changes due to a link going up and down.
- A . Yes
- B . No
B
Explanation:
The guard interval is set in units of seconds and is used to prevent frequent topology changes due to a link going up and down is not a guideline for configuring timers for Ethernet Ring Protection Switching (ERPS) on an ArubaOS-CX switch. The guard interval is set in units of milliseconds, not seconds, and it is used to prevent false ring failures due to short link outages or flapping1.
Is this part of the process for using NetEdit to update firmware on ArubaOS-CX switches?
Solution: Use a firmware update plan to manage both updating the Image on selected devices and reboot.
- A . Yes
- B . No
A
Explanation:
Use a firmware update plan to manage both updating the Image on selected devices and reboot is part of the process for using NetEdit to update firmware on ArubaOS-CX switches. NetEdit is a tool that provides automation and analytics for managing ArubaOS-CX switches. A firmware update plan is a type of plan that allows you to update the firmware image on one or more switches and reboot them as needed1.
Is this a way that a data center technology can help meet requirements for multi-tenancy?
Solution: Virtual Extensible LAN (VXLAN) enables multiple isolated Layer 3 domains, each with its own routing table, to share a physical network.
- A . Yes
- B . No
B
Explanation:
Virtual Extensible LAN (VXLAN) enables multiple isolated Layer 3 domains, each with its own routing table, to share a physical network is not a way that a data center technology can help meet requirements for multi-tenancy. Multi-tenancy is the ability to provide logical separation and isolation of network resources for different tenants or customers on a shared physical infrastructure. VXLAN is a feature that provides Layer 2 extension over Layer 3 networks using UDP encapsulation. VXLAN does not enable multiple isolated Layer 3 domains, but rather multiple isolated Layer 2 domains, each with its own VNI1.