AIF-C01 Exam Dumps - AWS Certified AI Practitioner Exam

Transitioning to a new large language model (LLM) on Amazon Bedrock typically involves minimal changes when the new model is pre-trained and available as a foundation model. Since the company is moving from one pre-trained LLM to another, the primary task is to ensure compatibility between the new model's input requirements and the existing application. Adjusting the prompt template is often necessary because different LLMs may have varying prompt formats, tokenization methods, or response behaviors, even for similar tasks like document extraction.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"When switching between foundation models in Amazon Bedrock, you may need to adjust the prompt template to align with the new model’s expected input format and optimize its performance for your use case. Prompt engineering is critical to ensure the model understands the task and generates accurate outputs."

(Source: AWS Bedrock User Guide, Prompt Engineering for Foundation Models)

Detailed Explanation:

Option A: Create a new labeled dataset.Creating a new labeled dataset is unnecessary when transitioning to a new pre-trained LLM, as pre-trained models are already trained on large datasets. This option would only be relevant if the company were training a custom model from scratch, which is not the case here.

Option B: Perform feature engineering.Feature engineering is typically associated with traditional machine learning models, not pre-trained LLMs. LLMs process raw text inputs, and transitioning to a new LLM does not require restructuring input features. This option is incorrect.

Option C: Adjust the prompt template.This is the correct approach. Different LLMs may interpret prompts differently due to variations in training data, tokenization, or model architecture. Adjusting the prompt template ensures the new LLM understands the task (e.g., document extraction) and produces the desired output format. AWS documentation emphasizes prompt engineering as a key step when adopting a new foundation model.

Option D: Fine-tune the LLM.Fine-tuning is not required for transitioning to a new pre-trained LLM unless the company needs to customize the model for a highly specific task. Since the question does not indicate a need for customization beyond document extraction (a common LLM capability), fine-tuning is unnecessary.

ï‚· 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.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Model Monitor detects:

Data drift

Concept drift

Model quality degradation

AWS MLOps guidance recommends Model Monitor to:

Continuously evaluate production models

Trigger alerts when performance deviates from baselines

Maintain long-term model reliability

Why the other options are incorrect:

Amazon A2I (A) adds human review workflows.

Rekognition (C) is an image analysis service.

Trusted Advisor (D) provides cost and security recommendations.

AWS AI document references:

Amazon SageMaker Model Monitor Overview

Detecting Model Drift on AWS

Production ML Monitoring Best Practices

Amazon SageMaker Clarify provides built-in tools to detect bias in data and models, and to generate detailed explainability reports for model predictions, including SHAP values and feature importance.

A is correct:

“Amazon SageMaker Clarify provides bias detection, explainability for ML models, and comprehensive reports to satisfy regulatory and ethical requirements.”

(Reference: Amazon SageMaker Clarify Overview)

B (Data Wrangler) is for data preparation, not bias/explainability.

C (Model Cards) document models, but don’t detect bias or explain predictions.

D (AI Service Cards) provide transparency for AWS AI services, not custom model explainability.

Amazon SageMaker JumpStart is the correct service for quickly deploying and consuming a foundation model (FM) within a team's VPC.

Amazon SageMaker JumpStart:

Provides access to a wide range of pre-trained models and solutions that can be easily deployed and consumed within a VPC.

Designed to simplify and accelerate the deployment of machine learning models, including foundation models.

Why Option B is Correct:

Rapid Deployment: JumpStart allows for quick deployment of models with minimal configuration, directly within a secure VPC environment.

Ease of Use: Provides a user-friendly interface to select and deploy models, reducing the time to value.

Why Other Options are Incorrect:

A. Amazon Personalize: Focuses on creating personalized recommendations, not deploying foundation models.

C. PartyRock: Not a recognized AWS service.

D. Amazon SageMaker endpoints: Endpoints are for deploying specific models, not a feature for quickly starting with pre-trained foundation models.

Amazon SageMaker Model Cards are specifically designed to support transparency, responsible AI, and governance throughout the machine learning lifecycle. According to AWS AI documentation, Model Cards provide a structured way to document critical information about machine learning models, including intended use cases, business context, training data assumptions, evaluation metrics, ethical considerations, and known limitations or risks. This makes Model Cards the correct feature for the requirements described.

AWS emphasizes that Model Cards help organizations meet internal governance standards and external regulatory or compliance expectations by improving model interpretability and accountability. They allow AI practitioners to clearly explain why a model was built, how it was trained, what data it relies on, and what risks or biases may exist. This aligns directly with the need to document business problems, training considerations, and usage risks.

Other options do not fully address these needs. Amazon SageMaker Model Registry focuses on versioning, approval workflows, and deployment tracking of models, but it does not provide comprehensive documentation for transparency or ethical considerations. Amazon SageMaker Model Monitor is designed to detect data drift, bias drift, and performance degradation in production, not to document assumptions or governance details. Model Dashboard offers a centralized view of deployed models and endpoints but does not provide structured, narrative documentation of model intent or risks.

AWS positions Model Cards as a core component of Responsible AI, enabling organizations to promote fairness, explainability, and trust in machine learning systems. By capturing standardized, auditable documentation, Model Cards ensure that stakeholders—including developers, auditors, and business leaders—can understand how a recommendation system should be used and where caution is required.

The correct answer is D because low latency and optimized inference speed are critical for real-time applications. For delivering real-time service quotes, the system must respond in milliseconds or a few seconds at most, making latency a primary concern when choosing the model.

From AWS Bedrock documentation:

"When selecting a foundation model for real-time applications, inference speed and latency are key evaluation metrics to ensure responsive user experiences."

Explanation of other options:

A. Model size affects performance and cost but doesn't directly guarantee low latency.

B. Training data quality is important for accuracy, but it doesn’t address real-time performance requirements.

C. GPU availability matters in infrastructure planning, not in model selection for latency optimization.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Model Selection Guide – Real-time Use Case Considerations

AWS ML Specialty Guide – Foundation Model Performance Criteria

The correct answer is D – F1 score, which is the harmonic mean of precision and recall. AWS documentation states that the F1 score is the preferred metric when evaluating ML models trained on imbalanced datasets, where one class appears significantly more often than others. Accuracy becomes misleading in these situations because a model can achieve high accuracy simply by predicting the majority class. Precision alone measures correctness of positive predictions, while recall measures completeness—neither fully captures class balancing performance. The F1 score provides a combined measurement that reflects how well the model identifies minority classes while avoiding excessive false positives. AWS’s ML Specialty Guide recommends using F1 for classification tasks where “class distribution is uneven or where both false negatives and false positives matter.” This metric provides a fairer assessment of overall model performance across all class categories.

Referenced AWS Documentation:

AWS Certified Machine Learning Specialty Guide – Metrics for Imbalanced Classes

Amazon SageMaker Developer Guide – Evaluating Classification Models