AIF-C01 Amazon Web Services AWS Certified AI Practitioner Exam Free Practice Exam Questions (2026 Updated)

The verified answer is A. Configure Amazon Macie to detect sensitive information in the documents that are uploaded to Amazon S3. The data is stored in Amazon S3, and the company wants automated sensitive information detection with the least development effort. AWS documentation states that Amazon Macie can automate discovery, logging, and reporting of sensitive data in an Amazon S3 data estate. Macie can use automated sensitive data discovery or sensitive data discovery jobs, and it can analyze S3 objects using AWS-managed data identifiers, custom data identifiers, or both.

This fits the requirement better than a custom ML or regex-based approach because Macie is purpose-built for discovering sensitive data in S3. AWS states that managed data identifiers can detect many types of sensitive data, including personally identifiable information, financial information, and credentials. Macie also produces sensitive data findings and discovery results, which can be monitored and processed by other AWS services.

Option B is incorrect because deploying an LLM on SageMaker would require model selection, deployment, prompt design, testing, security controls, and possibly custom redaction logic. That is not the least development effort.

Option C is incorrect because manually developing regex patterns is brittle and maintenance-heavy. It also requires custom development and does not fully automate sensitive information detection across many data types.

Option D is incorrect because asking customers not to share sensitive data is not a technical control and cannot guarantee detection or alerting.

Because the documents are in Amazon S3 and sensitive data detection must be automated, Amazon Macie is the correct solution.

The verified answer is C. Amazon Inspector. The company needs automated vulnerability assessment for Amazon EC2-based infrastructure. AWS documentation states that Amazon Inspector scans EC2 instances for package vulnerabilities and network reachability issues and produces findings. It compares instance metadata against vulnerability intelligence and security advisory rules. This is exactly the service used to assess EC2 infrastructure before deploying sensitive workloads such as generative AI models.

AWS also documents that Amazon Inspector scans EC2 instances for common vulnerabilities and exposures, operating system package vulnerabilities, programming language package vulnerabilities, network exposure issues, and network reachability issues. This confirms that Inspector is the correct service for automated vulnerability assessment of EC2-based ML infrastructure.

AWS CloudFormation is incorrect because it provisions infrastructure as code. It can create EC2 instances, security groups, and related resources, but it does not perform vulnerability assessment. Amazon Comprehend is incorrect because it is a natural language processing service used to extract insights from text. It does not scan infrastructure. AWS Trusted Advisor is incorrect because it provides best-practice recommendations across categories such as cost optimization, security, performance, and service limits, but it is not the dedicated automated vulnerability assessment service for EC2 instances.

The requirement is specific: scan EC2-based ML infrastructure for vulnerabilities before deployment. The AWS-native service that performs this function is Amazon Inspector.

Amazon SageMaker Feature Store is the correct solution for sharing and managing variables (features) across multiple teams during model development.

Amazon SageMaker Feature Store:

A fully managed repository for storing, sharing, and managing machine learning features across different teams and models.

It enables collaboration and reuse of features, ensuring consistent data usage and reducing redundancy.

Why Option A is Correct:

Centralized Feature Management: Provides a central repository for managing features, making it easier to share them across teams.

Collaboration and Reusability: Improves efficiency by allowing teams to reuse existing features instead of creating them from scratch.

Why Other Options are Incorrect:

B. SageMaker Data Wrangler: Helps with data preparation and analysis but does not provide a centralized feature store.

C. SageMaker Clarify: Used for bias detection and explainability, not for managing variables across teams.

D. SageMaker Model Cards: Provide model documentation, not feature management.

To securely use large language models (LLMs) on Amazon Bedrock, companies should design clear and specific prompts to avoid unintended outputs and ensure proper configuration of AWS Identity and Access Management (IAM) roles and policies with the principle of least privilege. This approach limits access to sensitive resources and minimizes the potential impact of security incidents.

