Free HP HPE6-A85 Übungsprüfungen - Seite 3 von 5

Question #21

What is the ideal Aruba access switch for a cost-effective connection to 200-380 clients, printers and APs per distribution rack?

A . Aruba CX 6400
B . Aruba CX 6200
C . Aruba CX 6300
D . Aruba CX 6000

Lösung einblenden Lösung ausblenden

Richtige Antwort: C
C

Explanation:

The ideal Aruba access switch for a cost-effective connection to 200-380 clients, printers and APs per distribution rack is the Aruba CX 6200. This switch series is a cloud-manageable, stackable access switch series that is ideal for enterprise branch offices and campus networks, as well as SMBs.

The CX 6200 series offers the following benefits:

– Enterprise-class connectivity: The CX 6200 series supports ACLs, robust QoS, and common protocols such as static and Access OSPF routing.

– Power and speed for users and IoT: The CX 6200 series provides built-in 1/10GbE uplinks and 30W to 60W of Class 4 to Class 6 PoE for powering devices such as APs and cameras.

– Scalable growth made simple: The CX 6200 series supports Aruba Virtual Switching Framework (VSF) that allows you to quickly grow your network to eight members in a single stack using high-performance built-in 10G SFP ports.

– Management flexibility: The CX 6200 series supports a choice of management, including cloud-based and on-prem Central, CLI, switch Web GUI and programmability with AOS-CX operating system, and REST APIs.

The other options are not ideal because:

– Aruba CX 6400: This switch series is a high-availability modular switch series that is ideal for versatile edge access to data center deployments. It offers more performance, scalability, and modularity than the CX 6200 series, but it is also more expensive and complex to deploy and manage. It may not be cost-effective for connecting 200-380 clients per distribution rack.

– Aruba CX 6300: This switch series is a layer 3 stackable access and aggregation switch series that offers Smart Rate and High Power PoE. It offers more features and performance than the CX 6200 series, but it is also more expensive and may not be necessary for connecting 200-380 clients per distribution rack.

– Aruba CX 6000: This switch series is a layer 2 access switch series that offers PoE. It offers less features and performance than the CX 6200 series, and it does not support VSF stacking or routing protocols. It may not be sufficient for connecting 200-380 clients per distribution rack.

References:

https://www.arubanetworks.com/products/switches/access/

https://www.arubanetworks.com/products/switches/access/6200-series/

https://www.arubanetworks.com/products/switches/access/6400-series/

https://www.arubanetworks.com/products/switches/access/6300-series/

https://www.arubanetworks.com/products/switches/access/6000-series/

Question #21

What is the ideal Aruba access switch for a cost-effective connection to 200-380 clients, printers and APs per distribution rack?

A . Aruba CX 6400
B . Aruba CX 6200
C . Aruba CX 6300
D . Aruba CX 6000

Lösung einblenden Lösung ausblenden

Richtige Antwort: C
C

Explanation:

The ideal Aruba access switch for a cost-effective connection to 200-380 clients, printers and APs per distribution rack is the Aruba CX 6200. This switch series is a cloud-manageable, stackable access switch series that is ideal for enterprise branch offices and campus networks, as well as SMBs.

The CX 6200 series offers the following benefits:

– Enterprise-class connectivity: The CX 6200 series supports ACLs, robust QoS, and common protocols such as static and Access OSPF routing.

– Power and speed for users and IoT: The CX 6200 series provides built-in 1/10GbE uplinks and 30W to 60W of Class 4 to Class 6 PoE for powering devices such as APs and cameras.

– Scalable growth made simple: The CX 6200 series supports Aruba Virtual Switching Framework (VSF) that allows you to quickly grow your network to eight members in a single stack using high-performance built-in 10G SFP ports.

– Management flexibility: The CX 6200 series supports a choice of management, including cloud-based and on-prem Central, CLI, switch Web GUI and programmability with AOS-CX operating system, and REST APIs.

The other options are not ideal because:

– Aruba CX 6400: This switch series is a high-availability modular switch series that is ideal for versatile edge access to data center deployments. It offers more performance, scalability, and modularity than the CX 6200 series, but it is also more expensive and complex to deploy and manage. It may not be cost-effective for connecting 200-380 clients per distribution rack.

– Aruba CX 6300: This switch series is a layer 3 stackable access and aggregation switch series that offers Smart Rate and High Power PoE. It offers more features and performance than the CX 6200 series, but it is also more expensive and may not be necessary for connecting 200-380 clients per distribution rack.

– Aruba CX 6000: This switch series is a layer 2 access switch series that offers PoE. It offers less features and performance than the CX 6200 series, and it does not support VSF stacking or routing protocols. It may not be sufficient for connecting 200-380 clients per distribution rack.

References:

https://www.arubanetworks.com/products/switches/access/

https://www.arubanetworks.com/products/switches/access/6200-series/

https://www.arubanetworks.com/products/switches/access/6400-series/

https://www.arubanetworks.com/products/switches/access/6300-series/

https://www.arubanetworks.com/products/switches/access/6000-series/

Question #23

You are configuring a network with a stacked pair of 6300M switches used for distribution and layer 3 services. You create a new VLAN for users that will be used on multiple access stacks of CX6200 switches connected downstream of the distribution stack You will be creating multiple VLANs/subnets similar to this will be utilized in multiple access stacks

What is the correct way to configure the routable interface for the subnet to be associated with this VLAN?

A . Create a physically routed interface in the subnet on the 6300M stack for each downstream switch.
B . Create an SVl in the subnet on each downstream switch
C . Create an SVl in the subnet on the 6300M stack, and assign the management address of each downstream switch stack to a different IP address in the same subnet
D . Create an SVl in the subnet on the 6300M stack.

