Free and Premium Amazon Web Services AIF-C01 Dumps Questions Answers

AWS Data Exchange is a service that allows companies to securely exchange data with third parties, such as independent software vendors (ISVs). AWS Data Exchange can be configured to provide notifications, including email notifications, when new datasets or compliance reports become available.

Option D (Correct): " AWS Data Exchange " : This is the correct answer because it enables the company to receive notifications, including email messages, when ISVs ' compliance reports are available.

Option A: " AWS Audit Manager " is incorrect because it focuses on assessing an organization ' s own compliance, not receiving third-party compliance reports.

Option B: " AWS Artifact " is incorrect as it provides access to AWS’s compliance reports, not ISVs ' .

Option C: " AWS Trusted Advisor " is incorrect as it offers optimization and best practices guidance, not compliance report notifications.

AWS AI Practitioner References:

AWS Data Exchange Documentation: AWS explains how Data Exchange allows organizations to subscribe to third-party data and receive notifications when updates are available.

AWS Glue is a serverless data integration service that enables users to extract, transform, and load (ETL) data. For a company with minimal programming experience, Amazon Q Developer provides an AI-powered assistant that can generate code, explain AWS services, and guide users through tasks like creating AWS Glue jobs. This makes it an ideal tool to help the company use AWS Glue effectively.

Exact Extract from AWS AI Documents:

From the AWS Documentation on Amazon Q Developer:

" Amazon Q Developer is an AI-powered assistant that helps developers by generating code, answering questions about AWS services, and providing step-by-step guidance for tasks such as building ETL pipelines with AWS Glue. It is designed to assist users with varying levels of expertise, including those with minimal programming experience. "

(Source: AWS Documentation, Amazon Q Developer Overview)

Detailed Explanation:

Option A: Amazon Q Developer

This is the correct answer. Amazon Q Developer can assist the company by generating AWS Glue scripts, explaining Glue concepts, and providing guidance on setting up ETL jobs, which is particularly helpful for users with limited programming experience.

Option B: AWS Config

AWS Config is used for tracking and managing resource configurations and compliance, not for assisting with coding or using services like AWS Glue. This option is incorrect.

Option C: Amazon Personalize

Amazon Personalize is a machine learning service for building recommendation systems, not for assisting with data integration or AWS Glue. This option is irrelevant.

Option D: Amazon Comprehend

Amazon Comprehend is an NLP service for analyzing text, not for helping users write code or use AWS Glue. This option does not meet the requirements.

Batch transform in Amazon SageMaker is designed for offline processing of large datasets. It is ideal for scenarios where immediate predictions are not required, and the inference can be done on large datasets that are multiple gigabytes in size. This method processes data in batches, making it suitable for analyzing archived data without the need for real-time access to predictions.

Option A (Correct): " Batch transform " : This is the correct answer because batch transform is optimized for handling large datasets and is suitable when immediate access to predictions is not required.

Option B: " Real-time inference " is incorrect because it is used for low-latency, real-time prediction needs, which is not required in this case.

Option C: " Serverless inference " is incorrect because it is designed for small-scale, intermittent inference requests, not for large batch processing.

Option D: " Asynchronous inference " is incorrect because it is used when immediate predictions are required, but with high throughput, whereas batch transform is more suitable for very large datasets.

AWS AI Practitioner References:

Batch Transform on AWS SageMaker: AWS recommends using batch transform for large datasets when real-time processing is not needed, ensuring cost-effectiveness and scalability.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

This scenario describes prompt injection, which is a well-documented security and safety risk in generative AI systems.

Prompt injection occurs when a user intentionally crafts input prompts to override, manipulate, or bypass system instructions, guardrails, or safety policies defined by the AI application developer. The user’s instruction explicitly attempts to override prior system instructions and force the model into unrestricted behavior.

AWS Responsible AI and Generative AI security guidance describe prompt injection as:

An attempt to alter model behavior through malicious or manipulative user input

A risk that can lead to policy violations, unsafe outputs, or data misuse

A key concern when deploying large language models (LLMs) in production systems

Why the other options are incorrect:

Data bias (B) refers to skewed or unrepresentative training data, not user manipulation at inference time.

Hallucination (C) refers to the model generating incorrect or fabricated information.

Data exposure (D) involves leaking sensitive or private data, not instruction hijacking.

AWS AI document references (for exact extracts):

AWS Responsible AI Overview — section on Generative AI risks

Amazon Bedrock Security Best Practices — section on prompt injection and input validation

AWS Generative AI Governance Guidance — discussion of instruction hierarchy and guardrails

The correct answer is D because Few-shot prompting involves providing the LLM with a few examples of the expected input-output format. This helps the model learn and mimic the pattern or structure required in the response — such as generating product descriptions that follow a specific template.

From AWS documentation:

" Few-shot prompting helps guide the model to produce structured and domain-specific outputs by supplying a small number of example inputs and corresponding outputs. "

Explanation of other options:

A. Zero-shot prompting provides no examples, which may lead to inconsistent formatting.

B. Chain-of-thought prompting is used to guide reasoning steps, not formatting.

C. One-shot prompting uses a single example, but few-shot typically yields better structure adherence.

Referenced AWS AI/ML Documents and Study Guides:

AWS Prompt Engineering Guide

Amazon Bedrock Developer Documentation – Prompting Techniques

AWS ML Specialty Study Guide – LLM Prompting Patterns

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.

AWS documentation defines prompt injection as a security and safety risk in which a user crafts input designed to override, manipulate, or bypass system-level instructions, safeguards, or intended model behavior. The example provided is a classic prompt injection attempt, where the user explicitly instructs the AI assistant to ignore prior rules and operate without restrictions.

In this scenario, the attacker is not exploiting training data or causing factual errors, but rather attempting to change the control flow and behavior of the AI system through malicious or manipulative prompts. AWS identifies prompt injection as a critical risk for generative AI systems, especially those exposed to end users through chat interfaces, APIs, or customer-facing applications.

The other options do not apply. Data bias relates to skewed or unfair training data. Hallucination refers to generating incorrect or fabricated information. Data exposure involves leaking sensitive or private data. None of these describe an attempt to override system instructions.

AWS recommends multiple mitigation strategies for prompt injection risks, including instruction hierarchy enforcement, prompt isolation, input validation, output filtering, and grounding responses using techniques such as Retrieval Augmented Generation. AWS also emphasizes the importance of clearly separating system instructions from user inputs to prevent unauthorized behavior changes.

Prompt injection is categorized by AWS as part of Responsible AI and security governance, highlighting the need for robust guardrails when deploying AI assistants in production. Therefore, the correct answer is prompt injection.

Experimenting and refining the prompt is the best approach to ensure that the chatbot using a foundation model (FM) produces responses that adhere to the company ' s tone.

Prompt Engineering:

Adjusting and refining the prompt allows for better control over the FM ' s outputs, ensuring they align with the desired tone and style.

This iterative process involves testing different prompts and modifying them based on the model ' s responses to achieve the desired outcome.

Why Option C is Correct:

Directly Influences Output Quality: Allows for fine-tuning of the model’s responses to match the company ' s tone.

Cost-Effective: Does not require modifying the model itself, only the inputs to it.

Why Other Options are Incorrect:

A. Low limit on tokens: Limits response length but not the adherence to company tone.

B. Batch inferencing: Relates to processing multiple inputs, not controlling response tone.

D. Higher temperature: Increases randomness in responses, which could deviate from the desired tone.

Comprehensive and Detailed Explanation from AWS AI Documents:

Classification requires predefined labels (categories). The company explicitly does not want to define categories.

Regression (linear or logistic) predicts numerical values or probabilities, not groups.

Clustering is an unsupervised learning technique that groups similar data points together based on their features without needing labeled categories.

AWS defines clustering as:

“Clustering is an unsupervised machine learning algorithm that automatically groups data points into clusters based on their similarities.”

This makes Clustering the correct choice for segmenting customers into groups without predefined labels.

???? Reference:

AWS ML Glossary – Clustering

Generative AI models (such as large language models) are designed to generate new content, such as text, summaries, images, and more. Summarizing text—like customer complaints—is a classic application of generative AI.

A is correct:

" Text summarization is a core generative AI use case, as it involves generating new, concise content from a larger body of text. "

(Reference: AWS Generative AI Use Cases)

B and C are standard ML classification/segmentation tasks.

D is a regression/prediction task, not generative.

The scenario involves analyzing customer feedback and automatically classifying it into categories such as product quality, customer service, and delivery experience. This task requires processing and understanding textual data, which is a core application of natural language processing (NLP). NLP encompasses techniques for analyzing, interpreting, and generating human language, including tasks like text classification, sentiment analysis, and topic modeling, all of which are relevant to this use case.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

" Natural Language Processing (NLP) enables machines to understand and process human language. Common NLP tasks include text classification, sentiment analysis, named entity recognition, and topic modeling. Services like Amazon Comprehend can be used to classify text into predefined categories based on content. "

