Newly Released Amazon Web Services AIF-C01 Exam PDF

 Block input prompts or model responses that contain harmful content such as hate, insults, violence, or misconduct:Content filters

 Avoid subjects related to illegal investment advice or legal advice:Denied topics

 Detect and block specific offensive terms:Word filters

 Detect and filter out information in the model’s responses that is not grounded in the provided source information:Contextual grounding check

The company is using a generative AI model on Amazon Bedrock and needs to mitigate undesirable and potentially harmful content in the model’s responses. Amazon Bedrock provides several guardrail mechanisms, including content filters, denied topics, word filters, and contextual grounding checks, to ensure safe and accurate outputs. Each mitigation action in the hotspot aligns with a specific Bedrock filter policy, and each policy must be used exactly once.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

*"Amazon Bedrock guardrails provide mechanisms to control model outputs, including:

Content filters: Block harmful content such as hate speech, violence, or misconduct.

Denied topics: Prevent the model from generating responses on specific subjects, such as illegal activities or advice.

Word filters: Detect and block specific offensive or inappropriate terms.

Contextual grounding check: Ensure responses are grounded in the provided source information, filtering out ungrounded or hallucinated content."*(Source: AWS Bedrock User Guide, Guardrails for Responsible AI)

Detailed Explanation:

Block input prompts or model responses that contain harmful content such as hate, insults, violence, or misconduct: Content filtersContent filters in Amazon Bedrock are designed to detect and block harmful content, such as hate speech, insults, violence, or misconduct, ensuring the model’s outputs are safe and appropriate. This matches the first mitigation action.

Avoid subjects related to illegal investment advice or legal advice: Denied topicsDenied topics allow users to specify subjects the model should avoid, such as illegal investment advice or legal advice, which could have regulatory implications. This policy aligns with the second mitigation action.

Detect and block specific offensive terms: Word filtersWord filters enable the detection and blocking of specific offensive or inappropriate terms defined by the user, making them ideal for this mitigation action focused on specific terms.

Detect and filter out information in the model’s responses that is not grounded in the provided source information: Contextual grounding checkThe contextual grounding check ensures that the model’s responses are based on the provided source information, filtering out ungrounded or hallucinated content. This matches the fourth mitigation action.

Hotspot Selection Analysis:

The hotspot lists four mitigation actions, each with the same dropdown options: "Select...," "Content filters," "Contextual grounding check," "Denied topics," and "Word filters." The correct selections are:

First action: Content filters

Second action: Denied topics

Third action: Word filters

Fourth action: Contextual grounding check

Each filter policy is used exactly once, as required, and aligns with Amazon Bedrock’s guardrail capabilities.

Amazon SageMaker Feature Store is the correct solution for sharing and managing variables (features) across multiple teams during model development.

Amazon SageMaker Feature Store:

A fully managed repository for storing, sharing, and managing machine learning features across different teams and models.

It enables collaboration and reuse of features, ensuring consistent data usage and reducing redundancy.

Why Option A is Correct:

Centralized Feature Management: Provides a central repository for managing features, making it easier to share them across teams.

Collaboration and Reusability: Improves efficiency by allowing teams to reuse existing features instead of creating them from scratch.

Why Other Options are Incorrect:

B. SageMaker Data Wrangler: Helps with data preparation and analysis but does not provide a centralized feature store.

C. SageMaker Clarify: Used for bias detection and explainability, not for managing variables across teams.

D. SageMaker Model Cards: Provide model documentation, not feature management.

When you have a labeled dataset and need to scale a generative AI solution for more complex or diverse product categories, fine-tuning the foundation model with your dataset is the best approach for consistent, accurate tagging.

D is correct:

“Fine-tuning a foundation model with your labeled data allows the model to generalize to new categories and improve tagging accuracy for your inventory.”

(Reference: Amazon Bedrock Fine-Tuning, AWS Generative AI)

A (zero-shot) and B (prompt templates) do not leverage the labeled data or scale as accurately.

C (continued pre-training) uses unlabeled data, not labeled.

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.