Lösung einblenden Lösung ausblenden

Richtige Antwort: D
D

Explanation:

The correct way to configure the routable interface for the subnet to be associated with this VLAN is to create an SVI Switched Virtual Interface (SVI) Switched Virtual Interface (SVI) is a virtual interface on a switch that represents a VLAN and provides Layer 3 routing functions for that VLAN. SVIs are used to enable inter-VLAN routing, provide gateway addresses for hosts in VLANs, apply ACLs or QoS policies to VLANs, etc. SVIs have some advantages over physical routed interfaces such as saving interface ports, reducing cable costs, simplifying network design, etc. SVIs are usually numbered according to their VLAN IDs (e.g., vlan 10) and assigned IP addresses within the subnet of their VLANs. SVIs can be created and configured by using commands such as interface vlan, ip address, no shutdown, etc. SVIs can be verified by using commands such as show ip interface brief, show vlan, show ip route, etc. in the subnet on the 6300M stack. An SVI is a virtual interface on a switch that represents a VLAN and provides Layer 3 routing functions for that VLAN. Creating an SVI in the subnet on the 6300M stack allows the switch to act as a gateway for the users in that VLAN and enable inter-VLAN routing between different subnets. Creating an SVI in the subnet on the 6300M stack also simplifies network design and management by reducing the number of physical interfaces and cables required for routing.

The other options are not correct ways to configure the routable interface for the subnet to be associated with this VLAN because:

– Create a physically routed interface in the subnet on the 6300M stack for each downstream switch: This option is incorrect because creating a physically routedinterface in the subnet on the 6300M stack for each downstream switch would require using one physical port and cable per downstream switch, which would consume interface resources and increase cable costs. Creating a physically routed interface in the subnet on the 6300M stack for each downstream switch would also complicate network design and management by requiring separate routing configurations and policies for each interface.

– Create an SVl in the subnet on each downstream switch: This option is incorrect because creating an SVI in the subnet on each downstream switch would not enable inter-VLAN routing between different subnets, as each downstream switch would act as a gateway for its own VLAN only. Creating an SVI in the subnet on each downstream switch would also create duplicate IP addresses in the same subnet, which would cause IP conflicts and routing errors.

– Create an SVl in the subnet on the 6300M stack, and assign the management address of each downstream switch stack to a different IP address in the same subnet: This option is incorrect because creating an SVI in the subnet on the 6300M stack, and assigning the management address of each downstream switch stack to a different IP address in the same subnet would not enable inter-VLAN routing between different subnets, as each downstream switch would still act as a gateway for its own VLAN only. Creating an SVI in the subnet on the 6300M stack, and assigning the management address of each downstream switch stack to a different IP address in the same subnet would also create unnecessary IP addresses in the same subnet, which would waste IP space and complicate network management.

References:

https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/index.html https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/cx-noscg/l3-routing/l3-routing-ov

https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/cx-noscg/l3-routing/l3-routing-co

Question #24

What can be done to dynamically set the PoE Priority on a switch port when deploying IP cameras APs. and other PoE devices?

A . Enable Quick PoE on the switch modules
B . Enable profiling for device provisioning
C . Configure PoE power management to Class-based Mode
D . Configure PoE power management to Dynamic Mode

Lösung einblenden Lösung ausblenden

Question #25

When using Aruba Central what can identify recommended steps to resolve network health issues and allows you to share detailed information with support personnel?

A . Overview Dashboard
B . OAlOps
C . Alerts and Events
D . Audit Trail

Lösung einblenden Lösung ausblenden

Question #26

A network technician at a branch office is connecting VolP phones to a newly configured AOS-CX switch. Users are complaining that voice quality is not as good as at the corporate office. Further investigation shows the local-priority value at the branch office is 1 while at the corporate office is 5.

What describes the issue regarding the default QoS behavior on the AOS-CX switch?

A . The QoS trust is set to DSCP by default, and the VolP phone’s local-priority value is mapped to 1.
B . The QoS trust is set to CoS by default, and the VolP phone’s local-priority value is mapped to 1.
C . The QoS trust is set to none by default, and each VolP phone’s local priority is configured for CoS map entry 1.
D . The QoS trust is set to none by default, and each VolP phone’s local priority is configured for CoS map entry 0.

Lösung einblenden Lösung ausblenden

Question #27

What does the status of "ALFOE" mean when checking LACP with "show lacp interfaces’"?

A . The interface on the local switch is configured as static-LAG
B . LACP is not configured on the peer side
C . LACP is in a synchronizing process
D . LACP is working fine with no problems

Lösung einblenden Lösung ausblenden

Question #28

You are in a meeting with a customer where you are asked to explain the network redundancy feature Multiple Spanning Tree (MSTP).

What is the correct statement for this feature?

A . MSTP configuration ID revision by default as current MSTP root priority
B . MSTP configuration ID name by default using switch IMC address
C . MSTP configuration ID name by default using switch serial number
D . MSTP configuration ID revision by default as switch serial number

Lösung einblenden Lösung ausblenden

Question #29

Which part of the WPA Key Hierarchy is used to encrypt and/or decrypt data“

A . Pairwise Temporal Key (PTK)
B . Pairwise Master Key (PMK)
C . Key Confirmation Key (KCK)
D . number used once (nonce)

Lösung einblenden Lösung ausblenden

Question #30

Match the phase of message processing with the Open Systems interconnection (OSl) layer.

Lösung einblenden Lösung ausblenden