Cisco 350-101 Exam
Implementing and Operating Cisco
Wireless Core Technologies (350-101
WLCOR)v1.0
https://www.passquestion.com/350-101.html
35% OFF on All, Including 350-101 Questions and Answers
Pass 350-101 Exam with PassQuestion 350-101 questions and
answers in the first attempt.
https://www.passquestion.com/
1/9
, 1.A school district is deploying Cisco Catalyst 9176 APs to remote sites with occasional WAN outages.
The IT team wants the APs to attempt joining a secondary or tertiary Catalyst 9800 WLC if the primary
controller is unreachable. The team must preconfigure all controller IP addresses using the AP CLI before
deploying.
Which set of CLI commands sets the primary, secondary, and tertiary controller IP addresses on a
Catalyst 9176 AP?
A. set controller primary-base main-wlc 10.10.10.10
set controller secondary-base backup 10.10.10.20
set controller tertiary-base tertiary-wlc 10.10.10.30
B. capwap ap primary-base main-wlc 10.10.10.10
capwap ap secondary-base backup-wlc 10.10.10.20
capwap ap tertiary-base tertiary-wlc 10.10.10.30
C. ap join primary 10.10.10.10
ap join secondary 10.10.10.20
ap join tertiary 10.10.10.30
D. capwap ap wlc primary 10.10.10.10
capwap ap wlc secondary 10.10.10.20
capwap ap wlc tertiary 10.10.10.30
Answer: B
Explanation:
Cisco lightweight and Catalyst access points use CAPWAP for AP-to-controller discovery and join
operations. For AP-side preconfiguration, Cisco documents the syntax as capwap ap {primary-base |
secondary-base | tertiary-base} controller-name controller-ip-address, specifically for configuring primary,
secondary, and tertiary controllers on the AP. This matches option B exactly because it includes the
CAPWAP AP command, the controller priority keyword, the controller name, and the controller
management IP address. (Cisco)
The Catalyst 9800 AP join process also recognizes these configured controller entries in priority order:
primary controller using capwap ap primary-base, secondary controller using capwap ap secondary-base,
and tertiary controller using capwap ap tertiary-base. (Cisco) This allows the AP to attempt a backup
controller when the preferred controller is unavailable, which is appropriate for remote sites with
intermittent WAN reachability.
Option A uses obsolete or invalid set controller syntax.
Option C invents an ap join command format.
Option D incorrectly inserts wlc into the AP CAPWAP command.
Reference topics: Wireless Network Implementation — CAPWAP discovery, AP join process, Catalyst
9800 controller redundancy, and AP CLI provisioning.
2.Refer to the exhibit.
2/9
Implementing and Operating Cisco
Wireless Core Technologies (350-101
WLCOR)v1.0
https://www.passquestion.com/350-101.html
35% OFF on All, Including 350-101 Questions and Answers
Pass 350-101 Exam with PassQuestion 350-101 questions and
answers in the first attempt.
https://www.passquestion.com/
1/9
, 1.A school district is deploying Cisco Catalyst 9176 APs to remote sites with occasional WAN outages.
The IT team wants the APs to attempt joining a secondary or tertiary Catalyst 9800 WLC if the primary
controller is unreachable. The team must preconfigure all controller IP addresses using the AP CLI before
deploying.
Which set of CLI commands sets the primary, secondary, and tertiary controller IP addresses on a
Catalyst 9176 AP?
A. set controller primary-base main-wlc 10.10.10.10
set controller secondary-base backup 10.10.10.20
set controller tertiary-base tertiary-wlc 10.10.10.30
B. capwap ap primary-base main-wlc 10.10.10.10
capwap ap secondary-base backup-wlc 10.10.10.20
capwap ap tertiary-base tertiary-wlc 10.10.10.30
C. ap join primary 10.10.10.10
ap join secondary 10.10.10.20
ap join tertiary 10.10.10.30
D. capwap ap wlc primary 10.10.10.10
capwap ap wlc secondary 10.10.10.20
capwap ap wlc tertiary 10.10.10.30
Answer: B
Explanation:
Cisco lightweight and Catalyst access points use CAPWAP for AP-to-controller discovery and join
operations. For AP-side preconfiguration, Cisco documents the syntax as capwap ap {primary-base |
secondary-base | tertiary-base} controller-name controller-ip-address, specifically for configuring primary,
secondary, and tertiary controllers on the AP. This matches option B exactly because it includes the
CAPWAP AP command, the controller priority keyword, the controller name, and the controller
management IP address. (Cisco)
The Catalyst 9800 AP join process also recognizes these configured controller entries in priority order:
primary controller using capwap ap primary-base, secondary controller using capwap ap secondary-base,
and tertiary controller using capwap ap tertiary-base. (Cisco) This allows the AP to attempt a backup
controller when the preferred controller is unavailable, which is appropriate for remote sites with
intermittent WAN reachability.
Option A uses obsolete or invalid set controller syntax.
Option C invents an ap join command format.
Option D incorrectly inserts wlc into the AP CAPWAP command.
Reference topics: Wireless Network Implementation — CAPWAP discovery, AP join process, Catalyst
9800 controller redundancy, and AP CLI provisioning.
2.Refer to the exhibit.
2/9
