Course menuMLA-C02

Exams / MLA-C02 / Real-time, serverless, async and batch inference / Question 2

MLA-C02 practice question: Real-time, serverless, async and batch inference (2 of 3)

Deployment and Orchestration of ML and AI Workflows A free question from our original MLA-C02 practice exam. Try it, then open the answer to see why each option is right or wrong.

Last verified against current AWS documentation ·How we write our questions

A logistics broker has an internal model that scores carrier invoices for duplicate billing. The tool is used by a few analysts during business hours, and it receives only a handful of requests per day with small payloads.

The broker wants the lowest cost for this light, unpredictable traffic and does not want to manage instance capacity, while still accepting that a request after an idle period may take a little longer.

Which endpoint type should the team choose?

Choose one answer.

  1. A. A real-time endpoint on a GPU instance that runs at all times, so that every request is answered at the same speed.
  2. B. A batch transform job that is started by hand each time an analyst wants a score for a new invoice.
  3. C. A serverless inference endpoint, which charges for the compute used during requests and needs no instance capacity to be managed.
  4. D. An Amazon EC2 instance running a web server that loads the model in memory and is managed by an auto scaling group with a minimum of two instances.
Show the answer and explanation

Answer: C

  • A. Wrong: A running GPU instance is paid for all day even though the traffic is a handful of requests. This is the highest cost for the light workload.
  • B. Wrong: Batch transform works for a set of records processed together, and it is not a request-time service for a single invoice. Starting a job by hand for each invoice adds delay and effort.
  • C. Right: Correct. Serverless inference fits intermittent traffic with small payloads, and the broker pays for the compute used rather than for idle instances. Requests after an idle period can see a slightly longer start. Learn more: Deploy models with SageMaker Serverless Inference (opens in a new tab)
  • D. Wrong: Two always-on instances cost more than the light traffic justifies, and the broker would manage the servers itself. The stem asks for lower cost with no capacity management.

Explanation

Serverless inference suits intermittent traffic with small payloads, because the broker pays for compute used and does not manage instances. A running real-time endpoint or two instances pay for idle time, and batch transform is not built for single on-demand requests.

Study

Keep practicing

Answer questions with a score at the end, or practice just this topic with the explanation after each one. No sign-up needed.

Want more on Real-time, serverless, async and batch inference? The 5 full-length practice sets have 8 more Real-time, serverless, async and batch inference questions, 325 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets