Question 370
A team has corrected this HPE compute solution issue: A business unit needs a low-code RAG prototype but an engineer insists every user must author custom serving containers first. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Match interface complexity to the user persona and task. This recurring assurance measure is tied to the diagnosed risk: The selected workflow ignores available managed or low-code AI application tooling. For the active incident, the corrective action remains: Evaluate suitable supported HPE AI Essentials application-building features and connectors.
Incorrect Answers
The prevention measure is relevant to this condition: Accelerator drivers, libraries and model runtime require a supported compatibility stack. Here the recurring weakness is: The selected workflow ignores available managed or low-code AI application tooling. Match interface complexity to the user persona and task.
The selected workflow ignores available managed or low-code AI application tooling. Using the proposed safeguard would guard against a separate risk: Uncontrolled software supply chains can replace or compromise production model containers. Match interface complexity to the user persona and task.
Compute, storage and accelerator memory vary substantially by training method and data volume. The selected safeguard helps with that exposure, but it leaves the recurrence risk here unaddressed. The selected workflow ignores available managed or low-code AI application tooling. Match interface complexity to the user persona and task.