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

A multi-modal embedding model is the correct type of foundation model (FM) for powering a search application that handles queries containing both text and images.

Multi-Modal Embedding Model:

Can process and integrate different types of data (e.g., text and images) into a common representation space, enabling a unified search capability.

Suitable for applications where queries or content involve multiple data modalities.

Why Option A is Correct:

Handles Multiple Modalities: Supports both text and image data, aligning with the application ' s requirement.

Improves Search Relevance: Allows for more accurate and relevant search results across different types of input data.

Why Other Options are Incorrect:

B. Text embedding model: Only handles text data, not images.

C. Multi-modal generation model: Focuses on generating outputs rather than embedding for search tasks.

D. Image generation model: Only handles image data, not suitable for text queries.

Guardrails for Amazon Bedrock provide mechanisms to filter and control the content generated by models to comply with privacy and policy requirements. Using guardrails ensures that sensitive or personal information is not included in the model ' s responses. Additionally, integrating Amazon CloudWatch alarms allows for real-time notification when a policy violation occurs.

Option C (Correct): " Use Guardrails for Amazon Bedrock to filter content. Set up Amazon CloudWatch alarms for notification of policy violations " : This is the correct answer because it directly addresses both the prevention of policy violations and the requirement to receive notifications when such violations occur.

Option A: " Use Amazon Macie to scan the model ' s output for sensitive data " is incorrect because Amazon Macie is designed to monitor data in S3, not to filter real-time model outputs.

Option B: " Configure AWS CloudTrail to monitor the model ' s responses " is incorrect because CloudTrail tracks API activity and is not suited for content moderation.

Option D: " Implement Amazon SageMaker Model Monitor to detect data drift " is incorrect because data drift detection does not address content moderation or privacy compliance.

AWS AI Practitioner References:

Guardrails in Amazon Bedrock: AWS provides guardrails to ensure AI models comply with content policies, and using CloudWatch for alerting integrates monitoring capabilities.

The problem involves a simple probability calculation that can be handled efficiently by straightforward mathematical rules and computations. Using machine learning techniques would introduce unnecessary complexity and operational overhead.

Option C (Correct): " Use code that will calculate probability by using simple rules and computations " : This is the correct answer because it directly solves the problem with minimal overhead, using basic probability rules.

Option A: " Use supervised learning to create a regression model " is incorrect as it overcomplicates the solution for a simple probability problem.

Option B: " Use reinforcement learning to train a model " is incorrect because reinforcement learning is not needed for a simple probability calculation.

Option D: " Use unsupervised learning to create a model " is incorrect as unsupervised learning is not applicable to this task.

AWS AI Practitioner References:

Choosing the Right Solution for AI Tasks: AWS recommends using the simplest and most efficient approach to solve a given problem, avoiding unnecessary machine learning techniques for straightforward tasks.

Directional stimulus prompting guides the foundation model to produce outputs aligned with business context. It’s particularly effective for aligning responses with public documents and improving coherence. From Bedrock Prompt Engineering Techniques documentation:

“Directional stimulus prompting provides structured prompts to steer the model output towards desired formats or behaviors using specific linguistic cues.”

Automated Reasoning checks are specifically designed to determine whether a foundation model ' s response is logically consistent with policies, rules, and requirements supplied by an organization. AWS states that Automated Reasoning checks “use mathematical techniques to validate natural language content against policies you define.”

This directly matches the scenario. The organization has company policies, and the AI assistant generates explanations of those policies. The requirement is not simply to remove harmful language or verify that the response came from retrieved source material. Instead, the company needs to validate whether the generated answer conforms to its defined policy rules.

Amazon Bedrock Automated Reasoning converts relevant natural-language content into formal logical representations and evaluates the model ' s claims against an Automated Reasoning policy. AWS explains that the resulting findings can identify statements that contradict policy rules, expose unstated assumptions, and provide verifiable reasoning about whether a response is consistent with the policy. The result can be classified as valid, invalid, satisfiable, or another logical outcome.

Content filters primarily detect categories of undesirable or harmful content, including configurable prompt-attack detection. They do not formally prove compliance with a company ' s business rules.

Contextual grounding checks determine whether responses are grounded in supplied source material and relevant to a user ' s query. This is particularly useful for detecting hallucination in RAG applications, but it is not the same as validating logical compliance with formal company policies.

Sensitive information filters detect information such as personally identifiable information and configured sensitive data patterns.

Therefore, because the organization specifically wants to validate AI-generated policy explanations against its defined policies, Automated Reasoning checks provide the purpose-built Amazon Bedrock Guardrails capability.

===========

The verified answer is A. Amazon Bedrock Guardrails. AWS documentation states that Amazon Bedrock Guardrails helps detect sensitive information, including personally identifiable information, in input prompts or model responses by using sensitive information filters. AWS also states that these filters can be configured to block or mask detected PII. This directly matches the requirement to prevent a customer service agent from disclosing PII during conversations.

