A city parking portal’s browser UI must show DNA Center wireless health and Meraki SSID status. Where should the integration store platform API tokens and issue those privileged controller calls?
Select an answer to reveal the explanation.
Short Explanation
Think of the browser as the storefront window and the server as the vault. Layout and click state live in the window; DNA Center or Meraki keys stay in the vault. Putting platform secrets in front-end JavaScript is a distributed-app design failure, not a convenience.
Full Explanation
When an app consumes Cisco platform APIs, privileged work belongs on the back-end: tokens, controller hostnames, and any call that must not leak a secret. The front-end owns presentation and local UX state only. Embedding DNA Center or Meraki credentials in browser or mobile-shell code exposes them to every client and violates sound distributed design. Keep a single trusted tier for those hops.