(Source: AWS AI Practitioner Learning Path, Module on AI and ML Concepts)

Detailed Explanation:

Option A: Computer visionComputer vision involves processing and analyzing visual data, such as images or videos. Since the scenario deals with textual customer feedback, computer vision is not applicable.

Option B: Natural language processing (NLP)This is the correct answer. The task of classifying customer feedback into categories requires understanding and processing text, which is an NLP task. AWS services like Amazon Comprehend are specifically designed for such text classification tasks.

Option C: Recommendation systemsRecommendation systems suggest items or content based on user preferences or behavior. The scenario does not involve recommending products or services but rather classifying feedback, so this option is incorrect.

Option D: Fraud detectionFraud detection involves identifying anomalous or fraudulent activities, typically in financial or transactional data. The scenario focuses on text classification, not anomaly detection, making this option irrelevant.

The company wants to fine-tune an ML model on Amazon Bedrock using sensitive data stored in private databases within a VPC, ensuring the data remains within its private network. AWS PrivateLink provides a secure, private connection between a VPC and AWS services like Amazon Bedrock, allowing data to stay within the company’s network without traversing the public internet. This meets the requirement for maintaining data privacy during fine-tuning.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" AWS PrivateLink enables you to securely connect your VPC to Amazon Bedrock without exposing data to the public internet. This is particularly useful for fine-tuning models with sensitive data, as it ensures that data remains within your private network. "

(Source: AWS Bedrock User Guide, Security and Networking)

Detailed Explanation:

Option A: Restrict access to Amazon Bedrock by using an AWS Identity and Access Management (IAM) service role.While IAM service roles control access to Amazon Bedrock, they do not address the requirement of keeping data within the private network during data transfer. This option is insufficient.

Option B: Restrict access to Amazon Bedrock by using an AWS Identity and Access Management (IAM) resource policy.IAM resource policies define permissions for Bedrock resources but do not ensure that data stays within the private network. This option is incorrect.

Option C: Use AWS PrivateLink to connect the VPC and Amazon Bedrock.This is the correct answer. AWS PrivateLink creates a secure, private connection between the VPC and Amazon Bedrock, ensuring that sensitive data does not leave the private network during fine-tuning, as required.

Option D: Use AWS Key Management Service (AWS KMS) keys to encrypt the data.While AWS KMS can encrypt data, encryption alone does not guarantee that data remains within the private network during transfer. This option does not fully meet the requirement.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

AWS CloudTrail records API calls and user activity across AWS services, including:

Who performed an action

What action was taken

When and from where the action occurred

AWS governance guidance identifies CloudTrail as the primary service for audit logging and accountability.

Why the other options are incorrect:

AWS Config (B) tracks configuration changes, not user actions.

Audit Manager (C) assesses compliance but does not record individual actions.

Trusted Advisor (D) provides best-practice recommendations.

AWS AI document references:

AWS CloudTrail Overview

Auditing User Activity on AWS

Governance and Compliance for AI Workloads

Amazon Bedrock Guardrails allow developers to create safeguards that filter harmful content and prevent sensitive topics from being discussed. This functionality helps mitigate prompt injection attacks with minimal implementation effort. According to the official Amazon Bedrock documentation:

“You can configure Guardrails for Amazon Bedrock to define denied topics, use content filters, and apply sensitive information filters, offering protection against prompt injection attacks with minimal development effort.”

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, as conversion rate (how many users upgrade to premium) and retention rate (how many stay subscribed) are primary indicators of a generative AI system’s business impact and ROI. According to AWS documentation, evaluating AI performance should go beyond technical accuracy to include business metrics that show real-world value. For a premium service, higher conversion implies successful personalization that attracts free users, while strong retention reflects sustained engagement and user satisfaction. Metrics like ARPU or query reduction are secondary indicators. AWS emphasizes outcome-based measurement to ensure AI initiatives contribute measurable ROI tied to customer adoption, loyalty, and profitability. Therefore, tracking conversion and retention gives the clearest long-term measure of financial success from generative AI.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – ML Business Metrics

AWS AI Adoption Framework – Value Realization and ROI Tracking

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

The verified answer is B. Data leakage. The model exposes sensitive company information because that information was inadvertently included in training data. AWS guidance warns that using sensitive data to train models can cause unintended disclosure of data from model output, including data leakage during inference. This is exactly the scenario: sensitive information entered the training process and later appeared in model output after deployment.

AWS security reference guidance for generative AI model customization identifies sensitive information disclosure as a threat where a model trained on datasets containing PII leaks sensitive information during inference. Although the question says company information rather than PII specifically, the same security principle applies: protected data included in training or continued pre-training can be memorized or reproduced by the model later.

Jailbreaking is incorrect because jailbreaking refers to attempts to bypass model safety controls through adversarial prompts. The problem here is not that a user bypassed safety controls; the sensitive information was already embedded through training data.

Contextual grounding is incorrect because grounding is a technique for improving answer accuracy by connecting model responses to trusted context, such as RAG sources. It is not a security risk.

Prompt injection is incorrect because prompt injection involves malicious input that attempts to override or manipulate model behavior at inference time. The question does not describe a malicious prompt. It describes accidental exposure from training data.

Therefore, the correct security risk is data leakage.

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.

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

The evaluation stage of the generative AI model lifecycle involves testing the model to assess its performance, including accuracy, coherence, and other metrics. This stage ensures the model meets the desired quality standards before deployment.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

" The evaluation phase in the machine learning lifecycle involves testing the model against validation or test datasets to measure its performance metrics, such as accuracy, precision, recall, or task-specific metrics for generative AI models. "

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

Detailed Explanation:

Option A: DeploymentDeployment involves making the model available for use in production. While monitoring occurs post-deployment, accuracy testing is performed earlier in the evaluation stage.

Option B: Data selectionData selection involves choosing and preparing data for training, not testing the model’s accuracy.

Option C: Fine-tuningFine-tuning adjusts a pre-trained model to improve performance for a specific task, but it is not the stage where accuracy is formally tested.

Option D: EvaluationThis is the correct answer. The evaluation stage is where tests are conducted to examine the model’s accuracy and other performance metrics, ensuring it meets requirements.

Comprehensive and Detailed Explanation (AWS AI documents):

According to AWS Generative AI and Foundation Model guidance, foundation models are pre-trained on very large and diverse datasets, enabling them to perform a wide range of tasks such as classification, summarization, labeling, and content generation without task-specific training.

For labeling online news articles, a foundation model can be used out of the box or with minimal prompt engineering, whereas a conventional ML model would typically require:

Task-specific labeled training data

Model training and validation cycles

Ongoing retraining as content evolves

Why the other options are incorrect:

B. Smaller and faster – Foundation models are generally larger, not smaller, than conventional ML models.

C. More transparent – FMs are often less transparent due to their size and complexity.

D. Not biased – Foundation models can still inherit biases from training data; bias mitigation is required.

AWS AI Study Guide References:

AWS Generative AI fundamentals

AWS Foundation Model characteristics and benefits

Amazon SageMaker JumpStart is the correct service for quickly deploying and consuming a foundation model (FM) within a team ' s VPC.

Amazon SageMaker JumpStart:

Provides access to a wide range of pre-trained models and solutions that can be easily deployed and consumed within a VPC.

Designed to simplify and accelerate the deployment of machine learning models, including foundation models.

Why Option B is Correct:

Rapid Deployment: JumpStart allows for quick deployment of models with minimal configuration, directly within a secure VPC environment.

Ease of Use: Provides a user-friendly interface to select and deploy models, reducing the time to value.

Why Other Options are Incorrect:

A. Amazon Personalize: Focuses on creating personalized recommendations, not deploying foundation models.

C. PartyRock: Not a recognized AWS service.

D. Amazon SageMaker endpoints: Endpoints are for deploying specific models, not a feature for quickly starting with pre-trained foundation models.

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 F1 score is a metric used to evaluate the performance of a classification model by considering both precision and recall. Precision measures the accuracy of positive predictions (i.e., the proportion of true positive predictions among all positive predictions made by the model), while recall measures the model ' s ability to identify all relevant positive instances (i.e., the proportion of true positive predictions among all actual positive instances). The F1 score is the harmonic mean of precision and recall, providing a single metric that balances both concerns. This is particularly useful when dealing with imbalanced datasets or when the cost of false positives and false negatives is significant. Options B, C, and D pertain to other aspects of model performance but are not related to the F1 score.

Amazon SageMaker Model Cards provide a standardized way to document important details about an AI model, such as its purpose, performance, intended usage, and known limitations. This enables transparency and compliance while fostering better communication between stakeholders. It does not store models physically or optimize computational requirements. References: AWS SageMaker Model Cards Documentation.

Network isolation is a key security feature for SageMaker. It ensures that training and inference jobs run in a VPC and are not accessible from the internet. Per the official SageMaker documentation:

“When you enable network isolation, your model can’t make any outbound network calls. This is useful for security and regulatory compliance when working with sensitive data.”

