Amazon Web Services Updated AIF-C01 Exam Questions and Answers by leonie

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.

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

Provide labeled data to customize a model to improve performance on specific tasks.

Correct Answer: Fine-tuning

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI guidance defines fine-tuning as the process of adapting a pre-trained foundation model using labeled, task-specific data. Fine-tuning adjusts the model’s parameters so it performs better on a particular task, such as classification, summarization, or domain-specific reasoning.

Fine-tuning is commonly used when:

High-quality labeled data is available

The goal is to improve accuracy on a specific task

The base FM already has strong general capabilities

AWS AI Study Guide References:

AWS foundation model customization methods

AWS fine-tuning concepts for generative AI

Provide unlabeled data to customize a foundation model for a specific domain.

Correct Answer: Continued pre-training

Comprehensive and Detailed Explanation (AWS AI documents):

AWS documentation describes continued pre-training as extending the training of a foundation model using large volumes of unlabeled, domain-specific data. This method helps the model better understand domain vocabulary, structure, and context without requiring labeled datasets.

Continued pre-training is useful when:

Large amounts of unlabeled domain data are available

The goal is to improve domain understanding rather than a single task

Labeling data would be expensive or impractical

AWS AI Study Guide References:

AWS generative AI training lifecycle

AWS guidance on domain adaptation using unlabeled data

Transfer knowledge from a larger and more intelligent model to a smaller model.

Correct Answer: Distillation

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI materials define distillation as a technique where a smaller model (student) learns to replicate the behavior of a larger, more capable model (teacher). The goal is to retain most of the performance while reducing model size, cost, and inference latency.

Distillation is commonly used to:

Reduce operational costs

Improve inference speed

Deploy models to resource-constrained environments

AWS AI Study Guide References:

AWS model optimization techniques

AWS knowledge distillation concepts