CCNA Network Infrastructure and Connectivity Practice Test 20 — 15 Questions

Question 1

You are connected to R1 via console. R1 and R2 are directly connected via GigabitEthernet0/0. Your task is to configure IPv4 and IPv6 addressing on both routers so that they can ping each other's IPv4 and IPv6 addresses. The current configuration has intentional faults: R1's IPv4 subnet mask is incorrect, R2 is missing its default gateway, and R1's IPv6 address uses EUI-64 but is not working due to a duplicate IP. Correct the IPv4 mask on R1, assign a static IPv6 address on R2, and ensure both routers can reach each other.

Accepted Answer

On R1, change the IPv4 mask to 255.255.255.252; on R2, assign IPv4 address 192.0.2.2/30 and IPv6 address 2001:db8:1::2/64; configure a default route on R2 pointing to 192.0.2.1.. R1's IPv4 mask was /28, but the correct mask for the link should be /30 to avoid overlapping subnets (192.0.2.0/28 includes both .1 and .14, but they are on the same link). R2 had no IPv6 address configured. Additionally, R1's EUI-64 address was valid but R2 needed a static IPv6 address. The solution: on R1, change the mask to 255.255.255.252; on R2, assign an IPv4 address with mask /30 and a static IPv6 address 2001:db8:1::2/64; also add a default route on R2 pointing to 192.0.2.1 for IPv4. After these changes, both routers can ping each other's IPv4 and IPv6 addresses.

Answer

On R1, change the IPv4 mask to 255.255.255.0; on R2, assign IPv4 address 192.0.2.2/24 and IPv6 address 2001:db8:1::2/64; no default route needed.

Answer

On R1, change the IPv4 mask to 255.255.255.252; on R2, assign IPv4 address 192.0.2.2/28 and IPv6 address 2001:db8:1::2/64; configure a default route on R2 pointing to 192.0.2.1.

Answer

On R1, change the IPv4 mask to 255.255.255.252; on R2, assign IPv4 address 192.0.2.2/30 and IPv6 address 2001:db8:1::1/64; configure a default route on R2 pointing to 192.0.2.1.

Question 2

You are connected to R1. The network administrator has partially configured IPv4 and IPv6 on the interfaces. However, PC1 (connected to R1's G0/1) cannot reach PC2 (connected to R2's G0/1). Configure R1 and R2 so that PC1 can ping PC2. Fix any addressing errors. Use IPv4 subnet 192.0.2.0/30 for the link between R1 and R2, and 198.51.100.0/24 for the PC LANs. For IPv6, use 2001:db8:1::/64 on R1's G0/1 and 2001:db8:2::/64 on R2's G0/1, with R1's G0/1 using EUI-64 and R2's G0/1 using a static address 2001:db8:2::1/64.

Accepted Answer

On R1, change the subnet mask on G0/0 from /24 to /30. On R1 G0/1, issue 'ipv6 address 2001:db8:1::/64 eui-64' and 'no shutdown'. Enable 'ipv6 unicast-routing' globally on both routers.. The issue is a subnet mask mismatch on the link between R1 and R2: R1 uses /24 (255.255.255.0) while R2 uses /30 (255.255.255.252). This prevents R1 from having a route to R2's LAN. Fix R1's G0/0 mask to /30. Additionally, R1's G0/1 IPv6 EUI-64 command is missing the interface identifier; the correct command is 'ipv6 address 2001:db8:1::/64 eui-64' but the interface must be enabled with 'no shutdown'. Also ensure IPv6 unicast-routing is enabled. The PCs have correct gateways.

Answer

On R1, change the subnet mask on G0/0 from /24 to /30. On R1 G0/1, issue 'ipv6 address 2001:db8:1::/64 eui-64' and 'no shutdown'. No need to enable IPv6 unicast-routing because it is on by default.

Answer

On R1, change the subnet mask on G0/0 from /24 to /30. On R1 G0/1, issue 'ipv6 address 2001:db8:1::/64' (without eui-64) and 'no shutdown'. Enable 'ipv6 unicast-routing' globally on both routers.

Answer

On R1, change the subnet mask on G0/0 from /24 to /30. On R1 G0/1, issue 'ipv6 address 2001:db8:1::/64 eui-64' and 'no shutdown'. Enable 'ipv6 unicast-routing' globally on both routers. Also, change the default gateway on PC1 to 2001:db8:1::1.

Question 3

