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

The correct answer is A, as the most effective way to ensure fairness in AI systems is to audit and diversify training data. AWS Responsible AI documentation stresses that bias originates primarily from unbalanced or incomplete datasets. By including samples from all demographic groups, the model learns patterns that generalize fairly across populations. AWS SageMaker Clarify supports data bias detection and offers fairness metrics like demographic parity and equal opportunity difference. Deeper models (option B) or secrecy (option C) do not mitigate bias and may worsen transparency. Static test datasets (option D) fail to capture evolving data distributions. Therefore, ongoing bias reviews and diverse datasets form the foundation of responsible generative AI for financial use cases.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation – Bias Detection

The correct answers are A and E because both directly align with AWS best practices for securing generative AI services and data privacy in enterprise applications.

From the AWS Amazon Q Business documentation:

"AWS Key Management Service (KMS) integrates with Amazon Q Business to encrypt sensitive data at rest. You can use customer-managed KMS keys to meet compliance requirements."

And:

"You must configure IAM access controls to manage which users and applications can access Amazon Q Business indexes, ensuring that only authorized users can retrieve information."

Explanation of other options:

B. Cross-account access is not a common requirement for internal enterprise use of Amazon Q Business unless explicitly sharing data across organizations. It’s not a requirement for securing access.

C. Amazon Inspector is a vulnerability management tool for EC2 and containers. It is unrelated to Amazon Q authentication or security.

D. Allowing public access would violate security and privacy principles and directly contradict the stated requirement.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Q Business Developer Guide – Security and Identity Management

AWS KMS Documentation – Integration with Bedrock and Amazon Q

AWS Certified Machine Learning Specialty Guide – Responsible AI and Governance Section

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Bedrock provides access to multimodal foundation models that can process both text and image inputs and generate intelligent responses.

Bedrock is designed for:

Building chatbots and conversational AI

Handling multimodal inputs

Integrating LLMs with enterprise applications

Why the other options are incorrect:

Amazon Comprehend (B) performs text analysis only.

Amazon Q (C) is a managed assistant, not a general chatbot platform.

Amazon Rekognition (D) analyzes images but does not generate conversational responses.

AWS AI document references:

Amazon Bedrock Overview

Multimodal Foundation Models on AWS

Building Chatbots with Amazon Bedrock

When a model performs well on the training data but poorly in production, it is often due to overfitting. Overfitting occurs when a model learns patterns and noise specific to the training data, which does not generalize well to new, unseen data in production. Increasing the volume of data used in training can help mitigate this problem by providing a more diverse and representative dataset, which helps the model generalize better.

Option C (Correct): "Increase the volume of data that is used in training": Increasing the data volume can help the model learn more generalized patterns rather than specific features of the training dataset, reducing overfitting and improving performance in production.

Option A: "Reduce the volume of data that is used in training" is incorrect, as reducing data volume would likely worsen the overfitting problem.

Option B: "Add hyperparameters to the model" is incorrect because adding hyperparameters alone does not address the issue of data diversity or model generalization.

Option D: "Increase the model training time" is incorrect because simply increasing training time does not prevent overfitting; the model needs more diverse data.

AWS AI Practitioner References:

Best Practices for Model Training on AWS: AWS recommends using a larger and more diverse training dataset to improve a model's generalization capability and reduce the risk of overfitting.

Building a well-architected ML workload follows a structured lifecycle as outlined in AWS best practices. The process begins with defining the business goal and framing the ML problem to ensure the project aligns with organizational objectives. Next, the model is developed, which includes data preparation, training, and evaluation. Once the model is ready, it is deployed tomake predictions in a production environment. Finally, the model is monitored to ensure it performs as expected and to address any issues like drift or degradation over time. This order ensures a systematic approach to ML development.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"The machine learning lifecycle typically follows these stages: 1) Define the business goal and frame the ML problem, 2) Develop the model (including data preparation, training, and evaluation), 3) Deploy the model to production, and 4) Monitor the model for performance and drift to ensure it continues to meet business needs."

(Source: AWS AI Practitioner Learning Path, Module on Machine Learning Lifecycle)

Detailed Explanation:

Step 1: Define business goal and frame ML problemThis is the first step in any ML project. It involves understanding the business objective (e.g., reducing churn) and framing the ML problem (e.g., classification or regression). Without this step, the project lacks direction. The hotspot lists this option as "Define business goal and frame ML problem," which matches this stage.

Step 2: Develop modelAfter defining the problem, the next step is to develop the model. This includes collecting and preparing data, selecting an algorithm, training the model, and evaluating its performance. The hotspot lists "Develop model" as an option, aligning with this stage.

Step 3: Deploy modelOnce the model is developed and meets performance requirements, it is deployed to a production environment to make predictions or automate decisions. The hotspot includes "Deploy model" as an option, which fits this stage.

