I think it's A - Primed WLC
Locally stored controller IPv4 or IPv6 address discovery—If the access point was previously associated to a controller, the IPv4 or IPv6 addresses of the primary, secondary, and tertiary controllers are stored in the access point’s nonvolatile memory. This process of storing controller IPv4 or IPv6 addresses on an access point for later deployment is called priming the access point.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-6/config-guide/b_cg86/ap_connectivity_to_cisco_wlc.html
Skliffi, We have to look at it as existing an existing access point not new. If the AP was already primed with the primary, secondary or tertiary controller, so it will join whatever the controller the access point was primed which is the primary controller.
The order of selecting a WLC according to the exam guide:
1: If the AP has previously joined a controller and has been configured or "primed" with a primary, secondary, and tertiary controller, it tries to join those controllers in succession.
2. If the AP does not know of any candidate controller, it tries to discover one (which includes the use of option 43).
Priming an AP directly overrules option 43, so A should be the correct answer.
A is correct
even if option 43 is set up to direct the AP to a specific WLC, the primed configuration takes precedence, and the AP will join the WLC it has been primed for.
Intra-Controller Roaming: client roaming across access points managed by the same controller.
Inter-Controller Roaming: client roaming across access points in managed by different controllers in the same mobility group and on the same subnet.
Inter-Subnet Roaming: client roaming across access points managed by different controllers in the same mobility group on different subnets.
Ref: How to configure the Lightweight AP in order to join the respective WLAN Controller - Cisco Community
Post by TCC_2
“…
Overview of the Wireless LAN Controller (WLC) Discovery and Join Process
…
In addition to these methods, the LAP does automatically look on the local subnet for controllers with a 255.255.255.255 local broadcast. Also, the LAP remembers the management IP address of any controller it joins across reboots. Therefore, if you put the LAP first on the local subnet of the management interface, it will find the controller's management interface and remember the address. This is called priming. This does not help find the controller if you replace a LAP later on. Therefore, Cisco recommends using the DHCP option 43 or DNS methods.
…”
A. The AP is joining a primed WLC
Correct answer.
B. The APs broadcast traffic is unable to reach the WLC through Layer 2
Wrong answer.
C. The AP multicast traffic is unable to reach the WLC through Layer 3
Wrong answer.
D. The WLC is running a different software version
Wrong answer.
Even if you don't know the right anser you can rule out b, c,d
Why should the AP user boadcast or multicast to communicat with the WLC, when he gets the IP Adresse in option 43. Communication between WLC and AP is always unicast!
D is Wrong becaus if the Software does not match the AP always loads the correct version from the WLC.
So only Anser A ist left
This section is not available anymore. Please use the main Exam Page.350-401 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Skliffi
Highly Voted 4 years, 3 months agoAlliam
4 years, 2 months agoTheNetworkStudent
Highly Voted 4 years, 2 months ago[Removed]
Most Recent 6 months, 2 weeks agoKZM
2 years, 1 month agoPudu_vlad
2 years, 2 months ago[Removed]
2 years, 5 months agoAldebeer
2 years, 7 months agoEddgar0
2 years, 7 months agoaohashi
2 years, 9 months agorettich
2 years, 9 months agoxziomal9
3 years, 2 months agoHamzaaa
3 years, 7 months agonetpeer
3 years, 8 months agoJclemente
3 years, 8 months agonuman_ahmed
3 years, 10 months agotonght
3 years, 10 months agohku68
3 years, 10 months ago