Free Practice Questions for Amazon Web Services AIF-C01 Exam

The company is building a chatbot using an LLM on Amazon Bedrock, and the chatbot needs to use content from previous customer messages to resolve requests. Adding previous messages to the model prompt (also known as providing conversation history) enables the LLM to maintain context across interactions, allowing it to respond coherently based on the ongoing conversation.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"To enable a large language model (LLM) to maintain context in a conversation, you can include previous messages in the model prompt. This approach, often referred to as providing conversation history, allows the LLM to generate responses that are contextually relevant toprior interactions."

(Source: AWS Bedrock User Guide, Building Conversational Applications)

Detailed Explanation:

Option A: Turn on model invocation logging to collect messages.Model invocation logging records interactions for auditing or debugging but does not provide the LLM with access to previous messages during inference to maintain conversation context.

Option B: Add messages to the model prompt.This is the correct answer. Including previous messages in the prompt gives the LLM the conversation history it needs to respond appropriately, a common practice for chatbots on Amazon Bedrock.

Option C: Use Amazon Personalize to save conversation history.Amazon Personalize is for building recommendation systems, not for managing conversation history in a chatbot. This option is irrelevant.

Option D: Use Provisioned Throughput for the LLM.Provisioned Throughput in Amazon Bedrock ensures consistent performance for model inference but does not address the need to use previous messages in the conversation.

Provide labeled data to customize a model to improve performance on specific tasks.

Correct Answer: Fine-tuning

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI guidance defines fine-tuning as the process of adapting a pre-trained foundation model using labeled, task-specific data. Fine-tuning adjusts the model’s parameters so it performs better on a particular task, such as classification, summarization, or domain-specific reasoning.

Fine-tuning is commonly used when:

High-quality labeled data is available

The goal is to improve accuracy on a specific task

The base FM already has strong general capabilities

AWS AI Study Guide References:

AWS foundation model customization methods

AWS fine-tuning concepts for generative AI

Provide unlabeled data to customize a foundation model for a specific domain.

Correct Answer: Continued pre-training

Comprehensive and Detailed Explanation (AWS AI documents):

AWS documentation describes continued pre-training as extending the training of a foundation model using large volumes of unlabeled, domain-specific data. This method helps the model better understand domain vocabulary, structure, and context without requiring labeled datasets.

Continued pre-training is useful when:

Large amounts of unlabeled domain data are available

The goal is to improve domain understanding rather than a single task

Labeling data would be expensive or impractical

AWS AI Study Guide References:

AWS generative AI training lifecycle

AWS guidance on domain adaptation using unlabeled data

Transfer knowledge from a larger and more intelligent model to a smaller model.

Correct Answer: Distillation

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI materials define distillation as a technique where a smaller model (student) learns to replicate the behavior of a larger, more capable model (teacher). The goal is to retain most of the performance while reducing model size, cost, and inference latency.

Distillation is commonly used to:

Reduce operational costs

Improve inference speed

Deploy models to resource-constrained environments

AWS AI Study Guide References:

AWS model optimization techniques

AWS knowledge distillation concepts

The correct answer is B – Data preprocessing, which involves cleaning, filtering, and transforming raw data before model training. AWS defines preprocessing as the step where irrelevant or poor-quality data (e.g., excessively short or misrecorded audio) is removed or normalized. The described task—filtering recordings by duration and language—is a textbook example of preprocessing since it prepares the dataset for downstream feature extraction. Feature engineering would occur afterward when converting audio signals into numerical representations (like Mel-frequency coefficients). Model training and data collection come after and before preprocessing respectively. Proper preprocessing ensures data consistency, reduces noise, and improves model accuracy, especially in audio-based healthcare models where clarity and consistency are critical.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Data Preprocessing and Cleaning

Amazon SageMaker Data Wrangler Documentation – Data Preparation Best Practices

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 retail company wants to build an ML model for product recommendations using responsible practices to decrease model bias. Collecting balanced and diverse data ensures the model does not favor specific groups, reducing bias and promoting fairness, a key responsible AI practice.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"To reduce model bias, it is critical to collect balanced and diverse data that represents various demographics and user groups. This practice ensures fairness and prevents the model from disproportionately favoring certain populations."

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

Detailed Explanation:

Option A: Use data from only customers who match the demography of the company's overall customer base.Limiting data to a specific demographic may reinforce existing biases, failing to address underrepresented groups and increasing bias.

Option B: Collect data from customers who have a past purchase history.Focusing only on customers with purchase history may exclude new users, potentially introducing bias, and does not address diversity.

Option C: Ensure that the data is balanced and collected from a diverse group.This is the correct answer. A balanced and diverse dataset reduces bias by ensuring the model learns from a representative sample, aligning with responsible AI practices.

Option D: Ensure that the data is from a publicly available dataset.Public datasets may not be diverse or representative of the company’s customer base and could introduce unrelated biases, failing to address fairness.

AWS documentation describes LLM-as-a-judge as an automated evaluation technique where a large language model is used to assess the outputs of another model based on qualitative criteria such as helpfulness, correctness, tone, and alignment with expectations. This approach enables scalable and repeatable evaluations without requiring human reviewers.