Option A (Correct): " Design clear and specific prompts. Configure AWS Identity and Access Management (IAM) roles and policies by using least privilege access " : This is the correct answer as it directly addresses both security practices in prompt design and access management.

Option B: " Enable AWS Audit Manager for automatic model evaluation jobs " is incorrect because Audit Manager is for compliance and auditing, not directly related to secure LLM usage.

Option C: " Enable Amazon Bedrock automatic model evaluation jobs " is incorrect because Bedrock does not provide automatic model evaluation jobs specifically for security purposes.

Option D: " Use Amazon CloudWatch Logs to make models explainable and to monitor for bias " is incorrect because CloudWatch Logs are used for monitoring and not directly for making models explainable or secure.

AWS AI Practitioner References:

Secure AI Practices on AWS: AWS recommends configuring IAM roles and using least privilege access to ensure secure usage of AI models.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Multimodal models are designed to process and reason across multiple data modalities, such as text, images, audio, and video.

AWS generative AI guidance defines multimodal use cases as those where:

Inputs come from different data types

The model combines visual, textual, or audio understanding

Outputs are generated based on combined context

Why the other options are incorrect:

A describes deployment strategy, not multimodality.

B describes training scale, not model capability.

C is a coding use case, not multimodal processing.

AWS AI document references:

Multimodal Foundation Models on AWS

Generative AI Capabilities and Use Cases

Building Multimodal Applications

Fairness refers to the absence of bias in AI models. Using non-representative datasets leads to biased predictions, affecting specific demographics unfairly. Explainability, privacy, and transparency are important but not directly related to this scenario. References: AWS Responsible AI Framework.

Amazon SageMaker ' s DeepAR is a supervised learning algorithm designed for forecasting scalar (one-dimensional) time series data. Time series data consists of sequences of data points indexed in time order, typically with consistent intervals between them. In the context of a retail store aiming to predict product demand, relevant time series data might include historical sales figures, inventory levels, or related metrics recorded over regular time intervals (e.g., daily or weekly). By training the DeepAR model on this historical time series data, the store can generate forecasts for future product demand. This capability is particularly useful for inventory management, staffing, and supply chain optimization. Other data types, such as text, image, or binary data, are not suitable for time series forecasting tasks and would not be appropriate inputs for the DeepAR algorithm.

To build an AI model responsibly and minimize bias, it is essential to ensure fairness and transparency throughout the model development and deployment process. This involves detecting and mitigating data imbalances and thoroughly evaluating the model ' s behavior to understand its impact on different groups.

Option A (Correct): " Detect imbalances or disparities in the data " : This is correct because identifying and addressing data imbalances or disparities is a critical step in reducing bias. AWS provides tools like Amazon SageMaker Clarify to detect bias during data preprocessing and model training.

Option C (Correct): " Evaluate the model ' s behavior so that the company can provide transparency to stakeholders " : This is correct because evaluating the model ' s behavior for fairness and accuracy is key to ensuring that stakeholders understand how the model makes decisions. Transparency is a crucial aspect of responsible AI.

Option B: " Ensure that the model runs frequently " is incorrect because the frequency of model runs does not address bias.

Option D: " Use the Recall-Oriented Understudy for Gisting Evaluation (ROUGE) technique to ensure that the model is 100% accurate " is incorrect because ROUGE is a metric for evaluating the quality of text summarization models, not for minimizing bias.

Option E: " Ensure that the model ' s inference time is within the accepted limits " is incorrect as it relates to performance, not bias reduction.

AWS AI Practitioner References:

Amazon SageMaker Clarify: AWS offers tools such as SageMaker Clarify for detecting bias in datasets and models, and for understanding model behavior to ensure fairness and transparency.

Responsible AI Practices: AWS promotes responsible AI by advocating for fairness, transparency, and inclusivity in model development and deployment.

When a model is trained on a dataset containing confidential or sensitive data, the model may inadvertently learn patterns from this data, which could then be reflected in its inference responses. To ensure that a model does not generate responses based on confidential data, the most effective approach is to remove the confidential data from the training dataset and then retrain the model.

