Question 990
A team has corrected this HPE compute solution issue: A RAG assistant's response time doubles after a larger document corpus is loaded, with no change to model size. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Trend corpus size, search latency and model inference separately. This recurring assurance measure is tied to the diagnosed risk: Retrieval latency and index behavior can dominate end-to-end response after corpus growth. For the active incident, the corrective action remains: Benchmark the vector retrieval stage and optimize supported index or storage resources.
Incorrect Answers
The compute node configuration may not qualify for the selected virtualization release. The selected safeguard helps with that exposure, but it leaves the recurrence risk here unaddressed. Retrieval latency and index behavior can dominate end-to-end response after corpus growth. Trend corpus size, search latency and model inference separately.
This control protects against a condition in which mixed-platform administration requires a supported inventory and governance design. The issue to prevent here is: Retrieval latency and index behavior can dominate end-to-end response after corpus growth. Trend corpus size, search latency and model inference separately.
Retrieval latency and index behavior can dominate end-to-end response after corpus growth. The proposed safeguard is intended for another failure mechanism: Stale compliance evidence does not reflect current required component levels. Trend corpus size, search latency and model inference separately.