Amazon SageMaker Ground Truth lets you create data labeling jobs and can integrate with Amazon Mechanical Turk (a distributed human workforce) to label large unlabeled datasets.

A (batch inference) applies models to already-trained data, not labeling.

B (PyTorch Distributed) is for distributed training, not labeling.

D (OCR) applies only to text extraction from images, not transactions.

E is incorrect; Ground Truth is the service for labeling, not " AI labeling job. "

???? Reference:

AWS Documentation – SageMaker Ground Truth

Amazon Bedrock Knowledge Bases enable Retrieval Augmented Generation (RAG) by letting you connect external company data sources to your foundation model in a serverless, cost-effective manner—without retraining or fine-tuning. This allows the model to answer questions and generate content grounded in your own documents or data.

A is correct:

“Knowledge Bases for Amazon Bedrock enable generative AI applications to retrieve and include your company’s information for more contextual responses, without the need for expensive retraining or custom models.”

(Reference: Amazon Bedrock Knowledge Bases)

B is not cost-effective or guaranteed to add your company’s context.

C (Agents) are for orchestrating workflows, not specifically RAG/context.

D (Custom model deployment) is costly and unnecessary for just adding context.

The verified answer is B. Amazon SageMaker Clarify. The model is used for customer loan applications, where explainability, transparency, and human-centered decision support are critical. AWS documentation states that SageMaker Clarify provides tools to help explain how machine learning models make predictions. These tools help ML developers, modelers, and internal stakeholders understand model characteristics before deployment and debug predictions after deployment.

SageMaker Clarify is specifically aligned with explainable AI because it provides feature attribution methods, including SHAP-based explanations. AWS documentation explains that Clarify can generate reports that contribute to model governance documentation and can help describe how a model works, what features influence its decisions, and how explanations are generated.

Amazon SageMaker Model Registry is incorrect because it manages model versions, approval status, and deployment tracking. It supports governance workflows, but it does not explain why a model made a decision.

Amazon SageMaker Pipelines is incorrect because it automates and orchestrates ML workflows such as training, evaluation, and deployment. It does not provide the core explainability function required here.

Amazon SageMaker Feature Store is incorrect because it stores, shares, and serves ML features for training and inference. It improves feature reuse and consistency, but it does not explain model decisions.

For a financial loan application model, stakeholders and regulators need to understand which factors influenced predictions. SageMaker Clarify is the AWS feature designed for this explainability requirement, so option B is correct.

Amazon SageMaker Clarify provides transparency and explainability for machine learning models by generating metrics, reports, and examples that help to understand model predictions. For a medical company that needs a foundation model to be transparent and explainable to meet regulatory requirements, SageMaker Clarify is the most suitable solution.

Amazon SageMaker Clarify:

It helps in identifying potential bias in the data and model, and also explains model behavior by generating feature attributions, providing insights into which features are most influential in the model ' s predictions.

These capabilities are critical in medical applications where regulatory compliance often mandates transparency and explainability to ensure that decisions made by the model can be trusted and audited.

Why Option B is Correct:

Transparency and Explainability: SageMaker Clarify is explicitly designed to provide insights into machine learning models ' decision-making processes, helping meet regulatory requirements by explaining why a model made a particular prediction.

Compliance with Regulations: The tool is suitable for use in sensitive domains, such as healthcare, where there is a need for explainable AI.

Why Other Options are Incorrect:

A. Amazon Inspector: Focuses on security assessments, not on explainability or model transparency.

C. Amazon Macie: Provides data security by identifying and protecting sensitive data, but does not help in making models explainable.

D. Amazon Rekognition: Used for image and video analysis, not relevant to making models explainable.

Thus, B is the correct answer for meeting transparency and explainability requirements for the foundation model

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 requirement is to deploy a customized machine learning (ML) model and monitor its quality for potential drift over time in a production environment. Let’s evaluate each option:

A. Amazon Rekognition: This service is designed for image and video analysis, such as object detection, facial recognition, and text extraction. It is not suited for deploying custom ML models or monitoring model quality drift.

B. Amazon SageMaker Clarify: This feature helps detect bias in ML models and explains model predictions. While it addresses fairness and interpretability, it does not specifically focus on monitoring model quality drift over time in production.

C. Amazon Comprehend: This is a natural language processing (NLP) service for extracting insights from text, such as sentiment analysis or entity recognition. It does not support deploying custom ML models or monitoring model performance drift.