You are connected to R1. Configure IPv4 and IPv6 addressing on interfaces G0/0 and G0/1 so that R1 can reach R2's loopback0 (198.51.100.1/32) and R2 can reach R1's loopback0 (203.0.113.1/32). The current configuration has a wrong subnet mask on R1 G0/0 and a missing default gateway on R2, causing reachability failures. Additionally, configure IPv6 using EUI-64 on R1 G0/1 and static IPv6 on R2 G0/1 to enable IPv6 ping between the two routers. All devices are routers.

Accepted Answer

On R1 G0/0, change subnet mask to 255.255.255.252; on R2, add ip route 0.0.0.0 0.0.0.0 10.0.0.1; for IPv6, on R2 G0/1 change address to 2001:db8:1::2/64.. The primary IPv4 issues are a subnet mask mismatch on the point-to-point link and a missing default gateway on R2. On R1 G0/0, the mask is /24 instead of /30; while both routers can reach each other directly, the mismatched subnet mask causes routing inconsistencies because R1 advertises the link as a /24, potentially affecting routing decisions. Fixing the mask to /30 ensures both routers agree on the subnet. R2 lacks a route to R1's loopback and the 192.168.1.0/24 network, so a default route via 10.0.0.1 resolves reachability. For IPv6, R1 G0/1 uses EUI-64, and R2 G0/1 must be on the same subnet (2001:db8:1::/64); R2's address was incorrectly set to 2001:db8:2::2/64, so changing it to 2001:db8:1::2/64 enables IPv6 ping.

Answer

On R1 G0/0, change subnet mask to 255.255.255.0; on R2, add ip route 0.0.0.0 0.0.0.0 10.0.0.1; for IPv6, on R2 G0/1 change address to 2001:db8:1::2/64.

Answer

On R1 G0/0, change subnet mask to 255.255.255.252; on R2, add ip route 0.0.0.0 0.0.0.0 10.0.0.2; for IPv6, on R2 G0/1 change address to 2001:db8:2::2/64.

Answer

On R1 G0/0, change subnet mask to 255.255.255.252; on R2, add ip route 0.0.0.0 0.0.0.0 10.0.0.1; for IPv6, on R2 G0/1 change address to 2001:db8:1::2/64 and on R1 G0/1 use static IPv6 instead of EUI-64.

Question 4

You are connected to R1. The network has three routers: R1, R2, and R3. R1's G0/0 is connected to R2's G0/0, and R1's G0/1 is connected to R3's G0/1. The goal is to configure R1 so that it can ping both R2 (192.0.2.2/30) and R3 (2001:db8:1::2/64). Currently, R1 cannot ping R2 due to a wrong subnet mask on R1's G0/0, and R3 is using an IPv6 EUI-64 address but R1 has been given a static IPv6 address that conflicts. Fix both issues and verify connectivity.

Accepted Answer

On G0/0, change the subnet mask to 255.255.255.252; on G0/1, remove the static IPv6 address and configure an EUI-64 address.. The problem has two issues. First, R1's G0/0 has IP 192.0.2.1 but its subnet mask is incorrectly set to 255.255.255.0 (/24) instead of the required 255.255.255.252 (/30) that matches R2's /30. This mask mismatch causes R1 to misclassify the subnet, preventing successful ping to R2. The fix is to change the mask to 255.255.255.252. Second, R1's G0/1 is configured with a static IPv6 address 2001:db8:1::1/64, but R3 uses EUI-64 and generates its address as 2001:db8:1::2. This duplicate address risk breaks communication. The correct solution is to remove the static IPv6 address and enable EUI-64 on G0/1, allowing R1 to derive a unique address from the prefix. Options B and D incorrectly change R1's IPv4 address to 192.0.2.2, which duplicates R2's address. Option B also sets a static IPv6 address of ::2, duplicating R3's address. Option C changes the mask to /24, which would temporarily allow communication but violates the intended point-to-point /30 design and does not adopt best practices; it also incorrectly applies a static IPv6 address with EUI-64, which is unnecessary and could still conflict.

Answer

On G0/0, change the IP address to 192.0.2.2/30; on G0/1, change the IPv6 address to 2001:db8:1::2/64.

Answer

On G0/0, change the subnet mask to 255.255.255.0; on G0/1, change the IPv6 address to 2001:db8:1::1/64 with EUI-64.

Answer

On G0/0, change the IP address to 192.0.2.2/30; on G0/1, remove the static IPv6 address and configure an EUI-64 address.

