An internal tool calls a model only a few times a day, at unpredictable moments. The team wants to avoid managing instances or scaling policies and to pay nothing for idle time. Which SageMaker AI inference option fits?
Choose an answer to check it. Afterward, select any option to review its explanation.
Running the model on your own server is the opposite of the requirement: the team would provision, scale and pay for the machine whether or not it is called.
Real-time inference gives low latency, which makes it tempting for any live call. It runs a persistent endpoint on an instance type you choose and is meant for sustained traffic, so this team would manage instances and pay while the tool sits idle.
Batch transform processes a large dataset that is available upfront, offline. These calls arrive one at a time at unpredictable moments, not as a dataset prepared in advance.
Serverless inference is built for intermittent or unpredictable traffic: SageMaker AI manages the infrastructure, so there are no instances or scaling policies to manage, and you pay only for use, not idle time.
id q44ac79d623