Amazon Web Services AIF-C01 - AWS Certified AI Practitioner Exam

AWS Data Exchange is a service that allows companies to securely exchange data with third parties, such as independent software vendors (ISVs). AWS Data Exchange can be configured to provide notifications, including email notifications, when new datasets or compliance reports become available.

Option D (Correct): "AWS Data Exchange": This is the correct answer because it enables the company to receive notifications, including email messages, when ISVs' compliance reports are available.

Option A: "AWS Audit Manager" is incorrect because it focuses on assessing an organization's own compliance, not receiving third-party compliance reports.

Option B: "AWS Artifact" is incorrect as it provides access to AWS’s compliance reports, not ISVs'.

Option C: "AWS Trusted Advisor" is incorrect as it offers optimization and best practices guidance, not compliance report notifications.

AWS AI Practitioner References:

AWS Data Exchange Documentation: AWS explains how Data Exchange allows organizations to subscribe to third-party data and receive notifications when updates are available.

The requirement is to improve the accuracy of a natural language generation (NLG) model that relies on rapidly changing inventory data. Let’s evaluate the options:

A. Transfer learning: This involves pre-training a model on a large dataset and fine-tuning it for a specific task. While effective for general model improvement, it does not specifically address the challenge of incorporating rapidly changing inventory data into the model’s responses.

B. Federated learning: This technique trains models across decentralized devices while keeping data localized, primarily for privacy purposes. It is not designed to handle rapidly changing data or improve NLG model accuracy in this context.

C. Retrieval Augmented Generation (RAG): RAG combines a language model with a retrieval mechanism that fetches relevant, up-to-date information (e.g., inventory data) from an external source during inference. This is ideal for scenarios with dynamic data, as it ensures the model’s responses are grounded in the latest information, improving accuracy.

D. One-shot prompting: This involves providing a single example to guide the model’s output. While useful for specific tasks, it does not scale well for rapidly changing data or ensure consistent accuracy with dynamic inventory updates.

Exact Extract Reference: According to AWS documentation on generative AI techniques, “Retrieval Augmented Generation (RAG) enhances large language models by retrieving relevant documents or data at inference time, enabling the model to generate accurate and contextually relevant responses, especially for dynamic or frequently updated datasets.” (Source: AWS Generative AI Glossary, https://aws.amazon.com/what-is/retrieval-augmented-generation/). This directly addresses the need for accuracy with rapidly changing inventory data.

RAG is the most suitable technique for this scenario, as it allows the model to access and incorporate the latest inventory data, making C the correct answer.

Comprehensive and Detailed Explanation (AWS AI documents):

AWS machine learning fundamentals classify K-means as an unsupervised learning algorithm used to group unlabeled data into clusters based on feature similarity and distance metrics. Because the data is unlabeled and the goal is grouping rather than prediction, K-means is the most appropriate choice.

Why the other options are incorrect:

XGBoost is a supervised learning algorithm that requires labeled data.

DeepAR forecasting is designed for time series forecasting.

Linear learner is typically used for supervised regression or classification tasks.

AWS AI Study Guide References:

AWS unsupervised learning concepts

AWS clustering algorithms overview

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

The correct answer is C because Amazon Bedrock Guardrails provides out-of-the-box configurable safety mechanisms to control the behavior of LLMs in generative AI applications. Guardrails can be configured with denylists, content filters, sensitive topics, and tone enforcement, all without retraining the model.

From AWS documentation:

"Amazon Bedrock Guardrails allows developers to define safety and responsible AI policies directly in the model inference layer, making it easy to prevent harmful, biased, or unsafe outputs with minimal configuration."

Explanation of other options:

A. Bedrock playgrounds are interactive environments for testing prompts and models but do not provide production-grade safety enforcement.

B. SageMaker Clarify focuses on bias detection and explainability for supervised ML models — it does not directly apply guardrails to LLM outputs.

D. SageMaker JumpStart is for model fine-tuning and deployment, not for enforcing safety policies on LLM responses.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Guardrails Overview

AWS Responsible AI Whitepaper

AWS Certified ML Specialty Study Guide – Safety in Generative AI

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.

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.

Amazon SageMaker Model Cards provide a standardized way to document and track model information, including versions and performance. According to AWS documentation:

“SageMaker Model Cards provide a single source of truth for model information including intended use, training details, evaluation metrics, and ethical considerations to support governance and collaboration.”

The scenario involves analyzing customer feedback and automatically classifying it into categories such as product quality, customer service, and delivery experience. This task requires processing and understanding textual data, which is a core application of natural language processing (NLP). NLP encompasses techniques for analyzing, interpreting, and generating human language, including tasks like text classification, sentiment analysis, and topic modeling, all of which are relevant to this use case.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"Natural Language Processing (NLP) enables machines to understand and process human language. Common NLP tasks include text classification, sentiment analysis, named entity recognition, and topic modeling. Services like Amazon Comprehend can be used to classify text into predefined categories based on content."

(Source: AWS AI Practitioner Learning Path, Module on AI and ML Concepts)

Detailed Explanation:

Option A: Computer visionComputer vision involves processing and analyzing visual data, such as images or videos. Since the scenario deals with textual customer feedback, computer vision is not applicable.

Option B: Natural language processing (NLP)This is the correct answer. The task of classifying customer feedback into categories requires understanding and processing text, which is an NLP task. AWS services like Amazon Comprehend are specifically designed for such text classification tasks.

Option C: Recommendation systemsRecommendation systems suggest items or content based on user preferences or behavior. The scenario does not involve recommending products or services but rather classifying feedback, so this option is incorrect.

Option D: Fraud detectionFraud detection involves identifying anomalous or fraudulent activities, typically in financial or transactional data. The scenario focuses on text classification, not anomaly detection, making this option irrelevant.