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

The correct answer is C – Use a negative prompt. Negative prompts instruct a generative image model to avoid certain features, objects, or styles in the output. This technique is fully supported by models like Amazon Nova Canvas on Bedrock, which are based on diffusion or image generation architectures. According to AWS documentation, negative prompts refine output control by telling the model what not to include, thereby improving brand alignment, compliance, or creative direction. A higher temperature increases randomness, not control. A detailed prompt helps, but without exclusion instructions, the model may still include unwanted elements. Changing the model may yield better output but doesn’t directly solve this control requirement. Negative prompts are purpose-built for this scenario.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Prompt Engineering for Image Models

AWS Generative AI Guide – Controlled Generation with Negative Prompts

The verified answer is D. Model deployment and inference. The question describes a trained model being made available to production applications through an API endpoint. That is deployment, and the runtime use of the model to answer queries is inference. AWS SageMaker documentation states that after training, you can get predictions, or inferences, from trained machine learning models, and SageMaker provides model deployment options to support ML inference needs. This directly matches the phrase “available to production applications through an API endpoint for runtime queries.”

Data preparation is incorrect because that phase happens before training. It includes collecting, cleaning, transforming, labeling, and preparing datasets so the model can learn from them. The question already says the model is trained, so the workflow has moved beyond data preparation.

Model training and tuning is incorrect because training and tuning are where the model learns patterns from data and hyperparameters may be adjusted to improve performance. The question is not describing learning, optimization, or retraining. It describes exposing the trained model to applications.

Model evaluation and validation is incorrect because evaluation checks whether the model meets quality, accuracy, fairness, safety, or business criteria before or during production use. The scenario does not describe testing the model; it describes making the model callable by production applications.

In the ML lifecycle, deploying a model means placing it into an environment where applications can send requests and receive predictions. Inference is the process of using the deployed model to generate outputs from new inputs. Because the company is exposing the trained model through an API endpoint for runtime queries, the activity is model deployment and inference.

Generative adversarial networks (GANs) are a type of deep learning model used for generating synthetic data based on existing datasets. GANs consist of two neural networks (a generator and a discriminator) that work together to create realistic data.

Option A (Correct): " Generative adversarial network (GAN) " : This is the correct answer because GANs are specifically designed for generating synthetic data that closely resembles the real data they are trained on.

Option B: " XGBoost " is a gradient boosting algorithm for classification and regression tasks, not for generating synthetic data.

Option C: " Residual neural network " is primarily used for improving the performance of deep networks, not for generating synthetic data.

Option D: " WaveNet " is a model architecture designed for generating raw audio waveforms, not synthetic data in general.

AWS AI Practitioner References:

GANs on AWS for Synthetic Data Generation: AWS supports the use of GANs for creating synthetic datasets, which can be crucial for applications like training machine learning models in environments where real data is scarce or sensitive.

The verified answer is C. Use batch inference with Amazon Bedrock. The workload has three decisive characteristics: it is repetitive, it processes a large volume of requests, and it does not require immediate responses. AWS documentation states that with Amazon Bedrock batch inference, users can submit multiple prompts and generate responses asynchronously. It also states that batch inference helps process a large number of requests efficiently by sending a single request and generating responses in an Amazon S3 bucket. That directly matches the weekly generation of exercise routines for all users.

AWS also explains that after the batch job is complete, the output files can be retrieved from Amazon S3, and batch inference can improve model inference performance on large datasets. This is the right architecture for offline or scheduled workloads where immediate response latency is not required.

Amazon Bedrock AgentCore is incorrect because AgentCore is for building, running, and managing agents, tools, memory, gateways, and agent workflows. The problem is not agent orchestration; it is cost-efficient high-volume offline inference.

Real-time inference with Amazon Bedrock on-demand endpoints is incorrect because real-time inference is better for interactive applications where users need immediate responses. The question explicitly says immediate responses are not required.

Real-time inference with SageMaker AI hosted endpoints is also incorrect for the same reason. Hosted endpoints are appropriate for low-latency inference requests, but this workload is scheduled and large-volume.

Therefore, Amazon Bedrock batch inference is the best solution.

