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

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI and generative AI evaluation guidance emphasizes that assessing the quality and behavior of a foundation model requires representative and diverse evaluation datasets. These datasets should reflect real-world usage patterns, edge cases, and multiple business scenarios to properly evaluate how the model behaves in production.

Using diverse datasets that cover various use cases and usage scenarios allows organizations to:

Evaluate robustness and generalization of the FM

Identify failure modes, bias, and unsafe behavior across different inputs

Validate that the model performs consistently across business workflows

Why the other options are incorrect:

A may remove meaningful real-world patterns and does not reflect realistic usage.

B risks reinforcing model biases and does not provide independent evaluation.

D does not reflect real or meaningful business scenarios and can distort evaluation results.

AWS AI Study Guide References:

AWS Responsible AI evaluation practices

AWS guidance on foundation model testing and validation

The financial institution needs an AI solution for loan approval decisions to be explainable for security and audit purposes. Explainability refers to the ability to understand and interpret how a model makes decisions. Model complexity directly impacts explainability: simpler models (e.g., logistic regression) are more interpretable, while complex models (e.g., deep neural networks) are harder to explain, often behaving like " black boxes. "

Exact Extract from AWS AI Documents:

From the Amazon SageMaker Developer Guide:

" Model complexity affects the explainability of AI solutions. Simpler models, such as linear regression, are inherently more interpretable, while complex models, such as deep neural networks, may require additional tools like SageMaker Clarify to provide insights into their decision-making processes. "

(Source: Amazon SageMaker Developer Guide, Explainability with SageMaker Clarify)

Detailed Explanation:

Option A: Model complexityThis is the correct answer. The complexity of the model directly influences how easily its decisions can be explained, a critical factor for audit and security purposes in loan approvals.

Option B: Training timeTraining time refers to how long it takes to train the model, which does not directly impact the explainability of its decisions.

Option C: Number of hyperparametersWhile hyperparameters affect model performance, they do not directly relate to explainability. A model with many hyperparameters might still be explainable if it is a simple model.

Option D: Deployment timeDeployment time refers to the time taken to deploy the model to production, which is unrelated to the explainability of its decisions.

Amazon Comprehend toxicity detection is a managed NLP service that can analyze text for harmful or toxic language using pre-trained models—no need for labeled data or custom training.

B is correct: Comprehend’s toxicity detection API is designed for this use case, works out-of-the-box, and requires no data labeling or model training.

A (Rekognition) is for image and video content moderation.

C would require labeled data for training.

D (Polly) is for text-to-speech, not content moderation.

“Amazon Comprehend can detect toxicity in text with pre-trained models, requiring no labeled training data.”

(Reference: Amazon Comprehend Toxicity Detection, AWS AI Practitioner Official Guide)

Adjusting the prompt is the correct solution to align the LLM outputs with the company ' s expectations for short, specific language responses.

Adjust the Prompt:

Modifying the prompt can guide the LLM to produce outputs that are shorter and tailored to the desired language.

A well-crafted prompt can provide specific instructions to the model, such as " Answer in a short sentence in Spanish. "

Why Option A is Correct:

Control Over Output: Adjusting the prompt allows for direct control over the style, length, and language of the LLM outputs.

Flexibility: Prompt engineering is a flexible approach to refining the model’s behavior without modifying the model itself.

Why Other Options are Incorrect:

B. Choose an LLM of a different size: The model size does not directly impact the response length or language.

C. Increase the temperature: Increases randomness in responses but does not ensure brevity or specific language.

D. Increase the Top K value: Affects diversity in model output but does not align directly with response length or language specificity.

Denied topics are the appropriate Amazon Bedrock Guardrails feature because the company wants to identify and prevent responses relating to a specific subject area—in this case, unwanted political content.

AWS explains: “You can specify a set of denied topics in a guardrail that are undesirable” for a generative AI application. When a prompt or response is identified as belonging to a configured denied topic, the guardrail can block that content and return the configured blocked-response message.

The company could therefore define a denied topic describing political advocacy, political commentary, politically influenced recommendations, or whatever political-content boundary its newsletter policy prohibits. Amazon Bedrock Guardrails evaluates content contextually against the topic definition rather than relying solely on individual keywords.