D. Amazon SageMaker Model Monitor: This feature is part of Amazon SageMaker and is specifically designed to monitor ML models in production. It tracks metrics such as data drift, model drift, and performance degradation over time, alerting users when issues are detected.

Exact Extract Reference: According to the AWS documentation on Amazon SageMaker, “Amazon SageMaker Model Monitor allows you to detect and remediate data and model quality issues in production. It continuously monitors the performance of deployed models, capturing data and model predictions to detect deviations from expected behavior, such as data drift or model performance degradation.” (Source: AWS SageMaker Documentation - Model Monitoring, https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor.html).

This directly aligns with the requirement to observe model quality drift, making Amazon SageMaker Model Monitor the correct choice.

AI governance frameworks aim to build trust and deploy human-centered AI technologies by establishing guidelines and policies for data usage, transparency, responsible AI practices, and compliance with regulations. This ensures ethical and accountable AI development and deployment.

Exact Extract from AWS AI Documents:

From the AWS Documentation on Responsible AI:

" AI governance frameworks establish trust in AI technologies by developing policies and guidelines for data management, transparency, responsible AI practices, and compliance with regulatory requirements, ensuring human-centered and ethical AI deployment. "

(Source: AWS Documentation, Responsible AI Governance)

Detailed Explanation:

Option A: Expanding initiatives across business units to create long-term business valueWhile expanding initiatives can drive value, it is not a core characteristic of AI governance frameworks focused on trust and human-centered AI.

Option B: Ensuring alignment with business standards, revenue goals, and stakeholder expectationsAlignment with business goals is important but not specific to AI governance frameworks for building trust and ethical AI deployment.

Option C: Overcoming challenges to drive business transformation and growthOvercoming challenges is a general business goal, not a defining characteristic of AI governance frameworks.

Option D: Developing policies and guidelines for data, transparency, responsible AI, and complianceThis is the correct answer. This option directly describes the core components of AI governance frameworks that ensure trust and ethical AI deployment.

The best solution is Amazon Bedrock Knowledge Bases, which allows for the seamless integration of structured and unstructured internal documents—such as PDFs, CSVs, and extracted image text—into a retrieval-augmented generation (RAG) pipeline. According to AWS documentation, Bedrock Knowledge Bases offer a no-code or low-code setup to link your enterprise data with foundation models for context-aware responses, without needing to fine-tune or retrain models. The system indexes documents in an Amazon S3 bucket, creates embeddings, and stores them in a vector store. At inference time, the model retrieves relevant context and incorporates it into its response. This approach provides dynamic and up-to-date responses while maintaining data privacy, with minimal operational overhead. Unlike fine-tuning or building a model from scratch in SageMaker, which requires considerable compute resources and model management, Bedrock Knowledge Bases are serverless and easy to configure. It is designed exactly for internal knowledge AI assistants.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Knowledge Bases

AWS Generative AI Best Practices – RAG Patterns for Enterprise Search

A summarization chatbot is ideal for extracting key points from legal documents. Large language models (LLMs) can be used to summarize complex texts, such as legal documents, making them more accessible and understandable.

Option C (Correct): " Develop a summarization chatbot " : This is the correct answer because a summarization chatbot uses LLMs to condense and extract key information from text, which is precisely the requirement for reading and summarizing legal documents.

Option A: " Build an automatic named entity recognition system " is incorrect because it focuses on identifying specific entities, not summarizing documents.

Option B: " Create a recommendation engine " is incorrect as it is used to suggest products or content, not summarize text.

Option D: " Develop a multi-language translation system " is incorrect because translation is unrelated to summarizing text.

AWS AI Practitioner References:

Using LLMs for Text Summarization on AWS: AWS supports developing summarization tools using its AI services, including Amazon Bedrock.

The problem involves a simple probability calculation that can be handled efficiently by straightforward mathematical rules and computations. Using machine learning techniques would introduce unnecessary complexity and operational overhead.

Option C (Correct): " Use code that will calculate probability by using simple rules and computations " : This is the correct answer because it directly solves the problem with minimal overhead, using basic probability rules.

Option A: " Use supervised learning to create a regression model " is incorrect as it overcomplicates the solution for a simple probability problem.

Option B: " Use reinforcement learning to train a model " is incorrect because reinforcement learning is not needed for a simple probability calculation.

Option D: " Use unsupervised learning to create a model " is incorrect as unsupervised learning is not applicable to this task.

AWS AI Practitioner References:

Choosing the Right Solution for AI Tasks: AWS recommends using the simplest and most efficient approach to solve a given problem, avoiding unnecessary machine learning techniques for straightforward tasks.