Question 740
A team has corrected this HPE compute solution issue: A demonstration works once but cannot be reproduced the next day because its model and source documents change silently. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Version model artifacts and demo datasets with acceptance evidence. This recurring assurance measure is tied to the diagnosed risk: Unversioned demo artifacts prevent repeatable evidence of the proposed solution. For the active incident, the corrective action remains: Freeze approved sample inputs and model version for the documented presentation.
Incorrect Answers
Unversioned demo artifacts prevent repeatable evidence of the proposed solution. The proposed safeguard is intended for another failure mechanism: The support case crosses a subsystem outside the agreed service coverage. Version model artifacts and demo datasets with acceptance evidence.
Demonstration data was not sanitized or approved for that environment. The option addresses that risk, not the one responsible for the present issue. Unversioned demo artifacts prevent repeatable evidence of the proposed solution. Version model artifacts and demo datasets with acceptance evidence.
The prevention measure is relevant to this condition: Deployment owners cannot obtain timely confirmation or change authorization. Here the recurring weakness is: Unversioned demo artifacts prevent repeatable evidence of the proposed solution. Version model artifacts and demo datasets with acceptance evidence.