Crush the AWS AIF-C01 AI Practitioner Exam Without the Fluff

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 ecommerce company is deploying a chatbot that needs safeguards to filter harmful content from input prompts and responses. Amazon Bedrock Guardrails provide mechanisms to ensure responsible AI usage by filtering harmful content, such as hate speech, violence, or misinformation, making it the appropriate feature for this requirement.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Amazon Bedrock Guardrails enable developers to implement safeguards for generative AI applications, such as chatbots, by filtering harmful content in input prompts and model responses. Guardrails include content filters, word filters, and denied topics to ensure safe and responsible outputs. "

(Source: AWS Bedrock User Guide, Guardrails for Responsible AI)

Detailed Explanation:

Option A: Amazon Bedrock GuardrailsThis is the correct answer. Amazon Bedrock Guardrails are specifically designed to filter harmful content from chatbot inputs and responses, ensuring safe interactions for users.

Option B: Amazon Bedrock AgentsAmazon Bedrock Agents are used to automate tasks and integrate with external tools, not to filter harmful content. This option does not meet the requirement.

Option C: Amazon Bedrock inference APIsAmazon Bedrock inference APIs allow users to invoke foundation models for generating responses, but they do not provide built-in content filtering mechanisms.

Option D: Amazon Bedrock custom modelsCustom models on Amazon Bedrock allow users to fine-tune models, but they do not inherently include safeguards for filtering harmful content unless explicitly implemented.

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 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.

The verified answer is C. Memory. In Amazon Bedrock AgentCore, Memory is the feature designed to preserve conversational context and make an assistant remember relevant information across interactions. AWS documentation states that AgentCore Memory supports both short-term and long-term memory. Short-term memory stores raw interactions that help the agent maintain context within a single session, while long-term memory automatically extracts and stores key insights from conversations across multiple sessions, including user preferences, important facts, and session summaries. This directly matches the requirement because the assistant must maintain context across multiple user interactions without the company building and operating its own memory infrastructure.

Option A. Gateway is incorrect because AgentCore Gateway is used to connect agents securely to tools, APIs, and enterprise services. It helps expose external capabilities to agents, but it does not provide persistent conversational context. Option B. Browser Tool is incorrect because the Browser Tool enables an agent to interact with websites or web-based workflows. It is useful for browser automation and web interaction, not memory retention. Option D. Code Interpreter is incorrect because Code Interpreter allows the agent to execute code for tasks such as calculations, file analysis, and data manipulation. It does not solve the requirement of remembering prior conversation details.

The key phrase in the question is “maintain context across multiple user interactions.” That is exactly the purpose of AgentCore Memory. AWS also explains that long-term memory provides persistent storage for session-specific context, enabling agents to maintain continuity and personalization across interactions. Therefore, when a conversational assistant needs continuity, personalization, and context retention without custom infrastructure management, the correct AgentCore feature is Memory.

The F1 score is a metric used to evaluate the performance of a classification model by considering both precision and recall. Precision measures the accuracy of positive predictions (i.e., the proportion of true positive predictions among all positive predictions made by the model), while recall measures the model ' s ability to identify all relevant positive instances (i.e., the proportion of true positive predictions among all actual positive instances). The F1 score is the harmonic mean of precision and recall, providing a single metric that balances both concerns. This is particularly useful when dealing with imbalanced datasets or when the cost of false positives and false negatives is significant. Options B, C, and D pertain to other aspects of model performance but are not related to the F1 score.

The correct answer is A because Amazon SageMaker Canvas is designed specifically for users with little or no machine learning or programming experience. It provides a visual interface to build ML models by simply uploading data, performing analysis, and generating predictions using a no-code environment.

From the AWS documentation:

" Amazon SageMaker Canvas enables business analysts and other users to generate accurate ML predictions using a visual, point-and-click interface without writing code or having prior ML experience. "

This feature allows the user to:

Import datasets (e.g., HR data)

Automatically explore the data

Select the prediction column (e.g., attrition)

Train the model

Generate and export predictions

Explanation of other options:

B. SageMaker Clarify is used to detect bias and explain ML predictions but not to build models or make predictions without code.

C. SageMaker Model Monitor monitors model quality in production but doesn’t build or train models.

D. SageMaker Data Wrangler is used for data preprocessing and transformation but still requires some technical configuration.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker Canvas Developer Guide

AWS Certified Machine Learning Specialty Study Guide – AutoML and No-Code Tools Section

AWS Machine Learning Blog: “Predict Employee Attrition with SageMaker Canvas”

The verified answer is A. Amazon Bedrock Guardrails. AWS documentation states that Amazon Bedrock Guardrails helps detect sensitive information, including personally identifiable information, in input prompts or model responses by using sensitive information filters. AWS also states that these filters can be configured to block or mask detected PII. This directly matches the requirement to prevent a customer service agent from disclosing PII during conversations.

Bedrock Guardrails supports handling sensitive information in two key ways. A block action can block requests or responses that include sensitive information, and a mask action can anonymize or redact detected information in model requests or responses. AWS gives examples of PII categories such as names, email addresses, phone numbers, usernames, passwords, addresses, credit card numbers, PINs, and other sensitive identifiers. For a customer service agent, this is exactly the right feature because PII could appear in either the user input or the model response.

Amazon Bedrock Flows is incorrect because flows help orchestrate generative AI workflows. They do not primarily provide PII filtering. Amazon Bedrock Knowledge Bases is incorrect because knowledge bases support Retrieval Augmented Generation by connecting models to enterprise data sources. They help ground responses but do not directly block PII disclosure. Amazon Bedrock Data Automation is incorrect because BDA is used to transform and extract insights from multimodal content such as documents, images, audio, and video. It is not the runtime guardrail feature for blocking or masking PII in conversations.

Therefore, the correct Amazon Bedrock feature is Amazon Bedrock Guardrails.