Explanation of Each Option:

Option A (Correct): " Delete the custom model. Remove the confidential data from the training dataset. Retrain the custom model. " This option is correct because it directly addresses the core issue: the model has been trained on confidential data. The only way to ensure that the model does not produce inferences based on this data is to remove the confidential information from the training dataset and then retrain the model from scratch. Simply deleting the model and retraining it ensures that no confidential data is learned or retained by the model. This approach follows the best practices recommended by AWS for handling sensitive data when using machine learning services like Amazon Bedrock.

Option B: " Mask the confidential data in the inference responses by using dynamic data masking. " This option is incorrect because dynamic data masking is typically used to mask or obfuscate sensitive data in a database. It does not address the core problem of the model beingtrained on confidential data. Masking data in inference responses does not prevent the model from using confidential data it learned during training.

Option C: " Encrypt the confidential data in the inference responses by using Amazon SageMaker. " This option is incorrect because encrypting the inference responses does not prevent the model from generating outputs based on confidential data. Encryption only secures the data at rest or in transit but does not affect the model ' s underlying knowledge or training process.

Option D: " Encrypt the confidential data in the custom model by using AWS Key Management Service (AWS KMS). " This option is incorrect as well because encrypting the data within the model does not prevent the model from generating responses based on the confidential data it learned during training. AWS KMS can encrypt data, but it does not modify the learning that the model has already performed.

AWS AI Practitioner References:

Data Handling Best Practices in AWS Machine Learning: AWS advises practitioners to carefully handle training data, especially when it involves sensitive or confidential information. This includes preprocessing steps like data anonymization or removal of sensitive data before using it to train machine learning models.

Amazon Bedrock and Model Training Security: Amazon Bedrock provides foundational models and customization capabilities, but any training involving sensitive data should follow best practices, such as removing or anonymizing confidential data to prevent unintended data leakage.

The correct answers are A and C because:

Amazon Transcribe converts spoken dialogue from video into text (captions or subtitles).

Amazon Translate translates that transcribed text into other languages.

Amazon Polly can then convert the translated text into lifelike speech for voice-overs in different languages.

From AWS documentation:

" Amazon Transcribe is used to create accurate speech-to-text transcripts. You can feed this text into Amazon Translate to support multilingual subtitles. To generate audio output, Amazon Polly provides neural text-to-speech in multiple languages. "

Explanation of other options:

B. Amazon Textract is used for extracting text from documents/images, not audio or video, and is not applicable here.

D. Amazon Translate does not generate speech — it only translates text.

E. Amazon Textract does not generate audio.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Transcribe Developer Guide – Media Transcription

Amazon Translate Developer Guide – Multilingual Support

Amazon Polly Documentation – Text-to-Speech in Multiple Languages

AWS ML Specialty Guide – Multimedia AI Workflows

Comprehensive and Detailed Explanation From Exact AWS AI documents:

BLEU is a widely used metric for evaluating machine translation by comparing machine-generated translations against reference (human) translations.

In this scenario:

Both systems are evaluated on the same dataset

The goal is to compare model output against human output

AWS ML evaluation guidance describes BLEU as suitable for relative comparison of translation quality across systems.

Why the other options are incorrect:

Absolute quality (A, C) is difficult to measure without human judgment.

BERTScore (D) is more computationally complex and less standard for operational comparisons.

AWS AI document references:

Evaluating Machine Translation Models

NLP Model Evaluation Metrics

Comparing AI and Human Translations

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI principles stress the importance of fairness, robustness, and accountability, which begin with the quality of the data used to train models. A responsible dataset should:

Be diverse, representing different populations, environments, and conditions to reduce bias

Be sourced from reputable and appropriate sources, ensuring data quality and ethical use

Have balanced categories, preventing the model from favoring one class over others and reducing the risk of discriminatory outcomes

These characteristics help ensure that the resulting image classification model behaves fairly, performs reliably across groups, and aligns with AWS Responsible AI best practices.

