Study guide

1.5 Customization Spectrum: Prompting vs RAG vs Fine-Tuning vs Continued Pre-training

AWS Certified Generative AI Developer - Professional AIP-C01

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Foundation Model Fundamentals

1.1 AIP-C01 Exam Structure, Logistics & Passing Strategy 1.2 AIP-C01 Scoring & Professional Decision Strategy 1.3 Foundation Model Landscape & Model Selection on Amazon Bedrock 1.4 Model Abstraction, Controlled Switching & Resilience 1.5 Customization Spectrum: Prompting vs RAG vs Fine-Tuning vs Continued Pre-training 1.6 Custom Model Deployment & Lifecycle Management

2 Chapter 2: Bedrock Knowledge Bases & RAG Architectures

2.1 Managed RAG Architecture with Bedrock Knowledge Bases 2.2 Knowledge Source Integration, Synchronization & Freshness 2.3 Data Ingestion, Parsing & Chunking Strategies 2.4 Embedding Models & Vector Representations 2.5 Vector Index Scale, Migration & Retrieval Evaluation 2.6 Vector Database Selection: OpenSearch Serverless vs Aurora pgvector vs Managed Stores 2.7 Vector Store Security, Multi-Tenancy & Connectivity

3 Chapter 3: Advanced Vector Search, Indexing & Data Compliance

3.1 Hybrid Search, Metadata Filtering & Semantic Reranking 3.2 Metadata Filtering, Reranking & Query Transformation 3.3 Fine-Tuning & Continued Pre-Training Data Pipeline Engineering 3.4 Data Validation, Multimodal Processing & Model Formatting 3.5 Data Privacy, Data Residency & Compliance Governance 3.6 Privacy Preservation, Source Lineage & Audit Evidence

4 Chapter 4: Prompt Engineering & Bedrock Runtime APIs

4.1 Advanced Prompt Engineering Techniques & Inference Parameters 4.2 Inference Parameters, Prompt Governance & Regression 4.3 Converse API vs InvokeModel API & Message Formatting 4.4 Tool Calling, FM API Resilience & Model Routing 4.5 Streaming Architectures & Asynchronous Event Processing 4.6 Resilient Streaming, Deployment & Asynchronous Processing

5 Chapter 5: Amazon Bedrock Agents & Tool Integration

5.1 Agentic Architecture, ReAct Reasoning Loops & Orchestration 5.2 Agent Frameworks, MCP & Lifecycle Management 5.3 Action Groups, OpenAPI Schemas & AWS Lambda Integration 5.4 Agent Memory, Session State & Multi-Agent Collaboration Patterns 5.5 Persistent State & Multi-Agent Coordination 5.6 Advanced Agent Prompt Templates & Flow Customization 5.7 Agent Safeguards, Tool Reliability & Cost Control

6 Chapter 6: Workflow Orchestration & Application Integration

6.1 Amazon Bedrock Prompt Flows & Visual Orchestration 6.2 Step Functions Orchestration & Human-in-the-Loop Workflows 6.3 Enterprise Integration: API Gateway, AppSync, and EventBridge 6.4 Hybrid Integration, GenAI Gateways & CI/CD Tooling

7 Chapter 7: AI Safety & Guardrails for Amazon Bedrock

7.1 Guardrails Architecture, Denied Topics & Content Filters 7.2 Content Safety, Defense in Depth & Threat Detection 7.3 Sensitive Information Filters & PII Redaction/Masking 7.4 Contextual Grounding Checks & Hallucination Prevention

8 Chapter 8: Security, Access Control & Network Architecture

8.1 IAM Least Privilege & Resource Policies for Bedrock 8.2 PrivateLink VPC Endpoints & Network Isolation 8.3 Encryption with AWS KMS & Cross-Account Access Patterns

9 Chapter 9: Governance, Auditing & Operational Logging

9.1 SageMaker Model Cards & AI Governance Frameworks 9.2 Lineage, Fairness, Transparency & Continuous Governance 9.3 Invocation Logging, CloudTrail Auditing & Observability 9.4 Responsible AI, Bias Mitigation & Red Teaming Methodologies

10 Chapter 10: Performance, Throughput & Cost Optimization

10.1 On-Demand vs Provisioned Throughput & Capacity Planning 10.2 Capacity Measurement, Scaling Patterns & Resilience 10.3 Batch Inference & Bedrock Intelligent Prompt Routing 10.4 Intelligent Prompt Routing & Application Eligibility 10.5 Prompt Caching, Token Optimization & Latency Reduction

11 Chapter 11: Testing, Evaluation & Troubleshooting GenAI Solutions

