Study guide

6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice

AWS AI Practitioner Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: AIF-C01 Orientation and Official Source Control

1.1 Credential Scope, Code, and Search Language 1.2 Exam Format, Cost, Score, and Delivery 1.3 Official Exam Guide, Skill Builder, and Practice Workflow 1.4 Target Candidate Boundaries and Out-of-Scope Tasks 1.5 Domain Weights and Study Prioritization 1.6 Exam Policy, Retake, Results, and Recertification

2 Chapter 2: AI/ML Foundations and Use-Case Fit

2.1 AI, ML, Deep Learning, and Core Terminology 2.2 Supervised, Unsupervised, and Reinforcement Learning 2.3 Data Types, Labels, Structure, and Quality 2.4 Inference Patterns: Batch, Real-Time, and Embedded AI 2.5 AI Use-Case Fit and No-AI Decisions 2.6 Classification, Regression, Clustering, Forecasting, and Recommendation 2.7 AI/ML Foundations Case Lab

3 Chapter 3: ML Lifecycle, Metrics, and Practitioner MLOps

3.1 Data Collection, EDA, Preprocessing, and Feature Concepts 3.2 Training, Evaluation, Deployment, and Monitoring Lifecycle 3.3 Model Sources: Managed APIs, Open Source, and Custom Models 3.4 Evaluation Metrics and Business Metrics 3.5 Practitioner MLOps: Repeatability, Monitoring, and Retraining 3.6 SageMaker Lifecycle Service Map 3.7 ML Lifecycle Case Lab

4 Chapter 4: Generative AI Foundations and Inference Concepts

4.1 Foundation Models, LLMs, Transformers, and Modalities 4.2 Tokens, Context Windows, Embeddings, and Vector Search 4.3 Inference Parameters: Temperature, Top-p, and Output Controls 4.4 Hallucination, Grounding, and Context Quality 4.5 GenAI Use-Case Fit and Risk Triage 4.6 Prompt Injection, Data Leakage, and User Input Risk 4.7 Generative AI Foundations Case Lab

5 Chapter 5: Prompting, Model Selection, Customization, and Evaluation

5.1 Prompt Engineering Patterns and Business Quality 5.2 Zero-Shot, Few-Shot, Templates, and Instruction Design 5.3 Model Selection: Capability, Latency, Cost, and Risk 5.4 RAG vs Fine-Tuning vs Prompting vs Custom Models 5.5 Model Evaluation, Human Review, and Red-Team Feedback 5.6 Cost, Performance, and Throughput Decision-Making 5.7 Prompting and Model Selection Case Lab

6 Chapter 6: Amazon Bedrock, RAG, Agents, and Guardrails

6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice 6.2 Knowledge Bases, RAG, Data Sources, and Grounding 6.3 AI Agents, Tools, Orchestration, and Business Workflows 6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data 6.5 Bedrock Model Evaluation, Monitoring, and Human Feedback 6.6 Bedrock Cost, Latency, Throughput, and Operational Fit 6.7 Bedrock, RAG, and Agents Case Lab

7 Chapter 7: AWS Managed AI/ML Services and SageMaker Map

7.1 Managed AI Services vs Foundation Model Apps vs Custom ML 7.2 Text, Language, Search, and Document AI Services 7.3 Vision, Speech, Contact Center, and Personalization Services 7.4 Amazon Quick, Amazon Q Developer, Kiro, and Practitioner Fit 7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler 7.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight 7.7 AWS AI Service Selection Case Lab

8 Chapter 8: Responsible AI, Human Review, and Safety

8.1 Fairness, Bias, Transparency, and Explainability 8.2 Privacy, Safety, Human Review, and Accountability 8.3 Guardrails, Clarify, Human Review, and Content Safety Controls 8.4 Responsible AI Risk Registers and Governance Workflows 8.5 Monitoring, Feedback, Drift, and Incident Response 8.6 Responsible AI Case Lab

9 Chapter 9: Security, Compliance, Governance, and Cost Controls

9.1 Shared Responsibility, IAM, and Least Privilege for AI 9.2 Encryption, Secrets, Networking, and Data Privacy 9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling 9.4 Logging, Monitoring, CloudTrail, CloudWatch, and Config 9.5 Compliance: Artifact, Config, Macie, and Policy Evidence 9.6 AI Cost Controls, Pricing, Throughput, and Budget Governance 9.7 Security and Governance Case Lab

10 Chapter 10: Integrated AWS AI Business Scenario Labs

10.1 Customer Support GenAI Assistant Lab 10.2 Document Intelligence and Compliance Review Lab 10.3 Personalization, Forecasting, and Fraud Detection Lab 10.4 Enterprise Search, RAG, and Knowledge Management Lab 10.5 Responsible AI and Security Review Board Lab 10.6 Cost, Performance, and Operations Review Lab 10.7 Full AIF-C01 Business Simulation

11 Chapter 11: Final Review, Exam Readiness, and Recertification