Question 5

You are connected to R1. Configure IPv4 and IPv6 addressing on R1's GigabitEthernet0/0 and GigabitEthernet0/1 interfaces so that R1 can ping both R2's IPv4 address (203.0.113.2) and R2's IPv6 address (2001:db8:1::2). The current configuration has an incorrect subnet mask on G0/0, missing default gateway, and R1's G0/1 has a duplicate IPv4 address with R3. Also, use EUI-64 for IPv6 on G0/0 and static IPv6 assignment on G0/1. Ensure all issues are resolved and connectivity verified.

Accepted Answer

Change G0/0 subnet mask to 255.255.255.252, add default gateway 203.0.113.2, change G0/1 IPv4 to 192.168.1.254, enable IPv6 routing, configure G0/0 with ipv6 address 2001:db8:1::/64 eui-64, and G0/1 with ipv6 address 2001:db8:2::1/64.. The subnet mask on G0/0 was incorrectly set to /24 instead of /30. While a /24 mask on 203.0.113.1 would include 203.0.113.2 in the same subnet from R1's perspective, the mismatch with R2's /30 mask leads to inconsistent subnet definitions and potential ARP or routing issues. Additionally, no default gateway was configured, so traffic to remote networks would fail. On G0/1, the IPv4 address 192.168.1.1 was already used by R3, causing a duplicate IP conflict. IPv6 was not configured on either interface. The fix involved correcting the subnet mask on G0/0 to 255.255.255.252, adding a default gateway (203.0.113.2), assigning a unique IPv4 address to G0/1 (192.168.1.254), enabling IPv6 routing globally with `ipv6 unicast-routing`, configuring EUI-64 on G0/0 (`ipv6 address 2001:db8:1::/64 eui-64`), and static IPv6 on G0/1 (`ipv6 address 2001:db8:2::1/64`).

Answer

Change G0/0 subnet mask to 255.255.255.0, add default gateway 203.0.113.1, change G0/1 IPv4 to 192.168.1.254, enable IPv6 routing, configure G0/0 with ipv6 address 2001:db8:1::1/64, and G0/1 with ipv6 address 2001:db8:2::1/64.

Answer

Change G0/0 subnet mask to 255.255.255.252, add default gateway 203.0.113.2, change G0/1 IPv4 to 192.168.1.1, enable IPv6 routing, configure G0/0 with ipv6 address 2001:db8:1::/64 eui-64, and G0/1 with ipv6 address 2001:db8:2::1/64.

Answer

Change G0/0 subnet mask to 255.255.255.252, add default gateway 203.0.113.2, change G0/1 IPv4 to 192.168.1.254, enable IPv6 routing, configure G0/0 with ipv6 address 2001:db8:1::1/64, and G0/1 with ipv6 address 2001:db8:2::/64 eui-64.

Question 6

You are connected to R1. The network has R1, R2, and a multilayer switch MLS1. Configure IPv4 and IPv6 addressing on R1's interfaces so that R1 can ping both R2 (198.51.100.2) and MLS1 (203.0.113.2) via IPv4. Additionally, configure IPv6 on G0/1 using EUI-64 with prefix 2001:db8:1::/64 and verify that R1 can ping the IPv6 address of MLS1 (2001:db8:1::2). The current configuration has incorrect subnet masks and missing IPv6 settings, causing reachability failures.

Accepted Answer

Change the subnet mask on G0/0 to 255.255.255.252, change G0/1 to 255.255.255.252, then configure IPv6 on G0/1 with the EUI-64 address using the prefix 2001:db8:1::/64.. The interfaces on R1 were configured with subnet masks that were not /30, which is required for these point-to-point links. With an incorrect mask, R1 does not consider the neighboring IPs (198.51.100.2 and 203.0.113.2) as directly connected, preventing ARP resolution and IPv4 reachability. Additionally, IPv6 was missing on G0/1. To fix, change the subnet mask on G0/0 to 255.255.255.252, change G0/1 to 255.255.255.252, then configure IPv6 on G0/1 with the EUI-64 address using the prefix 2001:db8:1::/64. After these changes, pings succeed.

Answer

Change the subnet mask on G0/0 to 255.255.255.0, change G0/1 to 255.255.255.0, then configure IPv6 on G0/1 with the EUI-64 address using the prefix 2001:db8:1::/64.

Answer

