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

Amazon SageMaker Ground Truth Plus provides a fully managed data labeling service where AWS manages the workforce, tools, and processes.

Data Wrangler is for data preparation and transformation.

Transcribe is for speech-to-text.

Macie is for sensitive data discovery, not labeling.

???? Reference:

AWS Documentation – SageMaker Ground Truth Plus

Comprehensive and Detailed Explanation (AWS AI documents):

Overfitting occurs when an ML model learns patterns too closely from training data, including noise, and fails to generalize to unseen data. According to AWS ML fundamentals, a key indicator of overfitting is high training accuracy combined with reduced accuracy on new or test data.

Option A directly reflects this behavior: the model performs well during training but loses accuracy when evaluated on new data, which is a textbook symptom of overfitting.

Why the other options are not overfitting:

B describes an under-featured model (underfitting risk).

C indicates poor data representativeness, not overfitting.

D reflects limited feature selection, which may lead to underfitting or bias, not overfitting.

AWS AI Study Guide References:

AWS Machine Learning concepts: bias vs. variance

AWS training and evaluation best practices

BLEU (Bilingual Evaluation Understudy) is a metric used to evaluate the accuracy of machine-generated translations by comparing them against reference translations. It is commonly used for translation tasks to measure how close the generated output is to professional human translations.

Option A (Correct): "Bilingual Evaluation Understudy (BLEU)": This is the correct answer because BLEU is specifically designed to evaluate the quality of translations, making it suitable for the company's use case.

Option B: "Root mean squared error (RMSE)" is incorrect because RMSE is used for regression tasks to measure prediction errors, not translation quality.

Option C: "Recall-Oriented Understudy for Gisting Evaluation (ROUGE)" is incorrect as it is used to evaluate text summarization, not translation.

Option D: "F1 score" is incorrect because it is typically used for classification tasks, not for evaluating translation accuracy.

AWS AI Practitioner References:

Model Evaluation Metrics on AWS: AWS supports various metrics like BLEU for specific use cases, such as evaluating machine translation models.

The correct answers are A and E because both directly align with AWS best practices for securing generative AI services and data privacy in enterprise applications.

From the AWS Amazon Q Business documentation:

"AWS Key Management Service (KMS) integrates with Amazon Q Business to encrypt sensitive data at rest. You can use customer-managed KMS keys to meet compliance requirements."

And:

"You must configure IAM access controls to manage which users and applications can access Amazon Q Business indexes, ensuring that only authorized users can retrieve information."

Explanation of other options:

B. Cross-account access is not a common requirement for internal enterprise use of Amazon Q Business unless explicitly sharing data across organizations. It’s not a requirement for securing access.

C. Amazon Inspector is a vulnerability management tool for EC2 and containers. It is unrelated to Amazon Q authentication or security.

D. Allowing public access would violate security and privacy principles and directly contradict the stated requirement.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Q Business Developer Guide – Security and Identity Management

AWS KMS Documentation – Integration with Bedrock and Amazon Q

AWS Certified Machine Learning Specialty Guide – Responsible AI and Governance Section

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Inference parameters control output behavior:

Higher temperature increases creativity and randomness

Shorter response length limits output size

AWS prompt and inference guidance recommends increasing temperature for creative tasks and reducing response length for concise outputs.

Why the other options are incorrect:

A reduces creativity.

B produces long outputs.

D produces deterministic and lengthy responses.

AWS AI document references:

Inference Parameters for Foundation Models

Controlling Creativity and Length in Text Generation

Prompt Engineering Best Practices

Amazon Textract (E) automatically extracts text and structured data from scanned documents, such as PDFs.

Amazon Bedrock (B) offers access to LLMs (such as Amazon Titan or Anthropic Claude) for tasks like summarization and generating embeddings for search.

Workflow:

Amazon Textract extracts text from PDFs in S3.

Amazon Bedrock LLMs summarize the extracted text.

(Optional: Summaries can be indexed using Amazon OpenSearch or another search solution.)

A (Translate) is for language translation, not extraction or summarization.

C (Transcribe) is for audio to text, not PDFs.

D (Polly) is for text-to-speech.

“Amazon Textract extracts text, forms, and tables from scanned documents... Bedrock provides generative AI models to perform summarization and other text generation tasks.”

(Reference: Amazon Textract, Amazon Bedrock, AWS GenAI RAG Reference)

Ongoing pre-training when fine-tuning a foundation model (FM) improves model performance over time by continuously learning from new data.

Ongoing Pre-Training:

Involves continuously training a model with new data to adapt to changing patterns, enhance generalization, and improve performance on specific tasks.

Helps the model stay updated with the latest data trends and minimize drift over time.

Why Option B is Correct:

Performance Enhancement: Continuously updating the model with new data improves its accuracy and relevance.

Adaptability: Ensures the model adapts to new data distributions or domain-specific nuances.

Why Other Options are Incorrect:

A. Decrease model complexity: Ongoing pre-training typically enhances complexity by learning new patterns, not reducing it.

C. Decreases training time requirement: Ongoing pre-training may increase the time needed for training.

D. Optimizes inference time: Does not directly affect inference time; rather, it affects model performance.

Model fine-tuning adapts a pre-trained model to a specific domain or task using labeled data. This is the preferred approach when you want highly customized behavior for a particular application or subject area.

(Reference: Amazon Bedrock Fine-Tuning)

Data augmentation is used to artificially increase the size of a labeled dataset, usually by transforming or generating variations of the original data. This helps improve model generalization when labeled data is limited.

(Reference: AWS Data Preparation Techniques, AWS AI Practitioner Guide)

Continued pre-training (also called domain-adaptive pre-training) further trains a foundation model on large amounts of unlabeled data from a specific domain, improving the model’s language understanding or generation for that domain.

(Reference: Amazon Bedrock Customization Options)

Comprehensive and Detailed Explanation From Exact AWS AI documents:

In Amazon Bedrock evaluations, Completeness measures how thoroughly a model or agent response addresses all aspects of the user prompt.

AWS evaluation guidance for LLM-as-a-judge explains that:

Completeness focuses on coverage of prompt requirements

It is especially useful for evaluating multi-part questions

It is a built-in qualitative metric in agent evaluation workflows

Why the other options are incorrect:

ROUGE (A) measures text overlap, mainly for summarization.

Following instructions (C) evaluates adherence, not coverage.

Refusal (D) measures appropriate refusal behavior.

AWS AI document references:

Amazon Bedrock Model Evaluation

LLM-as-a-Judge Metrics

Evaluating Agent Responses on AWS

Model misuse is a key example of output vulnerability, where the output of a model can be intentionally or unintentionally used in ways that create harm or deviate from the model’s intended purpose. According to AWS Responsible AI guidance, output vulnerabilities refer to flaws or weaknesses in how a model’s predictions or generations are interpreted or used by external systems or users. This could involve using a generative model to produce harmful content, manipulate outputs to spread misinformation, or expose private information. AWS recommends that safeguards such as Guardrails, Human-in-the-Loop (HITL) validation, and ethical guidelines be enforced to mitigate these output risks. In contrast, data poisoning and data leakage are input-level vulnerabilities that corrupt model training, and parameter stealing is a model-level attack where internal configurations are extracted. Model misuse specifically reflects how outputs can be abused, making it a textbook example of output vulnerability.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Output Vulnerabilities

Amazon Bedrock Documentation – Guardrails for Responsible Generation

AWS documentation describes LLM-as-a-judge as an automated evaluation technique where a large language model is used to assess the outputs of another model based on qualitative criteria such as helpfulness, correctness, tone, and alignment with expectations. This approach enables scalable and repeatable evaluations without requiring human reviewers.

In this scenario, the company needs to compare two foundation models across subjective dimensions that are difficult to measure using traditional metrics. LLM-as-a-judge allows the evaluator model to score or rank responses using predefined evaluation prompts and criteria, ensuring consistent and automated assessment.

The other options do not meet the requirements. String matching and ROUGE focus on lexical similarity and are unsuitable for evaluating tone or helpfulness in customer service interactions. Retrieval Augmented Generation is an architectural pattern, not an evaluation technique.

AWS highlights LLM-as-a-judge as a practical approach for automated qualitative evaluation of generative AI outputs, making it the correct choice.

The correct answer is C – A CSV file that consists of measurement data, which is a classic example of structured data. According to AWS documentation, structured data is data that is organized in a predefined schema, typically stored in tabular formats with fixed rows, columns, and data types. CSV files, relational databases, and spreadsheets fall into this category because their structure allows deterministic querying and processing. Measurement data contained in a CSV file is easy to analyze with SQL, Amazon Athena, Amazon Redshift, or SageMaker Data Wrangler. In contrast, options A and D (text comments and transcriptions) are examples of unstructured data, requiring NLP techniques. Option B (video files) represents unstructured multimedia data, requiring computer vision. Structured data is essential for supervised ML models, business analytics, and statistical modeling. AWS emphasizes that structured data provides the simplest path to feature engineering and model training due to its consistent format.

Referenced AWS Documentation:

AWS Data Analytics Whitepaper – Structured vs. Unstructured Data

Amazon SageMaker Data Wrangler Documentation

The correct answer is A because each foundation model on Amazon Bedrock (e.g., Claude, Titan, Mistral, Meta Llama) has a different maximum token limit, which defines the maximum number of tokens the model can accept in the prompt and generate in the response.

From AWS documentation:

"Each model in Amazon Bedrock has its own maximum token limit. Prompts exceeding the limit must be truncated or adjusted depending on the selected model."

Explanation of other options:

B. On-demand inference support is a platform feature that is uniformly supported across models on Bedrock.

C. All Bedrock LLMs support randomness control through temperature and top-p parameters.

D. Amazon Bedrock Guardrails are designed to work across supported models, though specific behaviors may vary slightly.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Model Comparison Guide

AWS Prompt Engineering and LLM Deployment Documentation

AWS ML Specialty Study Guide – Bedrock Model Capabilities

The correct answer is B, because AWS recommends that any generative AI initiative begin with use-case clarification, stakeholder alignment, and measurable business objectives. According to the AWS Generative AI Adoption Framework and the AWS Machine Learning Journey guidelines, successful AI projects start with defining specific business outcomes—such as revenue growth, reduced time-to-market, or improved campaign efficiency. Conducting stakeholder interviews ensures the organization identifies the highest-value marketing use cases, such as personalized campaigns or content generation, and sets KPIs to measure revenue impact within the target timeframe. AWS documentation emphasizes avoiding premature model training (option A), which is costly and unnecessary without validated requirements. Implementing a prebuilt assistant (option C) may help operations but does not guarantee alignment with the core revenue objective. Replicating competitor features (option D) may lack strategic alignment. Therefore, refining use cases and measurable goals is the foundational AWS-recommended approach for a targeted revenue-driven generative AI initiative.

