Which finding during a readiness review would most clearly signal that provisioning has been handled correctly for a modernisation workload?
Select an answer to reveal the explanation.
Short Explanation
You want to see compute and storage sized for the workload, repositories ready for generated artifacts, and access controlled and auditable. That shows provisioning was deliberate, tracked, and governed.
Full Explanation
The correct finding is that compute and storage are sized for the workload, repositories are in place for generated artifacts, and access to all of them is controlled and auditable. A readiness review is looking for evidence that compute, storage, repositories, and access were deliberately provisioned and governed, which is the finding that supports a safe rollout. The finding that resources were requested and created only after the migration cutover date was reached is wrong because provisioning after cutover means the team was building on resources that were never properly sized or secured in the first place. The finding that generated code is being saved to local folders on individual developers' machines is wrong because local, unmanaged folders are not a source of truth and put generated artifacts at risk of loss or inconsistency. The finding that every team member has been granted unrestricted access to every environment to avoid delays is wrong because unrestricted access defeats the purpose of access control rather than satisfying it. For the exam, look for sized, tracked, access-controlled resources as the marker of correct provisioning.