A civic Wi-Fi portal still ships idle Meraki location-API calls “in case we need them later,” and every release must understand and patch that surface. What maintainability action fits?
Select an answer to reveal the explanation.
Short Explanation
Keeping a spare radio that nobody uses still means checking its batteries every release. Idle location-API calls are a maintainability smell—YAGNI. Delete or isolate unused integration surface.
Full Explanation
Shipping idle location-API calls “in case we need them” still forces engineers to understand and patch that surface every release. Maintainability prefers deleting or isolating unused integration surface (YAGNI). Do not invent a new Cisco product as the unused hop; keep the example on an already-in-scope API the portal is not actively using.