The correct answer is D because low latency and optimized inference speed are critical for real-time applications. For delivering real-time service quotes, the system must respond in milliseconds or a few seconds at most, making latency a primary concern when choosing the model.

From AWS Bedrock documentation:

" When selecting a foundation model for real-time applications, inference speed and latency are key evaluation metrics to ensure responsive user experiences. "

Explanation of other options:

A. Model size affects performance and cost but doesn ' t directly guarantee low latency.

B. Training data quality is important for accuracy, but it doesn’t address real-time performance requirements.

C. GPU availability matters in infrastructure planning, not in model selection for latency optimization.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Model Selection Guide – Real-time Use Case Considerations

AWS ML Specialty Guide – Foundation Model Performance Criteria

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

The correct answer is C because Continued Pre-training (also known as domain-adaptive pre-training) involves training a pre-trained model further on unlabeled domain-specific data. This method helps adapt the LLM to a specific domain without needing labeled datasets, making it ideal for cases where the goal is to enhance the model’s understanding of technical language or terminology.

From AWS documentation:

" Continued pre-training allows an LLM to ingest large volumes of domain-specific text without labels to improve contextual understanding in a particular area. This is effective when adapting a foundation model to new knowledge without altering the model architecture. "

Explanation of other options:

A. Full training refers to building a model from scratch, which is extremely resource-intensive and unnecessary if a strong base model already exists.

B. Supervised fine-tuning requires labeled data, which the scenario explicitly lacks.

D. RAG is a method to retrieve external information at inference time, not a training technique using unlabeled data.

Referenced AWS AI/ML Documents and Study Guides:

AWS Bedrock Model Customization Documentation – Continued Pre-training

Amazon SageMaker JumpStart – Domain Adaptation Techniques

AWS Machine Learning Specialty Study Guide – Foundation Model Customization Section

The correct answer is B because Amazon SageMaker JumpStart provides pre-built solutions, including training workflows for popular open-source LLMs such as Falcon, LLaMA, and others. It allows practitioners to quickly launch fine-tuning jobs using predefined templates, minimizing operational setup and code complexity.

From AWS documentation:

" Amazon SageMaker JumpStart enables you to fine-tune and deploy foundation models with minimal setup. It provides easy-to-use interfaces and pre-built configurations for training, which significantly reduces the operational overhead required to train models. "

Explanation of other options:

A. PartyRock is designed for prototyping generative AI apps but does not support model training or fine-tuning.

C. Writing a custom script for SageMaker training is flexible but involves more operational effort, including handling infrastructure configuration.

D. Training on EC2 via a Jupyter notebook is fully manual and operationally intensive, including dependency setup, data handling, and resource scaling.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker JumpStart Developer Guide – Fine-tuning Foundation Models

AWS Certified Machine Learning Specialty Guide – Model Customization and JumpStart

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

AWS documentation identifies ROUGE as a standard evaluation metric for text summarization tasks. ROUGE measures the overlap of n-grams, sequences, or word pairs between a machine-generated summary and a human-written reference summary, making it ideal for automated evaluation.

In this scenario, the company needs a metric that directly compares generated summaries with human references. ROUGE scores quantify how much of the reference content is captured by the model output, which aligns with AWS recommendations for evaluating summarization quality.

The other metrics are not appropriate. F1 score is typically used for classification tasks. Perplexity measures language model confidence but does not compare outputs to reference summaries. Fréchet Inception Distance is used for image generation tasks, not text.

AWS consistently recommends ROUGE for summarization evaluation, making it the correct choice.

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

The correct answer is B – Hallucinations. AWS defines hallucinations as instances where a generative model produces confident but incorrect or fabricated information. This can occur when the model lacks relevant context or attempts to fill informational gaps during text generation. In product descriptions, hallucinations may lead to false features, incorrect specifications, or misleading claims—posing reputational and legal risks. AWS documentation recommends mitigating hallucinations through Retrieval-Augmented Generation (RAG), grounding responses in enterprise data using Bedrock Knowledge Bases, implementing Guardrails, or refining prompts with factual constraints. Toxicity (A) refers to harmful or offensive content, interpretability (C) concerns understanding model reasoning, and deterministic outputs (D) are not typical of LLMs. Therefore, the issue described aligns precisely with the definition of hallucination in AWS’s generative AI guidance.

Referenced AWS Documentation:

AWS Generative AI Whitepaper – Hallucination Mitigation

Amazon Bedrock Knowledge Bases – Grounding Model Responses

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.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Prompt management in Amazon Bedrock enables:

Reuse of standardized prompt templates

Parameterization of prompts with dynamic inputs

Consistent instruction application across use cases

AWS Bedrock guidance describes prompt management as the recommended solution for maintaining reusable prompt templates while injecting product-specific content.

Why the other options are incorrect:

Knowledge Bases (B) provide retrieval, not prompt templating.

Model evaluation (C) assesses quality, not generation.

Cross-region inference (D) addresses availability, not prompt reuse.

AWS AI document references:

Amazon Bedrock Prompt Management

Prompt Templates and Reusability

Managing Generative AI Prompts

Moderation APIs, such as Amazon Rekognition’s Content Moderation API, can help filter and block inappropriate or unwanted images from being returned by a chatbot. These APIs are specifically designed to detect and manage undesirable content in images.

Option A (Correct): " Implement moderation APIs " : This is the correct answer because moderation APIs are designed to identify and filter inappropriate content, ensuring the chatbot does not return unwanted images.

Option B: " Retrain the model with a general public dataset " is incorrect because retraining does not directly prevent inappropriate content from being returned.

Option C: " Perform model validation " is incorrect as it ensures model correctness, not content moderation.

Option D: " Automate user feedback integration " is incorrect because user feedback does not prevent inappropriate images in real-time.

AWS AI Practitioner References:

AWS Content Moderation Services: AWS provides moderation APIs for filtering unwanted content from applications.

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.

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.

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

Explainable AI (XAI) techniques such as SHAP (SHapley values) or feature attribution provide transparency by showing which input factors influenced decisions.

A is not scalable for complex use cases.

C does not guarantee real interpretability.

D ignores the regulatory need for explainability.

???? Reference:

AWS SageMaker Clarify – Explainable AI

The verified answer is C. Memory. In Amazon Bedrock AgentCore, Memory is the feature designed to preserve conversational context and make an assistant remember relevant information across interactions. AWS documentation states that AgentCore Memory supports both short-term and long-term memory. Short-term memory stores raw interactions that help the agent maintain context within a single session, while long-term memory automatically extracts and stores key insights from conversations across multiple sessions, including user preferences, important facts, and session summaries. This directly matches the requirement because the assistant must maintain context across multiple user interactions without the company building and operating its own memory infrastructure.

Option A. Gateway is incorrect because AgentCore Gateway is used to connect agents securely to tools, APIs, and enterprise services. It helps expose external capabilities to agents, but it does not provide persistent conversational context. Option B. Browser Tool is incorrect because the Browser Tool enables an agent to interact with websites or web-based workflows. It is useful for browser automation and web interaction, not memory retention. Option D. Code Interpreter is incorrect because Code Interpreter allows the agent to execute code for tasks such as calculations, file analysis, and data manipulation. It does not solve the requirement of remembering prior conversation details.

The key phrase in the question is “maintain context across multiple user interactions.” That is exactly the purpose of AgentCore Memory. AWS also explains that long-term memory provides persistent storage for session-specific context, enabling agents to maintain continuity and personalization across interactions. Therefore, when a conversational assistant needs continuity, personalization, and context retention without custom infrastructure management, the correct AgentCore feature is Memory.

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.

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

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

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

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

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

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

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

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.

Reinforcement learning from human feedback (RLHF) is the most effective approach to align large language models with company-specific values, ethics, and evolving moderation requirements. AWS documentation explains that RLHF uses direct human input to guide model behavior, enabling models to learn preferences that cannot be fully captured through static datasets or generic fine-tuning.

In this scenario, the company requires improvement within a short time frame of three months, alignment with organizational ethics, and adaptability to emerging trends and new forms of harmful content. RLHF meets these needs by incorporating real-time feedback from skilled human moderators, allowing the model to rapidly adjust its responses based on expert judgment.

AWS highlights that RLHF is particularly valuable for content moderation, safety alignment, and policy enforcement, where nuanced decisions and evolving standards are common. By rewarding desirable behaviors and penalizing undesirable outputs, the model continuously improves in a controlled and targeted manner.

The other options are less suitable. Continuous pre-training on large internet datasets is time-consuming, resource-intensive, and may introduce content misaligned with company values. Historical moderation datasets may not reflect new or emerging content patterns. Fine-tuning on general ethical guidelines lacks the specificity required for company-defined moderation policies and does not adapt quickly to new risks.

AWS positions RLHF as a key technique in responsible generative AI development, enabling organizations to maintain human oversight while improving model safety and alignment. Therefore, using RLHF with real-time input from skilled moderators is the most effective and compliant solution for this use case.