The verified answer is D. AWS Artifact. The company needs compliance documentation for submission to regulatory authorities. AWS Artifact is the AWS service designed for this exact requirement. AWS describes AWS Artifact as a self-service portal that provides on-demand access to AWS security and compliance reports and agreements. AWS also states that customers can use AWS Artifact to access AWS and independent software vendor security and compliance reports, download compliance reports, and manage compliance agreements. This directly matches the need to obtain documentation for auditors or regulators.

AWS compliance guidance also explains that AWS supports many security standards and compliance certifications, and AWS reports such as SOC reports help customers and auditors understand AWS controls established to support operations and compliance. AWS Artifact is the mechanism customers use to retrieve many of these compliance documents. Therefore, if the company is using Amazon Bedrock and needs compliance documentation related to AWS services, AWS Artifact is the appropriate service.

AWS Config is incorrect because it records, evaluates, and audits AWS resource configurations. It can help assess whether resources comply with internal rules, but it is not the service for obtaining AWS compliance reports for submission to regulators. Amazon Bedrock is incorrect because Bedrock is the generative AI service being used to process invoices; it does not serve as the compliance report portal. Amazon SageMaker AI is incorrect because SageMaker AI is used to build, train, deploy, and manage machine learning models. It is not the AWS service for downloading AWS compliance documentation.

The question is not asking how to process invoices securely or how to configure Bedrock controls. It is asking where to obtain formal compliance documentation. The correct AWS service is AWS Artifact.

The correct answer is B – Use Amazon Bedrock batch inference, which allows asynchronous generation of large-scale model outputs through APIs without requiring low-latency performance. According to AWS Bedrock documentation, batch inference is ideal for high-volume workloads that can tolerate delay, such as bulk content generation or summarization jobs. Unlike real-time inference, it processes requests in bulk, reducing cost and operational load. AWS handles the queuing, processing, and scaling automatically. Bedrock Agents (option C) are for workflow orchestration, not large-scale generation. AWS Lambda (option D) can automate tasks but is not optimized for high-volume LLM calls. Batch inference provides cost efficiency, scalability, and simplicity for delayed, asynchronous generation needs.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Batch Inference

AWS ML Specialty Study Guide – Scalable Inference Options

The verified answer is C. Controllability. AWS defines responsible AI through several dimensions, including fairness, explainability, privacy and security, safety, controllability, veracity and robustness, governance, and transparency. The exact wording in the question is the clue: the company wants mechanisms to monitor and direct AI system behavior. AWS describes controllability as having mechanisms to monitor and steer AI system behavior. That maps directly to the requirement.

Fairness is incorrect because fairness focuses on considering impacts on different groups of stakeholders. It is about avoiding unjust outcomes, biased treatment, or disproportionate harm across populations. The question does not describe demographic representation, biased outputs, or unequal model behavior.

Explainability is incorrect because explainability focuses on understanding and evaluating system outputs. It helps stakeholders understand why the model generated a result or how model behavior can be interpreted. The question is not asking about understanding a decision; it is asking about controlling and directing system behavior.

Safety is incorrect because safety focuses on reducing harmful system output and misuse. Safety is related, but the wording “monitor and direct AI system behavior” is specifically the AWS definition of controllability, not safety. Safety might include preventing toxic, harmful, or dangerous outputs, but controllability is the broader dimension about steering the system according to intended behavior.

Therefore, the responsible AI dimension being applied is controllability, because the company wants active mechanisms to guide, monitor, and steer how the generative AI application behaves in operation.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Prompt engineering is the primary method for controlling tone, style, and behavior of foundation model responses.

AWS generative AI guidance explains that:

Prompts can define tone, voice, and response structure

Iterative refinement ensures consistent outputs

Prompt refinement requires no model retraining

Why the other options are incorrect:

Token limits (A) affect length, not tone.

Batch inferencing (B) affects processing mode, not response style.

Higher temperature (D) increases randomness, reducing consistency.

AWS AI document references:

Prompt Engineering Best Practices

Controlling Model Output Tone

Using Prompts with Foundation Models on AWS

AWS PrivateLink enables private connectivity between VPCs and AWS services without exposing traffic to the public internet. This feature is critical for meeting regulatory compliance standards that require isolation from public internet traffic.

