Study guide

3.6 Privacy Preservation, Source Lineage & Audit Evidence

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

3.6 Privacy Preservation, Source Lineage & Audit Evidence

Key Takeaways Explain This Topic AI

Select redaction, pseudonymization, or tokenization from the use case instead of masking indiscriminately.

Apply retention separately to sources, intermediates, invocation logs, and evaluation data.

Glue catalogs, CloudTrail, and application decision logs can connect outputs to governed source versions.

Last updated: September 2026

  • 3.6 Privacy Preservation, Source Lineage & Audit Evidence
  • Access auditing and invocation evidence

CloudTrail records supported Bedrock API activity and is the primary source for identifying principals and configuration changes. A trail must be protected and retained according to policy; the word immutable applies only when the storage and administrative controls actually enforce it.

Optional Bedrock model invocation logging can deliver configured inference records to CloudWatch Logs, Amazon S3, or both. It is disabled by default, Region-scoped, and currently covers supported calls through the bedrock-runtime endpoint. Payload modality controls include text, image, embedding, audio, and video. Do not rely on an invented metadata-only mode: enable only approved modalities, inspect a synthetic canary record, and monitor delivery-success and delivery-failure metrics.

For workloads where raw prompts must not be retained, keep payload logging disabled for that path or sanitize data before every enabled sink. Application audit records can retain caller, request ID, model target, prompt release, Guardrail version, authorization result, and business outcome without copying protected text. Tokenization or redaction must occur before a downstream log receives the content; retention policy is not a substitute for minimization.

Source lineage links each generated result to source versions, ingestion jobs, parser and chunking configuration, embedding model, vector index version, retrieval settings, prompt release, and model target. Store those identifiers beside evaluation evidence so an auditor can reproduce the decision boundary without granting broad access to the source corpus.

Compliance Framework Matrix

Compliance Standard Scope / Industry Key Bedrock Requirement Implementation Mechanism

HIPAA Healthcare / Protected Health Information (PHI) Data must never be used for base training; encryption at rest & in transit; execute AWS BAA. Sign AWS Business Associate Agreement (BAA); enforce KMS CMK on S3 and OpenSearch; PrivateLink endpoints.

GDPR European Union / Data Privacy & Residency In-region processing; customer right to erasure; strict cross-border transfer limits. Target explicit eu-central-1 model ARNs; disable cross-region inference profiles; redact PII via Bedrock Guardrails.

SOC 1 / 2 / 3 Technology & SaaS / Internal Controls Independent third-party audit of security, availability, and confidentiality controls. Inherited via AWS compliance reports in AWS Artifact; CloudTrail auditing of all configuration changes.

FedRAMP High US Federal Government / High-Impact Data Strict cryptographic standards; dedicated government cloud regions; continuous monitoring. Deploy within AWS GovCloud (US) regions; enforce FIPS 140-3 validated cryptographic endpoints.

  • Exam Scenarios & Common Traps
  • Real-World Exam Scenario

A European healthcare conglomerate is deploying a medical diagnostic assistant on Amazon Bedrock. Under GDPR and German national healthcare regulations, patient consultation notes containing PHI must remain strictly within Germany ( eu-central-1 ). The security team mandates that customer keys must be used for all data at rest, and while all invocation activity must be audited for unauthorized access, actual medical consultation text must never be recorded in audit log files.

Architecture Solution :

Direct all application runtime calls to the explicit German model ARN: arn:aws:bedrock:eu-central-1::foundation-model/anthropic.claude-3-5-sonnet-20241022-v2:0 , strictly rejecting any eu. cross-region inference profile.

Configure an AWS KMS Customer Managed Key (CMK) in eu-central-1 with key policies allowing bedrock.amazonaws.com via service context.

Create the OpenSearch Serverless encryption policy specifying the KMS CMK prior to creating the vector collection.

Enable Amazon Bedrock Model Invocation Logging to an S3 bucket in eu-central-1 , configuring the logging settings to Metadata-Only ( textDataDeliveryEnabled: false ).

Common Architectural Traps

Trap 1: Assuming Third-Party Models Exfiltrate Data : Assuming that using Anthropic Claude on Bedrock sends data to Anthropic servers. Claude on Bedrock runs entirely inside AWS data centers with zero data sent to external parties.

Trap 2: Creating OpenSearch Collections Before Encryption Policies : Attempting to attach a KMS CMK after an OpenSearch Serverless collection is created. The encryption policy must precede collection creation.

Trap 3: Using Continental Inference Profiles Under Strict Sovereign Mandates : Assuming that the eu. cross-region inference profile satisfies single-country residency. Continental profiles route requests across multiple EU nations and violate national data confinement laws.

Privacy-preserving processing and source lineage

Detect sensitive data before it enters prompts, logs, or training sets. Amazon Macie can discover sensitive information in S3, while Amazon Comprehend PII detection or application logic can identify text fields for masking or tokenization. Choose deletion, redaction, pseudonymization, or reversible tokenization from the business requirement; masking everything can destroy utility, while masking only outputs leaves sensitive inputs exposed.

Apply retention to source objects, intermediate artifacts, invocation logs, and evaluation datasets separately. Record a data-source identifier and version in AWS Glue Data Catalog or another governed catalog, carry source attribution into retrieved chunks, and use CloudTrail plus application decision logs for auditability. Lineage should answer which source version influenced an output without copying restricted source content into an open log.