This distinction is important because political ideas can be expressed without using predictable keywords. A contextual denied-topic policy is consequently better suited than maintaining a static list of political terms.

Word filters , option A, block configured words or phrases through direct matching. They are useful for profanity, competitor names, or other exact terms but are less suitable for broad conceptual topics.

Sensitive information filters , option C, detect personally identifiable information and configured sensitive patterns. They address privacy rather than political subject matter.

Content filters , option D, detect predefined harmful-content categories. Current Amazon Bedrock Guardrails categories include Hate, Insults, Sexual, Violence, Misconduct, and Prompt Attack. Politics is not one of those predefined content-filter categories.

Denied topics are specifically intended for application-specific subjects that the organization chooses to prohibit. AWS gives examples such as a banking assistant being configured to avoid investment-advice or cryptocurrency discussions.

Consequently, the RAG architecture does not change the appropriate control. Guardrails can evaluate generated output after retrieval and generation, and the company can define politics-related content as an undesirable subject.

Therefore, the correct answer is B. Denied topics .

===========

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Meeting business objectives requires evaluating whether the model:

Solves the intended business problem

Produces actionable and relevant outputs

Aligns with functional and operational requirements

AWS model selection guidance emphasizes use-case alignment as the primary criterion for business success.

Why the other options are incorrect:

Benchmarks (A) measure technical performance, not business value.

Architecture (B) is an implementation detail.

Resource usage (D) affects cost, not objective fulfillment.

AWS AI document references:

Selecting Foundation Models for Business Use

Aligning AI Models with Business Outcomes

AI Evaluation Beyond Accuracy

AWS documentation explains that data masking is a technique used to obscure sensitive information while preserving the usability of the dataset for analytics and machine learning. When sharing data with third parties, AWS recommends masking only the fields that contain personally identifiable information (PII) to minimize data exposure while maintaining data utility.

Applying data masking to PII fields ensures that sensitive attributes such as names, email addresses, phone numbers, or identification numbers are replaced with anonymized or obfuscated values. This allows the third-party provider to train machine learning models without accessing real personal data.

Masking all fields would unnecessarily reduce the dataset’s usefulness and could negatively impact model performance. Data encryption protects data at rest or in transit, but once the third party decrypts the dataset for processing, PII would still be exposed. Data labeling helps identify sensitive fields but does not prevent exposure.

AWS emphasizes that selective masking is a best practice for privacy-preserving data sharing, particularly in ML workflows where data structure and statistical properties must remain intact. Therefore, applying data masking only to PII fields is the correct solution.

AWS guidance treats prompt injection as an adversarial security problem in which malicious or manipulated input attempts to override the intended instructions of a generative AI application. Among the choices provided, adversarial prompting is the relevant technique because it deliberately exercises a model with malicious, conflicting, or manipulative prompts to expose weaknesses before those weaknesses are exploited in production.

An exact AWS security statement is: “You can use an Amazon Bedrock Guardrail to help protect against prompt injection attacks.” AWS further recommends testing generative AI applications against adversarial inputs and prompt-injection attempts so that developers can identify weaknesses in prompt handling and strengthen defenses.

Adversarial prompting is therefore best understood as part of adversarial testing and hardening . For example, evaluators might intentionally submit prompts that request the model to ignore system instructions, disclose protected instructions, change its assigned persona, or follow malicious instructions embedded in retrieved data. If the application responds incorrectly, developers can strengthen system prompts, input validation, Amazon Bedrock Guardrails, output validation, IAM restrictions, or tool-access policies.

Zero-shot prompting simply asks a model to perform a task without providing worked examples. Least-to-most prompting decomposes a difficult problem into progressively more complex subproblems. Chain-of-thought prompting encourages intermediate reasoning. These techniques can improve task performance or reasoning quality, but they are not principally security techniques for discovering prompt-injection vulnerabilities.

A critical distinction is that adversarial prompting by itself is not a complete runtime defense. AWS recommends defense in depth, including Guardrails, input sanitization, restricted permissions, validation, monitoring, and adversarial testing. Nevertheless, given the four options, A is clearly the AWS-aligned answer .

===========

