A worker that polls every Meraki site every second exhausts the published controller quota and starves sibling civic apps. What design move should be chosen before implementation?
Select an answer to reveal the explanation.
Short Explanation
A shared water main has a meter—blasting every site every second empties the tank for everyone. Design for the vendor rate limit up front: shared poller, slower interval, or events. Ignoring the quota is not a plan.
Full Explanation
Platform rate limits are a first-class design input for Cisco-API consumers. A worker that polls every site every second will exhaust a published controller quota and starve sibling apps. Choose shared polling, a longer interval, or event-driven refresh before implementation—not Domain 2 Retry-After header coding as the primary point.