Comprehensive and Detailed Explanation From Exact AWS AI documents:
The correct technique is fine-tuning, which is explicitly supported by Amazon Bedrock for customizing foundation models using high-quality labeled datasets.
Fine-tuning involves:
Starting with a pre-trained foundation model
Training it further using domain-specific, labeled data
Improving accuracy for specialized tasks, such as product classification, image-based understanding, and specification extraction In this use case:
The company has labeled data
They want to customize model behavior
They require high accuracy and domain adaptation
These conditions match the definition of fine-tuning, not prompt-only methods.
Why the other options are incorrect:
A). Continued pre-training typically requires massive unlabeled datasets and is not the standard customization method exposed in Amazon Bedrock.
B). Creating an agent orchestrates model interactions and tools but does not customize the model's learned parameters.
D). Prompt engineering improves responses through prompt design but does not modify the underlying model weights, making it insufficient for deep domain adaptation.
AWS AI document references (for exact extracts):
Amazon Bedrock Documentation - section on Model customization and fine-tuning AWS Generative AI Study Guide - comparison of prompt engineering vs fine-tuning Foundation Models on AWS - explanation of fine-tuning with labeled datasets

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

Comprehensive and Detailed Explanation From Exact AWS AI documents:
The temperature parameter controls randomness in model outputs.
AWS generative AI guidance explains:
Higher temperature # more randomness and creativity
Lower temperature # more deterministic and predictable outputs
To increase diversity and creativity, the temperature should be increased.
Why the other options are incorrect:
Lower Top K (B) reduces output diversity.
Response length (C) affects size, not creativity.
Prompt length (D) does not directly control randomness.
AWS AI document references:
Inference Parameters for Foundation Models
Controlling Creativity in LLMs
Text Generation Configuration on AWS

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.
References:
AWS Bedrock User Guide: Inference Parameters for Text Generation (https://docs.aws.amazon.com/bedrock
/latest/userguide/model-parameters.html)
AWS AI Practitioner Learning Path: Module on Large Language Models and Inference Configuration Amazon Bedrock Developer Guide: Managing Model Outputs (https://docs.aws.amazon.com/bedrock/latest
/devguide/)

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