Question 410
A team has corrected this HPE compute solution issue: A service cannot recover an earlier model version because engineers overwrite the same artifact path on every release. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Enforce artifact versioning and release lineage in ML operations. This recurring assurance measure is tied to the diagnosed risk: Mutable unversioned artifacts prevent reliable rollback and audit. For the active incident, the corrective action remains: Store distinct immutable model versions and define a supported rollback method.
Incorrect Answers
This control protects against a condition in which the new model needs different accelerator memory and compute resource reservations. The issue to prevent here is: Mutable unversioned artifacts prevent reliable rollback and audit. Enforce artifact versioning and release lineage in ML operations.
Compute, storage and accelerator memory vary substantially by training method and data volume. The option addresses that risk, not the one responsible for the present issue. Mutable unversioned artifacts prevent reliable rollback and audit. Enforce artifact versioning and release lineage in ML operations.
The prevention measure is relevant to this condition: The model lifecycle lacks provenance and release-gate records. Here the recurring weakness is: Mutable unversioned artifacts prevent reliable rollback and audit. Enforce artifact versioning and release lineage in ML operations.