Free Practice Questions for Amazon Web Services AIF-C01 Exam

The correct answer is C because Amazon SageMaker JumpStart provides administrative controls that allow organizations to manage and restrict access to foundation models within the AWS environment.

According to the official AWS documentation:

" Amazon SageMaker JumpStart provides model access management capabilities that enable administrators to control which foundation models are visible and usable by end users. Using AWS Identity and Access Management (IAM) policies, you can restrict access to specific models or completely disable model discovery in JumpStart. "

This allows companies to enforce governance over which FMs their users can see and interact with, satisfying the requirement to control employee access to publicly available foundation models.

Explanation of other options:

A. AWS Cost Explorer is used to analyze billing and usage data but does not control access to services or models. It is helpful for budgeting and visibility, not access control.

B. AWS Artifact provides access to compliance reports and certifications, not tools for controlling user access to ML models.

D. Amazon OpenSearch Service is used for search and analytics on structured and unstructured data. It does not provide access control mechanisms for foundation models.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker JumpStart Documentation – Model Access Management

AWS IAM Documentation – Restricting Access to SageMaker Resources

AWS Machine Learning Specialty Certification Guide – Security and Governance Section

The verified answer is C. Faithfulness. The company is evaluating foundation models for a summarization task by using an LLM-as-a-judge evaluation job in Amazon Bedrock. AWS documentation states that with a model evaluation job that uses a judge model, Amazon Bedrock uses one LLM to score another model’s responses and provide an explanation of how it scored each prompt and response pair. AWS also states that Amazon Bedrock provides built-in metrics that can be selected for these judge-based evaluation jobs.

Among the answer choices, Faithfulness is the only valid built-in metric for an Amazon Bedrock LLM-as-a-judge model evaluation job. AWS API documentation lists the valid built-in metric names for LLM-as-a-judge evaluation jobs, including Correctness, Completeness, Faithfulness, Helpfulness, Coherence, Relevance, FollowingInstructions, ProfessionalStyleAndTone, and responsible AI metrics such as Harmfulness, Stereotyping, and Refusal. The same documentation identifies Summarization as a valid task type for model evaluation jobs. Therefore, Faithfulness is a valid built-in metric for evaluating whether generated summaries remain grounded in the source input rather than introducing unsupported claims.

Option A. Context relevance and option B. Context coverage are incorrect for this question because AWS lists those as metrics for knowledge base retrieval-only evaluation jobs, not general LLM-as-a-judge model evaluation of foundation model summarization output. These metrics evaluate retrieved context, not the quality of a summarization model’s generated response. Option D. RMSE is also incorrect because root mean square error is a regression metric. It is not a built-in LLM-as-a-judge metric for summarization in Amazon Bedrock.

Because the task is summarization and the evaluation job is LLM-as-a-judge, the correct built-in evaluation metric from the available choices is Faithfulness.

AWS Glue is a serverless data integration service that enables users to extract, transform, and load (ETL) data. For a company with minimal programming experience, Amazon Q Developer provides an AI-powered assistant that can generate code, explain AWS services, and guide users through tasks like creating AWS Glue jobs. This makes it an ideal tool to help the company use AWS Glue effectively.

Exact Extract from AWS AI Documents:

From the AWS Documentation on Amazon Q Developer:

" Amazon Q Developer is an AI-powered assistant that helps developers by generating code, answering questions about AWS services, and providing step-by-step guidance for tasks such as building ETL pipelines with AWS Glue. It is designed to assist users with varying levels of expertise, including those with minimal programming experience. "

(Source: AWS Documentation, Amazon Q Developer Overview)

Detailed Explanation:

Option A: Amazon Q Developer

This is the correct answer. Amazon Q Developer can assist the company by generating AWS Glue scripts, explaining Glue concepts, and providing guidance on setting up ETL jobs, which is particularly helpful for users with limited programming experience.

Option B: AWS Config

AWS Config is used for tracking and managing resource configurations and compliance, not for assisting with coding or using services like AWS Glue. This option is incorrect.

Option C: Amazon Personalize

Amazon Personalize is a machine learning service for building recommendation systems, not for assisting with data integration or AWS Glue. This option is irrelevant.

Option D: Amazon Comprehend

Amazon Comprehend is an NLP service for analyzing text, not for helping users write code or use AWS Glue. This option does not meet the requirements.

The correct answer is C because Continued Pre-training (also known as domain-adaptive pre-training) involves training a pre-trained model further on unlabeled domain-specific data. This method helps adapt the LLM to a specific domain without needing labeled datasets, making it ideal for cases where the goal is to enhance the model’s understanding of technical language or terminology.

From AWS documentation:

" Continued pre-training allows an LLM to ingest large volumes of domain-specific text without labels to improve contextual understanding in a particular area. This is effective when adapting a foundation model to new knowledge without altering the model architecture. "

Explanation of other options:

A. Full training refers to building a model from scratch, which is extremely resource-intensive and unnecessary if a strong base model already exists.

B. Supervised fine-tuning requires labeled data, which the scenario explicitly lacks.

D. RAG is a method to retrieve external information at inference time, not a training technique using unlabeled data.

Referenced AWS AI/ML Documents and Study Guides:

AWS Bedrock Model Customization Documentation – Continued Pre-training