11.1 Final 30-Day AIF-C01 Study Plan 11.2 Official Practice Resources and Weak-Domain Remediation 11.3 90-Minute Exam Timing, Flagging, and Guessing Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Results, Retake, and Recertification Plan 11.6 AWS AI Practitioner Final Mixed Review

6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice

Key Takeaways Explain This Topic AI

Amazon Bedrock is the managed AWS service for using foundation models through APIs, playgrounds, and application features without managing model-serving infrastructure.

Model choice is a business and technical decision involving modality, quality, latency, cost, Region support, context length, customization options, and governance needs.

A practitioner should distinguish Bedrock from SageMaker AI: Bedrock is usually the faster fit for managed foundation model applications, while SageMaker AI fits custom ML build and training control.

Model access, IAM, AWS Marketplace permissions, SCPs, and Region availability can determine whether a model can be used even before prompt design begins.

The strongest Bedrock design starts with a small evaluation, a model fallback plan, logging and privacy decisions, and clear success metrics.

Last updated: October 2026

Bedrock as the managed foundation model layer

Amazon Bedrock is a fully managed AWS service for building generative AI applications with foundation models. It gives teams a single managed place to access model providers, test prompts, run inference, customize models where supported, connect private data through Knowledge Bases, automate workflows with AI agents (Amazon Bedrock AgentCore), apply Guardrails, and evaluate model behavior. The practitioner-level point is not to memorize every model. It is to recognize Bedrock when the organization wants managed FM capabilities without standing up GPU infrastructure or building a full model platform.

A useful mental model is that Bedrock sits between business applications and foundation models. The application sends prompts, documents, messages, images, or other supported inputs to Bedrock runtime APIs such as Converse or InvokeModel. Bedrock routes the request to the selected model or inference profile and returns the response. The team still owns the application design, data permissions, user experience, risk review, and monitoring decisions.

Decision area Practitioner question Good Bedrock answer

Use case fit Does the business need generation, summarization, search, chat, extraction, or agentic task help? Use a managed FM when probabilistic output is acceptable and review controls match risk.

Model choice Which model best balances quality, speed, cost, modality, and Region support? Compare a short list with the same prompt set and business scoring rubric.

Access Can the account and principal invoke the model? Check IAM, AWS Marketplace permissions, SCPs, model access status, and Region availability.

Data Does the model need private current facts? Prefer RAG through Knowledge Bases before assuming fine-tuning is required.

Operations Can the app be monitored and governed? Plan CloudWatch metrics, CloudTrail, invocation logging decisions, guardrails, and evaluation.

Model access is a real deployment dependency. AWS documentation now describes default access to many Bedrock foundation models when the right AWS Marketplace permissions are present, while some third-party providers can still require first-use agreement steps or use-case details. Administrators can also restrict access with IAM policies and organization Service Control Policies. In a scenario, do not assume the model is unavailable because it has not been trained by your company. Also do not assume every user may call every model in every Region.

Model selection should begin with the task. A short customer-service response, a long legal summary, an image generation workflow, a multimodal document-understanding flow, and an embedding pipeline may need different models. Larger models often produce stronger reasoning or language quality, but they can cost more and respond more slowly. Smaller models can be appropriate for classification, extraction, routing, and high-volume internal tools when the prompt and evaluation show acceptable quality.

Bedrock does not remove responsibility for prompt design. A model can be powerful and still fail if the prompt lacks role, task, context, format, constraints, examples, or grounding. A responsible team creates a prompt template, tests expected and adversarial cases, defines refusal behavior, and logs enough metadata to investigate issues. The non-builder approving the solution should ask what success metric will prove that the selected model is good enough for the business workflow.

Distinguish Bedrock from SageMaker AI. Bedrock is the usual managed choice for teams that want to consume or customize foundation models, build RAG, use agents, or add guardrails without managing training and hosting infrastructure. SageMaker AI is more appropriate when the team needs deeper control over custom model development, training, feature engineering, ML pipelines, notebooks, experiments, or model hosting choices. The AIF-C01 target candidate does not need to implement those pipelines, but should recognize the service boundary.

A conservative Bedrock adoption path starts small. Pick one bounded workflow, such as drafting support replies from approved articles or summarizing call notes. Select two or three candidate models, use the same evaluation prompts, compare quality and latency, add guardrails for sensitive data and unsafe content, and run a human review pilot. Then estimate token usage, peak concurrency, retrieval needs, and support process changes before expanding.

Checklist for approving a Bedrock use case:

The task tolerates probabilistic outputs or includes human review where accuracy risk is high.

Required data sources, retention rules, and privacy constraints are known before prompts are designed.

The model shortlist is based on modality, quality, latency, cost, Region support, and terms of use.

IAM permissions, SCPs, and AWS Marketplace requirements are checked before rollout.

Evaluation prompts represent real work, edge cases, and unacceptable answers.

Monitoring, logging, guardrails, and fallback behavior are defined before production use.

Skill Builder practice should be hands-on but bounded. Open the Bedrock console in a permitted training or sandbox account, review the model catalog, compare playground responses for the same prompt, and notice which settings change output length and style. Then ask what would need to change before this prompt could be used in a real customer-facing workflow. That habit turns model demos into operational judgment.