Referenced AWS Documentation:

AWS Generative AI Adoption Framework

AWS ML Business Value and Use-Case Identification Guidelines

 Block input prompts or model responses that contain harmful content such as hate, insults, violence, or misconduct:Content filters

 Avoid subjects related to illegal investment advice or legal advice:Denied topics

 Detect and block specific offensive terms:Word filters

 Detect and filter out information in the model’s responses that is not grounded in the provided source information:Contextual grounding check

The company is using a generative AI model on Amazon Bedrock and needs to mitigate undesirable and potentially harmful content in the model’s responses. Amazon Bedrock provides several guardrail mechanisms, including content filters, denied topics, word filters, and contextual grounding checks, to ensure safe and accurate outputs. Each mitigation action in the hotspot aligns with a specific Bedrock filter policy, and each policy must be used exactly once.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

*"Amazon Bedrock guardrails provide mechanisms to control model outputs, including:

Content filters: Block harmful content such as hate speech, violence, or misconduct.

Denied topics: Prevent the model from generating responses on specific subjects, such as illegal activities or advice.

Word filters: Detect and block specific offensive or inappropriate terms.

Contextual grounding check: Ensure responses are grounded in the provided source information, filtering out ungrounded or hallucinated content."*(Source: AWS Bedrock User Guide, Guardrails for Responsible AI)

Detailed Explanation:

Block input prompts or model responses that contain harmful content such as hate, insults, violence, or misconduct: Content filtersContent filters in Amazon Bedrock are designed to detect and block harmful content, such as hate speech, insults, violence, or misconduct, ensuring the model’s outputs are safe and appropriate. This matches the first mitigation action.

Avoid subjects related to illegal investment advice or legal advice: Denied topicsDenied topics allow users to specify subjects the model should avoid, such as illegal investment advice or legal advice, which could have regulatory implications. This policy aligns with the second mitigation action.

Detect and block specific offensive terms: Word filtersWord filters enable the detection and blocking of specific offensive or inappropriate terms defined by the user, making them ideal for this mitigation action focused on specific terms.

Detect and filter out information in the model’s responses that is not grounded in the provided source information: Contextual grounding checkThe contextual grounding check ensures that the model’s responses are based on the provided source information, filtering out ungrounded or hallucinated content. This matches the fourth mitigation action.

Hotspot Selection Analysis:

The hotspot lists four mitigation actions, each with the same dropdown options: "Select...," "Content filters," "Contextual grounding check," "Denied topics," and "Word filters." The correct selections are:

First action: Content filters

Second action: Denied topics

Third action: Word filters

Fourth action: Contextual grounding check

Each filter policy is used exactly once, as required, and aligns with Amazon Bedrock’s guardrail capabilities.

A multi-modal embedding model is the correct type of foundation model (FM) for powering a search application that handles queries containing both text and images.

Multi-Modal Embedding Model:

Can process and integrate different types of data (e.g., text and images) into a common representation space, enabling a unified search capability.

Suitable for applications where queries or content involve multiple data modalities.

Why Option A is Correct:

Handles Multiple Modalities: Supports both text and image data, aligning with the application's requirement.

Improves Search Relevance: Allows for more accurate and relevant search results across different types of input data.

Why Other Options are Incorrect:

B. Text embedding model: Only handles text data, not images.

C. Multi-modal generation model: Focuses on generating outputs rather than embedding for search tasks.

D. Image generation model: Only handles image data, not suitable for text queries.

The correct answer is B because explainable AI (XAI) provides transparency into how models reach specific decisions. According to AWS documentation, techniques such as SHAP values (SHapley Additive exPlanations) or LIME can identify which input features (e.g., income, debt ratio, or credit history) most influenced a model’s prediction. This helps financial institutions comply with fairness and transparency requirements under regulatory frameworks like the Equal Credit Opportunity Act. AWS SageMaker Clarify is a built-in service that offers explainability reports and bias detection to enhance trust. Rule-based systems and UIs alone do not satisfy transparency standards, and accuracy improvements do not replace explainability. By implementing explainable AI, customers can understand and trust credit limit decisions, reducing bias concerns and ensuring compliance.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker Clarify Documentation – Explainability and Feature Attribution

AWS Responsible AI Practices – Transparency and Accountability

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.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

BLEU is a widely used metric for evaluating machine translation by comparing machine-generated translations against reference (human) translations.

In this scenario:

Both systems are evaluated on the same dataset

The goal is to compare model output against human output

AWS ML evaluation guidance describes BLEU as suitable for relative comparison of translation quality across systems.

Why the other options are incorrect:

Absolute quality (A, C) is difficult to measure without human judgment.

BERTScore (D) is more computationally complex and less standard for operational comparisons.

AWS AI document references:

Evaluating Machine Translation Models

NLP Model Evaluation Metrics

Comparing AI and Human Translations

Amazon SageMaker Model Cards document model details, performance, intended use cases, and risk considerations. They support responsible AI by improving transparency and governance.

Rekognition is computer vision.

Comprehend is NLP for entity/sentiment.

Lex is conversational AI.

???? Reference:

AWS Documentation – SageMaker Model Cards

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

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Feature engineering focuses on:

Creating new features

Selecting the most relevant existing features

Improving model signal and accuracy

AWS ML best practices identify feature engineering as a key driver of predictive performance.

Why the other options are incorrect:

Visualization (A) helps understanding, not feature creation.

Hyperparameter tuning (B) optimizes models, not features.

Data collection (D) expands datasets but does not engineer features.

AWS AI document references:

Feature Engineering Best Practices

Improving Model Accuracy on AWS

ML Model Development Lifecycle

Creating an Amazon Bedrock knowledge base allows the integration of external or private data sources with a foundation model (FM) like Amazon Titan. This integration helps supplement the model with relevant data from the company's private data sources to enhance its responses.

Option C (Correct): "Create an Amazon Bedrock knowledge base": This is the correct answer as it enables the company to incorporate private data into the FM to improve its effectiveness.

Option A: "Use a different FM" is incorrect because it does not address the need to supplement the current model with private data.

Option B: "Choose a lower temperature value" is incorrect as it affects output randomness, not the integration of private data.

Option D: "Enable model invocation logging" is incorrect because logging does not help in supplementing the model with additional data.

AWS AI Practitioner References:

Amazon Bedrock and Knowledge Integration: AWS explains how creating a knowledge base allows Amazon Bedrock to use external data sources to improve the FM’s relevance and accuracy.

Amazon SageMaker Ground Truth is designed to support human evaluation and labeling workflows using both internal teams and external workforces. AWS documentation states that Ground Truth enables organizations to build high-quality labeled datasets and conduct human reviews using private workforces, vendor-managed workforces, or third-party providers.

In this scenario, the company needs to evaluate toxicity in foundation model outputs, which requires nuanced human judgment. AWS highlights that Ground Truth supports tasks such as content moderation, sentiment analysis, and safety evaluation, making it well suited for assessing harmful or toxic content generated by models.

Ground Truth provides managed tooling for task distribution, reviewer instructions, quality control, and auditability. It allows companies to seamlessly scale operations by combining internal reviewers for sensitive data with external reviewers for higher-volume workloads, while maintaining consistent review standards.

The other options do not meet the requirement. Amazon Bedrock Agents orchestrate interactions with foundation models but do not manage human review workflows. Amazon Comprehend Custom focuses on training NLP models, not evaluating FM outputs. Amazon SageMaker JumpStart provides pretrained models and solutions, not human evaluation pipelines.

AWS positions SageMaker Ground Truth as a core service for human-in-the-loop machine learning and responsible AI, making it the correct choice for toxicity evaluation using both internal and external reviewers.

Summarization is a natural language processing (NLP) task that condenses long documents into concise, meaningful summaries while retaining the key information.

Regression predicts numerical values.

Clustering groups similar items.

Classification assigns data into predefined categories.

???? Reference:

AWS NLP Use Cases – Summarization

To build an AI model responsibly and minimize bias, it is essential to ensure fairness and transparency throughout the model development and deployment process. This involves detecting and mitigating data imbalances and thoroughly evaluating the model's behavior to understand its impact on different groups.

Option A (Correct): "Detect imbalances or disparities in the data": This is correct because identifying and addressing data imbalances or disparities is a critical step in reducing bias. AWS provides tools like Amazon SageMaker Clarify to detect bias during data preprocessing and model training.

Option C (Correct): "Evaluate the model's behavior so that the company can provide transparency to stakeholders": This is correct because evaluating the model's behavior for fairness and accuracy is key to ensuring that stakeholders understand how the model makes decisions. Transparency is a crucial aspect of responsible AI.

Option B: "Ensure that the model runs frequently" is incorrect because the frequency of model runs does not address bias.

Option D: "Use the Recall-Oriented Understudy for Gisting Evaluation (ROUGE) technique to ensure that the model is 100% accurate" is incorrect because ROUGE is a metric for evaluating the quality of text summarization models, not for minimizing bias.

Option E: "Ensure that the model's inference time is within the accepted limits" is incorrect as it relates to performance, not bias reduction.

AWS AI Practitioner References:

Amazon SageMaker Clarify: AWS offers tools such as SageMaker Clarify for detecting bias in datasets and models, and for understanding model behavior to ensure fairness and transparency.

Responsible AI Practices: AWS promotes responsible AI by advocating for fairness, transparency, and inclusivity in model development and deployment.

Measuring the model's accuracy against a predefined benchmark dataset is the correct strategy to evaluate the accuracy of a foundation model (FM) used in image classification tasks.

Model Accuracy Evaluation:

In image classification, the accuracy of a model is typically evaluated by comparing the predicted labels with the true labels in a benchmark dataset that is representative of the real-world data the model will encounter.

This approach provides a quantifiable measure of how well the model performs on known data and is a standard practice in machine learning.

Why Option B is Correct:

Benchmarking Accuracy: Using a predefined dataset allows for consistent and reliable evaluation of model performance.

Standard Practice: It is a widely accepted method for assessing the effectiveness of image classification models.

Why Other Options are Incorrect:

A. Total cost of resources: Does not measure model accuracy but rather the cost of operation.

