Pass the Amazon Web Services AWS Certified AI Practitioner AIF-C01 Questions and answers with CertsForce

Amazon Bedrock Guardrails allow developers to create safeguards that filter harmful content and prevent sensitive topics from being discussed. This functionality helps mitigate prompt injection attacks with minimal implementation effort. According to the official Amazon Bedrock documentation:

“You can configure Guardrails for Amazon Bedrock to define denied topics, use content filters, and apply sensitive information filters, offering protection against prompt injection attacks with minimal development effort.”

Sampling bias is the correct type of bias affecting the model output when it disproportionately flags people from a specific ethnic group.

Sampling Bias:

Occurs when the training data is not representative of the broader population, leading to skewed model outputs.

In this case, if the model disproportionately flags people from a specific ethnic group, it likely indicates that the training data was not adequately balanced or representative.

Why Option B is Correct:

Reflects Data Imbalance: A biased sample in the training data could result in unfair outcomes, such as disproportionately flagging a particular group.

Common Issue in ML Models: Sampling bias is a known problem that can lead to unfair or inaccurate model predictions.

Why Other Options are Incorrect:

A. Measurement bias: Involves errors in data collection or measurement, not sampling.

C. Observer bias: Refers to bias introduced by researchers or data collectors, not the model's output.

D. Confirmation bias: Involves favoring information that confirms existing beliefs, not relevant to model output bias.

An anomaly detection system is suitable for identifying unusual patterns or behaviors, such as suspicious IP addresses, which might indicate a potential threat.

Anomaly Detection:

Anomaly detection uses machine learning algorithms to identify deviations from normal behavior, such as unexpected traffic from a suspicious IP address.

This is a common approach for identifying potential threats or malicious activity in cybersecurity applications.

Why Option C is Correct:

Detects Suspicious Behavior: An anomaly detection system can monitor and detect IP addresses that exhibit unusual or suspicious patterns.

Real-time Monitoring: Provides continuous analysis of network traffic to identify potential security threats.

Why Other Options are Incorrect:

A. Speech recognition system: Is unrelated to detecting suspicious IP addresses.

B. NLP named entity recognition: Focuses on identifying entities in text, not IP address analysis.

D. Fraud forecasting system: Generally used for predicting fraud, not directly applicable to identifying suspicious IPs.

Thus, C is the correct answer for detecting suspicious IP addresses.

SageMaker Model Registry, SageMaker Serverless interference

This question requires selecting the appropriate Amazon SageMaker feature for two distinct steps in the AI model lifecycle. Let’s break down each step and evaluate the options:

Step 1: Managing different versions of the model

The goal here is to identify a SageMaker feature that supports version control and management of machine learning models. Let’s analyze the options:

SageMaker Clarify: This feature is used to detect bias in models and explain model predictions, helping with fairness and interpretability. It does not provide functionality for managing model versions.

SageMaker Model Registry: This is a centralized repository in Amazon SageMaker that allows users to catalog, manage, and track different versions of machine learning models. It supports model versioning, approval workflows, and deployment tracking, making it ideal for managing different versions of a model.

SageMaker Serverless Inference: This feature enables users to deploy models for inference without managing servers, automatically scaling based on demand. It is focused on inference (predictions), not on managing model versions.

Conclusion for Step 1: The SageMaker Model Registry is the correct choice for managing different versions of the model.

Exact Extract Reference: According to the AWS SageMaker documentation, “The SageMaker Model Registry allows you to catalog models for production, manage model versions, associate metadata, and manage approval status for deployment.” (Source: AWS SageMaker Documentation - Model Registry, https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry.html).

Step 2: Using the current model to make predictions

The goal here is to identify a SageMaker feature that facilitates making predictions (inference) with a deployed model. Let’s evaluate the options:

SageMaker Clarify: As mentioned, this feature focuses on bias detection and explainability, not on performing inference or making predictions.

SageMaker Model Registry: While the Model Registry helps manage and catalog models, it is not used directly for making predictions. It can store models, but the actual inference process requires a deployment mechanism.