Bedrock Guardrails supports handling sensitive information in two key ways. A block action can block requests or responses that include sensitive information, and a mask action can anonymize or redact detected information in model requests or responses. AWS gives examples of PII categories such as names, email addresses, phone numbers, usernames, passwords, addresses, credit card numbers, PINs, and other sensitive identifiers. For a customer service agent, this is exactly the right feature because PII could appear in either the user input or the model response.

Amazon Bedrock Flows is incorrect because flows help orchestrate generative AI workflows. They do not primarily provide PII filtering. Amazon Bedrock Knowledge Bases is incorrect because knowledge bases support Retrieval Augmented Generation by connecting models to enterprise data sources. They help ground responses but do not directly block PII disclosure. Amazon Bedrock Data Automation is incorrect because BDA is used to transform and extract insights from multimodal content such as documents, images, audio, and video. It is not the runtime guardrail feature for blocking or masking PII in conversations.

Therefore, the correct Amazon Bedrock feature is Amazon Bedrock Guardrails.

The correct answer is A because Amazon SageMaker Canvas is designed specifically for users with little or no machine learning or programming experience. It provides a visual interface to build ML models by simply uploading data, performing analysis, and generating predictions using a no-code environment.

From the AWS documentation:

" Amazon SageMaker Canvas enables business analysts and other users to generate accurate ML predictions using a visual, point-and-click interface without writing code or having prior ML experience. "

This feature allows the user to:

Import datasets (e.g., HR data)

Automatically explore the data

Select the prediction column (e.g., attrition)

Train the model

Generate and export predictions

Explanation of other options:

B. SageMaker Clarify is used to detect bias and explain ML predictions but not to build models or make predictions without code.

C. SageMaker Model Monitor monitors model quality in production but doesn’t build or train models.

D. SageMaker Data Wrangler is used for data preprocessing and transformation but still requires some technical configuration.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker Canvas Developer Guide

AWS Certified Machine Learning Specialty Study Guide – AutoML and No-Code Tools Section

AWS Machine Learning Blog: “Predict Employee Attrition with SageMaker Canvas”

Prompt injection attacks attempt to manipulate large language models into disregarding intended instructions or revealing protected information.

Fake completion involves supplying partially completed responses that influence subsequent model output. Extracting conversation history attempts to retrieve previous interactions that might contain confidential information. Ignoring the prompt template directly instructs the model to disregard its established behavioral constraints.

Extracting the prompt template exposes hidden instructions or formatting structures. AWS explains that attackers can subsequently imitate exposed template tags to introduce malicious instructions.

The fourth description specifically concerns template-tag spoofing, which AWS identifies as a potential consequence of prompt-template extraction rather than extraction itself. However, option B is the intended association among the available choices.

AWS recommends layered protection against prompt injection, including input validation, access controls, and appropriate guardrails.

Generative AI is a type of AI that creates new content, such as text, images, or audio, often mimicking human-like outputs. A practical use case for generative AI is employing a chatbot to provide human-like responses to customer queries in real time, as it leverages the ability of large language models (LLMs) to generate natural language responses dynamically.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Generative AI enables applications like chatbots to produce human-like text responses in real time, enhancing customer support by providing natural and contextually relevant answers to user queries. "

(Source: AWS Bedrock User Guide, Introduction to Generative AI)

Detailed Explanation:

Option A: Using an ML model to forecast product demandForecasting product demand typically involves predictive analytics using supervised learning (e.g., regression models), not generative AI, which focuses on creating new content.

Option B: Employing a chatbot to provide human-like responses to customer queries in real timeThis is the correct answer. Generative AI, particularly LLMs, is commonly used to power chatbots that generate human-like responses, making this a practical use case.

Option C: Using an analytics dashboard to track website traffic and user behaviorAn analytics dashboard involves data visualization and analysis, not generative AI, which is about creating new content.

Option D: Implementing a rule-based recommendation engine to suggest products to customersA rule-based recommendation engine relies on predefined rules, not generative AI. Generative AI could be used for more dynamic recommendations, but this scenario does not describe such a case.

Amazon SageMaker Clarify provides transparency and explainability for machine learning models by generating metrics, reports, and examples that help to understand model predictions. For a medical company that needs a foundation model to be transparent and explainable to meet regulatory requirements, SageMaker Clarify is the most suitable solution.

Amazon SageMaker Clarify:

It helps in identifying potential bias in the data and model, and also explains model behavior by generating feature attributions, providing insights into which features are most influential in the model ' s predictions.

These capabilities are critical in medical applications where regulatory compliance often mandates transparency and explainability to ensure that decisions made by the model can be trusted and audited.

