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

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI best practices emphasize that bias should be detected, measured, mitigated, and monitored throughout the ML lifecycle , especially for sensitive domains such as healthcare. When biased outcomes are observed, AWS guidance recommends addressing bias at the data and model level , not only at the output level.

Using Amazon SageMaker Clarify aligns directly with AWS Responsible AI principles because it is designed to:

Detect and quantify bias in datasets and model predictions across sensitive attributes such as demographic groups

Provide pre-training and post-training bias metrics , allowing practitioners to identify where bias originates

Support data-centric mitigation , including improving dataset balance and representativeness

After identifying bias with SageMaker Clarify, collecting additional balanced training data and retraining the model helps ensure that:

The model learns from a more representative dataset

Disparate treatment recommendations based on demographics are reduced

Fairness is improved while maintaining clinical accuracy

Why the other options are not sufficient or aligned with AWS best practices:

B. Prompt engineering can influence outputs but does not address underlying data or model bias and is not sufficient for regulated, high-risk domains like healthcare.

C. Content filtering removes outputs after generation but does not prevent biased decision-making by the model itself.

D. Separate FM endpoints by demographic group increases the risk of reinforcing bias and violates fairness principles rather than mitigating them.

AWS AI Study Guide References:

AWS Responsible AI principles: Fairness and Governance

Amazon SageMaker Clarify: bias detection and mitigation

AWS best practices for ML in high-risk domains such as healthcare

AWS documentation defines prompt injection as a security and safety risk in which a user crafts input designed to override, manipulate, or bypass system-level instructions, safeguards, or intended model behavior . The example provided is a classic prompt injection attempt, where the user explicitly instructs the AI assistant to ignore prior rules and operate without restrictions.

In this scenario, the attacker is not exploiting training data or causing factual errors, but rather attempting to change the control flow and behavior of the AI system through malicious or manipulative prompts. AWS identifies prompt injection as a critical risk for generative AI systems, especially those exposed to end users through chat interfaces, APIs, or customer-facing applications.

The other options do not apply. Data bias relates to skewed or unfair training data. Hallucination refers to generating incorrect or fabricated information. Data exposure involves leaking sensitive or private data. None of these describe an attempt to override system instructions.

AWS recommends multiple mitigation strategies for prompt injection risks, including instruction hierarchy enforcement, prompt isolation, input validation, output filtering, and grounding responses using techniques such as Retrieval Augmented Generation . AWS also emphasizes the importance of clearly separating system instructions from user inputs to prevent unauthorized behavior changes.

Prompt injection is categorized by AWS as part of Responsible AI and security governance , highlighting the need for robust guardrails when deploying AI assistants in production. Therefore, the correct answer is prompt injection.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

The F1 score is a standard evaluation metric that represents the harmonic mean of precision and recall.

In AWS ML evaluation guidance:

Precision measures correctness of positive predictions

Recall measures coverage of actual positive cases

F1 score balances both metrics into a single performance indicator

This makes the F1 score particularly useful when evaluating classification performance of foundation models.

Why the other options are incorrect:

Speed (B) is a latency metric.

Cost (C) measures operational efficiency.

Energy efficiency (D) is unrelated to predictive accuracy.

AWS AI document references:

Model Evaluation Metrics on AWS

Classification Performance Measurement

Amazon SageMaker Evaluation Best Practices

The ecommerce company is deploying a chatbot that needs safeguards to filter harmful content from input prompts and responses. Amazon Bedrock Guardrails provide mechanisms to ensure responsible AI usage by filtering harmful content, such as hate speech, violence, or misinformation, making it the appropriate feature for this requirement.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Amazon Bedrock Guardrails enable developers to implement safeguards for generative AI applications, such as chatbots, by filtering harmful content in input prompts and model responses. Guardrails include content filters, word filters, and denied topics to ensure safe and responsible outputs. "

(Source: AWS Bedrock User Guide, Guardrails for Responsible AI)

Detailed Explanation:

Option A: Amazon Bedrock GuardrailsThis is the correct answer. Amazon Bedrock Guardrails are specifically designed to filter harmful content from chatbot inputs and responses, ensuring safe interactions for users.

Option B: Amazon Bedrock AgentsAmazon Bedrock Agents are used to automate tasks and integrate with external tools, not to filter harmful content. This option does not meet the requirement.

Option C: Amazon Bedrock inference APIsAmazon Bedrock inference APIs allow users to invoke foundation models for generating responses, but they do not provide built-in content filtering mechanisms.

Option D: Amazon Bedrock custom modelsCustom models on Amazon Bedrock allow users to fine-tune models, but they do not inherently include safeguards for filtering harmful content unless explicitly implemented.