In SageMaker JumpStart, what is the primary advantage of selecting a 'Provisioned Throughput' option for a deployed model?
Provisioned Throughput reserves dedicated inference capacity for the endpoint, guaranteeing consistent performance regardless of other customers' traffic. This directly satisfies the stem's requirement for a primary advantage over on-demand hosting, where capacity is shared and throughput can be throttled under load.
Why this answer
Provisioned Throughput on a SageMaker JumpStart endpoint reserves dedicated inference capacity measured in Model Units, guaranteeing consistent latency and throughput regardless of other customers' traffic. It decouples your workload from shared on-demand capacity, which is critical for production workloads with steady or predictable traffic. This is the primary advantage over the default on-demand endpoint mode.
Exam trap
The trap here is conflating 'provisioned' with model-level optimizations like fine-tuning or quantization — the exam wants you to recognize it is purely an endpoint capacity guarantee.
How to eliminate wrong answers
Option A is wrong because fine-tuning is a separate SageMaker workflow (JumpStart fine-tuning or custom training jobs) and is not triggered by choosing Provisioned Throughput. Option B is wrong because provisioning affects compute allocation, not model artifact size — weights are unchanged. Option C is wrong because internet access is governed by VPC configuration and network isolation settings, not by the throughput mode of the endpoint.