Why the other options are incorrect:

B focuses on dataset size rather than quality, balance, or representativeness.

C increases the risk of bias and poor generalization.

D limits diversity and does not inherently ensure fairness or accountability.

AWS AI Study Guide References:

AWS Responsible AI principles: fairness and data quality

AWS guidance on dataset selection and preparation for responsible ML

The verified answer is B. AWS Artifact. AWS Artifact provides on-demand downloads of AWS security and compliance documents, including compliance reports and certifications. AWS documentation also states that AWS Artifact can provide security and compliance documents for independent software vendors who sell products on AWS Marketplace. This directly matches the requirement involving ISV compliance reports.

AWS Artifact documentation further explains that users can access AWS reports on the AWS reports tab and access independent software vendor reports on the Third-party reports tab. This confirms that AWS Artifact is the correct service for obtaining ISV compliance documentation.

The notification requirement also points to AWS Artifact. AWS documentation states that the AWS Artifact console can be used to configure email notifications for updates on agreements and reports in AWS Artifact. AWS Artifact sends those notifications through AWS User Notifications, and users can specify notification recipients and which notifications they receive.

AWS Audit Manager is incorrect because it helps automate evidence collection and compliance assessments for the customer’s AWS usage. It does not primarily provide ISV compliance report notifications. AWS Trusted Advisor is incorrect because it provides best-practice recommendations for AWS accounts, not ISV report availability. AWS Data Exchange is incorrect because it is used to find, subscribe to, and use third-party data products. It is not the compliance report and notification portal.

Therefore, the correct service is AWS Artifact.

AWS documentation recommends exposing deployed machine learning models through secure, managed API endpoints to provide controlled and scalable access for external consumers. Creating a secure API endpoint allows customers to invoke the model using standard HTTPS requests while maintaining strict security boundaries.

AWS services such as Amazon SageMaker support deploying models behind managed endpoints that integrate with AWS security features, including authentication, authorization, encryption in transit, throttling, and monitoring. By using an API-based approach, the company can ensure that external customers interact with the model without gaining direct access to the underlying infrastructure or credentials.

The other options introduce significant security risks. Sharing credentials directly violates AWS security best practices and could lead to unauthorized access. Custom authentication scripts in customer applications are difficult to standardize and maintain. Embedding the model directly into customer applications removes centralized control and makes updates and security management impractical.

AWS positions secure API endpoints as the preferred mechanism for exposing ML inference capabilities to external clients, making this the correct solution.

Amazon OpenSearch Service (formerly Amazon Elasticsearch Service) has introduced capabilities to support vector search, which allows companies to build vector database applications. This is particularly useful in machine learning, where vector representations (embeddings) of data are often used to capture semantic meaning.

Scalable index management and nearest neighbor search capability are the core features enabling vector database functionalities in OpenSearch. The service allows users to index high-dimensional vectors and perform efficient nearest neighbor searches, which are crucial for tasks such as recommendation systems, anomaly detection, and semantic search.

Here is why option C is the correct answer:

Scalable Index Management: OpenSearch Service supports scalable indexing of vector data. This means you can index a large volume of high-dimensional vectors and manage these indexes in a cost-effective and performance-optimized way. The service leverages underlying AWS infrastructure to ensure that indexing scales seamlessly with data size.

Nearest Neighbor Search Capability: OpenSearch Service ' s nearest neighbor search capability allows for fast and efficient searches over vector data. This is essential for applications like product recommendation engines, where the system needs to quickly find the most similar items based on a user ' s query or behavior.

AWS AI Practitioner References:

According to AWS documentation, OpenSearch Service ' s support for nearest neighbor search using vector embeddings is a key feature for companies building machine learning applications that require similarity search.

The service uses Approximate Nearest Neighbors (ANN) algorithms to speed up searches over large datasets, ensuring high performance even with large-scale vector data.

The other options do not directly relate to building vector database applications:

