A museums and culture department polls thousands of SD-WAN Edges through vManage APIs and starts receiving rate-limit responses. Which client strategy is most appropriate?
Select an answer to reveal the explanation.
Short Explanation
Rate limits are the museum velvet rope—push the whole crowd at once and security stops you. Stagger the Edge polls, slow down when told, and cache what you can. More parallel hammers just get more 429s.
Full Explanation
Large-scale controller API consumers must respect platform rate limits by pacing, staggering, caching, and backing off on 429/limit signals. Unbounded parallelism worsens throttling. Ignoring limits risks account lockouts or API rejection. Mass SSH CLI scrape abandons the controller’s inventory and monitoring model and can overload Edges.