Study guide
10.2 Document Intelligence and Compliance Review Lab
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
10.2 Document Intelligence and Compliance Review Lab
Key Takeaways Explain This Topic AI
Document intelligence projects should separate capture, extraction, classification, summarization, human review, retention, and audit evidence.
Amazon Textract, Amazon Comprehend, Amazon Bedrock, human review queues, S3, KMS, Macie, CloudTrail, and AWS Config can each play a different role in a compliant workflow.
Generated summaries should assist reviewers, not replace accountable compliance or legal decisions in high-impact document workflows.
Failure modes include poor scan quality, wrong document type classification, missing tables, leaked PII, unsupported conclusions, and unclear reviewer authority.
A strong lab requires a decision log, exception queue, sample evidence package, and review prompts for privacy, accuracy, and operational ownership.
Last updated: October 2026
Lab scenario: contract and policy review intake
A financial services operations team receives vendor contracts, policy attestations, insurance certificates, and audit questionnaires. Reviewers manually open PDFs, copy fields into a case system, flag missing clauses, and write a short compliance summary. The team wants AI assistance to extract fields, identify document type, summarize key obligations, and route exceptions. The chief compliance officer says the AI may assist reviewers, but it may not make final legal or compliance decisions.
Start by splitting the workflow into stages. Document upload and storage are not the same as text extraction. Extraction is not the same as legal interpretation. Summarization is not the same as approval. A practitioner should map each stage to the service that fits the job and the risk control that keeps the workflow auditable. This prevents the common mistake of asking one foundation model to read everything, decide everything, and store everything with no review trail.
Workflow stage AWS fit Practitioner control question
Secure intake Amazon S3 with KMS encryption and strict IAM Who can upload, read, tag, delete, and restore documents?
Sensitive data discovery Amazon Macie for S3 data discovery Are PII and sensitive buckets known before documents enter AI workflows?
OCR and forms Amazon Textract Are forms, tables, signatures, and low-quality scans tested separately?
Classification and entities Amazon Comprehend or Bedrock classification prompts Is the document type and field extraction accurate enough for routing?
Summary and clause review Amazon Bedrock with a controlled prompt and citations to extracted text Does the model state uncertainty and avoid unsupported legal conclusions?
Human review An internal review queue (Amazon A2I is no longer open to new customers) Which exceptions require a person and what evidence do they see?
Audit evidence CloudTrail, CloudWatch, AWS Config, and ticket history Can the organization prove who accessed and approved each document?
The pilot should use non-sensitive sample documents or approved redacted copies. Store them in a dedicated S3 bucket with default encryption using AWS KMS, bucket policies that deny public access, and least-privilege IAM roles. Enable object versioning if the retention plan requires it. Use tags such as document type, business unit, review status, data classification, and retention category. If Macie flags unexpected sensitive data in a location that should hold redacted samples only, stop and fix the intake process before expanding the lab.
Use Amazon Textract when the task is extracting printed or handwritten text, key-value pairs, and tables from documents. Test different formats: a clean PDF, a scanned image, a document with rotated pages, and a form with multiple tables. Expected observations include text blocks, detected forms, table cells, confidence values, and pages that need review. Failure modes include missing small print, merged table cells, low-confidence handwriting, and signatures being treated as ordinary marks. Do not hide confidence values from reviewers if they are important to the decision.
Add classification and summarization as separate steps. Amazon Comprehend can help with entity extraction and classification patterns for text, while Bedrock can generate a structured summary from extracted text. The prompt should ask for a concise summary, missing required fields, cited source snippets, and a list of uncertainties. It should not ask the model to decide whether a contract is legally acceptable. For high-impact reviews, route low-confidence extraction, missing clauses, conflicting clauses, or disallowed document types to human reviewers.
Decision log example:
Intake bucket: dedicated S3 bucket with KMS encryption, blocked public access, and restricted roles.
Extraction service: Textract for OCR, forms, and tables because the source is scanned PDFs.
Summarization service: Bedrock with a prompt that requires citations to extracted text and uncertainty flags.
Human review trigger: missing signature, low extraction confidence, unsupported summary claim, sensitive data mismatch, or high-value vendor category.
Evidence owner: compliance operations owns review notes, while cloud operations owns access logs and storage controls.
Retention rule: documents and outputs follow approved records policy, not model developer preference.
A responsible review queue shows the original document, extracted fields, confidence indicators, generated summary, citations, and reason for escalation. Reviewers should be able to approve, reject, correct fields, request more information, or mark the document out of scope. Their decision becomes the business record. The generated summary is supporting evidence, not the authority. If the team cannot explain how a reviewer changed or accepted AI output, the workflow is not ready for regulated use.
Compliance failure modes deserve explicit testing. Upload a document with a missing signature and confirm it routes to review. Upload a document with a table that Textract partially reads and confirm the low-confidence field is visible. Include a prompt injection inside a document, such as instructions telling the model to ignore policy, and verify guardrails and prompts do not follow it. Include a document with customer PII and confirm masking, access, logging, and retention behavior match the data classification.
Review prompts before the quiz:
Which documents are safe sample inputs, and who approved their use?
Which extracted fields can be auto-populated, and which require reviewer confirmation?
What evidence would an auditor need to reconstruct a review decision?
How are low confidence, missing clauses, and sensitive data mismatches routed?
What would make this workflow inappropriate for AI assistance until governance improves?