Amazon SageMaker endpoints provide fully managed, serverless model deployment for real-time and batch predictions, allowing companies to deploy ML models without handling any servers or infrastructure management.

D is correct: SageMaker endpoints let you deploy, scale, and monitor ML models with no infrastructure overhead.

A and B require infrastructure management.

C (CloudFront/S3) is not for model deployment, but for static content delivery.

“Amazon SageMaker endpoints allow you to deploy machine learning models for inference without the need to manage underlying infrastructure.”

(Reference: AWS SageMaker Model Deployment, AWS Certified AI Practitioner Study Guide)

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

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

The verified answer is A. Amazon Q in QuickSight. AWS documentation describes Amazon Q in QuickSight as part of QuickSight’s generative business intelligence capability. AWS states that with Amazon Quick chat, users can use the Generative BI authoring experience, create executive summaries of data, ask and answer questions of data, and generate data stories. This directly matches the question because the required service must create business intelligence reports and automatically generate executive summaries from user-provided data.

AWS documentation also explains that dashboard readers can generate executive summaries that provide a summary of all insights generated for a dashboard. These executive summaries help readers find key insights and information about a dashboard at a glance. In another QuickSight documentation page, AWS states that large language models can be used to generate executive summaries of dashboards, and that executive summaries are based on QuickSight’s suggested insights. This confirms that the service is Amazon Q in QuickSight, not a general-purpose AI service.

Amazon Rekognition is incorrect because it is a computer vision service used for image and video analysis, such as object detection, facial analysis, and content moderation. It is not a business intelligence reporting or executive-summary service. Amazon Textract is incorrect because it extracts text, handwriting, tables, and forms from documents. While Textract can help process documents, it does not create BI reports or generate executive summaries from dashboard data. Amazon Polly is incorrect because it converts text into lifelike speech. Polly is a speech synthesis service, not a BI analytics or reporting service.

Therefore, the only option that fits both parts of the requirement—business intelligence reporting and automatically generated executive summaries—is Amazon Q in QuickSight.

The verified selections are Few-shot prompting, Chain-of-thought prompting, and Zero-shot prompting. The first description matches few-shot prompting because AWS describes few-shot prompting as a technique that includes example outputs or demonstrations in the initial prompt so the model can understand the expected pattern before generating a response. The phrase “provide a small number of examples” is the key indicator. A few-shot prompt gives the model limited examples of the desired task, format, or reasoning style, and the model uses those examples as context for the next output.

The second description matches chain-of-thought prompting. AWS describes chain-of-thought prompting as a technique that helps a model solve a problem by following a series of intermediate reasoning steps before reaching the final answer. The wording “break down the step-by-step process” directly points to chain-of-thought prompting. This method is commonly associated with reasoning, arithmetic, logic, planning, and multi-step problem solving because the prompt encourages the model to work through intermediate steps rather than immediately outputting a final answer.

The third description matches zero-shot prompting because AWS describes zero-shot prompting as asking the model to perform a task without providing examples in the prompt. The model relies only on the instruction and its pre-trained knowledge. The phrase “without providing examples” is the decisive clue.

Role-based prompting is not used here because none of the descriptions asks the model to act as a specific persona, job role, or domain expert, such as “Act as a financial analyst” or “You are a security engineer.” Single-shot prompting is also not used because the first description says a “small number of examples,” which indicates few-shot prompting, not exactly one example. Therefore, the three correct hotspot mappings are Few-shot prompting, Chain-of-thought prompting, and Zero-shot prompting.

Hallucinations in large language models (LLMs) occur when the model generates outputs that are factually incorrect, irrelevant, or not grounded in the input data. To mitigate hallucinations, adjusting the model ' s inference parameters, particularly the temperature, is a well-documented approach in AWS AI Practitioner resources. The temperature parameter controls the randomness of the model ' s output. A lower temperature makes the model more deterministic, reducing the likelihood of generating creative but incorrect responses, which are often the cause of hallucinations.

Exact Extract from AWS AI Documents:

From the AWS documentation on Amazon Bedrock and LLMs:

" The temperature parameter controls the randomness of the generated text. Higher values (e.g., 0.8 or above) increase creativity but may lead to less coherent or factually incorrect outputs, while lower values (e.g., 0.2 or 0.3) make the output more focused and deterministic, reducing the likelihood of hallucinations. "

(Source: AWS Bedrock User Guide, Inference Parameters for Text Generation)

Detailed Explanation:

Option A: Set up Agents for Amazon Bedrock to supervise the model training.Agents for Amazon Bedrock are used to automate tasks and integrate LLMs with external tools, not to supervise model training or directly address hallucinations. This option is incorrect as it does not align with the purpose of Agents in Bedrock.

Option B: Use data pre-processing and remove any data that causes hallucinations.While data pre-processing can improve model performance, identifying and removing specific data that causes hallucinations is impractical because hallucinations are often a result of the model ' s generative process rather than specific problematic data points. This approach is not directly supported by AWS documentation for addressing hallucinations.

Option C: Decrease the temperature inference parameter for the model.This is the correct approach. Lowering the temperature reduces the randomness in the model ' s output, making it more likely to stick to factual and contextually relevant responses. AWS documentation explicitly mentions adjusting inference parameters like temperature to control output quality and mitigate issues like hallucinations.

Option D: Use a foundation model (FM) that is trained to not hallucinate.No foundation model is explicitly trained to " not hallucinate, " as hallucinations are an inherent challenge in LLMs. While some models may be fine-tuned for specific tasks to reduce hallucinations, this is not a standard feature of foundation models available on Amazon Bedrock.

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.

Amazon OpenSearch Service (formerly Amazon Elasticsearch Service) has introduced capabilities to support vector search, which allows companies to build vector database applications. This is particularly useful in machine learning, where vector representations (embeddings) of data are often used to capture semantic meaning.

Scalable index management and nearest neighbor search capability are the core features enabling vector database functionalities in OpenSearch. The service allows users to index high-dimensional vectors and perform efficient nearest neighbor searches, which are crucial for tasks such as recommendation systems, anomaly detection, and semantic search.

Here is why option C is the correct answer:

Scalable Index Management: OpenSearch Service supports scalable indexing of vector data. This means you can index a large volume of high-dimensional vectors and manage these indexes in a cost-effective and performance-optimized way. The service leverages underlying AWS infrastructure to ensure that indexing scales seamlessly with data size.

Nearest Neighbor Search Capability: OpenSearch Service ' s nearest neighbor search capability allows for fast and efficient searches over vector data. This is essential for applications like product recommendation engines, where the system needs to quickly find the most similar items based on a user ' s query or behavior.

AWS AI Practitioner References:

According to AWS documentation, OpenSearch Service ' s support for nearest neighbor search using vector embeddings is a key feature for companies building machine learning applications that require similarity search.

The service uses Approximate Nearest Neighbors (ANN) algorithms to speed up searches over large datasets, ensuring high performance even with large-scale vector data.

The other options do not directly relate to building vector database applications:

A. Integration with Amazon S3 for object storage is about storing data objects, not vector-based searching or indexing.

B. Support for geospatial indexing and queries is related to location-based data, not vectors used in machine learning.

D. Ability to perform real-time analysis on streaming data relates to analyzing incoming data streams, which is different from the vector search capabilities.

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

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

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

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

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

???? Reference:

AWS Documentation – SageMaker Ground Truth

The company is building a chatbot using an LLM to answer questions about HR policies, with access to a large digital documentation base. Retrieval Augmented Generation (RAG) optimizes the LLM’s responses by retrieving relevant information from the documentation base and using it to generate accurate, contextually grounded answers, reducing hallucinations and improving response quality.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Retrieval Augmented Generation (RAG) enhances the performance of large language models by retrieving relevant information from external knowledge bases, such as documentation or databases, and incorporating it into the generation process. This technique ensures responses are accurate and grounded in the provided data, making it ideal for applications like policy chatbots. "

(Source: AWS Bedrock User Guide, Retrieval Augmented Generation)

Detailed Explanation:

Option A: Use Retrieval Augmented Generation (RAG).This is the correct answer. RAG leverages the documentation base to provide the LLM with relevant HR policy information, optimizing the chatbot’s responses for accuracy and relevance.

Option B: Use few-shot prompting.Few-shot prompting provides a few examples in the prompt to guide the LLM, but it is less effective than RAG for large documentation bases, as it cannot dynamically retrieve specific policy details.

Option C: Set the temperature to 1.Setting the temperature to 1 controls the randomness of the LLM’s output but does not optimize responses using external documentation. This option is unrelated to the documentation base.

Option D: Decrease the token size.Decreasing token size (likely referring to limiting input/output tokens) may reduce response length but does not optimize the quality of responses using the documentation base.

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

The correct answer is A because Human-in-the-loop (HITL) is a post-processing strategy used to monitor, review, and filter outputs from generative AI models for toxicity, bias, or inappropriate content. It allows human reviewers to approve or reject model responses before they are delivered to end-users, ensuring alignment with ethical guidelines and company policies.