Option A (Correct): " AWS PrivateLink " : This is the correct answer because it allows secure access to Amazon Bedrock and other AWS services from a VPC without internet access, ensuring compliance with regulatory standards.

Option B: " Amazon Macie " is incorrect because it is a security service for data classification and protection, not for managing private network traffic.

Option C: " Amazon CloudFront " is incorrect because it is a content delivery network service and does not provide private network connectivity.

Option D: " Internet gateway " is incorrect as it enables internet access, which violates the VPC ' s no-internet-traffic policy.

AWS AI Practitioner References:

AWS PrivateLink Documentation: AWS highlights PrivateLink as a solution for connecting VPCs to AWS services privately, which is essential for organizations with strict regulatory requirements.

AWS documentation identifies hallucinations as a known limitation of generative AI models, particularly when used in business and production environments. Hallucinations occur when a model generates outputs that are unrelated, incorrect, fabricated, or unsupported by the input data or provided context. These outputs often appear confident and fluent, which can make them difficult to detect without additional validation.

Generative AI models, including large language models, operate using probabilistic token prediction based on patterns learned during training. AWS explains that these models do not have true reasoning or factual grounding unless explicitly provided with context or external knowledge. As a result, when prompts are ambiguous, incomplete, or outside the model’s training distribution, the model may produce responses that are irrelevant or misleading.

This behavior presents a risk for business use cases such as customer support, reporting, or decision-making systems. AWS highlights hallucinations as a key challenge that must be mitigated through techniques such as Retrieval Augmented Generation (RAG), prompt engineering, human review, and output validation.

The other options are not correct. Interpretability refers to the ability to understand model decisions, not incorrect outputs. Data bias relates to skewed or unfair training data. Nondeterminism refers to variability in outputs, not relevance or correctness.

AWS consistently categorizes hallucinations as a primary disadvantage of generative AI, making this the correct answer.

The context window determines how much information can fit into a single prompt when using a large language model (LLM) like those on Amazon Bedrock.

Context Window:

The context window is the maximum amount of text (measured in tokens) that a language model can process in a single pass.

For LLM applications, the size of the context window limits how much input data, such as text for sentiment analysis, can be fed into the model at once.

Why Option B is Correct:

Determines Prompt Size: The context window size directly informs how much information (e.g., words or sentences) can fit in one prompt.

Model Capacity: The larger the context window, the more information the model can consider for generating outputs.

Why Other Options are Incorrect:

A. Temperature: Controls randomness in model outputs but does not affect the prompt size.

C. Batch size: Refers to the number of training samples processed in one iteration, not the amount of information in a prompt.

D. Model size: Refers to the number of parameters in the model, not the input size for a single prompt.

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.

Amazon Bedrock is a fully managed service that provides access to foundation models (FMs) from various providers, enabling users to build and scale generative AI applications. It simplifies the process of integrating FMs into applications for tasks like text generation, chatbots, and more.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Amazon Bedrock is a fully managed service that makes foundation models (FMs) from leading AI providers available through a single API, enabling developers to build and scale generative AI applications with ease. "

(Source: AWS Bedrock User Guide, Introduction to Amazon Bedrock)

Detailed Explanation:

Option A: Amazon Q DeveloperAmazon Q Developer is an AI-powered assistant for coding and AWS service guidance, not a service for hosting or providing foundation models.

Option B: Amazon BedrockThis is the correct answer. Amazon Bedrock provides access to foundation models, making it the primary service for building and scaling generative AI applications.

Option C: Amazon KendraAmazon Kendra is an intelligent search service powered by machine learning, not a service for providing foundation models or building generative AI applications.

Option D: Amazon ComprehendAmazon Comprehend is an NLP service for text analysis tasks like sentiment analysis, not for providing foundation models or supporting generative AI.

Supervised learning is appropriate when the dataset is labeled. The model uses this data to learn patterns and classify images. Unsupervised learning, reinforcement learning, and active learning are not suitable since they either require unlabeled data or different problem settings. References: AWS Machine Learning Best Practices.

