Download Full Version AIF-C01 Amazon Web Services Exam

The correct answer is A because each foundation model on Amazon Bedrock (e.g., Claude, Titan, Mistral, Meta Llama) has a different maximum token limit, which defines the maximum number of tokens the model can accept in the prompt and generate in the response.

From AWS documentation:

" Each model in Amazon Bedrock has its own maximum token limit. Prompts exceeding the limit must be truncated or adjusted depending on the selected model. "

Explanation of other options:

B. On-demand inference support is a platform feature that is uniformly supported across models on Bedrock.

C. All Bedrock LLMs support randomness control through temperature and top-p parameters.

D. Amazon Bedrock Guardrails are designed to work across supported models, though specific behaviors may vary slightly.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Model Comparison Guide

AWS Prompt Engineering and LLM Deployment Documentation

AWS ML Specialty Study Guide – Bedrock Model Capabilities

Transfer learning is the correct strategy for adapting pre-trained models for new, related tasks without creating models from scratch.

Transfer Learning:

Involves taking a pre-trained model and fine-tuning it on a new dataset for a related task.

This approach is efficient because it leverages existing knowledge from a model trained on a large dataset, requiring less data and computational resources than training a new model from scratch.

Why Option B is Correct:

Adaptation of Pre-trained Models: Allows for adapting existing models to new tasks, which aligns with the company ' s goal of not starting from scratch.

Efficiency and Speed: Speeds up the model development process by building on the knowledge of pre-trained models.

Why Other Options are Incorrect:

A. Increase the number of epochs: Does not address the strategy of reusing pre-trained models.

C. Decrease the number of epochs: Similarly, does not apply to adapting pre-trained models.

D. Use unsupervised learning: Does not involve using pre-trained models for new tasks.

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.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Clarify provides tools for:

Model explainability

Bias detection

Transparency through metrics, reports, and explanations

For regulated industries such as healthcare, AWS recommends Clarify to:

Explain model predictions

Demonstrate fairness and accountability

Support regulatory and ethical requirements

Why the other options are incorrect:

Inspector (A) focuses on security vulnerabilities.

Macie (C) focuses on data security and privacy.

Rekognition (D) is for image labeling, not explainability.

AWS AI document references:

Amazon SageMaker Clarify Documentation

Responsible AI on AWS

Explainable AI for Regulated Industries