During 7Rs planning for a municipality, architects classify: an unused departmental intranet as retire, air-gapped OT historians as retain on-premises, a simple brochure website as rehost, and citizen payments as refactor. Which statement best reflects correct 7Rs evaluation?
Select an answer to reveal the explanation.
Short Explanation
Seven Rs aren’t a slogan—they’re a sorting hat. Retire the dead intranet, retain air-gapped OT for now, rehost the brochure site, refactor payments when the juice is worth the squeeze. Forcing everything to EC2 in wave one is how programs stall.
Full Explanation
The 7Rs framework assigns strategies per application: retire unused systems, retain what must stay (such as air-gapped OT), rehost simple web workloads, and refactor complex high-value apps like payments when modernization benefits justify effort. Mandating rehost-for-all, forbidding refactor on payments, or forcing OT onto Lambda in wave one misapplies the model.