Step 4: Monitor modelAfter deployment, the model must be monitored to ensure it performs well over time, addressing issues like data drift or performance degradation. The hotspot lists "Monitor model" as an option, completing the lifecycle.

Hotspot Selection Analysis:

The hotspot provides four steps, each with the same dropdown options: "Select...," "Deploy model," "Develop model," "Monitor model," and "Define business goal and frame ML problem." The correct selections are:

Step 1: Define business goal and frame ML problem

Step 2: Develop model

Step 3: Deploy model

Step 4: Monitor model

Each option is used exactly once, as required, and follows the logical order of the ML lifecycle.

The temperature parameter in a large language model (LLM) controls the randomness of the model's output. A lower temperature value makes the output more deterministic and consistent, meaning that the model is less likely to produce different results for the same input prompt.

Option A (Correct): "Decrease the temperature value": This is the correct answer because lowering the temperature reduces the randomness of the responses, leading to more consistent outputs for the same input.

Option B: "Increase the temperature value" is incorrect because it would make the output more random and less consistent.

Option C: "Decrease the length of output tokens" is incorrect as it does not directly affect the consistency of the responses.

Option D: "Increase the maximum generation length" is incorrect because this adjustment affects the output length, not the consistency of the model’s responses.

AWS AI Practitioner References:

Understanding Temperature in Generative AI Models: AWS documentation explains that adjusting the temperature parameter affects the model’s output randomness, with lower values providing more consistent outputs.

The company wants to enhance the response quality of an LLM for complex problem-solving tasks requiring detailed reasoning and step-by-step explanations. Chain-of-thought prompting encourages the LLM to break down the problem into intermediate steps, providing a clear reasoning process before arriving at the final answer, which is ideal for this requirement.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"Chain-of-thought prompting improves the reasoning capabilities of large language models by encouraging them to break down complex tasks into intermediate steps, providing a step-by-step explanation that leads to the final answer. This technique is particularly effective for problem-solving tasks requiring detailed reasoning."

(Source: AWS Bedrock User Guide, Prompt Engineering Techniques)

Detailed Explanation:

Option A: Few-shot promptingFew-shot prompting provides a few examples to guide the LLM but does not explicitly encourage step-by-step reasoning or detailed explanations.

Option B: Zero-shot promptingZero-shot prompting relies on the LLM’s pre-trained knowledge without examples, making it less effective for complex tasks requiring detailed reasoning.

Option C: Directional stimulus promptingDirectional stimulus prompting is not a standard technique in AWS documentation, likely a distractor, and does not address step-by-step reasoning.

Option D: Chain-of-thought promptingThis is the correct answer. Chain-of-thought prompting enhances response quality for complex tasks by guiding the LLM to reason step-by-step, providing detailed explanations.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

The correct technique is fine-tuning, which is explicitly supported by Amazon Bedrock for customizing foundation models using high-quality labeled datasets.

Fine-tuning involves:

Starting with a pre-trained foundation model

Training it further using domain-specific, labeled data

Improving accuracy for specialized tasks, such as product classification, image-based understanding, and specification extraction

In this use case:

The company has labeled data

They want to customize model behavior

They require high accuracy and domain adaptation

These conditions match the definition of fine-tuning, not prompt-only methods.

Why the other options are incorrect:

A. Continued pre-training typically requires massive unlabeled datasets and is not the standard customization method exposed in Amazon Bedrock.

B. Creating an agent orchestrates model interactions and tools but does not customize the model’s learned parameters.

D. Prompt engineering improves responses through prompt design but does not modify the underlying model weights, making it insufficient for deep domain adaptation.

AWS AI document references (for exact extracts):

Amazon Bedrock Documentation — section on Model customization and fine-tuning

AWS Generative AI Study Guide — comparison of prompt engineering vs fine-tuning

Foundation Models on AWS — explanation of fine-tuning with labeled datasets

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Q Business is a managed AI assistant designed to:

Allow employees to query internal enterprise data

Provide conversational answers

Respect enterprise security and access controls

AWS guidance positions Amazon Q Business as the solution for internal knowledge discovery and enterprise AI assistance.

Why the other options are incorrect:

Rekognition (A) analyzes images.

Textract (B) extracts text from documents.

Lex (C) builds conversational interfaces but does not provide enterprise data integration out of the box.

AWS AI document references:

Amazon Q Business Overview

Enterprise AI Assistants on AWS

Secure Access to Internal Data with AI

Providing examples of text passages with corresponding positive or negative labels in the prompt followed by the new text passage to be classified is the correct prompt engineering strategy for using a large language model (LLM) on Amazon Bedrock for sentiment analysis.

Example-Driven Prompts:

This strategy, known as few-shot learning, involves giving the model examples of input-output pairs (e.g., text passages with their sentiment labels) to help it understand the task context.