This scenario demonstrates intellectual property (IP) infringement, where an AI-generated artifact (a cloned voice) uses the identifiable traits of a person without permission. According to AWS Responsible AI practices, using a person’s likeness, image, or voice in generative AI systems requires explicit rights and consent. Foundation models trained or applied without respecting these ownership boundaries violate ethical and legal frameworks under IP law. The AWS documentation emphasizes that generative AI must respect copyrighted or trademarked works and human likenesses. Responsible deployment requires consent-based data usage, license tracking, and content watermarking to prevent misappropriation. AWS Bedrock enforces such compliance principles through Guardrails and policy-based moderation to ensure content generation aligns with ethical and lawful standards.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Guidelines – Intellectual Property and Ethical Use

Amazon Bedrock Documentation – Responsible Use of Generative AI

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.

Amazon SageMaker Serverless Inference is the correct solution for deploying an ML model to production in a way that allows a web application to use the model without the need to manage the underlying infrastructure.

Amazon SageMaker Serverless Inference provides a fully managed environment for deploying machine learning models. It automatically provisions, scales, and manages the infrastructure required to host the model, removing the need for the company to manage servers or other underlying infrastructure.

Why Option A is Correct:

No Infrastructure Management: SageMaker Serverless Inference handles the infrastructure management for deploying and serving ML models. The company can simply provide the model and specify the required compute capacity, and SageMaker will handle the rest.

Cost-Effectiveness: The serverless inference option is ideal for applications with intermittent or unpredictable traffic, as the company only pays for the compute time consumed while handling requests.

Integration with Web Applications: This solution allows the model to be easily accessed by web applications via RESTful APIs, making it an ideal choice for hosting the model and serving predictions.

Why Other Options are Incorrect:

B. Use Amazon CloudFront to deploy the model: CloudFront is a content delivery network (CDN) service for distributing content, not for deploying ML models or serving predictions.

C. Use Amazon API Gateway to host the model and serve predictions: API Gateway is used for creating, deploying, and managing APIs, but it does not provide the infrastructure or the required environment to host and run ML models.

D. Use AWS Batch to host the model and serve predictions: AWS Batch is designed for running batch computing workloads and is not optimized for real-time inference or hosting machine learning models.

Thus, A is the correct answer, as it aligns with the requirement of deploying an ML model without managing any underlying infrastructure.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Conversion rate measures the percentage of users who take a desired business action, such as completing a purchase after receiving recommendations.

In the context of:

Personalized product recommendations

Measuring direct impact on sales revenue

Conversion rate is the most relevant business metric, as it directly correlates AI-driven recommendations with revenue-generating outcomes.

Why the other options are incorrect:

Cross-domain performance (A) evaluates generalization across datasets, not revenue.

Solution efficiency (B) focuses on performance and cost, not sales impact.

User satisfaction (C) measures experience quality, not financial outcomes.

AWS AI document references:

AWS Generative AI Use Case Evaluation Guidance

Measuring Business Impact of AI Solutions

AI Metrics and KPIs on AWS

Amazon SageMaker Model Cards are specifically designed to support transparency, responsible AI, and governance throughout the machine learning lifecycle. According to AWS AI documentation, Model Cards provide a structured way to document critical information about machine learning models, including intended use cases, business context, training data assumptions, evaluation metrics, ethical considerations, and known limitations or risks. This makes Model Cards the correct feature for the requirements described.

AWS emphasizes that Model Cards help organizations meet internal governance standards and external regulatory or compliance expectations by improving model interpretability and accountability. They allow AI practitioners to clearly explain why a model was built, how it was trained, what data it relies on, and what risks or biases may exist. This aligns directly with the need to document business problems, training considerations, and usage risks.

Other options do not fully address these needs. Amazon SageMaker Model Registry focuses on versioning, approval workflows, and deployment tracking of models, but it does not provide comprehensive documentation for transparency or ethical considerations. Amazon SageMaker Model Monitor is designed to detect data drift, bias drift, and performance degradation in production, not to document assumptions or governance details. Model Dashboard offers a centralized view of deployed models and endpoints but does not provide structured, narrative documentation of model intent or risks.

AWS positions Model Cards as a core component of Responsible AI, enabling organizations to promote fairness, explainability, and trust in machine learning systems. By capturing standardized, auditable documentation, Model Cards ensure that stakeholders—including developers, auditors, and business leaders—can understand how a recommendation system should be used and where caution is required.