Study guide
10.6 Cost, Performance, and Operations 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.6 Cost, Performance, and Operations Review Lab
Key Takeaways Explain This Topic AI
AI cost review should include tokens, documents, pages, inference calls, training jobs, vector storage, data movement, monitoring, human review, and support operations.
Performance review should focus on latency, throughput, concurrency, retrieval quality, model size, prompt length, fallback paths, and user experience thresholds.
Operations review should define owners for monitoring, alerts, cost budgets, evaluation, incident response, model or data changes, and rollback.
CloudWatch, CloudTrail, Cost Explorer, AWS Budgets, tagging, Trusted Advisor, Well-Architected Tool, and service metrics help convert AI pilots into manageable workloads.
The best practitioner answer is often to reduce scope, use a smaller model, improve retrieval, shorten prompts, or add caching before buying more capacity.
Last updated: May 2026
Lab scenario: operations review for AI pilots
The company now has four AI pilots: a Bedrock support assistant, a Textract document workflow, a Personalize recommendation test, and a SageMaker Canvas forecasting experiment. Usage is growing, and finance asks why costs are rising. Support asks why assistant responses sometimes take too long. Security asks who reviews logs. Product asks whether the models are still accurate. The operations review turns a set of demos into managed workloads.
Start by listing cost drivers by service and workflow. Bedrock cost is often shaped by model choice, input tokens, output tokens, request volume, context length, provisioned or on-demand capacity choices where available, embeddings, retrieval, and evaluation. Textract cost can depend on document pages and feature type. Transcribe depends on audio duration. Personalize has data processing, training, campaign, and recommendation activity patterns. SageMaker AI can include notebook, training, endpoint, storage, and processing costs. Vector stores, S3, OpenSearch, logs, data transfer, and human review also matter.
Review area What to measure Common improvement
Model inference cost Requests, tokens, output length, model choice, peak usage Shorter prompts, smaller model, response limits, prompt reuse, or better routing.
Retrieval cost and quality Embedding volume, vector storage, index refresh, retrieved chunks Remove stale sources, improve metadata, tune chunking, reduce unnecessary context.
Document processing Pages, retries, low-confidence review rate Improve scan quality, split document types, route exceptions earlier.
Personalization and forecasting Training frequency, dataset size, campaign usage, analyst experiments Match refresh cadence to business change and retire unused experiments.
Monitoring and logs Log volume, retention, dashboard count, alarm noise Set retention, filter sensitive data, and keep actionable alerts.
Human operations Review minutes, escalation queues, support tickets Automate only low-risk steps and measure reviewer workload.
Performance review should start from user expectations. A support agent drafting a reply may tolerate a few seconds if citations are useful. A checkout fraud screen may need near real-time response or a deterministic fallback. A document batch review may run asynchronously. An executive forecast refresh can run overnight. Do not use one latency target for every AI workload. Define the workflow threshold, then test p50, p95, and failure behavior under realistic volume.
For Bedrock applications, latency can be affected by model size, prompt length, output length, retrieval calls, tool calls, guardrails, and downstream APIs. A larger model may not be needed for simple classification or extraction. A long prompt that includes irrelevant case history increases cost and latency. A knowledge base that retrieves too many chunks can confuse the model and slow the response. A strong operator asks whether quality improves enough to justify each extra token and call.
For operations, build an ownership map. Product owns whether the feature solves the business problem. Data owners own source freshness and data quality. Security owns access and incident review. Cloud operations owns alarms, dashboards, and cost guardrails. Model or application owners own prompt templates, evaluation sets, and release changes. Finance owns budget thresholds, but the workload team must explain the drivers. Without named owners, every AI issue becomes an unclear cross-team dispute.
Operations checklist:
Tag AI resources by application, owner, environment, cost center, and data classification.
Create AWS Budgets alerts for pilot and production spend thresholds.
Use Cost Explorer to review service, Region, tag, and usage trends.
Use CloudWatch metrics and logs for latency, errors, throttling, blocked prompts, and application outcomes.
Use CloudTrail to investigate API activity and access patterns.
Define log retention and encryption before storing prompts or responses.
Keep evaluation sets for prompt, model, retrieval, and data-source changes.
Document rollback: previous prompt, previous model, disabled action, or human-only workflow.
Failure modes often look like cost or latency symptoms, but the root cause is design. A support assistant may become expensive because every prompt includes a full transcript instead of a concise case summary. A RAG app may be slow because it retrieves a large number of chunks from stale documents. A document workflow may cost more than expected because failed scans are retried repeatedly. A forecasting experiment may keep unused compute resources running. A Personalize campaign may serve traffic even after the experiment ended.
The review should also consider value. A low-cost model is still waste if nobody uses the output. A high-cost model may be justified if it reduces regulated review time with strong human oversight and audit evidence. Use business metrics next to technical metrics: handle time, avoided rework, conversion rate, forecast error, fraud losses, review backlog, user satisfaction, and complaint rate. Cost optimization without outcome measurement can push teams toward cheaper but ineffective systems.
Review prompts before the quiz:
Which cost driver is growing fastest: tokens, documents, storage, training, endpoints, or logs?
Which latency target belongs to each workflow rather than the whole AI program?
Which resources are untagged or owned by a departed pilot team?
What prompt, model, data, or retrieval change requires a regression evaluation before release?
What fallback keeps the business running if the AI service is unavailable?