A city’s “common Cisco helper” still ships inside every portal release as a versioned library. The team wants that hop to scale and fail without rebuilding the UI. Which modularity choice matches that goal?
Select an answer to reveal the explanation.
Short Explanation
A shared cookbook still rides in every meal delivery. A separate kitchen can cook, scale, and burn dinner without rebuilding the dining room. Service modularity is a deploy-and-scale boundary—not just a neat folder name.
Full Explanation
Extracting a common Cisco helper as a versioned library still ships inside every app release, so UI rebuilds couple to that hop. Extracting the hop as its own service lets it scale and fail independently of the UI. Modularity here means a deploy and scale boundary, not merely packaging code into a named library.