A meter-space wait scorer already runs on AWS Lambda. After it is warm it meets latency, but the first call after idle nights misses the SLA. What ops control should they use?
Select an answer to reveal the explanation.
Short Explanation
After it is warm the Lambda scorer meets latency, but the first call after idle nights misses the SLA. Use provisioned concurrency. That is a cost-versus-latency tradeoff on the existing function, not a move to SageMaker serverless.
Full Explanation
Provisioned concurrency is the Lambda ops control for idle-night cold starts. It is a cost-versus-latency tradeoff on the existing function, not a Domain 3 move to a SageMaker serverless endpoint. Lex is not that control, and turning off logs does not warm the runtime.