Free Amazon Web Services AIF-C01 Practice Exam with Questions & Answers | Set: 14

The verified answer is A. Present the model Shapley values. AWS documentation states that SageMaker Clarify provides feature attributions based on Shapley values. These values can determine the contribution each feature made to model predictions and can be provided for individual predictions or at a global level for the model as a whole. That is exactly what stakeholders need when they ask for transparency and explainability: they need to understand which features influenced the model’s decisions and how strongly those features contributed.

AWS also explains that SageMaker Clarify helps explain how ML models make predictions and that transparency is critical for consumers and regulators. Clarify’s explainability uses a model-agnostic feature attribution approach and includes a scalable implementation of SHAP. These explanations answer practical stakeholder questions such as why the model made a prediction, how it makes predictions, and which features have the largest influence on model behavior.

Option B is incorrect because accuracy measures predictive correctness, not explainability. A model can be highly accurate while still being opaque. Accuracy alone does not show why a specific prediction was made.

Option C is incorrect because a confusion matrix summarizes classification performance by showing true positives, false positives, true negatives, and false negatives. It is useful for evaluation, but it does not explain individual feature influence or model reasoning.

Option D is incorrect because a secure inference endpoint protects access to the deployed model. Security is important, but it does not provide transparency or explainability.

Therefore, presenting Shapley values is the correct solution because it directly explains feature contributions to model predictions.

The correct answer is D – Classification. In this scenario, the goal is to assign each social media review to one of three predefined categories: positive, negative, or neutral. According to AWS documentation, classification models are used when “inputs must be mapped to one label from a fixed set of possible labels.” Sentiment analysis is one of the most common NLP classification tasks and is supported in Amazon Comprehend, Amazon SageMaker, and Amazon Bedrock. Open-ended generation produces free-form text and is not appropriate for categorical outputs. Summarization condenses long-form content, and machine translation converts text across languages. Only classification aligns with sentiment detection, enabling the model to learn sentiment cues such as emotional wording or tone markers. AWS highlights sentiment classification as a key use case for supervised learning with text data.

Referenced AWS Documentation:

Amazon Comprehend Documentation – Sentiment Classification

AWS ML Specialty Guide – Classification Algorithms

SageMaker Model Registry, SageMaker Serverless interference

This question requires selecting the appropriate Amazon SageMaker feature for two distinct steps in the AI model lifecycle. Let’s break down each step and evaluate the options:

Step 1: Managing different versions of the model

The goal here is to identify a SageMaker feature that supports version control and management of machine learning models. Let’s analyze the options:

SageMaker Clarify: This feature is used to detect bias in models and explain model predictions, helping with fairness and interpretability. It does not provide functionality for managing model versions.

SageMaker Model Registry: This is a centralized repository in Amazon SageMaker that allows users to catalog, manage, and track different versions of machine learning models. It supports model versioning, approval workflows, and deployment tracking, making it ideal for managing different versions of a model.

SageMaker Serverless Inference: This feature enables users to deploy models for inference without managing servers, automatically scaling based on demand. It is focused on inference (predictions), not on managing model versions.

Conclusion for Step 1: The SageMaker Model Registry is the correct choice for managing different versions of the model.

Exact Extract Reference: According to the AWS SageMaker documentation, “The SageMaker Model Registry allows you to catalog models for production, manage model versions, associate metadata, and manage approval status for deployment.” (Source: AWS SageMaker Documentation - Model Registry, https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry.html).

Step 2: Using the current model to make predictions

The goal here is to identify a SageMaker feature that facilitates making predictions (inference) with a deployed model. Let’s evaluate the options:

SageMaker Clarify: As mentioned, this feature focuses on bias detection and explainability, not on performing inference or making predictions.

SageMaker Model Registry: While the Model Registry helps manage and catalog models, it is not used directly for making predictions. It can store models, but the actual inference process requires a deployment mechanism.

SageMaker Serverless Inference: This feature allows users to deploy models for inference without managing infrastructure. It automatically scales based on traffic and is specifically designed for making predictions in a cost-efficient, serverless manner.

Conclusion for Step 2: SageMaker Serverless Inference is the correct choice for using the current model to make predictions.

Exact Extract Reference: The AWS documentation states, “SageMaker Serverless Inference is a deployment option that allows you to deploy machine learning models for inference without configuring or managing servers. It automatically scales to handle inference requests, making it ideal for workloads with intermittent or unpredictable traffic.” (Source: AWS SageMaker Documentation - Serverless Inference, https://docs.aws.amazon.com/sagemaker/latest/dg/serverless-inference.html).

Why Not Use the Same Feature Twice?

The question specifies that each SageMaker feature or resource should be selected one time or not at all. Since SageMaker Model Registry is used for version management and SageMaker Serverless Inference is used for predictions, each feature is selected exactly once. SageMaker Clarify is not applicable to either step, so it is not selected at all, fulfilling the question’s requirements.

The correct answer is A because code translation tasks require a model with deep understanding of syntax, semantic meaning, and the ability to maintain functional equivalence in different programming languages. Some foundation models offered via Amazon Bedrock (like CodeWhisperer or Meta’s Code LLMs) are designed with these capabilities in mind.

From AWS documentation:

" Generative AI models used for code generation and translation must understand programming semantics and syntax to generate accurate and secure code. These models are trained to recognize language-specific patterns and preserve logic when converting between languages. "

Explanation of other options:

B. Speed and error handling are secondary to correctness and comprehension in code translation tasks.

C. Creative content generation is not relevant for deterministic tasks like source code translation.

D. Model size may affect performance or latency but is not a primary selection criterion for translation accuracy.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Model Selection Guide – Code Generation and Translation

AWS Developer Tools – CodeWhisperer Capabilities

AWS ML Specialty Study Guide – LLM Use Cases in Software Engineering

Comprehensive and Detailed Explanation from AWS AI Documents:

Fine-tuning a foundation model means taking a pre-trained large model and continuing its training on domain-specific or task-specific data to specialize it for a particular use case. Fine-tuning does not retrain the FM from scratch (which would be costly and time-consuming). Instead, it improves model accuracy, relevance, and contextual adaptation for the intended application (e.g., legal, healthcare, customer support).

From AWS Docs:

“With Amazon Bedrock, you can fine-tune foundation models on your own data to specialize them for your unique use cases.”

“Fine-tuning a foundation model adapts it to a specific task by training on smaller sets of labeled data relevant to the problem domain.”

???? Reference:

AWS Documentation – Fine-tuning foundation models in Amazon Bedrock

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.