In this scenario, the company needs to compare two foundation models across subjective dimensions that are difficult to measure using traditional metrics. LLM-as-a-judge allows the evaluator model to score or rank responses using predefined evaluation prompts and criteria, ensuring consistent and automated assessment.

The other options do not meet the requirements. String matching and ROUGE focus on lexical similarity and are unsuitable for evaluating tone or helpfulness in customer service interactions. Retrieval Augmented Generation is an architectural pattern, not an evaluation technique.

AWS highlights LLM-as-a-judge as a practical approach for automated qualitative evaluation of generative AI outputs, making it the correct choice.

Reinforcement learning allows a model to learn and improve over time based on feedback from its environment. In this case, the chatbot can improve its responses by being rewarded for positive customer feedback, which aligns well with the goal of self-improvement based on past interactions and new information.

Option B (Correct): "Reinforcement learning with rewards for positive customer feedback": This is the correct answer as reinforcement learning enables the chatbot to learn from feedback and adapt its behavior accordingly, providing self-improvement capabilities.

Option A: "Supervised learning with a manually curated dataset" is incorrect because it does not support continuous learning from new interactions.

Option C: "Unsupervised learning to find clusters of similar customer inquiries" is incorrect because unsupervised learning does not provide a mechanism for improving responses based on feedback.

Option D: "Supervised learning with a continuously updated FAQ database" is incorrect because it still relies on manually curated data rather than self-improvement from feedback.

AWS AI Practitioner References:

Reinforcement Learning on AWS: AWS provides reinforcement learning frameworks that can be used to train models to improve their performance based on feedback.

Step 1: Define the business objective.

Step 2: Process the data.

Step 3: Develop and train the model.

Step 4: Deploy the model.

The correct order represents the machine learning lifecycle as defined by AWS in the Amazon SageMaker documentation and AWS Certified Machine Learning Specialty Study Guide. The lifecycle describes the sequence of tasks required to build, train, and deploy a custom ML model effectively.

From AWS documentation:

"The machine learning process begins with defining the business problem, followed by collecting and processing data, developing and training models, and finally deploying them into production for inference."

Step 1 – Define the business objective:

This step involves clearly identifying the business problem to be solved and determining the measurable outcomes expected from the ML model. This ensures alignment between business goals and ML outputs.

Step 2 – Process the data:

Data is collected, cleaned, transformed, and prepared for training. This includes handling missing values, normalizing data, and performing feature engineering — a crucial phase that influences model performance.

Step 3 – Develop and train the model:

The model is built and trained on the processed data using algorithms appropriate to the problem (e.g., regression, classification, clustering). Hyperparameters are tuned to optimize model accuracy.

Step 4 – Deploy the model:

Once validated, the model is deployed to a production environment (e.g., Amazon SageMaker endpoint) to make predictions on new data. Continuous monitoring and retraining ensure the model remains effective.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker Developer Guide – Machine Learning Lifecycle

AWS Certified Machine Learning Specialty Study Guide – Model Development Lifecycle

AWS ML Best Practices Whitepaper – End-to-End ML Workflow

The company wants an AI application to help employees check open customer claims, identify claim details, and access related documents. Agents for Amazon Bedrock can automate tasks by interacting with external systems, while Amazon Bedrock knowledge bases provide a repository of information (e.g., claim details and documents) that the agent can query to respond to employee requests, making this the best solution.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"Agents for Amazon Bedrock enable developers to build applications that can perform tasks by interacting with external systems and data sources. When paired with Amazon Bedrock knowledge bases, agents can access structured and unstructured data, such as documents or databases, to provide detailed responses for use cases like customer service or claims management."

(Source: AWS Bedrock User Guide, Agents and Knowledge Bases)

Detailed Explanation:

Option A: Use Agents for Amazon Bedrock with Amazon Fraud Detector to build the application.Amazon Fraud Detector is for detecting fraudulent activities, not for managing customer claims or accessing documents. This option is irrelevant.

Option B: Use Agents for Amazon Bedrock with Amazon Bedrock knowledge bases to build the application.This is the correct answer. Agents for Amazon Bedrock can interact with knowledge bases to retrieve claim details and documents, enabling employees to check open claims and access relevant information.

Option C: Use Amazon Personalize with Amazon Bedrock knowledge bases to build the application.Amazon Personalize is for building recommendation systems, not for retrieving claim details or documents. This option does not meet the requirements.

Option D: Use Amazon SageMaker AI to build the application by training a new ML model.Training a new ML model on SageMaker is unnecessary and complex for this use case, as the task can be efficiently handled by Agents and knowledge bases on Amazon Bedrock.

The correct answer is D because autoencoders are an unsupervised machine learning method commonly used for anomaly detection when labeled data is not available.

From AWS documentation:

"Autoencoders learn to compress and reconstruct input data. During anomaly detection, they learn normal patterns in data. Data points that the model cannot accurately reconstruct are flagged as anomalies."

This approach is ideal when there is no labeled data and when patterns must be learned based on normal behavior alone — a common situation in IoT sensor data environments.

Explanation of other options:

A. Linear regression requires labeled data and is used for predicting continuous values.

B. Classification requires labeled data to assign inputs into categories.

C. Decision trees are supervised learning models and also require labeled datasets.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Unsupervised Learning Techniques

Amazon SageMaker Examples – Anomaly Detection Using Autoencoders