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.

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.

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

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 From Exact AWS AI documents:

Amazon Bedrock provides access to multimodal foundation models that can process both text and image inputs and generate intelligent responses.

Bedrock is designed for:

Building chatbots and conversational AI

Handling multimodal inputs

Integrating LLMs with enterprise applications

Why the other options are incorrect:

Amazon Comprehend (B) performs text analysis only.

Amazon Q (C) is a managed assistant, not a general chatbot platform.

Amazon Rekognition (D) analyzes images but does not generate conversational responses.

AWS AI document references:

Amazon Bedrock Overview

Multimodal Foundation Models on AWS

Building Chatbots with Amazon Bedrock

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

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 correct answer is C because Amazon Bedrock Guardrails provides out-of-the-box configurable safety mechanisms to control the behavior of LLMs in generative AI applications. Guardrails can be configured with denylists, content filters, sensitive topics, and tone enforcement, all without retraining the model.

From AWS documentation:

" Amazon Bedrock Guardrails allows developers to define safety and responsible AI policies directly in the model inference layer, making it easy to prevent harmful, biased, or unsafe outputs with minimal configuration. "

Explanation of other options:

A. Bedrock playgrounds are interactive environments for testing prompts and models but do not provide production-grade safety enforcement.

B. SageMaker Clarify focuses on bias detection and explainability for supervised ML models — it does not directly apply guardrails to LLM outputs.

D. SageMaker JumpStart is for model fine-tuning and deployment, not for enforcing safety policies on LLM responses.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Guardrails Overview

AWS Responsible AI Whitepaper

AWS Certified ML Specialty Study Guide – Safety in Generative AI

Amazon SageMaker Ground Truth Plus is a managed data labeling service that includes human-in-the-loop (HITL) validation. This solution ensures high accuracy by involving human reviewers to validate the annotations and reduce the risk of incorrect annotations.

Amazon SageMaker Ground Truth Plus:

It allows for the creation of high-quality training datasets with human oversight, which minimizes errors in labeling and increases accuracy.

Human-in-the-loop workflows help verify the correctness of annotations, ensuring that generated images for protective eyewear meet high-quality standards.

Why Option A is Correct:

High Accuracy: Human-in-the-loop validation provides the ability to catch and correct errors in annotations, ensuring high-quality data.

Minimized Risk of Incorrect Annotations: Human review adds a layer of quality assurance, which is especially important in use cases like generating precise images for protective eyewear.

Why Other Options are Incorrect:

B. Amazon Bedrock: Does not offer a knowledge base for data augmentation; it focuses on running foundation models.

C. Amazon Rekognition: Provides image recognition and analysis, not a solution for minimizing annotation errors.

D. Amazon QuickSight: A data visualization tool, not relevant to image annotation or generation tasks.

Thus, A is the correct answer for generating high-accuracy images with minimized annotation risks.

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