From the AWS documentation:

" Human-in-the-loop (HITL) workflows in generative AI are used to validate and approve outputs of models, especially in applications where content quality, compliance, or harm reduction is critical. HITL is a key step in responsible AI implementations to mitigate hallucinations, bias, and unsafe content. "

Explanation of other options:

B. Data augmentation is a pre-processing technique to increase data diversity, not typically used in post-processing stages.

C. Feature engineering is relevant in traditional ML, especially structured data tasks, not typically used in generative AI post-processing.

D. Adversarial training is a model training strategy, not a post-processing mitigation approach.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Practices Whitepaper

AWS Generative AI Developer Guide – Human-in-the-loop and Post-processing

Amazon A2I Documentation – Integrating Human Review in ML Workflows

The verified answer is A. Balance class representation in the dataset. The requirement is to train an AI model on data that reflects the diversity of a global customer base. In AWS responsible AI guidance, dataset quality is directly connected to fairness, bias reduction, and model behavior across different user groups. AWS identifies dataset characteristics such as inclusivity, diversity, curated data sources, and balanced datasets as part of responsible AI knowledge for AI practitioners. This directly supports the need for a dataset that represents diverse users instead of overrepresenting one group and underrepresenting another.

AWS also explains that bias can result from imbalances in data or from differences in model performance across groups. Amazon SageMaker Clarify is designed to help detect and mitigate potential bias during data preparation, after training, and in deployed models by examining specified attributes. This supports the principle that the training dataset should be examined and balanced before model training so that the model does not preferentially learn patterns from majority groups while performing poorly for minority groups.

Option B is incorrect because using a regional dataset, even if complete, does not satisfy a global diversity requirement. A complete regional dataset may still exclude languages, demographics, cultural contexts, behaviors, and usage patterns from other regions. Option C is incorrect because oversampling majority class data worsens imbalance. It increases the dominance of already overrepresented groups and can amplify biased model behavior. Option D is also incorrect because dropping minority class records removes exactly the user groups that must be represented for a global customer base.

AWS SageMaker Clarify documentation specifically describes class imbalance bias as a situation where one facet has fewer training samples than another. AWS notes that models may preferentially fit larger facets at the expense of smaller facets, leading to higher training error for underrepresented groups. Therefore, balancing class representation is the best action because it improves dataset representativeness and supports responsible AI fairness for a diverse global user base.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

To secure data in Amazon Q Business, AWS recommends:

AWS KMS (A) to encrypt data at rest and manage encryption keys.

AWS IAM (E) to control authentication and authorization for users and services.

Together, these services ensure:

Strong access control

Data confidentiality

Compliance with enterprise security requirements

Why the other options are incorrect:

Cross-account access (B) does not inherently ensure privacy.

Amazon Inspector (C) is for vulnerability scanning, not authentication.

Public access (D) violates security best practices.

AWS AI document references:

Amazon Q Business Security Overview

Data Protection with AWS KMS

Access Control with AWS IAM

Amazon SageMaker Unified Studio provides a collaborative, secure, and centralized environment for end-to-end data, machine learning, and generative AI development. AWS documentation describes Unified Studio as a single interface where teams can prepare data, build models, train and deploy machine learning solutions, and develop generative AI applications.

In this use case, multiple teams must collaborate in a shared environment. SageMaker Unified Studio supports role-based access control, shared workspaces, and secure resource management, allowing developers to safely collaborate without compromising data or models. AWS highlights that Unified Studio integrates notebooks, pipelines, model development tools, and generative AI workflows into a consistent experience.

The service also supports model sharing, versioning, and reuse, enabling teams to build upon each other’s work. This directly satisfies the requirement to build and share both traditional ML models and generative AI applications securely.

The other options are not suitable. Amazon Lex is a conversational AI service, not a development environment. Amazon Bedrock PartyRock is a no-code generative AI playground and is not intended for enterprise collaboration. Amazon Q Developer focuses on developer productivity and code assistance, not unified AI development environments.

AWS positions SageMaker Unified Studio as the foundation for collaborative AI development at scale, making it the correct choice.

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

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

AWS documentation recommends exposing deployed machine learning models through secure, managed API endpoints to provide controlled and scalable access for external consumers. Creating a secure API endpoint allows customers to invoke the model using standard HTTPS requests while maintaining strict security boundaries.

AWS services such as Amazon SageMaker support deploying models behind managed endpoints that integrate with AWS security features, including authentication, authorization, encryption in transit, throttling, and monitoring. By using an API-based approach, the company can ensure that external customers interact with the model without gaining direct access to the underlying infrastructure or credentials.

The other options introduce significant security risks. Sharing credentials directly violates AWS security best practices and could lead to unauthorized access. Custom authentication scripts in customer applications are difficult to standardize and maintain. Embedding the model directly into customer applications removes centralized control and makes updates and security management impractical.

AWS positions secure API endpoints as the preferred mechanism for exposing ML inference capabilities to external clients, making this the correct solution.

The ML research team needs a mechanism to audit custom ML models while sharing model artifacts with other teams. Amazon SageMaker Model Cards provide a structured way todocument model details, including intended uses, training data, and inference performance, making them ideal for auditing and ensuring transparency when publishing models.

Exact Extract from AWS AI Documents:

From the Amazon SageMaker Developer Guide:

" Amazon SageMaker Model Cards enable you to document critical details about your machine learning models, such as intended uses, training data, evaluation metrics, and inference details. Model Cards support auditing by providing a centralized record that can be reviewed by teams to understand model behavior and limitations. "

(Source: Amazon SageMaker Developer Guide, SageMaker Model Cards)

Detailed Explanation:

Option A: Create documents with the relevant information. Store the documents in Amazon S3.While storing documents in S3 is feasible, it lacks the structured format and integration with SageMaker that Model Cards provide, making it less suitable for auditing purposes.

Option B: Use AWS AI Service Cards for transparency and understanding models.AWS AI Service Cards are not a standard feature in AWS documentation. This option appears to be a distractor and is not a valid solution.

Option C: Create Amazon SageMaker Model Cards with Intended uses and training and inference details.This is the correct answer. SageMaker Model Cards are specifically designed to document model details for auditing, transparency, and collaboration, meeting the team’s requirements.

Option D: Create model training scripts. Commit the model training scripts to a Git repository.Sharing training scripts in a Git repository provides access to code but does not offer a structured auditing mechanism for model details like intended uses or inference performance.

Fairness refers to the absence of bias in AI models. Using non-representative datasets leads to biased predictions, affecting specific demographics unfairly. Explainability, privacy, and transparency are important but not directly related to this scenario. References: AWS Responsible AI Framework.

The manufacturing company needs to create product descriptions in multiple languages, which requires automated language translation. Amazon Translate is a fully managed service that uses machine learning to provide high-quality translation between languages, making it the ideal solution for this task.

Exact Extract from AWS AI Documents:

From the Amazon Translate Developer Guide:

" Amazon Translate is a neural machine translation service that delivers fast, high-quality, and affordable language translation. It can be used to automatically translate text, such as product descriptions, into multiple languages to reach a global audience. "

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

Detailed Explanation:

Option A: Amazon TranslateThis is the correct answer. Amazon Translate automates the translation of text into multiple languages, directly addressing the company’s need to create product descriptions in different languages.

Option B: Amazon TranscribeAmazon Transcribe converts speech to text, which is unrelated to translating text into multiple languages. This option is incorrect.

Option C: Amazon KendraAmazon Kendra is an intelligent search service that uses machine learning to provide answers from documents, not for translating text. This option is irrelevant.

Option D: Amazon PollyAmazon Polly is a text-to-speech service that generates spoken audio from text, not for translating text into other languages. This option does not meet the requirements.

The company wants to enhance the response quality of an LLM for complex problem-solving tasks requiring detailed reasoning and step-by-step explanations. Chain-of-thought prompting encourages the LLM to break down the problem into intermediate steps, providing a clear reasoning process before arriving at the final answer, which is ideal for this requirement.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Chain-of-thought prompting improves the reasoning capabilities of large language models by encouraging them to break down complex tasks into intermediate steps, providing a step-by-step explanation that leads to the final answer. This technique is particularly effective for problem-solving tasks requiring detailed reasoning. "

(Source: AWS Bedrock User Guide, Prompt Engineering Techniques)

Detailed Explanation:

Option A: Few-shot promptingFew-shot prompting provides a few examples to guide the LLM but does not explicitly encourage step-by-step reasoning or detailed explanations.

Option B: Zero-shot promptingZero-shot prompting relies on the LLM’s pre-trained knowledge without examples, making it less effective for complex tasks requiring detailed reasoning.

Option C: Directional stimulus promptingDirectional stimulus prompting is not a standard technique in AWS documentation, likely a distractor, and does not address step-by-step reasoning.