C. Number of layers in the neural network: Does not directly correlate with the accuracy or performance of the model.

D. Color accuracy of images processed by the model: Is unrelated to the model’s classification accuracy.

Fine-tuning involves training a pre-trained AI model on a labeled dataset specific to a particular task or domain, adapting it to industry terminology and requirements. This process adjusts the model’s parameters to better fit the target use case, such as understanding specialized vocabulary or meeting domain-specific needs.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"Fine-tuning allows you to adapt a pre-trained foundation model to your specific use case by training it on a labeled dataset. This technique is commonly used to customize models forindustry-specific terminology, improving their accuracy for specialized tasks."

(Source: AWS Bedrock User Guide, Model Customization)

Detailed Explanation:

Option A: Data augmentationData augmentation involves generating synthetic data to expand a training dataset, typically for tasks like image or text generation. It does not specifically adapt models to industry terminology or requirements.

Option B: Fine-tuningThis is the correct answer. Fine-tuning trains a pre-trained model on a labeled dataset tailored to the target domain, enabling it to learn industry-specific terminology and requirements, as described in the question.

Option C: Model quantizationModel quantization reduces the precision of a model’s weights to optimize it for deployment (e.g., on edge devices). It does not involve training on labeled datasets or adapting to industry terminology.

Option D: Continuous pre-trainingContinuous pre-training extends the initial training of a model on a large, general dataset. While it can improve general performance, it is not specifically tailored to industry requirements using labeled datasets, unlike fine-tuning.

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

Comprehensive and Detailed Explanation from AWS AI Documents:

Fine-tuning a foundation model means taking a pre-trained large model and continuing its training on domain-specific or task-specific data to specialize it for a particular use case. Fine-tuning does not retrain the FM from scratch (which would be costly and time-consuming). Instead, it improves model accuracy, relevance, and contextual adaptation for the intended application (e.g., legal, healthcare, customer support).

From AWS Docs:

“With Amazon Bedrock, you can fine-tune foundation models on your own data to specialize them for your unique use cases.”

“Fine-tuning a foundation model adapts it to a specific task by training on smaller sets of labeled data relevant to the problem domain.”

???? Reference:

AWS Documentation – Fine-tuning foundation models in Amazon Bedrock

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

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.

Using Amazon Bedrock with large language models (LLMs) allows for efficient utilization of AI to answer queries based on context provided in product manuals. To achieve this cost-effectively, the company should avoid unnecessary use of resources.

Option A (Correct): "Use prompt engineering to add one PDF file as context to the user prompt when the prompt is submitted to Amazon Bedrock": This is the most cost-effective solution. By using prompt engineering, only the relevant content from one PDF file is added as context to each query. This approach minimizes the amount of data processed, which helps in reducing costs associated with LLMs' computational requirements.

Option B: "Use prompt engineering to add all the PDF files as context to the user prompt when the prompt is submitted to Amazon Bedrock" is incorrect. Including all PDF files would increase costs significantly due to the large context size processed by the model.

Option C: "Use all the PDF documents to fine-tune a model with Amazon Bedrock" is incorrect. Fine-tuning a model is more expensive than using prompt engineering, especially if done for multiple documents.

Option D: "Upload PDF documents to an Amazon Bedrock knowledge base" is incorrect because Amazon Bedrock does not have a built-in knowledge base feature for directly managing and querying PDF documents.

AWS AI Practitioner References:

Prompt Engineering for Cost-Effective AI: AWS emphasizes the importance of using prompt engineering to minimize costs when interacting with LLMs. By carefully selecting relevant context, users can reduce the amount of data processed and save on expenses.

Unsupervised learning involves discovering hidden patterns without labeled data. Example: clustering.

Image recognition (B) is supervised learning.

House price prediction (C) is regression (supervised).

Reinforcement learning allows a model to learn and improve over time based on feedback from its environment. In this case, the chatbot can improve its responses by being rewarded for positive customer feedback, which aligns well with the goal of self-improvement based on past interactions and new information.

Option B (Correct): "Reinforcement learning with rewards for positive customer feedback": This is the correct answer as reinforcement learning enables the chatbot to learn from feedback and adapt its behavior accordingly, providing self-improvement capabilities.

Option A: "Supervised learning with a manually curated dataset" is incorrect because it does not support continuous learning from new interactions.

Option C: "Unsupervised learning to find clusters of similar customer inquiries" is incorrect because unsupervised learning does not provide a mechanism for improving responses based on feedback.

Option D: "Supervised learning with a continuously updated FAQ database" is incorrect because it still relies on manually curated data rather than self-improvement from feedback.

AWS AI Practitioner References:

Reinforcement Learning on AWS: AWS provides reinforcement learning frameworks that can be used to train models to improve their performance based on feedback.

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

Comprehensive and Detailed Explanation From Exact Extract:

In a RAG (Retrieval Augmented Generation) architecture, there are steps that can be optimized using offline batch processing, particularly for operations that do not require real-time updates:

A. Generation of content embeddings:When new content is published, it can be processed in batches to generate embeddings (vector representations) offline. These embeddings are then used at query time for similarity search. As new documents come in daily, batch processing is ideal for generating embeddings for all new content together.

“Content/document embeddings are typically generated offline, as this operation can be computationally expensive and does not need to happen in real-time.”

(Reference: AWS GenAI RAG Blog, Amazon Bedrock RAG Pattern)

C. Creation of the search index:After generating the content embeddings, these are indexed in a vector database or search service. This indexing is also typically performed in batch as part of the offline pipeline.

“Building or updating the vector index is often performed as a batch operation, reflecting the latest state of the content repository.”

(Reference: AWS RAG Pattern Whitepaper)

B, D, and E are real-time steps. Embeddings for user queries (B), retrieval of relevant content (D), and response generation (E) must be processed in real-time to provide an interactive experience.

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

Amazon Bedrock provides an option to enable invocation logging to capture and store the input and output data of the models used. This is essential for monitoring and auditing purposes, particularly when handling customer data.

Option B (Correct): "Enable invocation logging in Amazon Bedrock": This is the correct answer as it directly enables the logging of all model invocations, ensuring transparency and traceability.

Option A: "Configure AWS CloudTrail" is incorrect because CloudTrail logs API calls but does not provide specific logging for model inputs and outputs.

Option C: "Configure AWS Audit Manager" is incorrect as Audit Manager is used for compliance reporting, not specific invocation logging for AI models.

Option D: "Configure model invocation logging in Amazon EventBridge" is incorrect as EventBridge is for event-driven architectures, not specifically designed for logging AI model inputs and outputs.

AWS AI Practitioner References:

Amazon Bedrock Logging Capabilities: AWS emphasizes using built-in logging features in Bedrock to maintain data integrity and transparency in model operations.

The correct answer is D – F1 score, which is the harmonic mean of precision and recall. AWS documentation states that the F1 score is the preferred metric when evaluating ML models trained on imbalanced datasets, where one class appears significantly more often than others. Accuracy becomes misleading in these situations because a model can achieve high accuracy simply by predicting the majority class. Precision alone measures correctness of positive predictions, while recall measures completeness—neither fully captures class balancing performance. The F1 score provides a combined measurement that reflects how well the model identifies minority classes while avoiding excessive false positives. AWS’s ML Specialty Guide recommends using F1 for classification tasks where “class distribution is uneven or where both false negatives and false positives matter.” This metric provides a fairer assessment of overall model performance across all class categories.

Referenced AWS Documentation:

AWS Certified Machine Learning Specialty Guide – Metrics for Imbalanced Classes

Amazon SageMaker Developer Guide – Evaluating Classification Models

The correct answer is B – Data preprocessing, which involves cleaning, filtering, and transforming raw data before model training. AWS defines preprocessing as the step where irrelevant or poor-quality data (e.g., excessively short or misrecorded audio) is removed or normalized. The described task—filtering recordings by duration and language—is a textbook example of preprocessing since it prepares the dataset for downstream feature extraction. Feature engineering would occur afterward when converting audio signals into numerical representations (like Mel-frequency coefficients). Model training and data collection come after and before preprocessing respectively. Proper preprocessing ensures data consistency, reduces noise, and improves model accuracy, especially in audio-based healthcare models where clarity and consistency are critical.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Data Preprocessing and Cleaning

Amazon SageMaker Data Wrangler Documentation – Data Preparation Best Practices

To securely use large language models (LLMs) on Amazon Bedrock, companies should design clear and specific prompts to avoid unintended outputs and ensure proper configuration of AWS Identity and Access Management (IAM) roles and policies with the principle of least privilege. This approach limits access to sensitive resources and minimizes the potential impact of security incidents.

Option A (Correct): "Design clear and specific prompts. Configure AWS Identity and Access Management (IAM) roles and policies by using least privilege access": This is the correct answer as it directly addresses both security practices in prompt design and access management.

Option B: "Enable AWS Audit Manager for automatic model evaluation jobs" is incorrect because Audit Manager is for compliance and auditing, not directly related to secure LLM usage.

Option C: "Enable Amazon Bedrock automatic model evaluation jobs" is incorrect because Bedrock does not provide automatic model evaluation jobs specifically for security purposes.

Option D: "Use Amazon CloudWatch Logs to make models explainable and to monitor for bias" is incorrect because CloudWatch Logs are used for monitoring and not directly for making models explainable or secure.

AWS AI Practitioner References:

Secure AI Practices on AWS: AWS recommends configuring IAM roles and using least privilege access to ensure secure usage of AI models.

Comprehensive and Detailed Explanation From Exact Extract:

The best practice for mitigating bias in AI/ML models, according to AWS and responsible AI frameworks, is to ensure that the training data is representative and diverse. If a model demonstrates bias (such as favoring a particular demographic), the recommended, cost-effective approach is to collect additional data from underrepresented groups and retrain (fine-tune) the model with the improved dataset.

A. Include more diverse training data. Fine-tune the model again by using the new data:

“The most effective method to reduce model bias is to curate and include diverse, representative training data, then retrain or fine-tune the model.”

(Reference: AWS Responsible AI, SageMaker Clarify Bias Mitigation)

B (RAG) is unrelated to model fairness or bias mitigation; it’s for grounding LLMs with external knowledge.

C (AWS Trusted Advisor) is for AWS resource optimization/security—not for ML model bias detection or mitigation.

D (Pre-train a new LLM) would be extremely costly and is unnecessary; fine-tuning with better data is much more efficient.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

