A rarely used legacy license server stays on-premises for now during the cloud migration program. Which 6 R-style decision is this?
Select an answer to reveal the explanation.
Short Explanation
Retain means "leave that odd tool alone for now." The dusty license server stays put while the rest of the city migrates. Not every box has to move on day one — keep it, track it, decide later.
Full Explanation
Retain deliberately leaves a system in place, temporarily or permanently, while other workloads migrate—typically when value is low, risk is high, or dependencies block an early move. Keeping a rarely used legacy license server on-premises during the cloud program is a retain decision in the 6 R-style framing used by many municipal migration offices. Rehost the license server to cloud IaaS in the current sprint no matter the risk fails because the chosen decision is to leave it. Retire immediately even though tools still depend on it fails because dependencies remain and shutdown would break consumers. Re-architect into serverless before discovery completes fails as premature transformation contrary to retain. Exam caveat: retain is an intentional strategy, not forgot about it; exams test whether you recognize conscious deferral versus migrate or retire. Operational check: inventory dependents, set a revisit date, isolate network exposure, and keep patching ownership clear so the on-premises license host does not become an unmanaged civic shadow system. 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.