A mall operator wants Meraki-powered foot-traffic analytics, needing opt-in Wi-Fi probe data delivered continuously to its analytics engine without polling the cloud. Which Location Scanning API design matches purpose and delivery?
Select an answer to reveal the explanation.
Short Explanation
You get live footfall without hammering the cloud by letting the network call you. Your stream flows like a ticker tape feeding your counter in real time.
Full Explanation
Meraki Location Scanning API purpose is presence and engagement analytics from Wi-Fi probe requests seen by access points, delivered as a continuous outbound POST stream of JSON observations to a customer collector URL, avoiding Dashboard polling and enabling real-time engines. Polling device configs infers nothing about live probes and misses the push delivery model. Switch syslog streaming carries event logs, not scanning observations, and cannot derive precise probe analytics. Reversed beacon push misstates direction and product, as Dashboard does not push beacons to APs for this feed. Exam caveat: remember scanning equals AP observations pushed to your URL, distinct from Dashboard REST polling. Practical check: configure the validator URL and confirm POSTs arrive with radio and client fields.