When a foundation model is customized directly in Amazon Bedrock, the correct way to use the customized model for inference is to purchase Provisioned Throughput.

Provisioned Throughput:

Enables consistent performance and predictable latency

Allows production use of customized Bedrock models

Is the required deployment mechanism for custom FMs in Bedrock

Why the other options are incorrect:

SageMaker endpoints (B) are not used for Bedrock-native custom models.

Model Registry (C) applies to SageMaker models.

Approval status (D) does not deploy or enable usage.

AWS AI document references:

Amazon Bedrock Custom Model Deployment

Provisioned Throughput for Foundation Models

Using Customized Models in Amazon Bedrock

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Prompt engineering is the primary method for controlling tone, style, and behavior of foundation model responses.

AWS generative AI guidance explains that:

Prompts can define tone, voice, and response structure

Iterative refinement ensures consistent outputs

Prompt refinement requires no model retraining

Why the other options are incorrect:

Token limits (A) affect length, not tone.

Batch inferencing (B) affects processing mode, not response style.

Higher temperature (D) increases randomness, reducing consistency.

AWS AI document references:

Prompt Engineering Best Practices

Controlling Model Output Tone

Using Prompts with Foundation Models on AWS

The correct answer is B because Amazon CloudWatch provides monitoring capabilities that include tracking usage metrics for Amazon Comprehend endpoints, such as invocation counts. You can configure CloudWatch to collect these metrics and create custom dashboards or alarms to report when an endpoint has zero usage over a period (e.g., 15 days).

From AWS documentation:

"Amazon CloudWatch enables you to collect and track metrics for Comprehend endpoints, create alarms, and automatically react to changes in your AWS resources."

This allows automated reporting and alerting for underused or idle endpoints.

Explanation of other options:

A. AWS Trusted Advisor focuses on general AWS resource optimization, security, and limits but does not track endpoint usage.

C. AWS CloudTrail tracks API calls but does not provide time-based monitoring or usage analysis over time.

D. AWS Config is used to track configuration changes and compliance, not endpoint usage metrics.

Referenced AWS AI/ML Documents and Study Guides:

Amazon CloudWatch Metrics for Amazon Comprehend

AWS Certified Machine Learning Specialty Guide – Monitoring and Logging Section

AWS Cloud Operations Guide – Resource Utilization Monitoring

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

Transitioning to a new large language model (LLM) on Amazon Bedrock typically involves minimal changes when the new model is pre-trained and available as a foundation model. Since the company is moving from one pre-trained LLM to another, the primary task is to ensure compatibility between the new model's input requirements and the existing application. Adjusting the prompt template is often necessary because different LLMs may have varying prompt formats, tokenization methods, or response behaviors, even for similar tasks like document extraction.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"When switching between foundation models in Amazon Bedrock, you may need to adjust the prompt template to align with the new model’s expected input format and optimize its performance for your use case. Prompt engineering is critical to ensure the model understands the task and generates accurate outputs."

(Source: AWS Bedrock User Guide, Prompt Engineering for Foundation Models)

Detailed Explanation:

Option A: Create a new labeled dataset.Creating a new labeled dataset is unnecessary when transitioning to a new pre-trained LLM, as pre-trained models are already trained on large datasets. This option would only be relevant if the company were training a custom model from scratch, which is not the case here.

Option B: Perform feature engineering.Feature engineering is typically associated with traditional machine learning models, not pre-trained LLMs. LLMs process raw text inputs, and transitioning to a new LLM does not require restructuring input features. This option is incorrect.

Option C: Adjust the prompt template.This is the correct approach. Different LLMs may interpret prompts differently due to variations in training data, tokenization, or model architecture. Adjusting the prompt template ensures the new LLM understands the task (e.g., document extraction) and produces the desired output format. AWS documentation emphasizes prompt engineering as a key step when adopting a new foundation model.

Option D: Fine-tune the LLM.Fine-tuning is not required for transitioning to a new pre-trained LLM unless the company needs to customize the model for a highly specific task. Since the question does not indicate a need for customization beyond document extraction (a common LLM capability), fine-tuning is unnecessary.

In generative AI models, such as those built on Amazon Bedrock, inference costs are driven by the number of tokens processed. A token can be as short as one character or as long as one word, and the more tokens consumed during the inference process, the higher the cost.

Option A (Correct): "Number of tokens consumed": This is the correct answer because the inference cost is directly related to the number of tokens processed by the model.

Option B: "Temperature value" is incorrect as it affects the randomness of the model's output but not the cost directly.

Option C: "Amount of data used to train the LLM" is incorrect because training data size affects training costs, not inference costs.

Option D: "Total training time" is incorrect because it relates to the cost of training the model, not the cost of inference.

AWS AI Practitioner References:

Understanding Inference Costs on AWS: AWS documentation highlights that inference costs for generative models are largely based on the number of tokens processed.

The correct answer is A – Explainability. According to AWS Responsible AI documentation, explainability refers to an AI system’s ability to clearly communicate why it produced a given result. In healthcare, clinical decision support systems must provide traceable, understandable reasoning, especially when generating treatment recommendations. AWS highlights explainability as critical for high-impact domains such as medicine because doctors and patients must trust and understand the basis for AI-driven decisions. Tools like Amazon SageMaker Clarify support feature attribution, helping clinicians understand which patient factors (e.g., age, symptoms, lab values) influenced a recommendation. Privacy and security (B) protect data but do not provide rationale. Fairness (C) ensures equitable treatment across demographics but does not explain decisions. Data governance (D) focuses on handling and controlling data, not model decision transparency. Explainability is the AWS principle that ensures clinical users can interpret, validate, and rely on AI-generated recommendations for patient care.

Referenced AWS Documentation:

AWS Responsible AI Whitepaper – Explainability

Amazon SageMaker Clarify – Feature Attribution and Model Insights

Generative AI is a type of AI that creates new content, such as text, images, or audio, often mimicking human-like outputs. A practical use case for generative AI is employing a chatbot to provide human-like responses to customer queries in real time, as it leverages the ability of large language models (LLMs) to generate natural language responses dynamically.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"Generative AI enables applications like chatbots to produce human-like text responses in real time, enhancing customer support by providing natural and contextually relevant answers to user queries."

(Source: AWS Bedrock User Guide, Introduction to Generative AI)

Detailed Explanation:

Option A: Using an ML model to forecast product demandForecasting product demand typically involves predictive analytics using supervised learning (e.g., regression models), not generative AI, which focuses on creating new content.

Option B: Employing a chatbot to provide human-like responses to customer queries in real timeThis is the correct answer. Generative AI, particularly LLMs, is commonly used to power chatbots that generate human-like responses, making this a practical use case.

Option C: Using an analytics dashboard to track website traffic and user behaviorAn analytics dashboard involves data visualization and analysis, not generative AI, which is about creating new content.

Option D: Implementing a rule-based recommendation engine to suggest products to customersA rule-based recommendation engine relies on predefined rules, not generative AI. Generative AI could be used for more dynamic recommendations, but this scenario does not describe such a case.

Sentiment analysis is the task of determining the emotional tone or intent behind a body of text (positive, negative, neutral).

This falls under Natural Language Processing (NLP) because it deals with understanding and processing human language.

Computer vision relates to images, robotics to autonomous machines, and time series forecasting to predicting values from sequential data.

???? Reference:

AWS ML Glossary – NLP

The retail company wants to build an ML model for product recommendations using responsible practices to decrease model bias. Collecting balanced and diverse data ensures the model does not favor specific groups, reducing bias and promoting fairness, a key responsible AI practice.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"To reduce model bias, it is critical to collect balanced and diverse data that represents various demographics and user groups. This practice ensures fairness and prevents the model from disproportionately favoring certain populations."

(Source: AWS AI Practitioner Learning Path, Module on Responsible AI)

Detailed Explanation:

Option A: Use data from only customers who match the demography of the company's overall customer base.Limiting data to a specific demographic may reinforce existing biases, failing to address underrepresented groups and increasing bias.

Option B: Collect data from customers who have a past purchase history.Focusing only on customers with purchase history may exclude new users, potentially introducing bias, and does not address diversity.

Option C: Ensure that the data is balanced and collected from a diverse group.This is the correct answer. A balanced and diverse dataset reduces bias by ensuring the model learns from a representative sample, aligning with responsible AI practices.

Option D: Ensure that the data is from a publicly available dataset.Public datasets may not be diverse or representative of the company’s customer base and could introduce unrelated biases, failing to address fairness.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

AWS PrivateLink enables private connectivity between AWS services through VPC endpoints, ensuring traffic does not traverse the public internet.

AWS guidance recommends PrivateLink for:

Secure, private service access

Regulatory and compliance requirements

VPC-based architecture

Why the other options are incorrect:

IAM (A) controls access, not network routing.

Macie (B) is a data security service.

VPC peering (D) is not required for Bedrock access.

AWS AI document references:

Amazon Bedrock Networking and Security

Private Connectivity with AWS PrivateLink

Secure AI Architectures on AWS

To manage the flow of data from Amazon S3 to SageMaker Studio notebooks securely, using a VPC with an S3 endpoint is the best solution.

Amazon SageMaker and S3 Integration:

Configuring SageMaker to use a Virtual Private Cloud (VPC) with an S3 endpoint allows the data flow between Amazon S3 and SageMaker Studio notebooks to occur over a private network.

This setup ensures that traffic between SageMaker and S3 does not traverse the public internet, enhancing security and performance.

Why Option C is Correct:

Secure Data Transfer: Ensures secure, private connectivity between SageMaker and S3, reducing exposure to potential security risks.

Direct Access to S3: Using an S3 endpoint in a VPC allows direct access to data in S3 without leaving the AWS network.

Why Other Options are Incorrect:

A. Amazon Inspector: Focuses on identifying security vulnerabilities, not managing data flow.

B. Amazon Macie: Monitors for sensitive data but does not manage data flow between S3 and SageMaker.

D. S3 Glacier Deep Archive: Is a storage class for archiving data, not for managing active data flow.

Comprehensive and Detailed Explanation (AWS AI documents):

AWS recommends Amazon SageMaker Feature Store as a centralized, managed repository for storing, discovering, and reusing features and datasets across teams and projects. Feature Store enables:

Feature discovery through searchable metadata

Reusability of curated datasets and features by future practitioners

Consistency between training and inference datasets

Governance and lineage, supporting responsible AI practices

Why the other options are incorrect:

A is intended for retrieval-augmented generation, not dataset sharing.

