AWS Certified AI Practitioner (AIF-C01)
Study another certificationProgress0%
Recent accuracy0%
Review due0questions
Answered0 / 550questions
Practice by topic
1 AI and ML fundamentalsAI, machine learning, deep learning, use cases, and development lifecycles.
2 Generative AI fundamentalsGenerative AI, foundation models, RAG, prompting, and AWS generative AI services.
3 Foundation model applicationsFoundation model design, prompting, adaptation, and evaluation.
4 Responsible AIFairness, transparency, explainability, and safety.
5 Security, compliance, and governance for AI systemsProtecting, auditing, governing, and assessing AI systems.
Practice by topic
Practice settings
Question count
10questions1550questions
This session: 10questions / eligible: 550 questions
Learning modes
Quick practice
Start quick practice
Question count
10questions1550questions
This session: 10 questions / pool: 550 questions
Review
Start review
Question count
0questions00questions
This session: 0 questions / pool: 0 questions
Browse questions by objective
Choose a topic to read an individual question, its hints, and explanations. No session setup is required.
1.1 Explain basic AI concepts and terminology21 questions
- Distinguishing AI and machine learning
- Distinguishing supervised and unsupervised learning
- Distinguishing training and inference
- Distinguishing classification and regression
- Understanding reinforcement learning
- Organizing AI and machine-learning terms
- Matching learning methods to goals
- Choosing predictive and generative models
- Separate request intent from named entities
- Distinguish image labels from object locations
- Use output meaning to distinguish classification, regression and generation
- Separate known intent classes from discovery of unknown groups
- Distinguish transcription from speaker diarization
- Separate OCR text locations from invoice validation
- Separate model training from inference with a fixed model
- Check transfer-learning reuse and target-task evaluation
- Separating regression and classification
- Separating supervised and unsupervised learning
- Understanding reinforcement learning
- Understanding ensembles
- Building an anomaly baseline
1.2 Identify practical use cases for AI32 questions
- Choosing classification or regression
- Selecting a generative AI business use case
- Identifying an anomaly-detection use case
- Selecting a recommendation use case
- Selecting a demand-forecasting use case
- Using NLP to route and analyze call transcripts
- Selecting a computer-vision use case
- Selecting anomaly detection
- Communicating forecast uncertainty
- Choose fixed-rule automation or machine learning for the requirement
- Separating drift from data quality
- Preventing evaluation leakage
- Evaluating imbalanced classes
- Keeping feature scaling consistent
- Setting a drift baseline
- Managing missing values
- Aligning label definitions
- Detecting feature drift
- Separating train and test data
- Finding target leakage
- Reducing overfitting
- Choosing metrics for imbalanced data
- Managing cross-validation splits
- Scaling features
- Using dimensionality reduction
- Tuning a classification threshold
- Validating synthetic data
- Auditing label quality
- Handling missing values
- Using stratified sampling
- Recognizing concept drift
- Handling out-of-distribution inputs
1.3 Describe the AI/ML development lifecycle49 questions
- Organizing the machine learning lifecycle
- Selecting production model-monitoring signals
- Assessing the impact of missing labels
- Separating evaluation data from training
- Detecting model drift
- Recognizing overfitting
- Keeping feature preprocessing consistent
- Choosing metrics for the business objective
- Preventing data leakage
- Splitting time-series data
- Detecting data drift
- Separating features and labels
- Separating evaluation data
- Preventing cross-validation leakage
- Evaluating class imbalance
- Choosing a missing-value policy
- Calibrating prediction probabilities
- Responding to concept drift
- Using stratified splits
- Handling outliers
- Evaluating hyperparameter search
- Choosing a learning method
- Preventing data leakage
- Separating dataset roles
- Recognizing reinforcement learning
- Using embedding similarity
- Managing a model lifecycle
- Handling missing values
- Evaluating data augmentation
- Scheduling retraining
- Creating features
- Matching metrics to business cost
- Managing model approval
- Gating model CI/CD
- Using a shadow deployment
- Designing a canary deployment
- Reproducing a model build
- Tracking experiments
- Defining rollback triggers
- Using active learning
- Handling experiment variation
- Tracking data lineage
- Choosing transfer learning
- Choosing batch or online inference
- Comparing throughput and latency
- Recording dataset provenance
- Making inference retries idempotent
- Checkpointing long AI jobs
- Excluding expired training data
2.1 Explain basic AI concepts and terminology44 questions
- Understanding foundation models
- Choosing the purpose of RAG
- Improving a prompt with specificity
- Distinguishing generation from classification
- Selecting benefits of foundation models
- Choosing a purpose for chunking
- Understanding multimodal models
- Recognizing generative-AI limitations
- Understanding Transformer attention
- Using embeddings for similarity
- Understanding foundation-model pretraining
- Understanding temperature
- Understanding diffusion models
- Distinguishing parameters and context
- Understanding encoder-decoder models
- Balancing embedding dimensions
- Understanding transfer learning
- Distinguishing token and document embeddings
- Choosing a multimodal model
- Separate characters, input tokens and output budgets
- Understanding attention
- Explaining diffusion generation
- Connecting generative AI applications to external tools
- Distinguishing pretraining and inference
- Using human preference feedback
- Managing a context limit
- Handling a knowledge cutoff
- Selecting a model by modality
- Evaluating quantization trade-offs
- Choosing adaptation methods
- Evaluating tokenization
- Choosing generation parameters
- Separate short-term memory, long-term memory and business knowledge
- Choosing a context window
- Selecting few-shot examples
- Handling multimodal limits
- Choosing coordination and result flow for multiple agents
- Managing model quotas
- Selecting a foundation model
- Handle the delay before long-term memory becomes available
- Aligning multimodal inputs
- Managing a token budget
- Checking provider data use
- Building a model selection matrix
2.3 Describe AWS infrastructure and technologies for building GenAI applications31 questions
- Choosing between Bedrock and SageMaker AI
- Understanding Knowledge Bases
- Understanding agent tool use
- Using prompt chaining
- Separating user input from trusted instructions
- Specifying an output schema
- Using few-shot examples
- Separating system instructions and user input
- Evaluating a prompt change
- Handling reasoning information safely
- Using message roles
- Validating prompt input
- Handling template variables safely
- Minimizing conversation memory
- Splitting a prompt workflow
- Reducing hallucinations
- Choosing generation parameters
- Approving tool execution
- Preventing output injection
- Validating tool arguments
- Ordering prompt constraints
- Tuning content-filter thresholds
- Budgeting prompt length
- Designing a safe refusal
- Separating instruction trust
- Understanding temperature
- Managing the context window
- Making generation reproducible
- Designing few-shot examples
- Using top-k and top-p
- Designing stop conditions
3.2 Choose effective prompt engineering techniques29 questions
- Requesting constrained structured output
- Adding role and constraints to a prompt
- Designing grounded RAG answers
- Filtering vector search by metadata
- Updating a RAG index
- Designing RAG chunk boundaries
- Combining keyword and vector search
- Measuring RAG retrieval quality
- Maintaining RAG permission boundaries
- Managing RAG freshness
- Improving a search query
- Pin a prompt version for production
- Considering RAG reranking
- Compressing retrieved context
- Evaluating hybrid retrieval
- Preserving document layout
- Applying authorization to RAG search
- Tuning chunk overlap
- Organizing duplicate documents
- Evaluating evidence ranking
- Clarify an ambiguous retrieval target
- Prioritizing exact identifiers
- Evaluating a reranker
- Versioning metadata filters
- Grounding answers with citations
- Updating a vector index
- Securing answer caches
- Calibrating confidence
- Compare prompt configuration changes and output quality
3.3 Describe the training and fine-tuning process for foundation models48 questions
- Choosing between RAG and fine-tuning
- Using precision and recall
- Combining human evaluation
- Evaluating retrieval relevance
- Detecting prompt-regression
- Combining quality and operational metrics
- Evaluating structured extraction
- Purpose of red-team evaluation
- Choosing precision and recall
- Combining automated and human evaluation
- Evaluating harmful content
- Designing pairwise human evaluation
- Understanding text-overlap metrics
- Using slice analysis
- Displaying answer uncertainty
- Measuring quality and latency trade-offs
- Checking confidence calibration
- Combining automatic and human evaluation
- Evaluating harmful output
- Separating offline and online metrics
- Reading a confusion matrix
- Knowing string-metric limits
- Sampling production quality
- Monitoring AI cost
- Setting AI rate limits
- Defining an AI SLO
- Choosing an incident fallback
- Routing drift alerts
- Reducing alert fatigue
- Monitoring with delayed labels
- Canary model release
- Detecting AI cost anomalies
- Securing response caching
- Designing model fallback
- Monitoring model versions
- Tracing an inference
- Staging a prompt rollout
- Setting drift alert thresholds
- Backing up and restoring AI configuration
- Separating provider SLA from measurements
- Retiring a model safely
- Isolating AI service health
- Inventorying AI dependencies
- Anonymizing AI usage analytics
- Controlling an AI budget
- Setting a data-quality SLO
- Rolling back a model
- Defining retraining triggers
3.4 Describe methods to evaluate foundation-model performance32 questions
- Selecting a text-generation evaluation metric
- Building a fixed evaluation set
- Operating generative-AI safety controls
- Validating generated output
- Monitoring inference cost
- Escalating uncertain answers
- Monitoring a generative-AI application
- Designing rate-limit fallbacks
- Responding to an AI incident
- Defining generative-AI SLOs
- Detecting quality drift
- Monitoring prompt abuse
- Building a fixed evaluation set
- Retrying inference failures
- Monitoring token cost
- Detecting input drift
- Tracing a generation workflow
- Autoscaling inference capacity
- Designing an inference health check
- Evaluating hallucinations
- Evaluating harmful output
- Standardizing human evaluation
- Maintaining a regression set
- Maintaining a golden set
- Understanding semantic metrics
- Verifying citations
- Evaluating RAG end to end
- Designing a human-review queue
- Comparing multilingual quality
- Explaining citation confidence
- Using user feedback safely
- Building a model benchmark
4.1 Explain the development of responsible AI systems40 questions
- Selecting bias-reduction activities
- Preparing representative fairness data
- Reducing model bias
- Considering user impact
- Considering group thresholds
- Minimizing personal data in AI
- Investigating proxy features
- Validating a fairness intervention
- Designing inclusive AI
- Investigating label noise
- Triggering human oversight
- Evaluating representational harm
- Evaluating subgroup fairness
- Mitigating data bias
- Balancing fairness evaluation and privacy
- Checking data representativeness
- Detecting disparate impact
- Creating labeling guidelines
- Comparing fairness thresholds
- Handling small subgroup metrics
- Measuring intersectional fairness
- Reviewing label bias
- Checking proxy attributes
- Understanding explanations
- Minimizing personal data
- Measuring group impact
- Checking representative data
- Threat-modeling privacy
- Designing accessible AI output
- Setting purpose-based retention
- Choosing fairness mitigations
- Managing AI consent
- Checking AI accessibility
- Notifying users about AI
- Showing content provenance
- Checking go-live readiness
- Reviewing copyright risk in generated content
- Tiering AI risk
- Making safety a release gate
- Comparing a new model without impact
4.2 Recognize the importance of transparent and explainable models42 questions
- Improving AI transparency and explainability
- Improving explainability
- Testing robustness
- Documenting model use conditions
- Explaining AI to different audiences
- Ensuring AI traceability
- Communicating explainability limits
- Documenting model information
- Disclosing AI use to users
- Making AI use transparent
- Routing cases to human review
- Explaining limits of explainability
- Recording model accountability
- Showing content provenance
- Designing an appeal workflow
- Disclosing high-impact AI use
- Linking explanations to evidence
- Assigning accountability
- Handling consent for AI use
- Providing transparency and appeal
- Assigning incident accountability
- Operating an AI risk register
- Maintaining model documentation
- Notifying users about AI
- Reviewing with stakeholders
- Designing human override
- Approving AI changes
- Handling appeals
- Measuring intersectional fairness
- Handling explainability limits
- Maintaining a model card
- Explaining fairness tradeoffs
- Controlling human overrides
- Defining human escalation
- Updating model documentation
- Monitoring fairness continuously
- Communicating an AI incident
- Reviewing model and data licenses
- Defining human-review criteria
- Handling an appeal of an AI decision
- Reviewing AI accessibility
- Recording an AI adoption decision
5.1 Explain methods to secure AI systems60 questions
- Protecting generative-AI inputs and outputs
- Designing least-privilege IAM for an AI application
- Identifying prompt injection
- Applying least privilege to an AI application
- Protecting personal information in AI inputs
- Managing encryption keys for AI data
- Protecting AI network paths
- Treating retrieved instructions as data
- Applying least privilege to an AI app
- Protecting AI application secrets
- Applying input and output guardrails
- Isolating AI service network paths
- Managing encryption keys
- Restricting endpoint policies
- Isolating instructions in retrieved documents
- Validating customer-category JSON
- Restricting encryption-key access
- Controlling sensitive data handling
- Using an execution role
- Not overtrusting private endpoints
- Rotating secrets
- Authenticating an inference endpoint
- Separating encryption in transit and at rest
- Controlling egress
- Limiting secret read access
- Tokenizing sensitive values
- Using IAM conditions
- Redacting sensitive logs
- Isolating document instructions
- Handling output-validation failures
- Applying authorization before retrieval
- Isolating inference networks
- Rotating inference secrets
- Restricting resource policies
- Separating encryption keys
- Protecting prompt logs
- Authenticating an inference endpoint
- Patching AI dependencies
- Using private inference paths
- Sanitizing generated output
- Providing an AI kill switch
- Handling personal data before prompting
- Preventing multi-turn injection
- Checking data residency
- Checking the model supply chain
- Checking JSON business rules and permissions
- Layering AI guardrails
- Red-teaming an AI system
- Verifying deletion requests
- Managing retention exceptions
- Performing a privacy impact assessment
- Handling harmful output
- Protecting personal data in embeddings
- Applying privacy by design
- Tracking training-data provenance
- Adding a training-data license gate
- Listing model dependencies
- Making audit evidence reproducible
- Testing adversarial input
- Stopping a dangerous AI feature
5.2 Recognize governance and compliance for AI systems56 questions
- Building an AI audit trail
- Defining AI log retention
- Reviewing compliance before AI adoption
- Adding human oversight to high-impact decisions
- Maintaining an AI model inventory
- Assigning AI asset ownership
- Managing AI-policy exceptions
- Designing audit-log retention
- Assessing third-party AI risk
- Recording AI approval evidence
- Checking AI data residency
- Managing an AI provider change
- Preserving AI incident evidence
- Setting retention and deletion policies
- Mapping compliance controls
- Protecting audit-log integrity
- Reviewing an AI service SLA
- Verifying deletion evidence
- Reviewing cross-border transfer
- Checking training-data rights
- Correlating audit events
- Deciding incident notification
- Balancing legal hold and deletion
- Reviewing the AI supply chain
- Handling deletion requests
- Preparing audit evidence
- Managing a model card
- Checking third-party licenses
- Managing retention exceptions
- Reviewing audit-log access
- Deleting records
- Managing regional requirements
- Reviewing an AI incident
- Securing AI logs
- Preventing secrets in prompts
- Reviewing AI access
- Encrypting data at rest and in transit
- Rotating encryption keys
- Separating AI governance roles
- Defining AI change approval
- Assembling audit evidence
- Rate limiting AI API abuse
- Minimizing key access
- Validating AI input
- Freezing AI changes during critical periods
- Auditing AI data access
- Approving policy exceptions
- Using a private inference path
- Decommissioning an AI service
- Bounding agent tool permissions
- Reviewing an AI vendor contract
- Distributing approved models
- Managing AI data residency
- Managing a policy exception
- Coordinating a third-party AI incident
- Assessing model-change impact
2.2 Explain foundation-model capabilities and limitations28 questions
- Understanding tokens and context length
- Choosing the purpose of embeddings
- Distinguishing pre-training and fine-tuning
- Reducing hallucinations with grounding
- Understanding model parameters
- Considering tokenization and input limits
- Designing a context window
- Reducing hallucination
- Designing multimodal input
- Comparing sampling parameters
- Delimiting input data
- Controlling output length
- Selecting grounded sources
- Summarizing long documents
- Improving few-shot examples
- Judging zero-shot use
- Separating instruction roles
- Writing a specific prompt
- Using role instructions
- Handling intermediate results
- Controlling summary source coverage
- Choosing chunk overlap
- Managing retrieval freshness
- Filtering with metadata
- Validating OCR ingestion
- Using language metadata
- Deduplicating documents
- Separating RAG and fine-tuning
3.1 Select and adapt foundation models38 questions
- Comparing models for latency
- Distinguishing zero-shot and few-shot prompting
- Choosing RAG instead of frequent retraining
- Selecting temperature for structured extraction
- Protecting customization data
- Matching model capability to requirements
- Choosing prompts before fine-tuning
- Selecting a model for latency
- Governing fine-tuning data
- Designing model routing
- Managing a model-version update
- Choosing prompts, RAG, or fine-tuning
- Considering efficient adaptation
- Comparing model capacity and latency
- Splitting customization data
- Comparing model cost and quality
- Considering model distillation
- Choosing an inference mode
- Choosing an adaptation method
- Rolling out a model update
- Selecting for latency
- Governing adaptation data
- Choosing a quality-cost frontier
- Selecting an embedding model
- Choosing vector dimensions
- Using hybrid search
- Choosing top-k
- Evaluating a reranker
- Choosing approximate nearest-neighbor search
- Using Recall@k
- Designing RAG chunks
- Explaining embedding search
- Choosing hybrid search
- Preserving grounding metadata
- Applying authorization to retrieval
- Managing retrieval freshness
- Rebuilding a vector index
- Refusing without evidence