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 verified answer is D. Amazon Nova Premier. The decisive requirement is the combination of a 1 million-token context window, multimodal document understanding, chart analysis, and video input. AWS documentation identifies Amazon Nova Premier as the most capable multimodal Amazon Nova understanding model. It supports text, image, and video inputs and generates text output. AWS also lists Amazon Nova Premier with a 1M context window, while Amazon Nova Pro and Amazon Nova Lite support 300k, and Amazon Nova Micro supports 128k and is text-only. Because the company’s legal documents are up to 1 million tokens long, Nova Premier is the only listed option that satisfies the context-length requirement.

AWS documentation also states that Amazon Nova Premier has a supported context length of 1 million tokens, which AWS equates to 1 million tokens of text, 500 images, or 90 minutes of video. The same documentation explains that Nova Premier excels at question answering on long documents. This directly matches the research company’s need to analyze very long legal documents and ingest video summaries for compliance reporting.

Amazon Nova Micro is incorrect because it is a text-only model and has a smaller context window. It cannot process embedded high-resolution charts or video inputs. Amazon Nova Lite is incorrect because it is multimodal, but its context window is 300k, which is below the 1 million-token requirement. Amazon Nova Pro is also incorrect for the same reason: it is highly capable and multimodal, but its context window is 300k rather than 1M. The requirement is not simply “multimodal”; it is long-context multimodal analysis at the 1 million-token scale. Therefore, the only model that fully meets the requirements is Amazon Nova Premier.

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Amazon Bedrock Prompt Management is designed to allow practitioners to create, version, store, and reuse prompts and system instructions when working with foundation models. It enables consistent reuse of contextual instructions across repeated interactions and applications.

Why the other options are incorrect:

Knowledge Bases store and retrieve external data, not reusable system instructions.

Guardrails enforce safety and policy controls, not prompt reuse.

Playgrounds are for experimentation and testing, not long-term prompt storage.

AWS AI Study Guide References:

Amazon Bedrock prompt management capabilities

AWS best practices for prompt engineering and reuse

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

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Bedrock provides access to multiple foundation models from different providers and enables customers to evaluate, compare, and select the most appropriate model for their generative AI use cases.

Amazon Bedrock:

Offers a choice of foundation models

Supports model evaluation and customization

Abstracts infrastructure management

Why the other options are incorrect:

Amazon Personalize (A) is a recommendation service.

Amazon Q Developer (C) is a coding assistant.

Amazon Rekognition (D) is an image and video analysis service.

AWS AI document references:

Amazon Bedrock Overview

Choosing Foundation Models on AWS

Generative AI Model Selection Guidance

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

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation – Bias Detection

The requirement is to improve the accuracy of a natural language generation (NLG) model that relies on rapidly changing inventory data. Let’s evaluate the options:

A. Transfer learning: This involves pre-training a model on a large dataset and fine-tuning it for a specific task. While effective for general model improvement, it does not specifically address the challenge of incorporating rapidly changing inventory data into the model’s responses.

B. Federated learning: This technique trains models across decentralized devices while keeping data localized, primarily for privacy purposes. It is not designed to handle rapidly changing data or improve NLG model accuracy in this context.

C. Retrieval Augmented Generation (RAG): RAG combines a language model with a retrieval mechanism that fetches relevant, up-to-date information (e.g., inventory data) from an external source during inference. This is ideal for scenarios with dynamic data, as it ensures the model’s responses are grounded in the latest information, improving accuracy.

D. One-shot prompting: This involves providing a single example to guide the model’s output. While useful for specific tasks, it does not scale well for rapidly changing data or ensure consistent accuracy with dynamic inventory updates.

Exact Extract Reference: According to AWS documentation on generative AI techniques, “Retrieval Augmented Generation (RAG) enhances large language models by retrieving relevant documents or data at inference time, enabling the model to generate accurate and contextually relevant responses, especially for dynamic or frequently updated datasets.” (Source: AWS Generative AI Glossary, https://aws.amazon.com/what-is/retrieval-augmented-generation/). This directly addresses the need for accuracy with rapidly changing inventory data.

RAG is the most suitable technique for this scenario, as it allows the model to access and incorporate the latest inventory data, making C the correct answer.

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.