SageMaker Serverless Inference: This feature allows users to deploy models for inference without managing infrastructure. It automatically scales based on traffic and is specifically designed for making predictions in a cost-efficient, serverless manner.

Conclusion for Step 2: SageMaker Serverless Inference is the correct choice for using the current model to make predictions.

Exact Extract Reference: The AWS documentation states, “SageMaker Serverless Inference is a deployment option that allows you to deploy machine learning models for inference without configuring or managing servers. It automatically scales to handle inference requests, making it ideal for workloads with intermittent or unpredictable traffic.” (Source: AWS SageMaker Documentation - Serverless Inference, https://docs.aws.amazon.com/sagemaker/latest/dg/serverless-inference.html).

Why Not Use the Same Feature Twice?

The question specifies that each SageMaker feature or resource should be selected one time or not at all. Since SageMaker Model Registry is used for version management and SageMaker Serverless Inference is used for predictions, each feature is selected exactly once. SageMaker Clarify is not applicable to either step, so it is not selected at all, fulfilling the question’s requirements.

The correct answer is D. Amazon Bedrock Agents are used to orchestrate and execute complex workflows by connecting foundation models with APIs, databases, and tools. According to AWS documentation, agents interpret user inputs, plan the necessary steps, call external APIs or systems, and return structured results. This allows the model to go beyond text generation into full automation workflows—such as booking tasks, querying internal systems, or summarizing reports. Option A describes multi-modal models, B refers to prompt tuning, and C misstates control delegation; agents act autonomously based on model reasoning. Thus, Bedrock Agents function as intelligent orchestrators, handling multi-step task execution through integrated tool use.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Agents Overview

AWS Generative AI Best Practices – Workflow Orchestration

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

Exploratory data analysis (EDA) involves understanding the data by visualizing it, calculating statistics, and creating correlation matrices. This stage helps identify patterns, relationships, and anomalies in the data, which can guide further steps in the ML pipeline.

Option C (Correct): "Exploratory data analysis": This is the correct answer as the tasks described (correlation matrix, calculating statistics, visualizing data) are all part of the EDA process.

Option A: "Data pre-processing" is incorrect because it involves cleaning and transforming data, not initial analysis.

Option B: "Feature engineering" is incorrect because it involves creating new features from raw data, not analyzing the data's existing structure.

Option D: "Hyperparameter tuning" is incorrect because it refers to optimizing model parameters, not analyzing the data.

AWS AI Practitioner References:

Stages of the Machine Learning Pipeline: AWS outlines EDA as the initial phase of understanding and exploring data before moving to more specific preprocessing, feature engineering, and model training stages.

Amazon SageMaker Ground Truth lets you create data labeling jobs and can integrate with Amazon Mechanical Turk (a distributed human workforce) to label large unlabeled datasets.

A (batch inference) applies models to already-trained data, not labeling.

B (PyTorch Distributed) is for distributed training, not labeling.

D (OCR) applies only to text extraction from images, not transactions.

E is incorrect; Ground Truth is the service for labeling, not "AI labeling job."

???? Reference:

AWS Documentation – SageMaker Ground Truth

To implement a large language model (LLM) responsibly, the firm should focus on fairness and mitigating bias, which are critical for ethical AI deployment.

A. Include Fairness Metrics for Model Evaluation:

Fairness metrics help ensure that the model's predictions are unbiased and do not unfairly discriminate against any group.

These metrics can measure disparities in model outcomes across different demographic groups, ensuring responsible AI practices.

C. Modify the Training Data to Mitigate Bias:

Adjusting training data to be more representative and balanced can help reduce bias in the model's predictions.

Mitigating bias at the data level ensures that the model learns from a diverse and fair dataset, reducing potential harms in deployment.

Why Other Options are Incorrect:

B. Adjust the temperature parameter of the model: Controls randomness in outputs but does not directly address fairness or bias.

D. Avoid overfitting on the training data: Important for model generalization but not directly related to responsible AI practices regarding fairness and bias.

E. Apply prompt engineering techniques: Useful for improving model outputs but not specifically for mitigating bias or ensuring fairness.