The AWS Certified AI Practitioner Exam (AIF-C01)

The verified answer is C. Use batch inference with Amazon Bedrock. The workload has three decisive characteristics: it is repetitive, it processes a large volume of requests, and it does not require immediate responses. AWS documentation states that with Amazon Bedrock batch inference, users can submit multiple prompts and generate responses asynchronously. It also states that batch inference helps process a large number of requests efficiently by sending a single request and generating responses in an Amazon S3 bucket. That directly matches the weekly generation of exercise routines for all users.

AWS also explains that after the batch job is complete, the output files can be retrieved from Amazon S3, and batch inference can improve model inference performance on large datasets. This is the right architecture for offline or scheduled workloads where immediate response latency is not required.

Amazon Bedrock AgentCore is incorrect because AgentCore is for building, running, and managing agents, tools, memory, gateways, and agent workflows. The problem is not agent orchestration; it is cost-efficient high-volume offline inference.

Real-time inference with Amazon Bedrock on-demand endpoints is incorrect because real-time inference is better for interactive applications where users need immediate responses. The question explicitly says immediate responses are not required.

Real-time inference with SageMaker AI hosted endpoints is also incorrect for the same reason. Hosted endpoints are appropriate for low-latency inference requests, but this workload is scheduled and large-volume.

Therefore, Amazon Bedrock batch inference is the best solution.

The correct answer is A because temperature controls the randomness of a language model ' s output. A higher temperature increases diversity by making the model more likely to explore less probable tokens, while a lower temperature results in more deterministic and repetitive outputs.

From AWS documentation:

" The temperature parameter in LLMs adjusts the randomness of generated responses. Higher values (e.g., 0.8–1.0) produce more creative and diverse output, while lower values (e.g., 0.1–0.3) make output more focused and repetitive. "

Explanation of other options:

B. Batch size is related to training efficiency, not output diversity.

C. Learning rate affects the training convergence rate, not inference-time output variety.

D. Optimizer type is a training configuration that influences how the model learns during training, not diversity during inference.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock – Parameter Tuning Guide

AWS Machine Learning Specialty Guide – LLM Inference Parameters

Amazon SageMaker Serverless Inference is the correct solution for deploying an ML model to production in a way that allows a web application to use the model without the need to manage the underlying infrastructure.

Amazon SageMaker Serverless Inference provides a fully managed environment for deploying machine learning models. It automatically provisions, scales, and manages the infrastructure required to host the model, removing the need for the company to manage servers or other underlying infrastructure.

Why Option A is Correct:

No Infrastructure Management: SageMaker Serverless Inference handles the infrastructure management for deploying and serving ML models. The company can simply provide the model and specify the required compute capacity, and SageMaker will handle the rest.

Cost-Effectiveness: The serverless inference option is ideal for applications with intermittent or unpredictable traffic, as the company only pays for the compute time consumed while handling requests.

Integration with Web Applications: This solution allows the model to be easily accessed by web applications via RESTful APIs, making it an ideal choice for hosting the model and serving predictions.

Why Other Options are Incorrect:

B. Use Amazon CloudFront to deploy the model: CloudFront is a content delivery network (CDN) service for distributing content, not for deploying ML models or serving predictions.

C. Use Amazon API Gateway to host the model and serve predictions: API Gateway is used for creating, deploying, and managing APIs, but it does not provide the infrastructure or the required environment to host and run ML models.

D. Use AWS Batch to host the model and serve predictions: AWS Batch is designed for running batch computing workloads and is not optimized for real-time inference or hosting machine learning models.

Thus, A is the correct answer, as it aligns with the requirement of deploying an ML model without managing any underlying infrastructure.

The requirement is a classic time-series forecasting problem. The retailer has historical observations indexed by time—weekly sales—and needs to predict numerical demand or inventory requirements over a future 12-week forecast horizon. AWS time-series forecasting capabilities are specifically designed for this type of workload.

AWS documentation for SageMaker AI time-series forecasting states that forecasting models predict “forecast horizon points in the future” based on historical time-series information. AWS also explains that SageMaker AutoML time-series models generate probabilistic forecasts by producing forecasts at configurable quantiles.

Probabilistic forecasting is particularly valuable for inventory planning. Instead of returning only a single demand estimate, the model can produce quantiles such as P10, P50, and P90. These estimates represent different demand scenarios and help the retailer make replenishment decisions according to acceptable stockout risk, storage cost, and service-level targets.

For example, P50 can represent a central estimate of future demand, while a higher quantile such as P90 can support a more conservative stocking policy where avoiding stockouts is especially important.

Option B is a deterministic inventory-management heuristic. Moving averages and fixed safety factors may be useful operational rules, but they do not fulfill the requirement to use an ML model for future prediction.

