A museum wants a wayfinding app to follow visitors. An engineer plans to scrape the controller's client list every minute. Which integration matches the job?
Select an answer to reveal the explanation.
Short Explanation
The app needs a location, and you are about to copy a client list by hand. Spaces is the feed built for that. A shared secret does not publish a map pin.
Full Explanation
Spaces is the product that turns wireless observations into a location feed for engagement and wayfinding. A museum app that follows visitors should use that feed. Scraping the controller client list every minute is a fragile substitute and is not the integration the job calls for. A RADIUS shared secret authenticates the controller to the policy server. It does not publish visitor coordinates. An RF profile sets radios. A channel change is not a stream of map coordinates. A guest passphrase is a credential, not a location API. A wayfinding app needs the Spaces location feed. Scraping the controller client list is the wrong integration. Check one live client after the change and do not retune the rest of the floor until that client matches the result you expected. Exam caveat: the location feed is only as good as the access-point placement and the map. Spaces will not invent coordinates the radios cannot support. Operational check: point a test client at the Spaces location feed and confirm the app tracks that client without reading the controller client page.