Amazon Web Services AIF-C01 - AWS Certified AI Practitioner Exam

Unsupervised learning involves training a model on unlabeled data, letting it find patterns or groupings on its own, without explicit outputs provided. Clustering is a primary unsupervised learning technique.

Option A is correct: Grouping customers based on purchase history (without predefined categories) is clustering, a classic unsupervised task.

B and C are supervised learning (classification and regression, respectively).

D is reinforcement learning, not unsupervised learning.

"Unsupervised learning involves training on data without labels and is often used for clustering or dimensionality reduction."

(Reference: AWS Certified AI Practitioner Official Study Guide, AWS ML Concepts)

Guardrails for Amazon Bedrock provide mechanisms to filter and control the content generated by models to comply with privacy and policy requirements. Using guardrails ensures that sensitive or personal information is not included in the model's responses. Additionally, integrating Amazon CloudWatch alarms allows for real-time notification when a policy violation occurs.

Option C (Correct): "Use Guardrails for Amazon Bedrock to filter content. Set up Amazon CloudWatch alarms for notification of policy violations": This is the correct answer because it directly addresses both the prevention of policy violations and the requirement to receive notifications when such violations occur.

Option A: "Use Amazon Macie to scan the model's output for sensitive data" is incorrect because Amazon Macie is designed to monitor data in S3, not to filter real-time model outputs.

Option B: "Configure AWS CloudTrail to monitor the model's responses" is incorrect because CloudTrail tracks API activity and is not suited for content moderation.

Option D: "Implement Amazon SageMaker Model Monitor to detect data drift" is incorrect because data drift detection does not address content moderation or privacy compliance.

AWS AI Practitioner References:

Guardrails in Amazon Bedrock: AWS provides guardrails to ensure AI models comply with content policies, and using CloudWatch for alerting integrates monitoring capabilities.

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 B – Hallucinations. AWS defines hallucinations as instances where a generative model produces confident but incorrect or fabricated information. This can occur when the model lacks relevant context or attempts to fill informational gaps during text generation. In product descriptions, hallucinations may lead to false features, incorrect specifications, or misleading claims—posing reputational and legal risks. AWS documentation recommends mitigating hallucinations through Retrieval-Augmented Generation (RAG), grounding responses in enterprise data using Bedrock Knowledge Bases, implementing Guardrails, or refining prompts with factual constraints. Toxicity (A) refers to harmful or offensive content, interpretability (C) concerns understanding model reasoning, and deterministic outputs (D) are not typical of LLMs. Therefore, the issue described aligns precisely with the definition of hallucination in AWS’s generative AI guidance.

Referenced AWS Documentation:

AWS Generative AI Whitepaper – Hallucination Mitigation

Amazon Bedrock Knowledge Bases – Grounding Model Responses

The problem involves a simple probability calculation that can be handled efficiently by straightforward mathematical rules and computations. Using machine learning techniques would introduce unnecessary complexity and operational overhead.

Option C (Correct): "Use code that will calculate probability by using simple rules and computations": This is the correct answer because it directly solves the problem with minimal overhead, using basic probability rules.

Option A: "Use supervised learning to create a regression model" is incorrect as it overcomplicates the solution for a simple probability problem.

Option B: "Use reinforcement learning to train a model" is incorrect because reinforcement learning is not needed for a simple probability calculation.

Option D: "Use unsupervised learning to create a model" is incorrect as unsupervised learning is not applicable to this task.

AWS AI Practitioner References:

Choosing the Right Solution for AI Tasks: AWS recommends using the simplest and most efficient approach to solve a given problem, avoiding unnecessary machine learning techniques for straightforward tasks.

Amazon S3 is the optimal choice for storing and uploading datasets used for machine learning model validation and training. It offers scalable, durable, and secure storage, making it ideal for holding datasets required by Amazon Bedrock for validation purposes.

Option A (Correct): "Amazon S3": This is the correct answer because Amazon S3 is widely used for storing large datasets that are accessed by machine learning models, including those in Amazon Bedrock.

Option B: "Amazon Elastic Block Store (Amazon EBS)" is incorrect because EBS is a block storage service for use with Amazon EC2, not for directly storing datasets for Amazon Bedrock.

Option C: "Amazon Elastic File System (Amazon EFS)" is incorrect as it is primarily used for file storage with shared access by multiple instances.

Option D: "AWS Snowcone" is incorrect because it is a physical device for offline data transfer, not suitable for directly providing data to Amazon Bedrock.

AWS AI Practitioner References:

Storing and Managing Datasets on AWS for Machine Learning: AWS recommends using S3 for storing and managing datasets required for ML model training and validation.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Prompt management in Amazon Bedrock enables:

Reuse of standardized prompt templates

Parameterization of prompts with dynamic inputs

Consistent instruction application across use cases

AWS Bedrock guidance describes prompt management as the recommended solution for maintaining reusable prompt templates while injecting product-specific content.

Why the other options are incorrect:

Knowledge Bases (B) provide retrieval, not prompt templating.

Model evaluation (C) assesses quality, not generation.

Cross-region inference (D) addresses availability, not prompt reuse.

AWS AI document references:

Amazon Bedrock Prompt Management

Prompt Templates and Reusability

Managing Generative AI Prompts

The context window determines how much information can fit into a single prompt when using a large language model (LLM) like those on Amazon Bedrock.

Context Window:

The context window is the maximum amount of text (measured in tokens) that a language model can process in a single pass.

For LLM applications, the size of the context window limits how much input data, such as text for sentiment analysis, can be fed into the model at once.

Why Option B is Correct:

Determines Prompt Size: The context window size directly informs how much information (e.g., words or sentences) can fit in one prompt.

Model Capacity: The larger the context window, the more information the model can consider for generating outputs.

Why Other Options are Incorrect:

A. Temperature: Controls randomness in model outputs but does not affect the prompt size.

C. Batch size: Refers to the number of training samples processed in one iteration, not the amount of information in a prompt.

D. Model size: Refers to the number of parameters in the model, not the input size for a single prompt.

The F1 score is a metric used to evaluate the performance of a classification model by considering both precision and recall. Precision measures the accuracy of positive predictions (i.e., the proportion of true positive predictions among all positive predictions made by the model), while recall measures the model's ability to identify all relevant positive instances (i.e., the proportion of true positive predictions among all actual positive instances). The F1 score is the harmonic mean of precision and recall, providing a single metric that balances both concerns. This is particularly useful when dealing with imbalanced datasets or when the cost of false positives and false negatives is significant. Options B, C, and D pertain to other aspects of model performance but are not related to the F1 score.

The most explainable model in machine learning is Linear regression. It provides clear mathematical relationships between input features and predicted outcomes, making it highly transparent. According to AWS documentation and Responsible AI best practices, linear regression models allow users to see the exact weight or coefficient assigned to each feature. This makes it easy to explain model decisions to non-technical stakeholders and is especially important in regulated industries like finance and healthcare. Support vector machines, random cut forests, and neural networks are more complex and often operate as black boxes with non-linear transformations that require additional explainability tools like SHAP or LIME. AWS recommends starting with simpler, interpretable models when transparency is a requirement.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Model Transparency and Explainability

Amazon SageMaker Documentation – Interpretable Models