11.1 Amazon Bedrock Model Evaluation (Automatic & Human Workflows) 11.2 Human, RAG & Continuous Evaluation 11.3 Evaluation Metrics & RAG Quality Benchmarking (Ragas, ROUGE, BLEU) 11.4 RAG and Agent Performance Evaluation 11.5 CloudWatch Metrics, Throttling & Operational Observability 11.6 Quota Diagnosis, Retry Control & Operational Troubleshooting 11.7 Troubleshooting Common GenAI Failure Modes & Agent Traces 11.8 Prompt Maintenance, Content Handling & Deployment Validation

1.5 Customization Spectrum: Prompting vs RAG vs Fine-Tuning vs Continued Pre-training

Key Takeaways Explain This Topic AI

Use RAG for current traceable facts and weight customization for repeatable behavior or domain adaptation.

Validate provenance, privacy, schema, holdout quality, and regression risk before starting a customization job.

Do not apply the obsolete rule that every custom Bedrock model requires Provisioned Throughput.

Last updated: September 2026

1.5 Customization Spectrum: Prompting vs RAG vs Fine-Tuning vs Continued Pre-training

Generative AI teams can change application behavior at several layers. Prompting changes runtime instructions. Retrieval-augmented generation (RAG) supplies current external evidence. Fine-tuning adapts model behavior from examples. Continued pre-training or parameter-efficient techniques can adapt a model more deeply to a domain. The correct choice follows from the type of gap, not from the assumption that more customization is always better.

Choose the least invasive effective technique

Technique Best fit Data shape Main operational concern

Prompt engineering Role, format, tone, reasoning scaffold, and a few demonstrations Instructions and examples in the request Token cost, prompt injection, regression control

RAG Current or private facts that need traceable sources Documents plus metadata in a retrieval system Retrieval quality, authorization, freshness, citations

Supervised fine-tuning Repeated task behavior, terminology, style, or output patterns Curated input-output examples Dataset quality, overfitting, evaluation, deployment support

Continued pre-training or PEFT Broad domain adaptation where the base model lacks domain language or patterns Large domain corpus or adapter-training data Compute cost, catastrophic forgetting, lifecycle complexity

Prompting is the fastest starting point because it does not alter weights. Use clear system instructions, structured delimiters, examples, and output schemas. Prompting is weak for large changing knowledge sets because every fact must fit in context and remain current.

RAG also leaves weights unchanged. The application retrieves authorized passages at request time and gives them to the model as evidence. RAG is the normal choice for policies, product data, legal material, and other changing facts. It can produce citations, but retrieval does not guarantee truth: weak chunking, missing metadata filters, or an unfaithful generator can still fail. Evaluate retrieval and generation separately.

Supervised fine-tuning learns from labeled examples. It is useful when a base model repeatedly violates an output pattern or lacks a specialized task behavior despite good prompts. Fine-tuning is not a database update mechanism and should not be the default way to memorize changing facts. Continued pre-training and parameter-efficient adaptation address deeper domain patterns, but require stronger data governance and regression testing.

Prepare and validate customization data

Training data is executable product behavior. Establish provenance, licensing, consent, retention, and access controls before a job begins. Remove duplicates, secrets, personal data that is not required, poisoned examples, and conflicting labels. Split training, validation, and final test data so the final set was not used to tune prompts or hyperparameters.

Validate the exact schema required by the selected model and customization method. Requirements vary; do not assume one universal JSONL prompt-completion format. Check file encoding, record limits, supported Regions, base-model eligibility, and service-role permissions. Record the source snapshot and preprocessing code so the model can be reproduced.

Evaluation should compare the customized candidate with the base model and with a prompt- or RAG-based alternative. Include task success, structured-output validity, hallucination rate, safety, latency, and total cost. Test general capabilities that might regress, not only the narrow training task.

Decision scenarios

Use prompting when the model already understands the task and needs clearer instructions or a few demonstrations. Use RAG when an answer depends on current private facts. Use supervised fine-tuning when hundreds or thousands of reviewed examples define a stable behavior that prompting cannot achieve economically. Consider deeper adaptation only when the base model systematically lacks domain language or patterns and the expected value justifies the added governance.

Combinations are common. A fine-tuned model can still use RAG for current facts. A RAG system still needs prompt engineering. A specialized classifier can route to a general model. Evaluate the simplest alternative beside the customized candidate so the team can quantify whether changing weights adds enough value.

Dataset splits must prevent leakage. Near-duplicate documents, templated customer messages, or multiple versions of the same case can make a held-out score look better than real generalization. Deduplicate before splitting, keep time-based or entity-based boundaries where appropriate, and reserve incident cases for regression testing.

Anti-pattern check

Do not customize solely to shorten a prompt until measured token savings exceed training, evaluation, and hosting costs. Do not use fine-tuning to bypass authorization or safety. Do not train on model outputs without quality review and provenance. Each of these choices can make a demo appear simpler while transferring risk into opaque weights.

Loading diagram... Foundation Model Customization Selection Architecture