Change the subnet mask on G0/0 to 255.255.255.252, change G0/1 to 255.255.255.252, then configure IPv6 on G0/1 with the static address 2001:db8:1::1/64.

Answer

Change the subnet mask on G0/0 to 255.255.255.252, change G0/1 to 255.255.255.252, then configure IPv6 on G0/1 with the EUI-64 address using the prefix 2001:db8:1::/32.

Question 7

You are managing a Cisco WLC (192.168.1.10) via its web UI. The wireless network 'CorpSecure' has been configured but clients cannot associate. Some report 'wrong password' errors; others see the SSID but fail to connect. Additionally, management access to the WLC web UI is intermittent. Identify and resolve the issues so that wireless clients can successfully associate with 'CorpSecure' using WPA3-Personal and the WLC web UI is reliably accessible from the management VLAN (VLAN 10).

Accepted Answer

Configure the SSID with WPA3-Personal; verify management interface is on VLAN 10 with correct gateway.. The primary issue is a security mismatch: the SSID is set to WPA2-PSK while clients expect WPA3, causing 'wrong password' errors. Since clients can see the SSID, broadcast is already enabled; the secondary connection failures may be due to incompatible devices, but the correct fix is to change the security to WPA3-Personal (AES). Additionally, verify that the management interface is on VLAN 10 with the correct gateway to ensure reliable WLC web UI access.

Answer

Change the SSID security to WPA2-PSK and disable SSID broadcast; reset the WLC to factory defaults.

Answer

Update the WLC firmware to the latest version and change the management VLAN to VLAN 1.

Answer

Reconfigure the SSID with WPA3-Enterprise and enable SSID broadcast; set the management interface to use DHCP.

Question 8

You are troubleshooting a wireless client association failure on a Cisco WLC. The client is unable to connect to the corporate SSID 'CorpNet' and reports an authentication error. Review the WLC configuration and fix the issue so that the client can associate and obtain an IP address from VLAN 100. The WLC management IP is 192.168.1.10/24.

Accepted Answer

Change the WLAN security to WPA2, enable SSID broadcast, and configure the WLAN interface to use VLAN 100 with a DHCP scope on that VLAN.. The client authentication and DHCP issues are caused by: (1) WPA3 being configured while the client only supports WPA2, (2) SSID broadcast disabled, preventing client discovery, and (3) the WLAN's client VLAN (100) lacking a DHCP server or scope. The management interface VLAN (1) does not interfere with client DHCP. To resolve, change security to WPA2, enable SSID broadcast, and ensure the WLAN is associated with the correct VLAN (100) and a DHCP scope exists on that VLAN.

Answer

Change the WLAN security to WPA3 only, enable SSID broadcast, and change the management interface IP to 192.168.100.10/24.

Answer

Keep WPA3, disable SSID broadcast for security, and configure the WLAN interface to use VLAN 100 with a DHCP scope on VLAN 1.

Answer

Change the WLAN security to WPA2, keep SSID broadcast disabled, and configure the WLAN interface to use VLAN 1.

Question 9

You are troubleshooting a wireless client connectivity issue on the Cisco WLC at 192.168.1.100. The client reports it can see the SSID 'CorpNet' and successfully associates, but cannot obtain an IP address or reach network resources. The WLAN is already configured with WPA3 security, and the SSID should remain hidden. Identify and correct the configuration issue.

Accepted Answer

The WLAN is mapped to the management interface. Use 'config wlan interface 1 CorpNet_VLAN' to assign the correct interface.. The WLAN is incorrectly mapped to the management interface, which places client traffic in the management VLAN instead of the correct CorpNet_VLAN. As a result, clients cannot obtain IP addresses or communicate beyond the WLC. Reassigning the WLAN to the CorpNet_VLAN interface with 'config wlan interface 1 CorpNet_VLAN' resolves the issue by placing client data in the proper VLAN.

Answer

The SSID is not hidden. Use 'config wlan disable-broadcast-ssid 1 enable' to hide the SSID.

Answer

WPA3 is not enabled on the WLAN. Use 'config wlan security wpa akm 6 enable' to enable WPA3.

Answer

The WLAN is disabled. Use 'config wlan enable 1' to enable the WLAN.

Question 10

You are connected to WLC-1 via the management interface (192.168.1.100/24). The wireless network 'CustomerNet' uses WPA3-Personal, but clients are failing to associate. The SSID is hidden and the correct VLAN is 30. Configure the WLAN and SSID parameters to allow successful client associations and verify the configuration.

