Exam 350-401 topic 1 question 193 discussion

The AP goes through this process on startup: The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address. The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via: DHCP option 43 (good for global companies where offices and controllers are on different continents) DNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join) Note: If you use CAPWAP, make sure that there is a DNS entry for cisco-capwap-controller. Management IP addresses of controllers the LAP remembers previously A Layer 3 broadcast on the subnet Statically configured information Controllers present in the mobility group of the WLC the AP last joined

i was suckered by not paying attention to the exact wording in the DNS record

1) LAP does automatically look on the local subnet for controllers with a 255.255.255.255 local broadcast. 2) Management IP addresses of controllers the LAP remembers previously. 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. 3) DHCP option 43 (good for global companies where offices and controllers are on different continents). 4) DNS resolution of "Cisco-capwap-controller.local_domain", (good for local businesses - can also be used to find where brand new APs join) https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html

E is wrong. kindly analyze first before commenting. thanks. correct domain name is cisco-capwap-controller.localdomain