B does not provide discoverability, governance, or long-term reuse.

D is designed for sharing data with external subscribers, not internal ML teams.

AWS AI Study Guide References:

Amazon SageMaker Feature Store overview

AWS best practices for feature management and reuse

Building a well-architected ML workload follows a structured lifecycle as outlined in AWS best practices. The process begins with defining the business goal and framing the ML problem to ensure the project aligns with organizational objectives. Next, the model is developed, which includes data preparation, training, and evaluation. Once the model is ready, it is deployed tomake predictions in a production environment. Finally, the model is monitored to ensure it performs as expected and to address any issues like drift or degradation over time. This order ensures a systematic approach to ML development.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"The machine learning lifecycle typically follows these stages: 1) Define the business goal and frame the ML problem, 2) Develop the model (including data preparation, training, and evaluation), 3) Deploy the model to production, and 4) Monitor the model for performance and drift to ensure it continues to meet business needs."

(Source: AWS AI Practitioner Learning Path, Module on Machine Learning Lifecycle)

Detailed Explanation:

Step 1: Define business goal and frame ML problemThis is the first step in any ML project. It involves understanding the business objective (e.g., reducing churn) and framing the ML problem (e.g., classification or regression). Without this step, the project lacks direction. The hotspot lists this option as "Define business goal and frame ML problem," which matches this stage.

Step 2: Develop modelAfter defining the problem, the next step is to develop the model. This includes collecting and preparing data, selecting an algorithm, training the model, and evaluating its performance. The hotspot lists "Develop model" as an option, aligning with this stage.

Step 3: Deploy modelOnce the model is developed and meets performance requirements, it is deployed to a production environment to make predictions or automate decisions. The hotspot includes "Deploy model" as an option, which fits this stage.

Step 4: Monitor modelAfter deployment, the model must be monitored to ensure it performs well over time, addressing issues like data drift or performance degradation. The hotspot lists "Monitor model" as an option, completing the lifecycle.

Hotspot Selection Analysis:

The hotspot provides four steps, each with the same dropdown options: "Select...," "Deploy model," "Develop model," "Monitor model," and "Define business goal and frame ML problem." The correct selections are:

Step 1: Define business goal and frame ML problem

Step 2: Develop model

Step 3: Deploy model

Step 4: Monitor model

Each option is used exactly once, as required, and follows the logical order of the ML lifecycle.

Comprehensive and Detailed Explanation from AWS AI Documents:

Amazon Bedrock ensures data privacy and security by not sharing customer inputs or outputs with third-party model providers.

The models are accessed via Bedrock’s API isolation layer, meaning that model providers do not see your data.

Customer data is not used for training or improving foundation models unless customers explicitly opt in.

From AWS Docs:

“Amazon Bedrock does not share your inputs and outputs with third-party model providers. Your data remains private, and is not used to improve the foundation models.”

This ensures full data privacy, especially for sensitive use cases like confidential documents.

???? Reference:

AWS Documentation – Data privacy in Amazon Bedrock

The correct answer is D because Amazon Bedrock provides access to foundation models (FMs) from various providers for generative AI use cases, including text generation. It supports generating content in a consistent tone, voice, or writing style using prompts or few-shot examples.

From AWS documentation:

"Amazon Bedrock allows you to build and scale generative AI applications using foundation models from AI21 Labs, Anthropic, Cohere, Meta, Mistral, Stability AI, and Amazon. These models can generate text with controlled tone and style for applications like branding, content creation, and copywriting."

Explanation of other options:

A. Amazon Comprehend is for natural language understanding, such as sentiment analysis and entity recognition, not generation.

B. Amazon Personalize is for building recommendation systems, not content generation.

C. Amazon Rekognition is for image and video analysis, not text generation.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Generative AI Use Cases

AWS Certified Machine Learning Specialty Guide – Content Generation with FMs

Step 1: Store meeting audio recordings in an Amazon S3 bucket.

Step 2: Convert meeting audio recordings to meeting text files by using Amazon Transcribe.

Step 3: Summarize meeting text files by using Amazon Bedrock.

The company wants to create an application to summarize meeting audio recordings, which requires a sequence of steps involving storage, speech-to-text conversion, and text summarization. Amazon S3 is the recommended storage service for audio files, Amazon Transcribe converts audio to text, and Amazon Bedrock provides generative AI capabilities for summarization. These three steps, in this order, create an efficient workflow for the application.

Exact Extract from AWS AI Documents:

From the Amazon Transcribe Developer Guide:

"Amazon Transcribe uses deep learning to convert audio files into text, supporting applications such as meeting transcription. Audio files can be stored in Amazon S3, and Transcribe can process them directly from an S3 bucket."

From the AWS Bedrock User Guide:

"Amazon Bedrock provides foundation models that can perform text summarization, enabling developers to build applications that generate concise summaries from text data, such as meeting transcripts."

(Source: Amazon Transcribe Developer Guide, Introduction to Amazon Transcribe; AWS Bedrock User Guide, Text Generation and Summarization)

Detailed Explanation:

Step 1: Store meeting audio recordings in an Amazon S3 bucket.Amazon S3 is the standard storage service for audio files in AWS workflows, especially for integration with services like Amazon Transcribe. Storing the recordings in S3 allows Transcribe to access and process them efficiently. This is the first logical step.

Step 2: Convert meeting audio recordings to meeting text files by using Amazon Transcribe.Amazon Transcribe is designed for automatic speech recognition (ASR), converting audio files (stored in S3) into text. This step is necessary to transform the meeting recordings into a format that can be summarized.

Step 3: Summarize meeting text files by using Amazon Bedrock.Amazon Bedrock provides foundation models capable of generative AI tasks like text summarization. Once the audio is converted to text, Bedrock can summarize the meeting transcripts, completing the application’s requirements.

Unused Options Analysis:

Convert meeting audio recordings to meeting text files by using Amazon Polly.Amazon Polly is a text-to-speech service, not for converting audio to text. This option is incorrect and not used.

Store meeting audio recordings in an Amazon Elastic Block Store (Amazon EBS) volume.Amazon EBS is for block storage, typically used for compute instances, not for storing files for processing by services like Transcribe. S3 is the better choice, so this option is not used.

Summarize meeting text files by using Amazon Lex.Amazon Lex is for building conversational interfaces (chatbots), not for text summarization. Bedrock is the appropriate service for summarization, so this option is not used.

Hotspot Selection Analysis:

The task requires selecting and ordering three steps from the list, with each step used exactly once or not at all. The selected steps—storing in S3, converting with Transcribe, and summarizing with Bedrock—form a complete and logical workflow for the application.

The correct answer is A, as the most effective way to ensure fairness in AI systems is to audit and diversify training data. AWS Responsible AI documentation stresses that bias originates primarily from unbalanced or incomplete datasets. By including samples from all demographic groups, the model learns patterns that generalize fairly across populations. AWS SageMaker Clarify supports data bias detection and offers fairness metrics like demographic parity and equal opportunity difference. Deeper models (option B) or secrecy (option C) do not mitigate bias and may worsen transparency. Static test datasets (option D) fail to capture evolving data distributions. Therefore, ongoing bias reviews and diverse datasets form the foundation of responsible generative AI for financial use cases.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation – Bias Detection

The company is building a chatbot using an LLM on Amazon Bedrock, and the chatbot needs to use content from previous customer messages to resolve requests. Adding previous messages to the model prompt (also known as providing conversation history) enables the LLM to maintain context across interactions, allowing it to respond coherently based on the ongoing conversation.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"To enable a large language model (LLM) to maintain context in a conversation, you can include previous messages in the model prompt. This approach, often referred to as providing conversation history, allows the LLM to generate responses that are contextually relevant toprior interactions."

(Source: AWS Bedrock User Guide, Building Conversational Applications)

Detailed Explanation:

Option A: Turn on model invocation logging to collect messages.Model invocation logging records interactions for auditing or debugging but does not provide the LLM with access to previous messages during inference to maintain conversation context.

Option B: Add messages to the model prompt.This is the correct answer. Including previous messages in the prompt gives the LLM the conversation history it needs to respond appropriately, a common practice for chatbots on Amazon Bedrock.

Option C: Use Amazon Personalize to save conversation history.Amazon Personalize is for building recommendation systems, not for managing conversation history in a chatbot. This option is irrelevant.

Option D: Use Provisioned Throughput for the LLM.Provisioned Throughput in Amazon Bedrock ensures consistent performance for model inference but does not address the need to use previous messages in the conversation.

AWS KMS provides customer-managed encryption keys (CMKs) that can be used to encrypt model artifacts and other sensitive data at rest.

Bedrock integrates with AWS KMS to allow encryption of customized models with your own keys.

Amazon Inspector is for vulnerability scanning, Amazon Macie for sensitive data discovery, AWS Secrets Manager for storing credentials and secrets.

???? Reference:

AWS Documentation – Using KMS with Amazon Bedrock

To use a custom model that has been trained to improve summarization quality, the company must deploy the model on an Amazon SageMaker endpoint. This allows the model to be used for real-time inference through Amazon Bedrock or other AWS services. By deploying the model in SageMaker, the custom model can be accessed programmatically via API calls, enabling integration with Amazon Bedrock.

Option B (Correct): "Deploy the custom model in an Amazon SageMaker endpoint for real-time inference": This is the correct answer because deploying the model on SageMaker enables it to serve real-time predictions and be integrated with Amazon Bedrock.

Option A: "Purchase Provisioned Throughput for the custom model" is incorrect because provisioned throughput is related to database or storage services, not model deployment.

Option C: "Register the model with the Amazon SageMaker Model Registry" is incorrect because while the model registry helps with model management, it does not make the model accessible for real-time inference.

Option D: "Grant access to the custom model in Amazon Bedrock" is incorrect because Bedrock does not directly manage custom model access; it relies on deployed endpoints like those in SageMaker.

AWS AI Practitioner References:

Amazon SageMaker Endpoints: AWS recommends deploying models to SageMaker endpoints to use them for real-time inference in various applications.

The business objective to evaluate the effect of an LLM chatbot aimed at reducing the actions required by call center employees should be average call duration.

Average Call Duration:

This metric measures the time taken to handle a customer call or query. A successful LLM chatbot should reduce the call duration by efficiently providing answers, minimizing the need for human intervention.

By decreasing the average call duration, the company can improve call center efficiency, reduce costs, and enhance the user experience.

Why Option B is Correct:

Direct Impact: The objective aligns directly with the goal of reducing the number of actions call center employees must take.

