A county IT portal must show device inventory plus health views from two different Cisco controller families. How should the privileged API sessions be arranged?
Select an answer to reveal the explanation.
Short Explanation
Think of a single city service desk that calls other departments for you. One back-end facade talks to inventory and both controllers; the browser only talks to that desk. Platform credentials never leave the server, and the front-end keeps one origin.
Full Explanation
A portal that must compose inventory with multiple Cisco controller-family health views should not open several browser-origin privileged API sessions. A back-end facade fans out so the front-end sees a single origin while DNA Center, Meraki, or similar credentials remain server-side. Leaking multiple Cisco API clients into the browser is a design failure, not a full-stack shortcut.