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
Modularity for a parks-department module that both renders HTML and embeds raw UCS and DNA Center calls means extracting a narrow platform-client boundary. Presentation depends on a stable interface such as get inventory or get wireless health; the client owns URLs, auth, retries, and payload mapping. UI and controller integration can then evolve on different release clocks without rewriting templates for every API tweak.
Inlining more controller URLs into HTML templates fails because it deepens the tangle and forces UI edits for platform changes. Merging UI and all platform SDKs into one mega-class fails by maximizing coupling so every pixel change and every SDK bump share a deploy risk. Duplicating raw API strings across every template fails through copy-paste drift and inconsistent auth or version handling.
Exam caveat: a module here is a design seam with a clear responsibility, not merely a separate file name still called from everywhere with leaked controller details.
Operational check: change a DNA Center base path or auth header in one client module and confirm HTML templates need no edit while automated tests against a fake client still pass.
Without that seam, UCS SDK upgrades and DNA Center schema changes force parks UI releases even when markup is untouched. The platform-client module should own retries, pagination, and error mapping so templates only consume stable view models. That separation is what 350-901 means by modularity in software development and design—not merely splitting files while raw controller URLs remain scattered through presentation code.