Operational Efficiency: Reducing call duration is a clear indicator of the chatbot's effectiveness in assisting customers without human help.

Why Other Options are Incorrect:

A. Website engagement rate: Is unrelated to call center operations.

C. Corporate social responsibility: Does not relate to call center efficiency.

D. Regulatory compliance: Is important but does not measure the effectiveness of a chatbot in reducing employee actions.

Amazon QuickSight is a fully managed business intelligence (BI) service that allows users to create and publish interactive dashboards that include visualizations like graphs, charts, and tables. "Amazon Q" is the natural language query feature within Amazon QuickSight. It enables users to ask questions about their data in natural language and receive visual responses such as graphs.

Option C (Correct): "Amazon Q in Amazon QuickSight": This is the correct answer because Amazon QuickSight Q is specifically designed to allow users to explore their data through natural language queries, and it can automatically generate graphs to display sales data and other metrics. This makes it an ideal choice for the company to automate the generation of graphs showing total sales for its top-selling products across various retail locations.

Option A, B, and D: These options are incorrect:

A. Amazon Q in Amazon EC2: Amazon EC2 is a compute service that provides virtual servers, but it is not directly related to generating graphs or providing natural language querying features.

B. Amazon Q Developer: This is not an existing AWS service or feature.

D. Amazon Q in AWS Chatbot: AWS Chatbot is a service that integrates with Amazon Chime and Slack for monitoring and managing AWS resources, but it is not used for generating graphs based on sales data.

AWS AI Practitioner References:

Amazon QuickSight Q is designed to provide insights from data by using natural language queries, making it a powerful tool for generating automated graphs and visualizations directly from queried data.

Business Intelligence (BI) on AWS: AWS services such as Amazon QuickSight provide business intelligence capabilities, including automated reporting and visualization features, which are ideal for companies seeking to visualize data like sales trends over time.

Precision is the metric that measures the proportion of true positives (actual frauds) among all flagged positives (flagged frauds). High precision ensures that most of the flagged cases are truly fraudulent, minimizing the number of false positives employees must review.

C is correct:

"Precision is the ratio of true positives to all predicted positives, and it answers: ‘Of all the cases flagged as fraud, how many were actually fraud?’ High precision means fewer non-fraudulent cases are sent for manual review."

(Reference: AWS ML Concepts – Precision and Recall, AWS Certified AI Practitioner Study Guide)

A (Recall) measures how many actual frauds are caught, but does not minimize false positives.

B (Accuracy) can be misleading in imbalanced datasets (like fraud detection).

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI principles stress the importance of fairness, robustness, and accountability, which begin with the quality of the data used to train models. A responsible dataset should:

Be diverse, representing different populations, environments, and conditions to reduce bias

Be sourced from reputable and appropriate sources, ensuring data quality and ethical use

Have balanced categories, preventing the model from favoring one class over others and reducing the risk of discriminatory outcomes

These characteristics help ensure that the resulting image classification model behaves fairly, performs reliably across groups, and aligns with AWS Responsible AI best practices.

Why the other options are incorrect:

B focuses on dataset size rather than quality, balance, or representativeness.

C increases the risk of bias and poor generalization.

D limits diversity and does not inherently ensure fairness or accountability.

AWS AI Study Guide References:

AWS Responsible AI principles: fairness and data quality

AWS guidance on dataset selection and preparation for responsible ML

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Clarify provides tools for:

Model explainability

Bias detection

Transparency through metrics, reports, and explanations

For regulated industries such as healthcare, AWS recommends Clarify to:

Explain model predictions

Demonstrate fairness and accountability

Support regulatory and ethical requirements

Why the other options are incorrect:

Inspector (A) focuses on security vulnerabilities.

Macie (C) focuses on data security and privacy.

Rekognition (D) is for image labeling, not explainability.

AWS AI document references:

Amazon SageMaker Clarify Documentation

Responsible AI on AWS

Explainable AI for Regulated Industries

The correct answer is C – Test the AI solution to ensure that it does not discriminate against any protected groups. According to AWS Responsible AI principles, fairness and bias mitigation are essential when AI is used for high-impact decisions such as hiring. AWS documentation emphasizes evaluating datasets, model outputs, and demographic performance to ensure that AI systems do not reinforce or reproduce discriminatory patterns. Services such as Amazon SageMaker Clarify support automated bias detection and explainability, helping teams identify and mitigate unwanted correlations in training data or model predictions. Option A violates AWS guidance, as human-in-the-loop review is required for sensitive decisions. Option B risks amplifying historical bias because training on only “successful” hires can create feedback loops. Option D contradicts transparency principles, which AWS states are crucial for accountability in regulated or ethical decision-making domains. Therefore, rigorous fairness testing aligns with AWS’s recommended practices for responsible AI in hiring workflows.

Referenced AWS Documentation:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation

With Amazon Bedrock, AWS handles infrastructure security and patching (shared responsibility model).

Customers are responsible for securing their data (encryption, IAM, policies) both in transit and at rest.

Provisioning infrastructure (D) and platform patching (A, B) are AWS responsibilities.

???? Reference:

AWS Shared Responsibility Model

SageMaker Clarify provides model explainability, bias detection, and helps visualize how input features affect predictions.

Canvas is for low-code ML building.

Feature Store is for storing and managing ML features.

Ground Truth is for data labeling.

???? Reference:

AWS Documentation – Amazon SageMaker Clarify

Inference is the correct answer because it is the AI process that occurs when a deployed model analyzes new data (such as an image) to make predictions or identify objects.

Inference:

In the context of machine learning, inference is the process of using a trained model to make predictions on new, unseen data.

When the deep learning model is deployed to production and receives a new image for analysis, it uses the learned patterns from the training phase to identify objects in the image. This is known as inference.

Why Option B is Correct:

Inference Process: Involves applying the trained model to real-world data (the new image) to identify objects.

Deployment Context: The model has already been trained, and the deployment to production indicates it is being used for inference.

Why Other Options are Incorrect:

A. Training: Refers to the process of teaching the model using historical data, not making predictions on new data.

C. Model deployment: Refers to the process of making a trained model available for use in production.

D. Bias correction: Is a process to adjust a model to minimize bias, not for analyzing new images.

Directional stimulus prompting guides the foundation model to produce outputs aligned with business context. It’s particularly effective for aligning responses with public documents and improving coherence. From Bedrock Prompt Engineering Techniques documentation:

“Directional stimulus prompting provides structured prompts to steer the model output towards desired formats or behaviors using specific linguistic cues.”

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI and generative AI evaluation guidance emphasizes that assessing the quality and behavior of a foundation model requires representative and diverse evaluation datasets. These datasets should reflect real-world usage patterns, edge cases, and multiple business scenarios to properly evaluate how the model behaves in production.

Using diverse datasets that cover various use cases and usage scenarios allows organizations to:

Evaluate robustness and generalization of the FM

Identify failure modes, bias, and unsafe behavior across different inputs

Validate that the model performs consistently across business workflows

Why the other options are incorrect:

A may remove meaningful real-world patterns and does not reflect realistic usage.

B risks reinforcing model biases and does not provide independent evaluation.

D does not reflect real or meaningful business scenarios and can distort evaluation results.

AWS AI Study Guide References:

AWS Responsible AI evaluation practices

AWS guidance on foundation model testing and validation

Anomaly detection identifies unusual behavior (such as suspicious IP traffic) compared to normal baselines.

Speech recognition (A) is irrelevant.

NER in NLP (B) extracts entities from text, not detect malicious IPs.

Fraud forecasting (D) predicts fraudulent transactions but not directly suspicious IP activity.

???? Reference:

AWS Documentation – Anomaly Detection

AWS CloudTrail: Logs all API calls to Amazon Bedrock.

Amazon S3 Intelligent-Tiering: Optimizes storage costs for long-term retention with automatic tiering.

According to Amazon Bedrock Logging Documentation:

“CloudTrail records API activity and events, and logs can be stored in S3. For cost optimization, use S3 Intelligent-Tiering to retain logs long-term.”

The correct answer is C – Re-train the model with fresh data. AWS SageMaker Model Monitor is designed to detect data drift, feature drift, and model quality degradation in real-time. When drift exceeds a set threshold, AWS recommends initiating a retraining workflow with updated data to restore model accuracy. According to AWS documentation, data drift indicates that the distribution of incoming data has changed significantly from the original training dataset—often due to new user behaviors, market changes, or seasonal patterns. Restarting the endpoint (A) does not address degraded model performance. Adjusting sensitivity (B) suppresses the alert but does not fix the underlying issue. Experiments tracking (D) is helpful for monitoring model versions but is not corrective. Retraining ensures the model adapts to new data patterns and continues to perform reliably, which is the AWS-endorsed response to drift detection alerts.

Referenced AWS Documentation:

Amazon SageMaker Model Monitor – Detecting Drift

AWS ML Ops Best Practices – Continuous Retraining

The requirement is to identify an AWS database service that supports the storage and querying of embeddings (from a generative AI model) as vectors. Embeddings are typically high-dimensional numerical representations of data (e.g., text, images) used in AI applications like conversational search. The database must support vector storage and efficient vector similarity searches. Let’s evaluate each option:

A. Amazon Athena: Amazon Athena is a serverless query service for analyzing data in Amazon S3 using SQL. It is designed for ad-hoc querying of structured data but does not natively support vector storage or vector similarity searches, making it unsuitable for this use case.

B. Amazon Aurora PostgreSQL: Amazon Aurora PostgreSQL is a fully managed relational database compatible with PostgreSQL. With the pgvector extension (available in PostgreSQL and supported by Aurora PostgreSQL), it can store and query vector embeddings efficiently. The pgvector extension enables vector similarity searches (e.g., using cosine similarity or Euclidean distance), which is critical for conversational search applications using embeddings from generative AI models.

C. Amazon Redshift: Amazon Redshift is a data warehousing service optimized for analytical queries on large datasets. While it supports machine learning features and can store numerical data, it does not have native support for vector embeddings or vector similarity searches as of May 17, 2025, making it less suitable for this use case.

D. Amazon EMR: Amazon EMR is a managed big data platform for processing large-scale data using frameworks like Apache Hadoop and Spark. It is not a database service and is not designed for storing or querying vector embeddings in the context of a conversational search application.