Amazon SageMaker is AWS’s fully managed ML service that supports retraining and deploying models with new, recent data for continuous improvement. This directly meets the requirement to iterate and continuously improve model accuracy.

A is correct:

" Amazon SageMaker enables teams to retrain models using the most recent data, ensuring ongoing improvement in model accuracy. "

(Reference: Amazon SageMaker Overview)

B (Amazon Personalize) is for recommendations, not general ML or waste reduction.

C (CloudWatch) is for monitoring, not ML training or deployment.

D (Rekognition) is for image/video analysis.

The verified answer is D. Enhanced ability to identify bias and improve model governance. Increasing model transparency improves the ability of technical teams, business stakeholders, risk teams, and compliance teams to understand how a model behaves, what factors influence its predictions, and whether it shows unfair or biased behavior. AWS SageMaker Clarify documentation states that SageMaker Clarify provides tools to help explain how machine learning models make predictions. These tools help modelers, developers, and internal stakeholders understand model characteristics before deployment and debug predictions after deployment.

AWS also connects transparency directly to fairness, bias detection, explainability, and governance. AWS guidance states that SageMaker Clarify can be used to create comprehensive reports on model fairness and explainability for stakeholders, including risk and compliance-aligned teams and external regulators. These reports document bias detection and mitigation efforts and provide transparency into responsible AI practices. This directly supports option D because transparency improves the organization’s ability to identify bias and strengthen governance.

Option A is incorrect because transparency does not reduce the need for validation. A transparent model still requires validation, testing, monitoring, and governance controls. Option B is incorrect because transparency does not eliminate regulatory compliance monitoring. In fact, transparency often supports and strengthens compliance monitoring rather than replacing it. Option C is incorrect because transparency does not automatically remove all bias. It helps teams detect, explain, measure, and mitigate bias, but bias mitigation still requires deliberate actions such as representative data preparation, metric evaluation, retraining, sampling changes, or governance review.

Therefore, the correct outcome of increasing model transparency is an improved ability to identify bias and improve model governance.

Amazon Augmented AI (Amazon A2I) is designed to enable human review workflows for machine learning predictions where human judgment is required. AWS documentation states that A2I allows organizations to integrate human reviewers into AI workflows to review low-confidence predictions or samples selected by business rules. This directly aligns with the requirement to involve employees in validating and improving translation outputs.

In this scenario, the translation model produces a confidence score, which is a common trigger used by Amazon A2I to route predictions to human reviewers. AWS explicitly describes that A2I supports use cases such as natural language processing, translation, content moderation, and document processing, where automated models may need human oversight to ensure accuracy and quality.

Amazon A2I provides managed workflows, reviewer task interfaces, and audit trails that allow employees to review, correct, and validate model outputs. The feedback collected through A2I can then be used to improve future model training, increasing translation quality over time.

The other options do not meet the requirement. Amazon SageMaker Clarify focuses on bias detection and explainability, not human review workflows. Amazon SageMaker Model Monitor is used to detect data drift and model performance degradation in production, not to involve humans in validating predictions. Amazon Bedrock Agents are designed to orchestrate tasks and interactions with foundation models, not to manage human-in-the-loop review processes.

AWS positions Amazon A2I as a core service for implementing human-in-the-loop machine learning, making it the correct solution for incorporating employees into a structured translation review process.

BLEU (Bilingual Evaluation Understudy) is a metric used to evaluate the accuracy of machine-generated translations by comparing them against reference translations. It is commonly used for translation tasks to measure how close the generated output is to professional human translations.

Option A (Correct): " Bilingual Evaluation Understudy (BLEU) " : This is the correct answer because BLEU is specifically designed to evaluate the quality of translations, making it suitable for the company ' s use case.

Option B: " Root mean squared error (RMSE) " is incorrect because RMSE is used for regression tasks to measure prediction errors, not translation quality.

Option C: " Recall-Oriented Understudy for Gisting Evaluation (ROUGE) " is incorrect as it is used to evaluate text summarization, not translation.

Option D: " F1 score " is incorrect because it is typically used for classification tasks, not for evaluating translation accuracy.

AWS AI Practitioner References:

Model Evaluation Metrics on AWS: AWS supports various metrics like BLEU for specific use cases, such as evaluating machine translation models.

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.