Why Option B is Correct:

Transparency and Explainability: SageMaker Clarify is explicitly designed to provide insights into machine learning models ' decision-making processes, helping meet regulatory requirements by explaining why a model made a particular prediction.

Compliance with Regulations: The tool is suitable for use in sensitive domains, such as healthcare, where there is a need for explainable AI.

Why Other Options are Incorrect:

A. Amazon Inspector: Focuses on security assessments, not on explainability or model transparency.

C. Amazon Macie: Provides data security by identifying and protecting sensitive data, but does not help in making models explainable.

D. Amazon Rekognition: Used for image and video analysis, not relevant to making models explainable.

Thus, B is the correct answer for meeting transparency and explainability requirements for the foundation model

Amazon Bedrock provides large language models (LLMs) that are optimized for natural language understanding and text summarization tasks, making it the best choice for creating concise summaries of user reviews. Time-series forecasting, classification, and image analysis (Rekognition) are not suitable for summarizing textual data. References: AWS Bedrock Documentation.

Using Amazon Bedrock with large language models (LLMs) allows for efficient utilization of AI to answer queries based on context provided in product manuals. To achieve this cost-effectively, the company should avoid unnecessary use of resources.

Option A (Correct): " Use prompt engineering to add one PDF file as context to the user prompt when the prompt is submitted to Amazon Bedrock " : This is the most cost-effective solution. By using prompt engineering, only the relevant content from one PDF file is added as context to each query. This approach minimizes the amount of data processed, which helps in reducing costs associated with LLMs ' computational requirements.

Option B: " Use prompt engineering to add all the PDF files as context to the user prompt when the prompt is submitted to Amazon Bedrock " is incorrect. Including all PDF files would increase costs significantly due to the large context size processed by the model.

Option C: " Use all the PDF documents to fine-tune a model with Amazon Bedrock " is incorrect. Fine-tuning a model is more expensive than using prompt engineering, especially if done for multiple documents.

Option D: " Upload PDF documents to an Amazon Bedrock knowledge base " is incorrect because Amazon Bedrock does not have a built-in knowledge base feature for directly managing and querying PDF documents.

AWS AI Practitioner References:

Prompt Engineering for Cost-Effective AI: AWS emphasizes the importance of using prompt engineering to minimize costs when interacting with LLMs. By carefully selecting relevant context, users can reduce the amount of data processed and save on expenses.

The company needs to address the degradation in model inference quality after 4 months in production and prevent future occurrences by receiving notifications. Retraining the model can address the current degradation, likely caused by data drift (changes in the data distribution over time). Amazon SageMaker Model Monitor is designed to detect and monitor model drift, alerting the company when inference quality degrades, thus meeting both requirements.

Exact Extract from AWS AI Documents:

From the Amazon SageMaker Developer Guide:

" Amazon SageMaker Model Monitor enables you to monitor machine learning models in production for data drift, model performance degradation, and other quality issues. It can detect drift in feature distributions and inference quality, sending notifications when deviations are detected, allowing you to take corrective actions such as retraining the model. "

(Source: Amazon SageMaker Developer Guide, Monitoring Models with SageMaker Model Monitor)

Detailed Explanation:

Option A: Retrain the model. Monitor model drift by using Amazon SageMaker Clarify.SageMaker Clarify is used for bias detection and explainability, not for monitoring model drift or inference quality in production. This option does not fully meet the requirements.

Option B: Retrain the model. Monitor model drift by using Amazon SageMaker Model Monitor.This is the correct answer. Retraining addresses the current degradation, and SageMaker Model Monitor can detect future drift in inference quality, sending notifications to prevent recurrence, as required.

Option C: Build a new model. Monitor model drift by using Amazon SageMaker Feature Store.SageMaker Feature Store is for managing and sharing features, not for monitoring model drift or inference quality. Building a new model may not be necessary if retraining can address the issue.

Option D: Build a new model. Monitor model drift by using Amazon SageMaker JumpStart.SageMaker JumpStart provides pre-trained models and solutions for quick deployment, but it does not offer specific tools for monitoring model drift or inference quality in production.

Amazon Bedrock Knowledge Bases with Retrieval Augmented Generation (RAG) is the appropriate architecture because it separates frequently changing enterprise information from the foundation model ' s learned parameters. Instead of retraining or fine-tuning the FM every time documentation changes, the application retrieves relevant information from the current knowledge source at query time and supplies that information as context to the model.

AWS specifically states that adding a knowledge base improves cost-effectiveness by “removing the need to continually train your model to be able to use your private data.” This directly satisfies the requirement to avoid recurring model-training costs.

