Pass the Amazon Web Services AWS Certified AI Practitioner AIF-C01 Questions and answers with Dumpstech

To implement a large language model (LLM) responsibly, the firm should focus on fairness and mitigating bias, which are critical for ethical AI deployment.

A. Include Fairness Metrics for Model Evaluation:

Fairness metrics help ensure that the model's predictions are unbiased and do not unfairly discriminate against any group.

These metrics can measure disparities in model outcomes across different demographic groups, ensuring responsible AI practices.

C. Modify the Training Data to Mitigate Bias:

Adjusting training data to be more representative and balanced can help reduce bias in the model's predictions.

Mitigating bias at the data level ensures that the model learns from a diverse and fair dataset, reducing potential harms in deployment.

Why Other Options are Incorrect:

B. Adjust the temperature parameter of the model: Controls randomness in outputs but does not directly address fairness or bias.

D. Avoid overfitting on the training data: Important for model generalization but not directly related to responsible AI practices regarding fairness and bias.

E. Apply prompt engineering techniques: Useful for improving model outputs but not specifically for mitigating bias or ensuring fairness.

The correct answer is C, because Amazon Nova Micro is a smaller, lower-cost foundation model that is text-only, while Nova Lite is a more capable multimodal model that supports images, videos, and text. According to AWS Bedrock documentation, the Nova model family includes variants that differ in capability and cost. Nova Micro is optimized for lightweight text-based tasks, including summarization, question answering, and basic reasoning. This makes it cheaper to operate and well-suited for cost-sensitive workloads. Nova Lite, on the other hand, is a multimodal FM that can analyze documents, screenshots, photographs, charts, and videos, making it ideal for media companies requiring cross-format understanding. AWS clarifies that both Micro and Lite use transformer-based architectures, and run on managed infrastructure that abstracts hardware considerations. Therefore, the main differentiator is capability—and Nova Micro being text-only is the more cost-effective option. Nova Lite is appropriate only when image or video analysis is required.

Referenced AWS Documentation:

Amazon Bedrock – Nova Model Family Overview

AWS Generative AI Model Selection Guide

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 correct answer is C – Amazon Kendra, AWS’s enterprise search service designed for organizations with large, diverse document repositories. Kendra uses machine learning and natural language understanding (NLU) to provide semantic search, meaning it retrieves results based on meaning rather than keyword matching. According to AWS documentation, Kendra is ideal for educational, enterprise, and knowledge-management scenarios where users need fast, accurate retrieval across PDFs, HTML, Office documents, FAQs, and multimedia transcripts. Kendra connectors can index content from S3, SharePoint, LMS platforms, and internal databases, making it perfect for large volumes of training materials. Amazon Comprehend (A) is for NLP tasks like entity extraction, not enterprise search. Amazon Textract (B) extracts text from PDFs and scanned materials but does not provide search capabilities. Amazon Personalize (D) is for personalized recommendations, not document retrieval. Kendra is purpose-built for enterprise search and aligns directly with the company's needs.

Referenced AWS Documentation:

Amazon Kendra Developer Guide – Enterprise Search

AWS ML Specialty Guide – Intelligent Search Systems

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 correct answer is A because temperature controls the randomness of a language model's output. A higher temperature increases diversity by making the model more likely to explore less probable tokens, while a lower temperature results in more deterministic and repetitive outputs.

From AWS documentation:

"The temperature parameter in LLMs adjusts the randomness of generated responses. Higher values (e.g., 0.8–1.0) produce more creative and diverse output, while lower values (e.g., 0.1–0.3) make output more focused and repetitive."

Explanation of other options:

B. Batch size is related to training efficiency, not output diversity.

C. Learning rate affects the training convergence rate, not inference-time output variety.

D. Optimizer type is a training configuration that influences how the model learns during training, not diversity during inference.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock – Parameter Tuning Guide

AWS Machine Learning Specialty Guide – LLM Inference Parameters

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Q Developer is a fully managed generative AI assistant designed specifically to help developers write, test, and debug code.

Amazon Q Developer:

Generates code and test cases

Explains existing code

Integrates directly into developer workflows and IDEs

Requires minimal setup and operational overhead

Why the other options are incorrect:

Amazon Q Business (A) is focused on business knowledge and enterprise data.

Bedrock Agents (B) orchestrate workflows and API calls, not developer productivity tools.

SageMaker Clarify (D) focuses on explainability and bias detection.

AWS AI document references:

Amazon Q Developer Overview

Developer Productivity with Generative AI on AWS

Generative AI Tools for Software Development

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.

Decreasing the number of tokens in the prompt reduces the cost associated with using an LLM model on Amazon Bedrock, as costs are often based on the number of tokens processed by the model.

Token Reduction Strategy:

By decreasing the number of tokens (words or characters) in each prompt, the company reduces the computational load and, therefore, the cost associated with invoking the model.

Since the model is performing well with few-shot prompting, reducing token usage without sacrificing performance can lower monthly costs.

Why Option B is Correct:

Cost Efficiency: Directly reduces the number of tokens processed, lowering costs without requiring additional adjustments.

Maintaining Performance: If the model is already performing well, a reduction in tokens should not significantly impact its performance.

Why Other Options are Incorrect:

A. Fine-tuning: Can be costly and time-consuming and is not needed if the current model is already performing well.

C. Increase the number of tokens: Would increase costs, not lower them.

D. Use Provisioned Throughput: Is unrelated to token costs and applies more to read/write capacity in databases.

The correct answers are A and C because:

Amazon Transcribe converts spoken dialogue from video into text (captions or subtitles).

Amazon Translate translates that transcribed text into other languages.

Amazon Polly can then convert the translated text into lifelike speech for voice-overs in different languages.

From AWS documentation:

"Amazon Transcribe is used to create accurate speech-to-text transcripts. You can feed this text into Amazon Translate to support multilingual subtitles. To generate audio output, Amazon Polly provides neural text-to-speech in multiple languages."

Explanation of other options:

B. Amazon Textract is used for extracting text from documents/images, not audio or video, and is not applicable here.

D. Amazon Translate does not generate speech — it only translates text.

E. Amazon Textract does not generate audio.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Transcribe Developer Guide – Media Transcription

Amazon Translate Developer Guide – Multilingual Support

Amazon Polly Documentation – Text-to-Speech in Multiple Languages

AWS ML Specialty Guide – Multimedia AI Workflows