Service Comparison

Batch Transform vs Real-Time Inference

The inference pattern follows latency and traffic shape.

What They Have in Common

Each option can solve part of the scenario. The exam expects you to choose the one that satisfies the stated constraints with the right operational burden, security boundary, availability model, and cost behavior.

Key Differences

OptionPrimary modelBest useSecurityAvailabilityOperations and cost
Batch transformOffline scoringLarge scheduled jobs, no persistent endpointIAM, S3/KMS input and output controlsJob retries and output durability depend on the workflowPay for batch compute; shut down capacity after jobs
Real-time endpointSynchronous low-latency inferenceUser-facing predictions, steady or bursty live requestsIAM, VPC, KMS, endpoint and model controlsDeploy multiple instances/AZs for endpoint resiliencePay for provisioned endpoint capacity; manage scaling and versions
Async inferenceLarge payload or longer inferenceQueue-style inference without immediate responseIAM, S3/KMS, endpoint and invocation controlsManaged queueing; design retries and failure handlingPay for inference and storage; lower always-on pressure than real time

Typical Exam Clues

Practice After Studying

Return to the certification guide that includes this comparison and launch domain training from there.

Sources and Review Metadata