A library-network team runs twenty copies of one deployable that absorbs Meraki load, yet every SSID-enable change still requires rebuilding the inventory UI. What does that design still lack?
Select an answer to reveal the explanation.
Short Explanation
Twenty photocopies of a tangled notebook still force every edit through the whole book. Horizontal copies absorb load but are not enough without module seams. Independent boundaries let SSID work ship without rebuilding inventory UI.
Full Explanation
Scale-out alone does not deliver modularity. Twenty copies of one deployable can absorb load and still fail modularity if an SSID-enable change requires rebuilding the inventory UI. Evaluate whether seams let teams ship and scale independently; horizontal copies are necessary but not sufficient without those boundaries.