Which two design considerations should be considered when building a Cisco Meraki dashboard out of available APIs? (Choose two)

Cisco Meraki enforces a rate limit of five API calls per second per organization, and exceeding this threshold results in HTTP 429 responses; dashboards that poll frequently must implement throttling logic to stay within this limit.

The Meraki API version must be explicitly included in the URL path (e.g., '/api/v1/'); omitting it results in an error because the base URL without a version is not a valid endpoint.

API access to the Meraki Dashboard is disabled by default and must be enabled by an organization administrator under Organization > Settings > Dashboard API access; without this step, all API requests return a 404 or unauthorized error.

Meraki API requests require only the API key passed in the 'X-Cisco-Meraki-API-Key' header; user credentials such as username and password are not used for API authentication.

A Meraki organization administrator can regenerate their API key at any time from their profile page; the key is not permanent and regenerating it immediately invalidates the old key.