It allows the model to learn from these examples and apply the learned pattern to classify new text passages correctly.

Why Option A is Correct:

Guides the Model: Providing labeled examples teaches the model how to perform sentiment analysis effectively, increasing accuracy.

Contextual Relevance: Aligns the model's responses to the specific task of classifying sentiment.

Why Other Options are Incorrect:

B. Detailed explanation of sentiment analysis: Unnecessary for the model's operation; it requires examples, not explanations.

C. New text passage without context: Provides no guidance or learning context for the model.

D. Unrelated task examples: Would confuse the model and lead to inaccurate results.

Transitioning to a new large language model (LLM) on Amazon Bedrock typically involves minimal changes when the new model is pre-trained and available as a foundation model. Since the company is moving from one pre-trained LLM to another, the primary task is to ensure compatibility between the new model's input requirements and the existing application. Adjusting the prompt template is often necessary because different LLMs may have varying prompt formats, tokenization methods, or response behaviors, even for similar tasks like document extraction.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"When switching between foundation models in Amazon Bedrock, you may need to adjust the prompt template to align with the new model’s expected input format and optimize its performance for your use case. Prompt engineering is critical to ensure the model understands the task and generates accurate outputs."

(Source: AWS Bedrock User Guide, Prompt Engineering for Foundation Models)

Detailed Explanation:

Option A: Create a new labeled dataset.Creating a new labeled dataset is unnecessary when transitioning to a new pre-trained LLM, as pre-trained models are already trained on large datasets. This option would only be relevant if the company were training a custom model from scratch, which is not the case here.

Option B: Perform feature engineering.Feature engineering is typically associated with traditional machine learning models, not pre-trained LLMs. LLMs process raw text inputs, and transitioning to a new LLM does not require restructuring input features. This option is incorrect.

Option C: Adjust the prompt template.This is the correct approach. Different LLMs may interpret prompts differently due to variations in training data, tokenization, or model architecture. Adjusting the prompt template ensures the new LLM understands the task (e.g., document extraction) and produces the desired output format. AWS documentation emphasizes prompt engineering as a key step when adopting a new foundation model.

Option D: Fine-tune the LLM.Fine-tuning is not required for transitioning to a new pre-trained LLM unless the company needs to customize the model for a highly specific task. Since the question does not indicate a need for customization beyond document extraction (a common LLM capability), fine-tuning is unnecessary.

Amazon SageMaker Unified Studio provides a collaborative, secure, and centralized environment for end-to-end data, machine learning, and generative AI development. AWS documentation describes Unified Studio as a single interface where teams can prepare data, build models, train and deploy machine learning solutions, and develop generative AI applications.

In this use case, multiple teams must collaborate in a shared environment. SageMaker Unified Studio supports role-based access control, shared workspaces, and secure resource management, allowing developers to safely collaborate without compromising data or models. AWS highlights that Unified Studio integrates notebooks, pipelines, model development tools, and generative AI workflows into a consistent experience.

The service also supports model sharing, versioning, and reuse, enabling teams to build upon each other’s work. This directly satisfies the requirement to build and share both traditional ML models and generative AI applications securely.

The other options are not suitable. Amazon Lex is a conversational AI service, not a development environment. Amazon Bedrock PartyRock is a no-code generative AI playground and is not intended for enterprise collaboration. Amazon Q Developer focuses on developer productivity and code assistance, not unified AI development environments.

AWS positions SageMaker Unified Studio as the foundation for collaborative AI development at scale, making it the correct choice.

The correct answer is A because Amazon Macie is a fully managed data security and privacy service that uses machine learning to automatically detect sensitive data such as PII (personally identifiable information) in Amazon S3. It requires no custom development, and it can be configured to generate alerts when sensitive data is detected in newly uploaded objects.

From AWS documentation:

"Amazon Macie automatically discovers and classifies sensitive data in S3 buckets and generates alerts when it detects sensitive content, such as names, addresses, and credit card numbers."

Explanation of other options:

B. Deploying an LLM on SageMaker to perform redaction is custom and operationally intensive.

C. Regex-based detection is brittle and requires extensive manual work, with high maintenance overhead.

D. Asking customers to avoid sharing sensitive data is not enforceable and does not meet compliance or security standards.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Macie Documentation – Sensitive Data Discovery and Alerting

AWS Security Best Practices – Data Privacy and Governance

AWS ML Specialty Guide – Governance and Compliance Automation

The ML research team needs a mechanism to audit custom ML models while sharing model artifacts with other teams. Amazon SageMaker Model Cards provide a structured way todocument model details, including intended uses, training data, and inference performance, making them ideal for auditing and ensuring transparency when publishing models.

Exact Extract from AWS AI Documents:

From the Amazon SageMaker Developer Guide:

