Question 260
An online scoring API waits seconds to retrieve every feature although the business latency budget is 100 ms. What should the team specify?
Explanation
Correct Answer
Real-time inference must fit feature access latency into the endpoint SLA, not only model computation time.
Incorrect Answers
Package only the retrieval interface and fetch credentials from a managed runtime secret store. This is useful for the distinct issue: A model needs a third-party feature API, but developers embed its token in the serialized model artifact. The relevant technical rationale or evidence for that issue is: Model artifacts may be redistributed; separating secrets from interface metadata avoids credential leakage across consumers. Here the reported issue is: An online scoring API waits seconds to retrieve every feature although the business latency budget is 100 ms. The relevant response is: Design a low-latency online feature retrieval path and validate its performance in the model package. The first result cannot verify this different correction: Real-time inference must fit feature access latency into the endpoint SLA, not only model computation time.
Include a tested input-feature schema and retrieval mapping in the model contract. It addresses another case: Production model calls fail because online feature lookups return a different field name from the training pipeline. For that case, the distinguishing justification or acceptance check is: Schema and mapping metadata prevent silent training-serving differences in feature names and data types. The present case instead states: An online scoring API waits seconds to retrieve every feature although the business latency budget is 100 ms. It calls for Design a low-latency online feature retrieval path and validate its performance in the model package. Showing success for the other case would not establish: Real-time inference must fit feature access latency into the endpoint SLA, not only model computation time.
The alternative, Use time-consistent feature retrieval tied to each prediction event timestamp, belongs to a different technical condition: A fraud model trained using point-in-time account balances but production code reads the latest balance for old records during batch replay. There the source-specific mechanism or proof is: Point-in-time lookup avoids hindsight leakage and makes historical inference comparable to the original live decision. The condition asked about here is: An online scoring API waits seconds to retrieve every feature although the business latency budget is 100 ms. A suitable correction is Design a low-latency online feature retrieval path and validate its performance in the model package; the targeted justification or result is: Real-time inference must fit feature access latency into the endpoint SLA, not only model computation time.