Accepted Answer

Create a new interface 'vlan30' with VLAN 30, then create a new WLAN with SSID 'CustomerNet', set security to WPA3-Personal, enable SSID broadcast, and assign the 'vlan30' interface.. The GuestNet WLAN (ID 2) currently uses WPA2 with PSK, but clients expect WPA3-Personal. Additionally, the SSID is hidden (broadcast disabled) and the interface is set to guest (VLAN 20) instead of the required VLAN 30. To fix, create a new WLAN (or modify WLAN 2) to use WPA3-Personal, enable SSID broadcast, and assign it to a new interface mapped to VLAN 30. Configure the interface first, then apply to the WLAN.

Answer

Modify the existing GuestNet WLAN: change security to WPA3-Personal, enable SSID broadcast, and change the interface to 'guest' (VLAN 20).

Answer

Create a new WLAN with SSID 'CustomerNet', set security to WPA2-PSK, enable SSID broadcast, and assign the 'guest' interface (VLAN 20).

Answer

Modify the GuestNet WLAN: change security to WPA3-Personal, keep SSID broadcast disabled, and change the interface to a new interface mapped to VLAN 30.

Question 11

You are managing a Cisco WLC (WLC-1) with IP 10.10.10.10. A wireless client reports it can see the SSID 'CorpNet' but fails to associate. The SSID is configured for WPA3, but the client only supports WPA2. Additionally, the WLAN is mapped to VLAN 100, but the AP is on VLAN 10, causing a mismatch. Your task: reconfigure the WLAN to use WPA2-PSK with AES encryption, correct the VLAN assignment to 10, and ensure the SSID is hidden. Also, verify that management access via the WLC web UI is restricted to the 192.168.1.0/24 subnet.

Accepted Answer

Change security to WPA2-PSK with AES, disable PMF, map WLAN to management interface (VLAN 10), disable SSID broadcast, restrict HTTP/HTTPS access to 192.168.1.0/24.. The client cannot associate because the WLAN requires WPA3 (PMF required) but the client only supports WPA2. Also, the WLAN is mapped to VLAN 100, but the AP is on VLAN 10, causing a VLAN mismatch that prevents client traffic from reaching the correct subnet. The SSID is broadcast (visible), and management access is open to all subnets. To fix: change the WLAN security to WPA2-PSK with AES, disable PMF, map the WLAN to the management interface (VLAN 10), disable SSID broadcast, and restrict HTTP/HTTPS access to subnet 192.168.1.0/24.

Answer

Change security to WPA2-PSK with TKIP, enable PMF, map WLAN to VLAN 100, enable SSID broadcast, restrict HTTP access to 192.168.1.0/24.

Answer

Change security to WPA3-PSK with AES, disable PMF, map WLAN to VLAN 10, disable SSID broadcast, restrict HTTP/HTTPS access to 10.10.10.0/24.

Answer

Change security to WPA2-PSK with AES, enable PMF, map WLAN to VLAN 10, enable SSID broadcast, restrict HTTP/HTTPS access to 192.168.1.0/24.

Question 12

You are connected to WLC-1 via SSH. A new SSID 'CorpSecure' must be configured for 5 GHz clients using WPA3-Personal. However, after creation, clients can see the SSID but fail to associate. Review the WLC configuration and fix the issue so that clients can successfully associate and obtain an IP address from VLAN 100 (subnet 10.0.100.0/24).

Accepted Answer

Change the WLAN security to WPA3-Personal, enable AES-CCMP for WPA3, set the radio policy to 5 GHz, and ensure the WLAN is mapped to the dynamic interface for VLAN 100.. The SSID was configured with WPA2 instead of WPA3. The WLC also had no radio policy set for 5 GHz only. To fix, change the WLAN security to WPA3-Personal, enable AES-CCMP for WPA3, and set the radio policy to 5 GHz. Additionally, ensure the WLAN is mapped to the appropriate dynamic interface for VLAN 100, not the management interface, and that client VLAN 100 is reachable. The commands to modify the WLAN are: config wlan security wpa3 1 enable, config wlan security wpa3 psk ascii CorpSecurePass123 1, config wlan radio policy 802.11a-only 1, and config wlan enable 1.

Answer

Change the WLAN security to WPA2-Personal, enable TKIP encryption, and set the radio policy to 5 GHz.

Answer

