Today's design review turns to which choice best matches sound practice for standing up infrastructure for a modernisation workload. Which is it?
Select an answer to reveal the explanation.
Short Explanation
You want to provision compute, storage, repositories, and access deliberately and early, sized for the workload and under controlled access. That gives the team a governed foundation before the work starts. Everything else invites sprawl.
Full Explanation
The correct choice is the one that provisions compute, storage, repositories, and access deliberately and early, sized for the workload and governed by controlled access. Early, deliberate provisioning of sized compute and storage, artifact repositories, and controlled access is what lets a modernisation project scale safely from proof of concept to production. Provisioning resources only once the migration has reached cutover is incorrect because it leaves the team without the infrastructure they need throughout the project's active work. Relying on unmanaged local folders as the source of truth for generated artifacts is incorrect because unmanaged local folders cannot serve as a reliable, auditable source of truth. Allowing each developer to create separate, untracked resources is incorrect because untracked, developer-created resources produce exactly the sprawl and loss of governance that provisioning is meant to prevent. For the exam, favour early, governed provisioning over convenience-driven shortcuts.