Libraries plan a phased move of catalog databases to AWS with continuous sync until go-live. Which statement best describes that approach?
Select an answer to reveal the explanation.
Short Explanation
Move the card catalog in waves while the old system and the new one stay in step, then flip when ready. Continuous sync for a phased migration is a solid approach — it is not banned in favor of a surprise weekend leap. You do not delete accounts after every batch or rebuild from screenshots.
Full Explanation
Phased replication with continuous sync is a valid migration approach versus relying only on a single big-bang cutover. Libraries moving catalog databases to AWS can keep catalogs consistent until go-live, reducing weekend-risk drama for patrons and staff.
Continuous sync is not forbidden in favor of only unannounced big-bang cutovers. Phased moves do not require deleting AWS accounts after each sync batch. Catalog data can be replicated; it need not be recreated from screenshots.
Exam caveat: Know that phased/sync approaches are legitimate; big-bang-only dogma is a distractor. Operational check: run continuous sync in a pilot catalog, measure lag, rehearse cutover with librarians, and publish a patron communication plan for the go-live window.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.