Change the WLAN security to WPA3-Personal, enable AES-CCMP, but leave the radio policy as 'All' (both 2.4 GHz and 5 GHz).

Answer

Change the WLAN security to WPA3-Personal, enable AES-CCMP, set the radio policy to 5 GHz, but do not enable the WLAN after changes.

Question 13

You are connected to the Cisco WLC (WLC-1) via its management IP 192.168.1.10. The wireless network 'CorpNet' is configured but clients cannot associate. Troubleshoot and resolve the issue: clients report 'Association failed' and the SSID is not visible in site surveys. Ensure that after your fix, the SSID is broadcast, WPA3 is used, and the WLAN is mapped to VLAN 20. Also, verify the WLC management interface is accessible over HTTPS.

Accepted Answer

Enable the WLAN, set Broadcast SSID to Enabled, create a dynamic interface for VLAN 20 and map the WLAN to it, and enable the HTTPS server.. The WLAN was disabled, the SSID was hidden (Broadcast SSID Disabled), and it was incorrectly mapped to the management interface instead of a user VLAN. Additionally, HTTPS access was disabled. The solution: enable the WLAN, enable SSID broadcast, change the interface to a VLAN 20 interface (e.g., create a dynamic interface 'vlan20' with VLAN 20), and enable the HTTPS server for management access. Note: On an AireOS WLC, the correct commands use `config wlan enable `, `config wlan broadcast-ssid enable `, and `config network secureweb enable` for HTTPS.

Answer

Enable the WLAN, set Broadcast SSID to Enabled, change the interface to the management interface, and enable the HTTPS server.

Answer

Enable the WLAN, keep Broadcast SSID Disabled for security, create a dynamic interface for VLAN 20 and map the WLAN to it, and enable the HTTPS server.

Answer

Enable the WLAN, set Broadcast SSID to Enabled, create a dynamic interface for VLAN 20 and map the WLAN to it, but leave HTTPS disabled for security.

Question 14

You are troubleshooting a wireless client association failure on a Cisco WLC. A client reports it can see the SSID 'GuestNet' but fails to connect, while another client using the same SSID connects fine. You must check the WLC configuration, identify the cause, and fix it so that both clients can associate successfully.

Accepted Answer

Enable WPA3 Transition Mode and set PMF to Optional.. The client that cannot associate is likely a legacy client that does not support WPA3. The WLAN 'GuestNet' has WPA3 enabled with 'PMF Required', which forces all clients to support WPA3 and PMF. To fix this, enable WPA3 Transition Mode (which allows both WPA2 and WPA3 clients) and set PMF to Optional. This will allow the older client to associate using WPA2 while newer clients can use WPA3.

Answer

Change the WLAN security to WPA2-PSK only and disable PMF.

Answer

Disable PMF on the WLAN and keep WPA3 enabled.

Answer

Change the WLAN to use WPA2-PSK with PMF Required.

Question 15

You are connected to a Cisco 9800 WLC (WLC1) via its management interface. A wireless client reports association failures with SSID 'CorpNet'. The client uses WPA3-Personal, but the WLAN is configured for WPA2. Additionally, the SSID is hidden and the client is on the wrong VLAN (VLAN 20 instead of VLAN 100). Fix these issues so the client can associate successfully with WPA3, on VLAN 100, and with the SSID broadcast enabled.

Accepted Answer

Enable SSID broadcast, change security to WPA3-Personal, and assign VLAN 100 in the policy tag.. The WLAN was configured for WPA2-PSK with a hidden SSID, and the policy tag assigned VLAN 20 instead of VLAN 100. To fix: (1) Enable SSID broadcast with 'broadcast-ssid'. (2) Change security to WPA3-Personal by removing WPA2 and enabling WPA3 with 'security wpa wpa3' and 'security wpa psk set-ccmp'. (3) Assign VLAN 100 in the policy tag with 'vlan 100'. The client should then associate.

Answer

Enable SSID broadcast, change security to WPA2-PSK, and assign VLAN 20 in the policy tag.

Answer

Disable SSID broadcast, change security to WPA3-Personal, and assign VLAN 100 in the policy tag.

Answer

Enable SSID broadcast, change security to WPA3-Enterprise, and assign VLAN 100 in the policy tag.

CCNA Network Infrastructure and Connectivity Practice Test 20 — 15 Questions

Exhibit

CCNA Network Infrastructure and Connectivity Practice Test 20 — 15 Questions

Exhibit