With Amazon Bedrock Knowledge Bases, the organization connects supported data sources, ingests and indexes the documents, and retrieves relevant chunks when a user asks a question. RAG then combines that retrieved content with the user ' s query so that the FM can generate an answer grounded in company information. AWS describes RAG as using information from data sources to improve the relevance and accuracy of generated responses.

When source documents change, the knowledge base can be synchronized or re-ingested so the retrieval layer reflects the updated content. This is substantially more appropriate than fine-tuning the model after every documentation change.

Option B would unnecessarily introduce repeated customization jobs, cost, operational overhead, and model-version management. Option C would become stale because static examples would continue referencing earlier documentation. Option D is especially unsuitable because cached answers can become outdated and would not verify them against newly updated source material.

RAG is specifically designed for scenarios where models require access to current, proprietary, or rapidly changing information without embedding that knowledge permanently into model weights.

Therefore, A. Amazon Bedrock Knowledge Bases with RAG is the correct solution.

===========

Temperature is an inference parameter that directly influences the randomness and creativity of content generated by a foundation model.

During text generation, a language model assigns probabilities to potential next tokens. Temperature adjusts this probability distribution, affecting how predictably the model selects subsequent tokens.

A lower temperature generally produces more deterministic, consistent responses, making it useful for factual question answering and structured business applications.

A higher temperature increases the likelihood of selecting less probable tokens, potentially producing more diverse and creative responses.

Token length controls output size, while an end token sequence determines when generation stops.

Top K also affects output diversity by restricting the number of candidate tokens. However, temperature is the standard answer because it directly regulates sampling randomness and creativity.

AWS documents both temperature and Top K as generation-control parameters.

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

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Feature engineering focuses on:

Creating new features

Selecting the most relevant existing features

Improving model signal and accuracy

AWS ML best practices identify feature engineering as a key driver of predictive performance.

Why the other options are incorrect:

Visualization (A) helps understanding, not feature creation.

Hyperparameter tuning (B) optimizes models, not features.

Data collection (D) expands datasets but does not engineer features.

AWS AI document references:

Feature Engineering Best Practices

Improving Model Accuracy on AWS

ML Model Development Lifecycle

The mobile app for users with visual impairment needs to hear user speech and provide voice responses, requiring speech-to-text (speech recognition) and text-to-speech capabilities. Deep learning neural networks are widely used for speech recognition tasks, as they can effectively process and transcribe spoken language. AWS services like Amazon Transcribe, which uses deep learning for speech recognition, can fulfill this requirement by converting user speech to text, and Amazon Polly can generate voice responses.

Exact Extract from AWS AI Documents:

From the AWS Documentation on Amazon Transcribe:

" Amazon Transcribe uses deep learning neural networks to perform automatic speech recognition (ASR), converting spoken language into text with high accuracy. This is ideal for applications requiring voice input, such as accessibility features for visually impaired users. "

(Source: Amazon Transcribe Developer Guide, Introduction to Amazon Transcribe)

Detailed Explanation:

Option A: Use a deep learning neural network to perform speech recognition.This is the correct answer. Deep learning neural networks are the foundation of modern speech recognition systems, as used in AWS services like Amazon Transcribe. They enable the app to hear and transcribe user speech, and a service like Amazon Polly can handle voice responses, meeting the requirements.

Option B: Build ML models to search for patterns in numeric data.This option is irrelevant, as the task involves processing speech (audio data) and generating voice responses, not analyzing numeric data patterns.

Option C: Use generative AI summarization to generate human-like text.Generative AI summarization focuses on summarizing text, not processing speech orgenerating voice responses. This option does not address the core requirement of speech recognition.

Option D: Build custom models for image classification and recognition.Image classification and recognition are unrelated to processing speech or generating voice responses, making this option incorrect for an app focused on audio interaction.

The verified answer is B. Data leakage. The model exposes sensitive company information because that information was inadvertently included in training data. AWS guidance warns that using sensitive data to train models can cause unintended disclosure of data from model output, including data leakage during inference. This is exactly the scenario: sensitive information entered the training process and later appeared in model output after deployment.

AWS security reference guidance for generative AI model customization identifies sensitive information disclosure as a threat where a model trained on datasets containing PII leaks sensitive information during inference. Although the question says company information rather than PII specifically, the same security principle applies: protected data included in training or continued pre-training can be memorized or reproduced by the model later.

Jailbreaking is incorrect because jailbreaking refers to attempts to bypass model safety controls through adversarial prompts. The problem here is not that a user bypassed safety controls; the sensitive information was already embedded through training data.

Contextual grounding is incorrect because grounding is a technique for improving answer accuracy by connecting model responses to trusted context, such as RAG sources. It is not a security risk.

Prompt injection is incorrect because prompt injection involves malicious input that attempts to override or manipulate model behavior at inference time. The question does not describe a malicious prompt. It describes accidental exposure from training data.

Therefore, the correct security risk is data leakage.