A municipal records office still ships monthly archive tapes by courier to an off-site vault and wants a pathfinder migration that proves cloud storage value before touching line-of-business apps. Which process is the strongest early migration candidate?
Select an answer to reveal the explanation.
Short Explanation
Don't start your cloud journey by open-heart surgery on ERP. The tape-courier archive is a process, not just an app, and swapping that dusty courier run for cloud storage is a perfect pathfinder that proves value without betting the city.
Full Explanation
A municipal records office that still ships monthly archive tapes by courier to an off-site vault needs a pathfinder migration that proves cloud storage value before touching line-of-business apps. Migrating the tape-courier archival storage process to cloud object storage is the strongest early candidate: clear value, limited application rewrite, and a visible operational win for records staff and auditors. Rewriting the entire ERP general-ledger module as Lambda microservices in the first sprint fails as a pathfinder—it maximizes complexity and blast radius before the landing zone is proven. Moving the emergency 911 CAD cluster in the same weekend as the records vault fails by coupling a pathfinder with life-safety systems. Retiring Active Directory on-premises before any storage proof-of-concept begins fails sequencing: identity retirement is not a storage pathfinder prerequisite and risks widespread access failure across the city. Exam caveat: early pathfinders favor bounded storage or simple workloads over ERP rewrites and 911 moves. Operational check: select a noncritical archive corpus, land it in S3 with lifecycle and encryption, measure courier cost avoided, document lessons for the PMO, then scale the pattern before LOB cutovers.