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?

1. A. Create a physically routed interface in the subnet on the 6300M stack for each downstream switch.
2. B. Create an SVl in the subnet on each downstream switch
3. 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
4. D. Create an SVl in the subnet on the 6300M stack.

Correct Answer: D
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-overview.htm https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7295/cx-noscg/l3-routing/l3-routing-config.htm

Where are wireless client roaming decisions made?

1. A. Client device
2. B. Virtual Controller
3. C. Joint decision made by the origination and destination APs
4. D. Aruba Central

Correct Answer: A
Wireless client roaming decisions are made by the client device based on its own criteria, such as signal strength, noise level, data rate, etc. The network can influence the client??s roaming decision by providing information such as neighbor reports, load
balancing, band steering, etc., but the final decision is up to the client. References:https://www.arubanetworks.com/techdocs/Instant_86_WebHelp/Content/instan t-ug/wlan-roaming/client-roaming.htm

The customer has a requirement to create authorization policies for their users with Windows 10 clients, with a requirement Tor authorizing both device and user credentials within one Radius session.
What would be the correct solution for the requirement?

1. A. ClearPass 6.9 with EAP-TTLS
2. B. ClearPass 6.9 with EAP-TLS
3. C. ClearPass 6.9 with PEAP
4. D. ClearPass 6.9 with EAP-TEAP

Correct Answer: D
EAP-TEAP is a tunnel-based authentication method that supports both device and user authentication within a single RADIUS session. ClearPass 6.9 supports EAP-TEAP as anauthentication method for Windows 10 clients. References: https://www.arubanetworks.com/techdocs/ClearPass/6.9/Guest/Content/CPPM_UserGuide
/EAP-TEAP/EAP-TEAP.htm

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

Solution:
The OSI model divides the networking process into seven layers, each representing a different step of the transmission chain. Each layer has its own function and is responsible for well-defined tasks. User data passes sequentially from the highest layer down through the lower layers until the device transmits it externally. The lowest layer, the physical layer, converts the data into bits that can be sent over a physical medium. The second layer, the data link layer, organizes the bits into frames that can be transmitted over a link between two nodes. The third layer, the network layer, organizes the frames into packets that can be routed across a network of nodes. The fourth layer, the transport layer, organizes the packets into segments that can provide reliable and error-free communication between two end points12. References: 1 https://www.linode.com/docs/guides/introduction-to-osi- networking-model/ 2 https://en.wikipedia.org/wiki/OSI_model

Does this meet the goal?

1. A. Yes
2. B. No

Correct Answer: A

Which statement about manual switch provisioning with Aruba Central is correct?

1. A. Manual provisioning does not require DHCP and requires DNS
2. B. Manual provisioning does not require DHCP and does not require DNS
3. C. Manual provisioning requires DHCP and does not require DNS
4. D. Manual provisioning requires DHCP and requires DNS

Correct Answer: B
Manual provisioning is a method to add switches to Aruba Central without using DHCP or DNS. It requires the user to enter the switch serial number, MAC address, and activation code in Aruba Central, and then configure the switch with the same activation code and Aruba Central??s IP address. References:https://help.central.arubanetworks.com/latest/documentation/online_help/conte nt/devices/switches/provisioning/manual-provisioning.htm