The verified answer is B. Amazon SageMaker Clarify. The model is used for customer loan applications, where explainability, transparency, and human-centered decision support are critical. AWS documentation states that SageMaker Clarify provides tools to help explain how machine learning models make predictions. These tools help ML developers, modelers, and internal stakeholders understand model characteristics before deployment and debug predictions after deployment.

SageMaker Clarify is specifically aligned with explainable AI because it provides feature attribution methods, including SHAP-based explanations. AWS documentation explains that Clarify can generate reports that contribute to model governance documentation and can help describe how a model works, what features influence its decisions, and how explanations are generated.

Amazon SageMaker Model Registry is incorrect because it manages model versions, approval status, and deployment tracking. It supports governance workflows, but it does not explain why a model made a decision.

Amazon SageMaker Pipelines is incorrect because it automates and orchestrates ML workflows such as training, evaluation, and deployment. It does not provide the core explainability function required here.

Amazon SageMaker Feature Store is incorrect because it stores, shares, and serves ML features for training and inference. It improves feature reuse and consistency, but it does not explain model decisions.

For a financial loan application model, stakeholders and regulators need to understand which factors influenced predictions. SageMaker Clarify is the AWS feature designed for this explainability requirement, so option B is correct.

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:

Generative AI models offer adaptability, meaning they can generalize across:

Different markets

New product lines

Variations in language and complaint structure

Unlike hard-coded logic, generative models can adapt to new patterns and inputs without requiring extensive rule rewrites, making them ideal for scaling text-based processing applications.

Why the other options are incorrect:

Predictability (A) is typically lower in generative models.

Less sensitivity (C) is incorrect; generative models are sensitive to input variations.

Explainability (D) is generally limited in large generative models.

AWS AI document references:

Generative AI Benefits and Trade-offs

Modernizing Text Processing with Foundation Models

Scaling NLP Solutions on AWS

Building and training a generative AI model from scratch provides the company with the most ownership and control over security responsibilities. In this scenario, the company is responsible for all aspects of the security of the data, the model, and the infrastructure.

Option D (Correct): " Building and training a generative AI model from scratch by using specific data that a customer owns " : This is the correct answer because it involves complete ownership of the model, data, and infrastructure, giving the company the highest level of responsibility for security.

Option A: " Using a third-party enterprise application that has embedded generative AI features " is incorrect as the company has minimal control over the security of the AI features embedded within a third-party application.

Option B: " Building an application using an existing third-party generative AI foundation model (FM) " is incorrect because security responsibilities are shared with the third-party model provider.

Option C: " Refining an existing third-party generative AI FM by fine-tuning the model with business-specific data " is incorrect as the foundation model and part of the security responsibilities are still managed by the third party.

AWS AI Practitioner References:

Generative AI Security Scoping Matrix on AWS: AWS provides a security responsibility matrix that outlines varying levels of control and responsibility depending on the approach to developing and using AI models.

The verified answer is A. AWS PrivateLink. The requirement is that API calls between generative AI applications and foundation models must not travel across the public internet. AWS documentation states that AWS PrivateLink can create a private connection between a VPC and Amazon Bedrock. With this configuration, applications can access Amazon Bedrock as if it were inside the VPC, without requiring an internet gateway, NAT device, VPN connection, or Direct Connect connection. AWS also states that instances in the VPC do not need public IP addresses to access Amazon Bedrock. This exactly satisfies the requirement for private API communication to foundation models.

Amazon Q is incorrect because Amazon Q is a generative AI assistant service for business, developer, and data use cases. It is not the network service used to privately route API calls between applications and FMs.

Amazon CloudFront is incorrect because CloudFront is a content delivery network. It caches and delivers content through edge locations, but it is not the correct service for private VPC-to-AWS-service connectivity that avoids the public internet.

AWS CloudTrail is incorrect because CloudTrail records account activity and API events for governance, audit, and security analysis. It helps track what happened, but it does not provide private network connectivity.

The key phrase is “must not travel across the public internet.” In AWS architecture, that requirement points to private connectivity using VPC endpoints powered by AWS PrivateLink. Therefore, the correct service is AWS PrivateLink.