Before moving the records-management workload, teams size CPU, RAM, and disk so cloud resources match the workload profile. Which migration consideration is this?
Select an answer to reveal the explanation.
Short Explanation
Measure twice, provision once — size CPU, RAM, and disk from real workload needs before the move. That is resource allocation planning, not "buy the biggest box and hope." Cloud flexibility helps later; day-one sizing still matters.
Full Explanation
Migration planning includes allocating compute, memory, and storage that fit observed or projected workload profiles so performance and cost stay aligned after cutover. Right-sizing from workload data is a core consideration. Blindly choosing maximum sizes, skipping estimates, or ignoring capacity entirely increases cost and risk even when autoscaling exists.