A. Integration with Amazon S3 for object storage is about storing data objects, not vector-based searching or indexing.

B. Support for geospatial indexing and queries is related to location-based data, not vectors used in machine learning.

D. Ability to perform real-time analysis on streaming data relates to analyzing incoming data streams, which is different from the vector search capabilities.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Fairness is a core principle of AWS Responsible AI. It requires that AI systems:

Do not produce biased or discriminatory outcomes

Treat individuals and groups equitably

Are evaluated and mitigated for bias across protected attributes

AWS Responsible AI guidance specifically highlights fairness as the principle used to identify, measure, and mitigate bias in AI systems such as recommendation engines.

Why the other options are incorrect:

Governance (A) focuses on oversight and policies.

Explainability (B) explains decisions but does not directly mitigate bias.

Controllability (C) focuses on human oversight and intervention.

AWS AI document references:

AWS Responsible AI Principles

Bias and Fairness in ML Systems

Responsible AI Best Practices on AWS

Provide labeled data to customize a model to improve performance on specific tasks.

Correct Answer: Fine-tuning

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI guidance defines fine-tuning as the process of adapting a pre-trained foundation model using labeled, task-specific data. Fine-tuning adjusts the model’s parameters so it performs better on a particular task, such as classification, summarization, or domain-specific reasoning.

Fine-tuning is commonly used when:

High-quality labeled data is available

The goal is to improve accuracy on a specific task

The base FM already has strong general capabilities

AWS AI Study Guide References:

AWS foundation model customization methods

AWS fine-tuning concepts for generative AI

Provide unlabeled data to customize a foundation model for a specific domain.

Correct Answer: Continued pre-training

Comprehensive and Detailed Explanation (AWS AI documents):

AWS documentation describes continued pre-training as extending the training of a foundation model using large volumes of unlabeled, domain-specific data. This method helps the model better understand domain vocabulary, structure, and context without requiring labeled datasets.

Continued pre-training is useful when:

Large amounts of unlabeled domain data are available

The goal is to improve domain understanding rather than a single task

Labeling data would be expensive or impractical

AWS AI Study Guide References:

AWS generative AI training lifecycle

AWS guidance on domain adaptation using unlabeled data

Transfer knowledge from a larger and more intelligent model to a smaller model.

Correct Answer: Distillation

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI materials define distillation as a technique where a smaller model (student) learns to replicate the behavior of a larger, more capable model (teacher). The goal is to retain most of the performance while reducing model size, cost, and inference latency.

Distillation is commonly used to:

Reduce operational costs

Improve inference speed

Deploy models to resource-constrained environments

AWS AI Study Guide References:

AWS model optimization techniques

AWS knowledge distillation concepts

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Clarify provides tools for:

Model explainability

Bias detection

Transparency through metrics, reports, and explanations

For regulated industries such as healthcare, AWS recommends Clarify to:

Explain model predictions

Demonstrate fairness and accountability

Support regulatory and ethical requirements

Why the other options are incorrect:

Inspector (A) focuses on security vulnerabilities.

Macie (C) focuses on data security and privacy.

Rekognition (D) is for image labeling, not explainability.

AWS AI document references:

Amazon SageMaker Clarify Documentation

Responsible AI on AWS

Explainable AI for Regulated Industries

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Retrieval Augmented Generation (RAG) enhances LLM responses by:

Retrieving relevant information from external knowledge sources

Injecting retrieved content into the prompt context

Reducing hallucinations and improving factual accuracy

AWS generative AI guidance describes RAG as a best practice when models must use up-to-date or domain-specific knowledge that is not embedded in the model weights.

Why the other options are incorrect:

RL (A) focuses on reward-based learning.

NLP (B) is a broad field, not a specific technique.

Transfer learning (D) adapts model weights but does not retrieve external data at inference time.

AWS AI document references:

Retrieval Augmented Generation on AWS

Improving LLM Accuracy with External Knowledge

Generative AI Architectures