"Amazon SageMaker Model Cards enable you to document critical details about your machine learning models, such as intended uses, training data, evaluation metrics, and inference details. Model Cards support auditing by providing a centralized record that can be reviewed by teams to understand model behavior and limitations."

(Source: Amazon SageMaker Developer Guide, SageMaker Model Cards)

Detailed Explanation:

Option A: Create documents with the relevant information. Store the documents in Amazon S3.While storing documents in S3 is feasible, it lacks the structured format and integration with SageMaker that Model Cards provide, making it less suitable for auditing purposes.

Option B: Use AWS AI Service Cards for transparency and understanding models.AWS AI Service Cards are not a standard feature in AWS documentation. This option appears to be a distractor and is not a valid solution.

Option C: Create Amazon SageMaker Model Cards with Intended uses and training and inference details.This is the correct answer. SageMaker Model Cards are specifically designed to document model details for auditing, transparency, and collaboration, meeting the team’s requirements.

Option D: Create model training scripts. Commit the model training scripts to a Git repository.Sharing training scripts in a Git repository provides access to code but does not offer a structured auditing mechanism for model details like intended uses or inference performance.

The correct answer is D – F1 score, which is the harmonic mean of precision and recall. AWS documentation states that the F1 score is the preferred metric when evaluating ML models trained on imbalanced datasets, where one class appears significantly more often than others. Accuracy becomes misleading in these situations because a model can achieve high accuracy simply by predicting the majority class. Precision alone measures correctness of positive predictions, while recall measures completeness—neither fully captures class balancing performance. The F1 score provides a combined measurement that reflects how well the model identifies minority classes while avoiding excessive false positives. AWS’s ML Specialty Guide recommends using F1 for classification tasks where “class distribution is uneven or where both false negatives and false positives matter.” This metric provides a fairer assessment of overall model performance across all class categories.

Referenced AWS Documentation:

AWS Certified Machine Learning Specialty Guide – Metrics for Imbalanced Classes

Amazon SageMaker Developer Guide – Evaluating Classification Models

Amazon SageMaker Canvas is a visual, no-code machine learning interface that allows users to build machine learning models without having any coding experience or knowledge of machine learning algorithms. It enables users to analyze internal and external data, and make predictions using a guided interface.

Option D (Correct): "Import the data into Amazon SageMaker Canvas. Build ML models and demand forecast predictions by selecting the values in the data from SageMaker Canvas": This is the correct answer because SageMaker Canvas is designed for users without coding experience, providing a visual interface to build predictive models with ease.

Option A: "Store the data in Amazon S3 and use SageMaker built-in algorithms" is incorrect because it requires coding knowledge to interact with SageMaker's built-in algorithms.

Option B: "Import the data into Amazon SageMaker Data Wrangler" is incorrect. Data Wrangler is primarily for data preparation and not directly focused on creating ML models without coding.

Option C: "Use Amazon Personalize Trending-Now recipe" is incorrect as Amazon Personalize is for building recommendation systems, not for general demand forecasting.

AWS AI Practitioner References:

Amazon SageMaker Canvas Overview: AWS documentation emphasizes Canvas as a no-code solution for building machine learning models, suitable for business analysts and users with no coding experience.

AWS documentation defines prompt injection as a security and safety risk in which a user crafts input designed to override, manipulate, or bypass system-level instructions, safeguards, or intended model behavior. The example provided is a classic prompt injection attempt, where the user explicitly instructs the AI assistant to ignore prior rules and operate without restrictions.

In this scenario, the attacker is not exploiting training data or causing factual errors, but rather attempting to change the control flow and behavior of the AI system through malicious or manipulative prompts. AWS identifies prompt injection as a critical risk for generative AI systems, especially those exposed to end users through chat interfaces, APIs, or customer-facing applications.

The other options do not apply. Data bias relates to skewed or unfair training data. Hallucination refers to generating incorrect or fabricated information. Data exposure involves leaking sensitive or private data. None of these describe an attempt to override system instructions.

AWS recommends multiple mitigation strategies for prompt injection risks, including instruction hierarchy enforcement, prompt isolation, input validation, output filtering, and grounding responses using techniques such as Retrieval Augmented Generation. AWS also emphasizes the importance of clearly separating system instructions from user inputs to prevent unauthorized behavior changes.

Prompt injection is categorized by AWS as part of Responsible AI and security governance, highlighting the need for robust guardrails when deploying AI assistants in production. Therefore, the correct answer is prompt injection.

Amazon Bedrock Guardrails allow developers to create safeguards that filter harmful content and prevent sensitive topics from being discussed. This functionality helps mitigate prompt injection attacks with minimal implementation effort. According to the official Amazon Bedrock documentation:

“You can configure Guardrails for Amazon Bedrock to define denied topics, use content filters, and apply sensitive information filters, offering protection against prompt injection attacks with minimal development effort.”