Question 340
A team promotes a new model based only on successful smoke tests at one request per second. Production handles 1,000 requests per second. What validation is missing?
Explanation
Correct Answer
Passing low-load checks does not demonstrate sufficient throughput or acceptable tail latency under real demand.
Incorrect Answers
Require an approved release gate tied to measured canary health and the exact model version. A separate source case supports that approach when: A new deployment was validated but receives 100 percent of requests without an approval record. The supporting rationale or observable result is: Controlled promotion separates technical availability from authorized activation of a production model revision. This question describes a different issue: A team promotes a new model based only on successful smoke tests at one request per second. Production handles 1,000 requests per second. Address it through Conduct representative load and latency tests before ramping serving traffic, with the required justification or evidence: Passing low-load checks does not demonstrate sufficient throughput or acceptable tail latency under real demand.
Route traffic back to the known-good deployment using endpoint traffic weights. This is useful for the distinct issue: A new model's production error rate rises sharply during the initial 10-percent rollout. The relevant technical rationale or evidence for that issue is: Traffic rollback can restore the previous serving model without deleting evidence from the failed candidate deployment. Here the reported issue is: A team promotes a new model based only on successful smoke tests at one request per second. Production handles 1,000 requests per second. The relevant response is: Conduct representative load and latency tests before ramping serving traffic. The first result cannot verify this different correction: Passing low-load checks does not demonstrate sufficient throughput or acceptable tail latency under real demand.
Preserve the immutable prior model artifact, environment, and deployment manifest. It addresses another case: The operator needs a reproducible way to return to an exact prior model if rollback occurs weeks after the current release. For that case, the distinguishing justification or acceptance check is: Rollback must restore known code and dependencies, not rely on an ambiguous latest registry reference. The present case instead states: A team promotes a new model based only on successful smoke tests at one request per second. Production handles 1,000 requests per second. It calls for Conduct representative load and latency tests before ramping serving traffic. Showing success for the other case would not establish: Passing low-load checks does not demonstrate sufficient throughput or acceptable tail latency under real demand.