A senior engineer notices generated Java artifacts are being kept only in local folders on individual laptops rather than a shared repository. What task follows from this finding?
Select an answer to reveal the explanation.
Short Explanation
You don't want generated artifacts scattered across laptops that get lost, reimaged, or replaced. Provision a proper repository for the generated artifacts, alongside the compute, storage and access controls the project needs.
Full Explanation
The correct answer is to provision a proper repository for the generated artifacts, alongside the compute, storage and access controls the project needs. Local folders are not a managed source of truth; the appropriate response is to provision a shared repository as part of the project's governed infrastructure, alongside sized compute, storage and controlled access.
Leaving the arrangement as is, since local folders are simpler to work with day to day, is incorrect because leaving artifacts on individual machines risks loss, inconsistency and no audit trail of what was generated when.
Waiting until the project reaches migration cutover before setting up a shared repository is incorrect because delaying until cutover leaves the project running on unmanaged storage for its most active period.
Asking each developer to back up their own local folder independently and considering the risk addressed is incorrect because independent local backups still leave artifacts fragmented across machines rather than centrally tracked.
For the exam, generated artifacts need a governed repository from early in the project, not a workaround at the end.