How to use a custom trained model in Amazon Bedrock?
A company is using an Amazon Bedrock base model to summarize documents for an internal use case. The company trained a custom model to improve the summarization quality. Which action must the company take to use the custom model through Amazon Bedrock?
Community Votes
58% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests the specific Bedrock rule that custom (fine-tuned or imported) models can only be invoked through Provisioned Throughput — on-demand inference is not available for them.
To invoke a custom fine-tuned or imported model through Amazon Bedrock, you must purchase Provisioned Throughput for that custom model. Community candidates are split between provisioning throughput and granting access, but AWS documentation makes the throughput requirement explicit for custom models.
Many candidates choose D (Grant access) because granting model access is a familiar Bedrock step for base models, but access alone does not enable invocation of a custom model without Provisioned Throughput.
Community Discussion (26 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
The correct answer is A: Purchase Provisioned Throughput for the custom model.
In Amazon Bedrock, custom models — which include models that have been fine-tuned via Bedrock's model customization feature or imported from your own account — behave differently from base foundation models when it comes to invocation. While base models can be invoked on a pay-per-token on-demand basis, custom models can only be invoked using Provisioned Throughput. This is a hard requirement stated in the AWS documentation: you must purchase a Provisioned Throughput commitment (measured in model units) for each custom model before any InvokeModel calls can succeed against it.
Why option A is correct: Provisioned Throughput provides dedicated, guaranteed capacity for a model. For custom models specifically, AWS does not offer an on-demand invocation path at all — the only way to call a fine-tuned or imported model through the Bedrock API is by attaching it to a Provisioned Throughput purchase. This is why the company must take this action.
Why option D is the common trap: Option D — Grant access to the custom model in Amazon Bedrock — is a real and necessary step for base models (e.g., enabling Claude or Llama in your account). Many candidates, including several in the community discussion, correctly note that access must be granted, but they conflate this with the invocation-enabling step for custom models. Granting access is a prerequisite for base models, but it does not unlock invocation of a custom model; only Provisioned Throughput does. Community members such as LR2023 and Ginopress explicitly reference the Bedrock customization documentation to support answer A.
Why options B and C are wrong:
- B (Deploy in a SageMaker endpoint) defeats the purpose of using Bedrock. Once a model is customized or imported into Bedrock, it is invoked through Bedrock's unified API — not through SageMaker endpoints.
- C (Register in SageMaker Model Registry) is a SageMaker MLOps workflow step and is unrelated to invoking a model through Bedrock. Bedrock has its own model catalog and customization pipeline.
Official Reference
Exam Strategy
When a Bedrock question involves a custom, fine-tuned, or imported model and asks what is required to use/invoke it, immediately look for Provisioned Throughput as the answer — on-demand invocation is never available for custom models. Reserve 'Grant access' answers for questions about enabling base foundation models in a new account.
Related Analysis
Practice All AIF-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AIF-C01 Practice Test →