AIF-C01 Exam Dumps - Amazon Web Services AWS Certified AI Practitioner Questions and Answers

Comprehensive and Detailed Explanation From Exact AWS AI documents:

According to MLOps best practices, once an ML model is deployed to production—especially an open-source pre-trained model—the organization must continuously monitor model outputs to ensure:

Model predictions remain accurate over time

No performance degradation due to data drift or concept drift

Outputs remain aligned with business and ethical expectations

AWS MLOps guidance emphasizes monitoring in production as a mandatory step for maintaining model reliability and governance.

Why the other options are incorrect:

A (Hyperparameter tuning) is optional and model-dependent.

B (Labeling data) is required only when training or fine-tuning, not when using a pre-trained model directly.

D (Feature engineering) is less relevant for modern pre-trained NLP models.

AWS AI document references:

MLOps Best Practices on AWS

Amazon SageMaker Model Monitoring

Operationalizing Machine Learning on AWS

The requirement is to identify an AWS database service that supports the storage and querying of embeddings (from a generative AI model) as vectors. Embeddings are typically high-dimensional numerical representations of data (e.g., text, images) used in AI applications like conversational search. The database must support vector storage and efficient vector similarity searches. Let’s evaluate each option:

A. Amazon Athena: Amazon Athena is a serverless query service for analyzing data in Amazon S3 using SQL. It is designed for ad-hoc querying of structured data but does not natively support vector storage or vector similarity searches, making it unsuitable for this use case.

B. Amazon Aurora PostgreSQL: Amazon Aurora PostgreSQL is a fully managed relational database compatible with PostgreSQL. With the pgvector extension (available in PostgreSQL and supported by Aurora PostgreSQL), it can store and query vector embeddings efficiently. The pgvector extension enables vector similarity searches (e.g., using cosine similarity or Euclidean distance), which is critical for conversational search applications using embeddings from generative AI models.

C. Amazon Redshift: Amazon Redshift is a data warehousing service optimized for analytical queries on large datasets. While it supports machine learning features and can store numerical data, it does not have native support for vector embeddings or vector similarity searches as of May 17, 2025, making it less suitable for this use case.

D. Amazon EMR: Amazon EMR is a managed big data platform for processing large-scale data using frameworks like Apache Hadoop and Spark. It is not a database service and is not designed for storing or querying vector embeddings in the context of a conversational search application.

Exact Extract Reference: According to the AWS documentation, “Amazon Aurora PostgreSQL-Compatible Edition supports the pgvector extension, which enables efficient storage and similarity searches for vector embeddings. This makes it suitable for AI/ML workloads such as natural language processing and recommendation systems that rely on vector data.” (Source: AWS Aurora Documentation - Using pgvector with Aurora PostgreSQL, https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/PostgreSQLpgvector.html). Additionally, the pgvector extension supports operations like nearest-neighbor searches, which are essential for querying embeddings in a conversational search system.

Amazon Aurora PostgreSQL with the pgvector extension directly meets the requirement for storing and querying embeddings as vectors, making B the correct answer.

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

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.

Amazon SageMaker Model Monitor is specifically designed to automatically detect and alert on changes in model quality, such as data drift, prediction drift, or other anomalies in model performance once deployed.

D is correct:

" Amazon SageMaker Model Monitor continuously monitors the quality of machine learning models in production. It automatically detects concept drift, data drift, and other quality issues, enabling teams to take corrective actions. "

(Reference: Amazon SageMaker Model Monitor Documentation, AWS Certified AI Practitioner Study Guide)

A (JumpStart) provides prebuilt solutions and models, not monitoring.

B (HyperPod) is for large-scale training, not model monitoring.

C (Data Wrangler) is for data preparation, not ongoing model quality monitoring.

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.

The correct answer is C, as conversion rate (how many users upgrade to premium) and retention rate (how many stay subscribed) are primary indicators of a generative AI system’s business impact and ROI. According to AWS documentation, evaluating AI performance should go beyond technical accuracy to include business metrics that show real-world value. For a premium service, higher conversion implies successful personalization that attracts free users, while strong retention reflects sustained engagement and user satisfaction. Metrics like ARPU or query reduction are secondary indicators. AWS emphasizes outcome-based measurement to ensure AI initiatives contribute measurable ROI tied to customer adoption, loyalty, and profitability. Therefore, tracking conversion and retention gives the clearest long-term measure of financial success from generative AI.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – ML Business Metrics

AWS AI Adoption Framework – Value Realization and ROI Tracking

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.

The verified answer is A. Amazon Bedrock Guardrails . The requirement is to prevent a deployed foundation model from returning answers about a specific unwanted topic: politics. AWS documentation states that Amazon Bedrock Guardrails provides configurable safeguards to help you build safe generative AI applications . It also explains that guardrails provide safety and privacy controls across foundation models and help detect and filter undesirable content in user inputs and model responses. Most importantly for this question, AWS specifically identifies denied topics as a guardrail capability. With denied topics, you can define a set of topics that are undesirable in the context of your application, and the filter helps block them if they are detected in user queries or model responses. That exactly matches the scenario because the company wants political questions blocked before answers are sent to users.

Amazon Bedrock Agents is incorrect because agents are used to build applications that can reason, orchestrate tasks, call APIs, and connect to knowledge sources or action groups. Agents do not primarily exist to block topic categories in model input or output. Amazon SageMaker Clarify is incorrect because AWS describes SageMaker Clarify as a service for fairness, model explainability, feature attribution, and bias detection. It is useful for understanding model behavior and detecting bias, but it is not the correct control for filtering political responses from a generative AI application.

Amazon SageMaker Model Monitor is also incorrect because it monitors deployed model quality, data quality, bias drift, and feature attribution drift. Monitoring can identify problems after deployment, but it does not directly enforce real-time content filtering for foundation model responses. The question asks for a solution that ensures political answers are not sent to users. AWS Bedrock Guardrails is purpose-built for that control by applying safeguards to FM inputs and outputs.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

AWS PrivateLink enables private connectivity between AWS services through VPC endpoints, ensuring traffic does not traverse the public internet.

AWS guidance recommends PrivateLink for:

Secure, private service access

Regulatory and compliance requirements

VPC-based architecture

Why the other options are incorrect:

IAM (A) controls access, not network routing.

Macie (B) is a data security service.

VPC peering (D) is not required for Bedrock access.

AWS AI document references:

Amazon Bedrock Networking and Security

Private Connectivity with AWS PrivateLink

Secure AI Architectures on AWS