Option D: Chain-of-thought promptingThis is the correct answer. Chain-of-thought prompting enhances response quality for complex tasks by guiding the LLM to reason step-by-step, providing detailed explanations.

The correct answer is regression. In machine learning, regression models are designed to predict continuous numerical values based on input features. Common use cases include predicting house prices, sales forecasting, temperature trends, or medical risk scores. According to AWS SageMaker documentation, regression tasks fall under supervised learning where the output is a real-valued number rather than a class label. For instance, linear regression is one of the most commonly used models for predicting a single continuous output. By contrast, diffusion models are typically used in generative image tasks, transformers are architectures (not specific to numeric output), and multi-modal models process various data types like text, images, and audio. Only regression models are purpose-built for making precise numeric predictions, which aligns with AWS best practices when the output is a quantity, not a category.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Regression Models

Amazon SageMaker Built-in Algorithms – Linear Learner (Regression and Classification)

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

The scenario where a student copies content from generative AI to write essays represents the challenge of plagiarism in responsible AI use.

Plagiarism:

Occurs when someone uses content generated by AI (or any source) without proper attribution, claiming it as their own.

This is a key challenge with generative AI models, which can produce human-like text that might be misused for academic or other purposes.

Why Option C is Correct:

Represents Unauthorized Use: Copying content directly from AI without attribution is a clear case of plagiarism.

Ethical Concern: Highlights the ethical considerations around using AI-generated content responsibly.

Why Other Options are Incorrect:

A. Toxicity: Refers to harmful or offensive content generation, not content copying.

B. Hallucinations: When AI generates incorrect or nonsensical information, not plagiarism.

D. Privacy: Involves the misuse or exposure of personal information, not copying content.

Chain-of-thought prompting is a prompt engineering technique where you instruct the model to explain its reasoning step by step, which is particularly useful for tasks involving logic, math, or reasoning.

A is correct: Asking the model to " explain its reasoning step by step " directly invokes chain-of-thought prompting, as documented in AWS and generative AI literature.

B is unrelated (prompt injection is a security concern).

C (few-shot) provides examples, but doesn’t specifically require step-by-step reasoning.

D (templating) is about structuring the prompt format.

" Chain-of-thought prompting elicits step-by-step explanations from LLMs, which improves performance on complex reasoning tasks. "

(Reference: Amazon Bedrock Prompt Engineering Guide, AWS Certified AI Practitioner Study Guide)

The correct answer is D. Amazon Bedrock Agents are used to orchestrate and execute complex workflows by connecting foundation models with APIs, databases, and tools. According to AWS documentation, agents interpret user inputs, plan the necessary steps, call external APIs or systems, and return structured results. This allows the model to go beyond text generation into full automation workflows—such as booking tasks, querying internal systems, or summarizing reports. Option A describes multi-modal models, B refers to prompt tuning, and C misstates control delegation; agents act autonomously based on model reasoning. Thus, Bedrock Agents function as intelligent orchestrators, handling multi-step task execution through integrated tool use.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Agents Overview

AWS Generative AI Best Practices – Workflow Orchestration

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

Amazon Comprehend Medical is designed for processing medical records and extracting key clinical entities, useful for summaries. Per the AWS Comprehend Medical documentation:

“Amazon Comprehend Medical enables extraction of relevant medical information from unstructured clinical text such as medications, conditions, and relationships, making it ideal for summarization tasks.”

Amazon Transcribe is the correct solution for converting audio from customer calls into text, allowing the company to analyze and extract key information from the conversations.

Amazon Transcribe:

It is a fully managed automatic speech recognition (ASR) service that converts speech into text, making it easier to perform text-based analysis on audio data.

After transcribing the audio, further analysis can be performed using other AWS services like Amazon Comprehend to extract insights such as sentiment, key phrases, or entities.

Why Option B is Correct:

Conversion to Text: Transcribing audio recordings is the first step in gaining insights from spoken conversations, allowing for further processing.

Enables Further Analysis: Once the audio is transcribed into text, other tools and services can be used to analyze the content more deeply.

Why Other Options are Incorrect:

A. Amazon Lex: Is used for building conversational interfaces, not for transcribing or analyzing audio from customer calls.

C. Amazon SageMaker Model Monitor: Monitors ML models for bias and data drift, not for audio analysis.

D. Amazon Comprehend: Can analyze text but cannot transcribe audio; it would be used after transcription is completed.

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 verified answer is C. Incorporating continuous human feedback across model development, training, and deployment phases and using performance evaluation to improve model accuracy. The question asks for human-in-the-loop improvement throughout the ML lifecycle, not a one-time review and not fully automated correction. AWS AI Practitioner guidance describes the foundation model lifecycle as including data selection, model selection, pre-training, fine-tuning, evaluation, deployment, and feedback. Because feedback is part of the lifecycle, human review should not be limited to the first training stage only.

AWS generative AI lifecycle guidance also emphasizes continuous improvement and feedback loops. It explains that operationalizing a generative AI application is not a one-time event, but an ongoing process driven by real-world usage, feedback systems, automated feedback loops, direct user feedback mechanisms, and strategic human-in-the-loop interventions. This supports option C because it combines human feedback across phases with performance evaluation to improve model behavior and accuracy over time.

Option A is incorrect because it removes human intervention. Automated testing is valuable, but it is not human-in-the-loop. Option B is incorrect because collecting human feedback only during initial training is too narrow. It ignores post-training evaluation, deployment monitoring, user feedback, drift, and iterative improvement. Option D is incorrect because it relies on automated reinforcement learning and predefined metrics without human oversight. That again contradicts the “human-in-the-loop” requirement.

The strongest clue is the phrase “throughout the ML lifecycle.” A correct human-in-the-loop strategy must include human review, human feedback, and evaluation during development, training, deployment, and ongoing improvement. Therefore, option C is the only answer that satisfies both parts of the requirement: continuous human involvement and lifecycle-based model improvement.

The correct answer is A because adversarial prompting is a defensive technique used to identify and protect against prompt injection attacks in large language models (LLMs). In adversarial prompting, developers intentionally test the model with manipulated or malicious prompts to evaluate how it behaves under attack and to harden the system by refining prompts, filters, and validation logic.

From AWS documentation:

" Adversarial prompting is used to evaluate and defend generative AI models against harmful or manipulative inputs (prompt injections). By testing with adversarial examples, developers can identify vulnerabilities and apply safeguards such as Guardrails or context filtering to prevent model misuse. "

Prompt injection occurs when an attacker tries to override system or developer instructions within a prompt, leading the model to disclose restricted information or behave undesirably. Adversarial prompting helps uncover and mitigate these risks before deployment.

Explanation of other options:

B. Zero-shot prompting provides no examples and does not protect against injection attacks.

C. Least-to-most prompting is a reasoning technique used to break down complex problems step-by-step, not a security measure.

D. Chain-of-thought prompting encourages detailed reasoning by the model but can actually increase exposure to prompt injection if not properly constrained.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Practices – Prompt Injection and Safety Testing

Amazon Bedrock Developer Guide – Secure Prompt Design and Evaluation

AWS Generative AI Security Whitepaper – Adversarial Testing and Guardrails

The verified answer is A. AWS Audit Manager. The requirement is recurring compliance assessments with documented evidence mapped to regulatory frameworks. AWS documentation states that AWS Audit Manager helps customers continually audit AWS usage to simplify risk and compliance management. It automates evidence collection so customers can assess whether policies, procedures, and controls are operating effectively. AWS also states that Audit Manager provides prebuilt frameworks that structure and automate assessments for compliance standards and regulations.

The key phrase is “documented evidence mapped to regulatory frameworks.” AWS Audit Manager creates assessments from frameworks, automatically runs resource assessments, collects data from in-scope AWS accounts, transforms that data into audit-friendly evidence, and attaches it to relevant controls. That is the exact service function being tested. AWS also explains that Audit Manager can generate reports for auditors and supports prebuilt frameworks for standards such as PCI DSS, GDPR, HIPAA, SOC 2, and AWS operational best practices.

AWS Trusted Advisor is incorrect because Trusted Advisor provides recommendations for cost optimization, performance, security, fault tolerance, service quotas, and operational excellence. It is not a compliance-evidence automation service.

AWS Secrets Manager is incorrect because it stores, rotates, and manages secrets such as database credentials and API keys. It does not automate compliance assessments.

Amazon Inspector is incorrect because it scans workloads for software vulnerabilities and unintended network exposure. It is security-focused, but it does not create recurring evidence-mapped compliance assessments.

Therefore, the correct service is AWS Audit Manager.

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 B – Enable model invocation logging in Amazon Bedrock. AWS Bedrock provides native functionality to log all model invocations, including input prompts, parameters, and generated outputs, to Amazon CloudWatch Logs or S3. According to AWS documentation, this feature helps developers monitor model usage, analyze errors, and audit for compliance. Unlike CloudTrail or Audit Manager, which record API events and compliance data respectively, invocation logging captures real inference transactions. EventBridge is used for event routing, not persistent log storage. Bedrock’s logging feature ensures complete traceability for debugging, usage analytics, and governance in accordance with Responsible AI principles.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Model Invocation Logging

