A city lists "buy more on-premises racks" as its AWS Cloud migration strategy. What is the correct evaluation of that plan?
Select an answer to reveal the explanation.
Short Explanation
Buying more racks doubles down on the old basement — that is expansion, not migrating to AWS. Real strategies look like replication, refactoring, or shipping data with Snow Family devices. More shelves of metal do not finish a cloud cutover or unlock CAF benefits by themselves.
Full Explanation
Buying more on-premises racks is not a cloud migration strategy to AWS. A city listing that plan as its AWS migration approach has described expanding the old model, not adopting cloud—staff should correct the strategy before spending further CapEx under a cloud label.
Buying more racks is not the preferred Snow Family pattern, does not complete database replication cutover, and is not required before any CAF benefit can be realized. Those distractors dress expansion of on-premises as migration progress.
Exam caveat: Migration strategies move workloads to cloud services/patterns; more racks ≠ AWS migration. Operational check: rewrite the migration plan with target AWS services, data movement approach, and decommission milestones for on-premises capacity being left behind.
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.