Amazon Web Services Updated AIF-C01 Exam Questions and Answers by fallon

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 correct answer is D because Amazon OpenSearch Service supports k-Nearest Neighbor (k-NN) search and vector similarity search, which are required for semantic search tasks, such as matching natural language queries to image embeddings.

From AWS documentation:

" Amazon OpenSearch Service supports k-NN search, which allows you to run efficient similarity searches on large-scale datasets using vector embeddings generated by models. This enables applications like natural language-based image search and personalized recommendations. "

In this use case, image data can be encoded into vectors using foundation models (e.g., via Amazon Bedrock or SageMaker), and OpenSearch Service can index and retrieve results based on vector similarity.

Explanation of other options:

A. Amazon Comprehend is for text-based NLP tasks and does not provide vector similarity or search functionality.

B. Amazon Personalize is for user-item recommendations and personalization, not vector-based semantic search.

C. Amazon Polly is a text-to-speech service and not related to image search or vector databases.

Referenced AWS AI/ML Documents and Study Guides:

Amazon OpenSearch Service Documentation – k-NN and Vector Search

AWS ML Specialty Study Guide – Semantic Search and Vector Indexing

AWS Generative AI Best Practices – Embeddings and Vector Databases

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Bedrock Agents are designed to:

Interpret user intent

Plan multi-step actions

Invoke APIs and backend services

Complete transactional workflows

This makes Agents ideal for task-oriented applications such as travel reservations, where the system must:

Understand customer requests

Call reservation APIs

Orchestrate end-to-end transactions

Why the other options are incorrect:

Prompt routing (B) selects prompts or models but does not invoke APIs.

Knowledge Bases (C) retrieve information but do not execute actions.

Guardrails (D) enforce safety and compliance, not task execution.

AWS AI document references:

Amazon Bedrock Agents Documentation

Building Task-Oriented Generative AI Applications

Foundation Model Orchestration on AWS

The verified answer is D. Enhanced ability to identify bias and improve model governance. Increasing model transparency improves the ability of technical teams, business stakeholders, risk teams, and compliance teams to understand how a model behaves, what factors influence its predictions, and whether it shows unfair or biased behavior. AWS SageMaker Clarify documentation states that SageMaker Clarify provides tools to help explain how machine learning models make predictions. These tools help modelers, developers, and internal stakeholders understand model characteristics before deployment and debug predictions after deployment.

AWS also connects transparency directly to fairness, bias detection, explainability, and governance. AWS guidance states that SageMaker Clarify can be used to create comprehensive reports on model fairness and explainability for stakeholders, including risk and compliance-aligned teams and external regulators. These reports document bias detection and mitigation efforts and provide transparency into responsible AI practices. This directly supports option D because transparency improves the organization’s ability to identify bias and strengthen governance.

Option A is incorrect because transparency does not reduce the need for validation. A transparent model still requires validation, testing, monitoring, and governance controls. Option B is incorrect because transparency does not eliminate regulatory compliance monitoring. In fact, transparency often supports and strengthens compliance monitoring rather than replacing it. Option C is incorrect because transparency does not automatically remove all bias. It helps teams detect, explain, measure, and mitigate bias, but bias mitigation still requires deliberate actions such as representative data preparation, metric evaluation, retraining, sampling changes, or governance review.

Therefore, the correct outcome of increasing model transparency is an improved ability to identify bias and improve model governance.