AWS Responsible AI Documentation – Monitoring and Auditability

The correct answer is B – Use Amazon Bedrock batch inference, which allows asynchronous generation of large-scale model outputs through APIs without requiring low-latency performance. According to AWS Bedrock documentation, batch inference is ideal for high-volume workloads that can tolerate delay, such as bulk content generation or summarization jobs. Unlike real-time inference, it processes requests in bulk, reducing cost and operational load. AWS handles the queuing, processing, and scaling automatically. Bedrock Agents (option C) are for workflow orchestration, not large-scale generation. AWS Lambda (option D) can automate tasks but is not optimized for high-volume LLM calls. Batch inference provides cost efficiency, scalability, and simplicity for delayed, asynchronous generation needs.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Batch Inference

AWS ML Specialty Study Guide – Scalable Inference Options

The most direct business KPI for sales performance is conversion rate (percentage of users who purchase after AI assistant interaction).

Number of interactions (B) shows engagement, not sales impact.

Sentiment analysis (C) shows customer satisfaction but not revenue impact.

NLU accuracy (D) is a technical metric, not a business outcome.

???? Reference:

AWS Generative AI Use Cases – Measuring Business Value

Amazon CloudWatch is designed for real-time monitoring of applications and infrastructure. It supports metrics and logs for ML model performance and resource utilization. According to the AWS Certified AI Practitioner Study Guide:

“Amazon CloudWatch is a monitoring service that provides data and actionable insights to monitor your ML workloads and applications in real time, ensuring performance and scalability.”

The company wants an AI application to help employees check open customer claims, identify claim details, and access related documents. Agents for Amazon Bedrock can automate tasks by interacting with external systems, while Amazon Bedrock knowledge bases provide a repository of information (e.g., claim details and documents) that the agent can query to respond to employee requests, making this the best solution.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Agents for Amazon Bedrock enable developers to build applications that can perform tasks by interacting with external systems and data sources. When paired with Amazon Bedrock knowledge bases, agents can access structured and unstructured data, such as documents or databases, to provide detailed responses for use cases like customer service or claims management. "

(Source: AWS Bedrock User Guide, Agents and Knowledge Bases)

Detailed Explanation:

Option A: Use Agents for Amazon Bedrock with Amazon Fraud Detector to build the application.Amazon Fraud Detector is for detecting fraudulent activities, not for managing customer claims or accessing documents. This option is irrelevant.

Option B: Use Agents for Amazon Bedrock with Amazon Bedrock knowledge bases to build the application.This is the correct answer. Agents for Amazon Bedrock can interact with knowledge bases to retrieve claim details and documents, enabling employees to check open claims and access relevant information.

Option C: Use Amazon Personalize with Amazon Bedrock knowledge bases to build the application.Amazon Personalize is for building recommendation systems, not for retrieving claim details or documents. This option does not meet the requirements.

Option D: Use Amazon SageMaker AI to build the application by training a new ML model.Training a new ML model on SageMaker is unnecessary and complex for this use case, as the task can be efficiently handled by Agents and knowledge bases on Amazon Bedrock.

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

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Knowledge Bases

AWS Generative AI Best Practices – RAG Patterns for Enterprise Search

The correct answer is C – Use a negative prompt. Negative prompts instruct a generative image model to avoid certain features, objects, or styles in the output. This technique is fully supported by models like Amazon Nova Canvas on Bedrock, which are based on diffusion or image generation architectures. According to AWS documentation, negative prompts refine output control by telling the model what not to include, thereby improving brand alignment, compliance, or creative direction. A higher temperature increases randomness, not control. A detailed prompt helps, but without exclusion instructions, the model may still include unwanted elements. Changing the model may yield better output but doesn’t directly solve this control requirement. Negative prompts are purpose-built for this scenario.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Prompt Engineering for Image Models

AWS Generative AI Guide – Controlled Generation with Negative Prompts

The correct answer is D – Classification. In this scenario, the goal is to assign each social media review to one of three predefined categories: positive, negative, or neutral. According to AWS documentation, classification models are used when “inputs must be mapped to one label from a fixed set of possible labels.” Sentiment analysis is one of the most common NLP classification tasks and is supported in Amazon Comprehend, Amazon SageMaker, and Amazon Bedrock. Open-ended generation produces free-form text and is not appropriate for categorical outputs. Summarization condenses long-form content, and machine translation converts text across languages. Only classification aligns with sentiment detection, enabling the model to learn sentiment cues such as emotional wording or tone markers. AWS highlights sentiment classification as a key use case for supervised learning with text data.

Referenced AWS Documentation:

Amazon Comprehend Documentation – Sentiment Classification

AWS ML Specialty Guide – Classification Algorithms

Domain adaptation fine-tuning involves training a foundation model (FM) further using a specific dataset that includes domain-specific terminology and content, such as scientific terms in research papers. This process allows the model to better understand and handle complex terminology, improving its performance on specialized tasks.

Option B (Correct): " Use domain adaptation fine-tuning to adapt the FM to complex scientific terms " : This is the correct answer because fine-tuning the model on domain-specific data helps it learn and adapt to the specific language and terms used in the research papers, resulting in better performance.

Option A: " Use few-shot prompting to define how the FM can answer the questions " is incorrect because while few-shot prompting can help in certain scenarios, it is less effective than fine-tuning for handling complex domain-specific terms.

Option C: " Change the FM inference parameters " is incorrect because adjusting inference parameters will not resolve the issue of the model ' s lack of understanding of complex scientific terminology.

Option D: " Clean the research paper data to remove complex scientific terms " is incorrect because removing the complex terms would result in the loss of important information and context, which is not a viable solution.

AWS AI Practitioner References:

Domain Adaptation in Amazon Bedrock: AWS recommends fine-tuning models with domain-specific data to improve their performance on specialized tasks involving unique terminology.

The least operational overhead comes from automated tools that can scan and evaluate LLM outputs for toxicity. AWS and SageMaker JumpStart support integrations with automatic evaluation tools and APIs (such as Amazon Comprehend or third-party toxicity classifiers).

B is correct: Automated evaluation provides quick, scalable, and repeatable analysis, requiring minimal human intervention.

A and C require manual effort, increasing operational overhead.

D (RLHF) is resource-intensive and not designed for rapid, automated model comparison.

" Automated evaluation can quickly assess generated text for specific attributes like toxicity, sentiment, or compliance using pre-trained classifiers, reducing human involvement and operational complexity. "

(Reference: AWS SageMaker JumpStart Evaluation, AWS AI Practitioner Guide)

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.

Building and training a generative AI model from scratch provides the company with the most ownership and control over security responsibilities. In this scenario, the company is responsible for all aspects of the security of the data, the model, and the infrastructure.

Option D (Correct): " Building and training a generative AI model from scratch by using specific data that a customer owns " : This is the correct answer because it involves complete ownership of the model, data, and infrastructure, giving the company the highest level of responsibility for security.

Option A: " Using a third-party enterprise application that has embedded generative AI features " is incorrect as the company has minimal control over the security of the AI features embedded within a third-party application.

Option B: " Building an application using an existing third-party generative AI foundation model (FM) " is incorrect because security responsibilities are shared with the third-party model provider.

Option C: " Refining an existing third-party generative AI FM by fine-tuning the model with business-specific data " is incorrect as the foundation model and part of the security responsibilities are still managed by the third party.

AWS AI Practitioner References:

Generative AI Security Scoping Matrix on AWS: AWS provides a security responsibility matrix that outlines varying levels of control and responsibility depending on the approach to developing and using AI models.

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.

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

Token Reduction Strategy:

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

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

Why Option B is Correct:

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

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

Why Other Options are Incorrect:

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

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

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

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Model Monitor detects:

Data drift

Concept drift

Model quality degradation

AWS MLOps guidance recommends Model Monitor to:

Continuously evaluate production models

Trigger alerts when performance deviates from baselines

Maintain long-term model reliability

Why the other options are incorrect:

Amazon A2I (A) adds human review workflows.

Rekognition (C) is an image analysis service.

Trusted Advisor (D) provides cost and security recommendations.

AWS AI document references:

Amazon SageMaker Model Monitor Overview

Detecting Model Drift on AWS

Production ML Monitoring Best Practices

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Inference latency measures the time it takes for a model to:

Receive an input request

Process the request

Return an output

AWS performance guidance emphasizes inference latency as a critical metric for real-time and user-facing AI applications.

Why the other options are incorrect:

Model size (A) refers to number of parameters.

Context window (C) defines input length capacity.

Fine-tuning (D) is a customization process.

AWS AI document references:

Foundation Model Performance Metrics

Latency Considerations for AI Applications

Optimizing Inference on AWS

Use Case 1:

The company’s chatbot needs predictions from the LLM to understand users ' intent with minimal latency.

