A parks-department module both renders HTML and embeds raw UCS and DNA Center API calls in the same unit. What modularity change lets the UI and the controller hop evolve on different clocks?
Select an answer to reveal the explanation.
Short Explanation
Mixing the storefront paint job with the warehouse radio is a ball of mud. A narrow platform-client module owns UCS or DNA Center hops; the UI just asks that module. Each side can ship without waiting on the other.
Full Explanation
A unit that both renders HTML and embeds raw Cisco platform calls cannot be scaled or replaced on its own. A narrow platform-client module creates an independently replaceable seam so the UI and the controller integration change on different clocks. That modularity is a design boundary, not merely a folder rename.