An unused departmental Access application is shut down instead of migrated. Which migration strategy decision is this?
Select an answer to reveal the explanation.
Short Explanation
If nobody drives the car, do not pay to ship it across the country — park it at the scrapyard. Unused Access app? Retire it. Migration budget should not babysit zombies.
Full Explanation
Retire decommissions a workload that no longer delivers value instead of investing in migration. Shutting down an unused departmental Access application rather than moving it is retire: it removes cost, attack surface, and operational noise from the municipal estate. Rehost onto cloud VMs despite zero active users fails because migration spend without business value wastes cloud budget. Replatform onto managed SQL with no business owner fails for the same reason and adds orphaned managed resources. Retain forever as a production system with no usage metrics fails because the correct decision is removal, not indefinite keep. Exam caveat: retire is a first-class migration strategy outcome; Cloud+ expects you not to migrate everything by default. Operational check: confirm usage telemetry and business owner sign-off, export any records required for retention law, revoke accounts, wipe media per policy, and update the civic application catalog so discovery tools stop listing the Access app as active. In municipal platform operations, record the chosen control and the rejected alternatives in the change record so future on-call engineers understand the failure modes avoided for citizen services. Re-check the decision after the next provider feature change or compliance update to ensure the same answer still holds for the city's estate.