→ Answer: Real-time inference

Chatbots require low-latency, immediate responses to user input. Real-time inference is ideal for these interactive use cases.

Use Case 2:

A data processing job needs to query the LLM to process gigabytes of text files on weekends.

→ Answer: Batch transform

Batch transform is designed for asynchronous, high-throughput jobs where latency is not critical. It’s ideal for scheduled or large-scale processing like weekend batch jobs on large datasets.

Use Case 3:

The company’s engineering team needs to create an API that can process small pieces of text content and provide low-latency predictions.

→ Answer: Real-time inference

An API requiring fast response time for small content sizes is best served by real-time inference to meet latency requirements.

The company is developing an ML model to predict customer churn, a binary classification task (churn or no churn). The F1 score is an evaluation metric that balances precision and recall, making it suitable for assessing the performance of binary classification models, especially when dealing with imbalanced datasets, which is common in churn prediction.

Exact Extract from AWS AI Documents:

From the Amazon SageMaker Developer Guide:

" The F1 score is a metric for evaluating binary classification models, combining precision and recall into a single value. It is particularly useful for tasks like churn prediction, where class imbalance may exist, ensuring the model performs well on both positive and negative classes. "

(Source: Amazon SageMaker Developer Guide, Model Evaluation Metrics)

Detailed Explanation:

Option A: F1 scoreThis is the correct answer. The F1 score is ideal for binary classification tasks like churn prediction, as it measures the model’s ability to correctly identify both churners and non-churners.

Option B: Mean squared error (MSE)MSE is used for regression tasks to measure the average squared difference between predicted and actual values, not for binary classification.

Option C: R-squaredR-squared is a metric for regression models, indicating how well the model explains the variability of the target variable. It is not applicable to classification tasks.

Option D: Time used to train the modelTraining time is not an evaluation metric for model performance; it measures the duration of training, not the model’s accuracy or effectiveness.

Foundation models have a context window (max tokens), which limits the size of the input text (prompt + instructions).

If the input (e.g., a very long book) exceeds this limit, the model cannot process it, causing failure.

Temperature (A) and Top P (C) control randomness, not input size.

Fine-tuning (B) is irrelevant to input truncation failures.

???? Reference:

AWS Documentation – Amazon Bedrock Model Parameters (context size limits)

The correct answer is B because Amazon Augmented AI (Amazon A2I) allows developers to integrate human review workflows into ML systems. It supports defining confidence thresholds, such that only low-confidence predictions are sent to human reviewers.

From AWS documentation:

" Amazon A2I provides built-in human review workflows for ML predictions. You can configure confidence thresholds to determine when human review is triggered, enabling continual adjustment based on accuracy needs. "

This supports use cases where business decisions (like financial approvals) require manual oversight for edge cases.

Explanation of other options:

A. Amazon Personalize is used for recommendation systems, not human review.

C. Amazon Inspector is for security assessment and vulnerability scanning.

D. AWS Audit Manager is used for compliance audits, not ML prediction reviews.

Referenced AWS AI/ML Documents and Study Guides:

Amazon A2I Developer Guide – Confidence Threshold Configuration

AWS ML Specialty Guide – Human-in-the-Loop Systems

AWS Responsible AI Documentation – Review and Escalation Workflows

Amazon Bedrock is a service that provides foundational models for building generative AI applications. When creating an application for children, it is crucial to ensure that the generated content is appropriate for the target audience. " Guardrails " in Amazon Bedrock provide mechanisms to control the outputs and topics of generated content to align with desired safety standards and appropriateness levels.

Option C (Correct): " Guardrails for Amazon Bedrock " : This is the correct answer because guardrails are specifically designed to help users enforce content moderation, filtering, and safety checks on the outputs generated by models in Amazon Bedrock. For a children’s application, guardrails ensure that all content generated is suitable and appropriate for the intended audience.

Option A: " Amazon Rekognition " is incorrect. Amazon Rekognition is an image and video analysis service that can detect inappropriate content in images or videos, but it does not handle text or story generation.

Option B: " Amazon Bedrock playgrounds " is incorrect because playgrounds are environments for experimenting and testing model outputs, but they do not inherently provide safeguards to ensure content appropriateness for specific audiences, such as children.

Option D: " Agents for Amazon Bedrock " is incorrect. Agents in Amazon Bedrock facilitate building AI applications with more interactive capabilities, but they do not provide specific guardrails for ensuring content appropriateness for children.

AWS AI Practitioner References:

Guardrails in Amazon Bedrock: Designed to help implement controls that ensure generated content is safe and suitable for specific use cases or audiences, such as children, by moderating and filtering inappropriate or undesired content.

Building Safe AI Applications: AWS provides guidance on implementing ethical AI practices, including using guardrails to protect against generating inappropriate or biased content.

The verified answer is C. Use batch inference with Amazon Bedrock. The workload has three decisive characteristics: it is repetitive, it processes a large volume of requests, and it does not require immediate responses. AWS documentation states that with Amazon Bedrock batch inference, users can submit multiple prompts and generate responses asynchronously. It also states that batch inference helps process a large number of requests efficiently by sending a single request and generating responses in an Amazon S3 bucket. That directly matches the weekly generation of exercise routines for all users.

AWS also explains that after the batch job is complete, the output files can be retrieved from Amazon S3, and batch inference can improve model inference performance on large datasets. This is the right architecture for offline or scheduled workloads where immediate response latency is not required.

Amazon Bedrock AgentCore is incorrect because AgentCore is for building, running, and managing agents, tools, memory, gateways, and agent workflows. The problem is not agent orchestration; it is cost-efficient high-volume offline inference.

Real-time inference with Amazon Bedrock on-demand endpoints is incorrect because real-time inference is better for interactive applications where users need immediate responses. The question explicitly says immediate responses are not required.

Real-time inference with SageMaker AI hosted endpoints is also incorrect for the same reason. Hosted endpoints are appropriate for low-latency inference requests, but this workload is scheduled and large-volume.

Therefore, Amazon Bedrock batch inference is the best solution.

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 F1 score is the harmonic mean of precision and recall, making it a balanced metric for evaluating model performance when there is an imbalance between false positives and false negatives. Speed, cost, and energy efficiency are unrelated to the F1 score. References: AWS Foundation Models Guide.

The correct answer is B – Adaptability and responsiveness, which are core strengths of generative AI models such as the foundation models available in Amazon Bedrock. According to AWS documentation, generative AI systems excel at understanding natural language variations, meaning they can interpret different phrasings, synonyms, sentence structures, and conversational styles while still generating contextually consistent answers. This capability comes from pretraining on diverse natural language corpora, allowing models to generalize across multiple linguistic patterns. AWS highlights that generative AI models are designed to handle “flexible, dynamic, and conversational inputs” and provide responses grounded in understanding user intent rather than matching exact keywords. Options A and D describe infrastructure performance characteristics, not the reasoning ability required for this use case. Option C (deterministic outputs) is incorrect because LLMs are inherently probabilistic and not fixed unless using advanced constraints. Therefore, generative AI’s adaptability to varied user phrasing makes it ideal for assistants requiring consistent, intent-based responses.

Referenced AWS Documentation:

Amazon Bedrock Developer Guide – Foundation Model Capabilities

AWS Generative AI Best Practices – Natural Language Understanding

Fine-tuning is the process of training a pre-trained LLM with a labeled dataset specific to a desired task—in this case, mapping user messages to JSON outputs. Fine-tuning leverages supervised learning to specialize the model’s outputs.

C is correct:

“Fine-tuning is a supervised learning approach in which a model is further trained on a custom, labeled dataset to adapt to a specific use case.”

(Reference: Amazon Bedrock Fine-Tuning, AWS Certified AI Practitioner Study Guide)

A is incorrect—unsupervised learning does not use labeled data.

B (continued pre-training) uses unlabeled data.

D (RLHF) uses reward signals and human feedback, not direct labeled input/output pairs.

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.

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

Adjusting the prompt is the correct solution to align the LLM outputs with the company ' s expectations for short, specific language responses.

Adjust the Prompt:

Modifying the prompt can guide the LLM to produce outputs that are shorter and tailored to the desired language.

A well-crafted prompt can provide specific instructions to the model, such as " Answer in a short sentence in Spanish. "

Why Option A is Correct:

Control Over Output: Adjusting the prompt allows for direct control over the style, length, and language of the LLM outputs.

Flexibility: Prompt engineering is a flexible approach to refining the model’s behavior without modifying the model itself.

Why Other Options are Incorrect:

B. Choose an LLM of a different size: The model size does not directly impact the response length or language.

C. Increase the temperature: Increases randomness in responses but does not ensure brevity or specific language.

D. Increase the Top K value: Affects diversity in model output but does not align directly with response length or language specificity.

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

Regression predicts continuous numerical values (e.g., stock prices, temperatures).

A is classification (genre selection).

B is clustering.

D is generative AI/computer vision.

???? Reference:

AWS ML Glossary – Regression