Amazon SageMaker JumpStart – Domain Adaptation Techniques

AWS Machine Learning Specialty Study Guide – Foundation Model Customization Section

Comprehensive and Detailed Explanation From Exact AWS AI documents:

According to MLOps best practices, once an ML model is deployed to production—especially an open-source pre-trained model—the organization must continuously monitor model outputs to ensure:

Model predictions remain accurate over time

No performance degradation due to data drift or concept drift

Outputs remain aligned with business and ethical expectations

AWS MLOps guidance emphasizes monitoring in production as a mandatory step for maintaining model reliability and governance.

Why the other options are incorrect:

A (Hyperparameter tuning) is optional and model-dependent.

B (Labeling data) is required only when training or fine-tuning, not when using a pre-trained model directly.

D (Feature engineering) is less relevant for modern pre-trained NLP models.

AWS AI document references:

MLOps Best Practices on AWS

Amazon SageMaker Model Monitoring

Operationalizing Machine Learning on AWS

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI best practices emphasize that bias should be detected, measured, mitigated, and monitored throughout the ML lifecycle, especially for sensitive domains such as healthcare. When biased outcomes are observed, AWS guidance recommends addressing bias at the data and model level, not only at the output level.

Using Amazon SageMaker Clarify aligns directly with AWS Responsible AI principles because it is designed to:

Detect and quantify bias in datasets and model predictions across sensitive attributes such as demographic groups

Provide pre-training and post-training bias metrics, allowing practitioners to identify where bias originates

Support data-centric mitigation, including improving dataset balance and representativeness

After identifying bias with SageMaker Clarify, collecting additional balanced training data and retraining the model helps ensure that:

The model learns from a more representative dataset

Disparate treatment recommendations based on demographics are reduced

Fairness is improved while maintaining clinical accuracy

Why the other options are not sufficient or aligned with AWS best practices:

B. Prompt engineering can influence outputs but does not address underlying data or model bias and is not sufficient for regulated, high-risk domains like healthcare.

C. Content filtering removes outputs after generation but does not prevent biased decision-making by the model itself.

D. Separate FM endpoints by demographic group increases the risk of reinforcing bias and violates fairness principles rather than mitigating them.

AWS AI Study Guide References:

AWS Responsible AI principles: Fairness and Governance

Amazon SageMaker Clarify: bias detection and mitigation

AWS best practices for ML in high-risk domains such as healthcare

Comprehensive and Detailed Explanation From Exact AWS AI documents:

To secure data in Amazon Q Business, AWS recommends:

AWS KMS (A) to encrypt data at rest and manage encryption keys.

AWS IAM (E) to control authentication and authorization for users and services.

Together, these services ensure:

Strong access control

Data confidentiality

Compliance with enterprise security requirements

Why the other options are incorrect:

Cross-account access (B) does not inherently ensure privacy.

Amazon Inspector (C) is for vulnerability scanning, not authentication.

Public access (D) violates security best practices.

AWS AI document references:

Amazon Q Business Security Overview

Data Protection with AWS KMS

Access Control with AWS IAM

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.

The ecommerce company’s chatbot, powered by AI, automates customer order submissions and is accessible 24/7 via the website. Prompt injection is an AI system input vulnerability where malicious users craft inputs to manipulate the chatbot’s behavior, such as bypassing safeguards or accessing unauthorized information. This vulnerability must be resolved before the chatbot is made available to ensure security.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Prompt injection is a vulnerability in AI systems, particularly chatbots, where malicious inputs can manipulate the model’s behavior, potentially leading to unauthorized actions or harmful outputs. Implementing guardrails and input validation can mitigate this risk. "

(Source: AWS Bedrock User Guide, Security Best Practices)

Detailed Explanation:

Option A: Data leakageData leakage refers to the unintended exposure of sensitive data during model training or inference, not an input vulnerability affecting a chatbot’s operation.

Option B: Prompt injectionThis is the correct answer. Prompt injection is a critical input vulnerability for chatbots, where malicious prompts can exploit the AI to produce harmful or unauthorized responses, a risk that must be addressed before launch.

Option C: Large language model (LLM) hallucinationsLLM hallucinations refer to the model generating incorrect or ungrounded responses, which is an output issue, not an input vulnerability.

Option D: Concept driftConcept drift occurs when the data distribution changes over time, affecting model performance. It is not an input vulnerability but a long-term performance issue.

Exploratory data analysis (EDA) involves understanding the data by visualizing it, calculating statistics, and creating correlation matrices. This stage helps identify patterns, relationships, and anomalies in the data, which can guide further steps in the ML pipeline.

Option C (Correct): " Exploratory data analysis " : This is the correct answer as the tasks described (correlation matrix, calculating statistics, visualizing data) are all part of the EDA process.

Option A: " Data pre-processing " is incorrect because it involves cleaning and transforming data, not initial analysis.

Option B: " Feature engineering " is incorrect because it involves creating new features from raw data, not analyzing the data ' s existing structure.

Option D: " Hyperparameter tuning " is incorrect because it refers to optimizing model parameters, not analyzing the data.

AWS AI Practitioner References:

Stages of the Machine Learning Pipeline: AWS outlines EDA as the initial phase of understanding and exploring data before moving to more specific preprocessing, feature engineering, and model training stages.