Municipal Wi-Fi staff will use a browser dashboard that shows Meraki location counts and Intersight inventory. Where must the Meraki API key and Intersight private key live?
Select an answer to reveal the explanation.
Short Explanation
Privileged keys stay in the back office—like the vault behind the counter—not in every visitor’s pocket. The browser gets tidy view data; Meraki keys and Intersight private keys never ride in the SPA.
Full Explanation
When constructing a Cisco API dashboard, privileged collection stays on the server-side collector. Meraki keys, FDM password grants, Intersight private keys, and DNA tokens must not live in the browser. The front end receives already-shaped, least-privilege view data. Placing credentials in client JavaScript, public repos, or script-readable cookies violates that construction step.