Option C performs segmentation rather than forecasting actual stock or demand quantities.

Option D removes anomalous data and then relies on manual replenishment rules. Anomaly treatment can be part of data preparation, but it does not itself produce the requested 12-week ML forecast.

AWS forecasting models are specifically designed to learn trends, seasonality, recurrent patterns, and relationships from historical time-series data and generate future predictions.

Therefore, the correct solution is A. Generate probabilistic time-series forecasts of weekly product demand by using historical sales records.

===========

The correct answer is C, because Amazon Nova Micro is a smaller, lower-cost foundation model that is text-only, while Nova Lite is a more capable multimodal model that supports images, videos, and text. According to AWS Bedrock documentation, the Nova model family includes variants that differ in capability and cost. Nova Micro is optimized for lightweight text-based tasks, including summarization, question answering, and basic reasoning. This makes it cheaper to operate and well-suited for cost-sensitive workloads. Nova Lite, on the other hand, is a multimodal FM that can analyze documents, screenshots, photographs, charts, and videos, making it ideal for media companies requiring cross-format understanding. AWS clarifies that both Micro and Lite use transformer-based architectures, and run on managed infrastructure that abstracts hardware considerations. Therefore, the main differentiator is capability—and Nova Micro being text-only is the more cost-effective option. Nova Lite is appropriate only when image or video analysis is required.

Referenced AWS Documentation:

Amazon Bedrock – Nova Model Family Overview

AWS Generative AI Model Selection Guide

Creating a prompt template that teaches the LLM to detect attack patterns is the most effective way to reduce the risk of the model being manipulated through prompt engineering.

Prompt Templates for Security:

A well-designed prompt template can guide the LLM to recognize and respond appropriately to potential manipulation attempts.

This strategy helps prevent the model from performing undesirable actions or exposing sensitive information by embedding security awareness directly into the prompts.

Why Option A is Correct:

Teaches Model Security Awareness: Equips the LLM to handle potentially harmful inputs by recognizing suspicious patterns.

Reduces Manipulation Risk: Helps mitigate risks associated with prompt engineering attacks by proactively preparing the LLM.

Why Other Options are Incorrect:

B. Increase the temperature parameter: This increases randomness in responses, potentially making the LLM more unpredictable and less secure.

C. Avoid LLMs not listed in SageMaker: Does not directly address the risk of prompt manipulation.

D. Decrease the number of input tokens: Does not mitigate risks related to prompt manipulation.

Comprehensive and Detailed Explanation From Exact Extract:

In a RAG (Retrieval Augmented Generation) architecture, there are steps that can be optimized using offline batch processing, particularly for operations that do not require real-time updates:

A. Generation of content embeddings:When new content is published, it can be processed in batches to generate embeddings (vector representations) offline. These embeddings are then used at query time for similarity search. As new documents come in daily, batch processing is ideal for generating embeddings for all new content together.

“Content/document embeddings are typically generated offline, as this operation can be computationally expensive and does not need to happen in real-time.”

(Reference: AWS GenAI RAG Blog, Amazon Bedrock RAG Pattern)

C. Creation of the search index:After generating the content embeddings, these are indexed in a vector database or search service. This indexing is also typically performed in batch as part of the offline pipeline.

“Building or updating the vector index is often performed as a batch operation, reflecting the latest state of the content repository.”

(Reference: AWS RAG Pattern Whitepaper)

B, D, and E are real-time steps. Embeddings for user queries (B), retrieval of relevant content (D), and response generation (E) must be processed in real-time to provide an interactive experience.

Fairness refers to the absence of bias in AI models. Using non-representative datasets leads to biased predictions, affecting specific demographics unfairly. Explainability, privacy, and transparency are important but not directly related to this scenario. References: AWS Responsible AI Framework.

The correct answer is C – Re-train the model with fresh data. AWS SageMaker Model Monitor is designed to detect data drift, feature drift, and model quality degradation in real-time. When drift exceeds a set threshold, AWS recommends initiating a retraining workflow with updated data to restore model accuracy. According to AWS documentation, data drift indicates that the distribution of incoming data has changed significantly from the original training dataset—often due to new user behaviors, market changes, or seasonal patterns. Restarting the endpoint (A) does not address degraded model performance. Adjusting sensitivity (B) suppresses the alert but does not fix the underlying issue. Experiments tracking (D) is helpful for monitoring model versions but is not corrective. Retraining ensures the model adapts to new data patterns and continues to perform reliably, which is the AWS-endorsed response to drift detection alerts.

Referenced AWS Documentation:

Amazon SageMaker Model Monitor – Detecting Drift

AWS ML Ops Best Practices – Continuous Retraining