Exact Extract Reference: According to the AWS documentation, “Amazon Aurora PostgreSQL-Compatible Edition supports the pgvector extension, which enables efficient storage and similarity searches for vector embeddings. This makes it suitable for AI/ML workloads such as natural language processing and recommendation systems that rely on vector data.” (Source: AWS Aurora Documentation - Using pgvector with Aurora PostgreSQL, Additionally, the pgvector extension supports operations like nearest-neighbor searches, which are essential for querying embeddings in a conversational search system.

Amazon Aurora PostgreSQL with the pgvector extension directly meets the requirement for storing and querying embeddings as vectors, making B the correct answer.

The correct answer is D because autoencoders are an unsupervised machine learning method commonly used for anomaly detection when labeled data is not available.

From AWS documentation:

"Autoencoders learn to compress and reconstruct input data. During anomaly detection, they learn normal patterns in data. Data points that the model cannot accurately reconstruct are flagged as anomalies."

This approach is ideal when there is no labeled data and when patterns must be learned based on normal behavior alone — a common situation in IoT sensor data environments.

Explanation of other options:

A. Linear regression requires labeled data and is used for predicting continuous values.

B. Classification requires labeled data to assign inputs into categories.

C. Decision trees are supervised learning models and also require labeled datasets.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Unsupervised Learning Techniques

Amazon SageMaker Examples – Anomaly Detection Using Autoencoders

Generative AI models are used to create new content based on existing data. One common use case is generating photorealistic images from text descriptions, which is particularly useful in digital marketing, where visual content is key to engaging potential customers.

Option B (Correct): "Creating photorealistic images from text descriptions for digital marketing": This is the correct answer because generative AI models, like those offered by Amazon Bedrock, can create images based on text descriptions, making them highly valuable for generating marketing materials.

Option A: "Improving network security by using intrusion detection systems" is incorrect because this is a use case for traditional machine learning models, not generative AI.

Option C: "Enhancing database performance by using optimized indexing" is incorrect as it is unrelated to generative AI.

Option D: "Analyzing financial data to forecast stock market trends" is incorrect because it typically involves predictive modeling rather than generative AI.

AWS AI Practitioner References:

Use Cases for Generative AI Models on AWS: AWS highlights the use of generative AI for creative content generation, including image creation, text generation, and more, which is suited for digital marketing applications.

Amazon Bedrock provides large language models (LLMs) that are optimized for natural language understanding and text summarization tasks, making it the best choice for creating concise summaries of user reviews. Time-series forecasting, classification, and image analysis (Rekognition) are not suitable for summarizing textual data. References: AWS Bedrock Documentation.

The correct answer is C because BERTScore is a commonly used metric to evaluate the semantic similarity between generated text (like summaries) and reference text. It uses contextual embeddings from BERT to compare generated and reference sentences, making it highly suitable for evaluating generative tasks like summarization.

From AWS documentation:

"Amazon Bedrock supports BERTScore for evaluating generative text tasks, such as summarization or translation, by comparing the semantic similarity between the output and a reference."

Explanation of other options:

A. AUC is used for binary classification models, not generative text.

B. F1 score is also used for classification problems (precision/recall balance).

D. Real World Knowledge (RWK) score is not a standard or supported evaluation metric in Amazon Bedrock.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Model Evaluation Metrics

AWS ML Specialty Guide – Evaluating Generative Models

AWS Generative AI Developer Tools

Tokens in generative AI models are the smallest units that the model processes, typically representing words, subwords, or characters. They are essential for the model to understand and generate language, breaking down text into manageable parts for processing.

Option A (Correct): "Tokens are the basic units of input and output that a generative AI model operates on, representing words, subwords, or other linguistic units": This is the correct definition of tokens in the context of generative AI models.

Option B: "Mathematical representations of words" describes embeddings, not tokens.

Option C: "Pre-trained weights of a model" refers to the parameters of a model, not tokens.

Option D: "Prompts or instructions given to a model" refers to the queries or commands provided to a model, not tokens.

AWS AI Practitioner References:

Understanding Tokens in NLP: AWS provides detailed explanations of how tokens are used in natural language processing tasks by AI models, such as in Amazon Comprehend and other AWS AI services.

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.

AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises networks, ensuring traffic does not traverse the public internet.

A is correct:

"AWS PrivateLink provides private connectivity to services across VPCs, keeping API traffic off the public internet."

(Reference: AWS PrivateLink Overview)

B (Amazon Q) is a generative AI assistant, not a network security/control tool.

C (CloudFront) is a CDN, not for private API calls.

D (CloudTrail) is for logging and monitoring, not secure connectivity.

RAG combines large pre-trained models with retrieval mechanisms to fetch relevant context from a knowledge base. This approach is cost-effective as it eliminates the need for frequent model retraining while ensuring responses are contextually accurate and up to date. References: AWS RAG Techniques.

Decision trees are an interpretable machine learning algorithm that clearly documents the decision-making process by showing how each input feature affects the output. This transparency is particularly useful when explaining how the model arrives at a certain decision, making it suitable for classifying genes into categories.

Option A (Correct): "Decision trees": This is the correct answer because decision trees provide a clear and interpretable representation of how input features influence the model's output, making it ideal for understanding the inner mechanisms affecting predictions.

Option B: "Linear regression" is incorrect because it is used for regression tasks, not classification.

Option C: "Logistic regression" is incorrect as it does not provide the same level of interpretability in documenting decision-making processes.

Option D: "Neural networks" is incorrect because they are often considered "black boxes" and do not easily explain how they arrive at their outputs.

AWS AI Practitioner References:

Interpretable Machine Learning Models on AWS: AWS supports using interpretable models, such as decision trees, for tasks that require clear documentation of how input data affects output decisions.

The correct answer is Data residency, which ensures that data remains stored and processed within specific geographical or jurisdictional boundaries. AWS defines data residency as the practice of keeping sensitive or regulated data, such as healthcare records, inside designated regions to meet local privacy laws like HIPAA or GDPR. Amazon SageMaker, Bedrock, and other AWS services allow region-specific resource deployment, guaranteeing data never leaves the country. Data quality refers to accuracy and consistency, while discoverability and enrichment concern accessibility and augmentation, not compliance. Data residency is central to AWS’s Shared Responsibility Model, ensuring organizations maintain sovereignty over healthcare data.

Referenced AWS AI/ML Documents and Study Guides:

AWS Data Privacy Whitepaper – Data Residency and Compliance

AWS ML Specialty Guide – Data Governance and Security

Amazon Nova Pro is a multimodal foundation model in Amazon Bedrock that supports text, images, and multiple languages.

Nova Lite is optimized for lightweight, faster inference at lower cost.

Nova Canvas is a creative tool for visual design.

Nova Reel is optimized for video-related use cases.

???? Reference:

AWS Documentation – Amazon Nova Models

Explainability refers to the ability of an AI system to make its decision-making process clear and understandable to humans.

A is correct:

"Explainability is crucial for human-centered AI, especially in healthcare, to ensure that doctors and patients understand the rationale behind AI-driven recommendations."

(Reference: AWS Responsible AI)

B relates to protecting data, not explanations.

C is about treating groups equally.

D is about managing data lifecycle, not providing rationales.

An anomaly detection system is suitable for identifying unusual patterns or behaviors, such as suspicious IP addresses, which might indicate a potential threat.

Anomaly Detection:

Anomaly detection uses machine learning algorithms to identify deviations from normal behavior, such as unexpected traffic from a suspicious IP address.

This is a common approach for identifying potential threats or malicious activity in cybersecurity applications.

Why Option C is Correct:

Detects Suspicious Behavior: An anomaly detection system can monitor and detect IP addresses that exhibit unusual or suspicious patterns.

Real-time Monitoring: Provides continuous analysis of network traffic to identify potential security threats.

Why Other Options are Incorrect:

A. Speech recognition system: Is unrelated to detecting suspicious IP addresses.

B. NLP named entity recognition: Focuses on identifying entities in text, not IP address analysis.

D. Fraud forecasting system: Generally used for predicting fraud, not directly applicable to identifying suspicious IPs.

Thus, C is the correct answer for detecting suspicious IP addresses.

The correct answer is Text embeddings model, which transforms input text into dense vector representations. These vectors preserve semantic meaning and are ideal for similarity search, retrieval-augmented generation (RAG), and semantic search use cases, especially with Amazon OpenSearch Service. According to AWS Bedrock documentation, embeddings models are specifically designed to map text into a numerical space where related concepts are placed closer together. This allows efficient querying and ranking of documents based on the user’s question. This step is critical in chatbots using private knowledge bases. Text completion and instruction-following models focus on generating or following tasks, not producing embeddings. Image generation models are irrelevant here. Therefore, using a text embeddings model ensures that the chatbot retrieves contextually relevant results from stored vectors.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Text Embeddings Models

AWS ML Specialty Guide – Semantic Search and Vector Databases

Underfitting occurs when a machine learning model is too simple to capture the underlying patterns in the training data. AWS documentation explains that an underfit model performs poorly on both training and test datasets, which directly matches the scenario described.

In this case, the model shows low accuracy during training and evaluation, indicating that it has not learned sufficient relationships from the data. AWS identifies common causes of underfitting as insufficient model complexity, inadequate feature representation, overly aggressive regularization, or insufficient training time.

Underfitting is different from overfitting. Overfitting occurs when a model performs well on training data but poorly on test data, which is not the situation here. Hallucination applies to generative AI outputs, not supervised ML model accuracy. Cross-validation is a model evaluation technique, not a cause of poor performance.

AWS emphasizes the importance of diagnosing underfitting early in the model development lifecycle. Remedies include increasing model complexity, adding relevant features, reducing regularization, or selecting a more expressive algorithm. These steps allow the model to better learn from the data and improve accuracy across both training and test sets.

AWS machine learning best practices clearly associate low performance on both datasets with underfitting, making this the most likely cause of the problem described.

The ML model shows 90% recall on training data but only 40% recall on unseen testing data, indicating a significant performance drop. This discrepancy suggests the model has learned the training data too well, including noise and specific patterns that do not generalize to new data, which is a classic sign of overfitting.

Exact Extract from AWS AI Documents:

From the Amazon SageMaker Developer Guide:

"Overfitting occurs when a model performs well on training data but poorly on unseen test data, as it has learned patterns specific to the training set, including noise, that do not generalize. A large gap between training and testing performance metrics, such as recall, is a common indicator of overfitting."

(Source: Amazon SageMaker Developer Guide, Model Evaluation and Overfitting)

Detailed Explanation:

Option A: The model is overfitting on the training data.This is the correct answer. The significant drop in recall from 90% (training) to 40% (testing) indicates the model is overfitting, as it performs well on training data but fails to generalize to unseen data.

Option B: The model is underfitting on the training data.Underfitting occurs when the model performs poorly on both training and testing data due to insufficient learning. With 90% recall on training data, the model is not underfitting.

Option C: The model has insufficient training data.Insufficient training data could lead to poor performance, but the high recall on trainingdata (90%) suggests the model has learned the training data well, pointing to overfitting rather than a lack of data.

Option D: The model has insufficient testing data.Insufficient testing data might lead to unreliable test metrics, but it does not explain the large performance gap between training and testing, which is more indicative of overfitting.

To determine customer sentiments based on written customer reviews, the company can use Amazon Comprehend and Amazon Bedrock.

Amazon Comprehend:

A natural language processing (NLP) service that uses machine learning to uncover insights and relationships in text.

Can analyze customer reviews to detect sentiments (positive, negative, neutral, or mixed) automatically.

Amazon Bedrock:

Provides access to foundational models (FMs) from multiple AI companies for tasks such as text generation, summarization, and sentiment analysis.

The company can use a pre-trained sentiment analysis model available on Amazon Bedrock for processing customer reviews.

Why Other Options are Incorrect:

A. Amazon Lex: Used for building conversational interfaces like chatbots, not for sentiment analysis.

C. Amazon Polly: Converts text to speech; it doesn't analyze sentiment.

E. Amazon Rekognition: Analyzes images and videos, not text.

Amazon SageMaker Clarify provides built-in tools to detect bias in data and models, and to generate detailed explainability reports for model predictions, including SHAP values and feature importance.

A is correct:

“Amazon SageMaker Clarify provides bias detection, explainability for ML models, and comprehensive reports to satisfy regulatory and ethical requirements.”

(Reference: Amazon SageMaker Clarify Overview)

B (Data Wrangler) is for data preparation, not bias/explainability.

C (Model Cards) document models, but don’t detect bias or explain predictions.

D (AI Service Cards) provide transparency for AWS AI services, not custom model explainability.

The mobile app for users with visual impairment needs to hear user speech and provide voice responses, requiring speech-to-text (speech recognition) and text-to-speech capabilities. Deep learning neural networks are widely used for speech recognition tasks, as they can effectively process and transcribe spoken language. AWS services like Amazon Transcribe, which uses deep learning for speech recognition, can fulfill this requirement by converting user speech to text, and Amazon Polly can generate voice responses.

Exact Extract from AWS AI Documents:

From the AWS Documentation on Amazon Transcribe:

"Amazon Transcribe uses deep learning neural networks to perform automatic speech recognition (ASR), converting spoken language into text with high accuracy. This is ideal for applications requiring voice input, such as accessibility features for visually impaired users."

(Source: Amazon Transcribe Developer Guide, Introduction to Amazon Transcribe)

Detailed Explanation:

Option A: Use a deep learning neural network to perform speech recognition.This is the correct answer. Deep learning neural networks are the foundation of modern speech recognition systems, as used in AWS services like Amazon Transcribe. They enable the app to hear and transcribe user speech, and a service like Amazon Polly can handle voice responses, meeting the requirements.

Option B: Build ML models to search for patterns in numeric data.This option is irrelevant, as the task involves processing speech (audio data) and generating voice responses, not analyzing numeric data patterns.

Option C: Use generative AI summarization to generate human-like text.Generative AI summarization focuses on summarizing text, not processing speech orgenerating voice responses. This option does not address the core requirement of speech recognition.

Option D: Build custom models for image classification and recognition.Image classification and recognition are unrelated to processing speech or generating voice responses, making this option incorrect for an app focused on audio interaction.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Neptune is a fully managed graph database service optimized for storing and querying highly connected data.

AWS guidance highlights that graph databases are ideal for:

Fraud detection

Relationship analysis

Pattern discovery across entities such as users, transactions, and accounts

Amazon Neptune supports popular graph models and enables ML-driven investigations by efficiently traversing relationships, which is critical for fraud pattern analysis.

Why the other options are incorrect:

OpenSearch (A) is optimized for search and log analytics.

Aurora (B) is a relational database, not graph-based.

MemoryDB (D) is an in-memory data store for low-latency workloads.

AWS AI document references:

Amazon Neptune Overview

Graph-Based Fraud Detection on AWS

Using Graph Databases for Investigations

Comprehensive and Detailed Explanation (AWS AI documents):

AWS machine learning fundamentals emphasize the bias–variance tradeoff as a core concept in building models that generalize well to unseen data. A model that is accurate on unseen (test or production) data must balance these two properties effectively.

Low bias means the model can capture the underlying patterns in the data and is not overly simplistic.

Low variance means the model’s predictions are stable and not overly sensitive to fluctuations or noise in the training dataset.

A model with low bias and low variance is best positioned to generalize well to new, unseen fraud data, which is critical in fraud detection systems where patterns evolve and false positives or false negatives can be costly.

Why the other options are incorrect:

High bias leads to underfitting and poor learning of fraud patterns.

High variance leads to overfitting, where the model performs well on training data but poorly on unseen data.

AWS AI Study Guide References:

AWS Machine Learning concepts: bias, variance, and generalization

AWS best practices for model training and evaluation in Amazon SageMaker

Exploratory data analysis (EDA) involves understanding the data by visualizing it, calculating statistics, and creating correlation matrices. This stage helps identify patterns, relationships, and anomalies in the data, which can guide further steps in the ML pipeline.

Option C (Correct): "Exploratory data analysis": This is the correct answer as the tasks described (correlation matrix, calculating statistics, visualizing data) are all part of the EDA process.

Option A: "Data pre-processing" is incorrect because it involves cleaning and transforming data, not initial analysis.

Option B: "Feature engineering" is incorrect because it involves creating new features from raw data, not analyzing the data's existing structure.

Option D: "Hyperparameter tuning" is incorrect because it refers to optimizing model parameters, not analyzing the data.

AWS AI Practitioner References:

Stages of the Machine Learning Pipeline: AWS outlines EDA as the initial phase of understanding and exploring data before moving to more specific preprocessing, feature engineering, and model training stages.

The correct answer is C because in image generation tasks using foundation models like Stable Diffusion on Amazon Bedrock, the number of generation steps directly influences the fidelity and level of detail of the generated image. Fewer steps can produce more abstract or less defined images, while more steps allow the model to refine details, resulting in higher realism.

From AWS documentation:

"In diffusion-based image generation models, the number of inference steps (generation steps) determines how refined the final image is. Lower steps produce faster but less detailed outputs. Increasing steps results in more detailed and higher-quality images."

Explanation of other options:

A. Model checkpoint refers to saved versions of the model during training, not inference-time generation settings.

B. Batch size affects training/inference throughput, not image detail.

D. Token length is relevant for text models, not image generation.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Model Parameters for Image Generation

Stable Diffusion on Amazon Bedrock – Developer Guide

AWS ML Specialty Guide – Generative AI Configuration

Amazon SageMaker Feature Store is the correct solution for sharing and managing variables (features) across multiple teams during model development.

Amazon SageMaker Feature Store:

A fully managed repository for storing, sharing, and managing machine learning features across different teams and models.

It enables collaboration and reuse of features, ensuring consistent data usage and reducing redundancy.

Why Option A is Correct:

Centralized Feature Management: Provides a central repository for managing features, making it easier to share them across teams.

Collaboration and Reusability: Improves efficiency by allowing teams to reuse existing features instead of creating them from scratch.

Why Other Options are Incorrect:

B. SageMaker Data Wrangler: Helps with data preparation and analysis but does not provide a centralized feature store.

C. SageMaker Clarify: Used for bias detection and explainability, not for managing variables across teams.

D. SageMaker Model Cards: Provide model documentation, not feature management.

Amazon SageMaker Canvas is a visual, no-code tool for building and deploying ML models. According to the official SageMaker Canvas documentation:

“SageMaker Canvas provides a visual point-and-click interface that allows business analysts to generate accurate ML predictions without writing any code.”

The company is developing ML applications for various use cases, and the task is to select the correct ML paradigm (supervised or unsupervised learning) for each. Supervised learning involves training a model on labeled data to make predictions, while unsupervised learning identifies patterns or structures in unlabeled data. Each use case aligns with one of these paradigms based on its requirements.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"Supervised learning uses labeled data to train models for tasks like classification (e.g., binary or multi-class classification), where the model predicts a category. Unsupervised learning works with unlabeled data for tasks like clustering (e.g., K-means clustering) or dimensionality reduction, identifying patternsor reducing data complexity without predefined labels."

(Source: AWS AI Practitioner Learning Path, Module on Machine Learning Strategies)

Detailed Explanation:

Binary classification: Supervised learningBinary classification involves predicting one of two classes (e.g., yes/no, spam/not spam) using labeled data, making it a supervised learning task. The model learns from examples where the correct class is provided.

Multi-class classification: Supervised learningMulti-class classification extends binary classification to predict one of multiple classes (e.g., categorizing items into several groups). Like binary classification, it requires labeled data, so it falls under supervised learning.

K-means clustering: Unsupervised learningK-means clustering groups data into clusters based on similarity, without requiring labeled data. This is a classic unsupervised learning task, as the algorithm identifies patterns in the data on its own.

Dimensionality reduction: Unsupervised learningDimensionality reduction (e.g., using techniques like PCA) reduces the number of features in a dataset while preserving important information. It does not require labeled data, making it an unsupervised learning task.

Hotspot Selection Analysis:

The hotspot lists four use cases, each with a dropdown containing "Select...," "Supervised learning," and "Unsupervised learning." The correct selections are:

Binary classification: Supervised learning

Multi-class classification: Supervised learning

K-means clustering: Unsupervised learning

Dimensionality reduction: Unsupervised learning

Each paradigm (supervised and unsupervised learning) is used twice, as the question allows for paradigms to be selected one or more times.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Clarify is designed to detect and explain bias in ML models and datasets.

AWS Responsible AI guidance recommends Clarify to:

Identify bias in predictions

Analyze feature attribution

Support fairness and ethical AI practices

Why the other options are incorrect:

Rekognition (A) analyzes images, not recommendation bias.

Amazon Q Developer (B) assists developers with code.

Comprehend (C) performs NLP tasks, not bias analysis.

AWS AI document references:

Amazon SageMaker Clarify Documentation

Detecting Bias in AI Systems

Responsible AI on AWS

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