A senior engineer reviews a modernisation plan that has developers each creating their own untracked compute and storage as needed. What is the concern with this approach?

The correct answer is that letting each developer create separate, untracked compute and storage bypasses central provisioning of resources, repositories, and access control, leaving generated artifacts and infrastructure scattered and unmanaged. This undermines the governed provisioning a modernisation project depends on and leaves generated code and configuration without a managed home. Treating this as only a cost concern versus a single shared environment is wrong because cost is secondary; the core problem is loss of governance and traceability. Treating it as no concern because developers best judge their own resource needs is wrong because individual judgement cannot replace consistent, access-controlled infrastructure across a shared project. Treating it as only a pilot-phase concern is wrong because untracked resources remain risky throughout the project and often matter more as it scales toward production. For the exam, provisioning is meant to be centrally managed, not left to individual discretion.