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

The verified answer is A. Continuous pre-training. The company wants to expose an existing LLM to medical papers so the model becomes more familiar with medical topics, terminology, and writing patterns. AWS generative AI documentation defines continued pre-training as extending the pre-training phase of a foundation model by exposing it to additional unlabeled text from specific domains or corpora. It also explains that continued pre-training helps the model acquire deeper knowledge of new domains and adapt to domain-specific terminology and content types.

That exactly matches the scenario. Medical papers are typically domain text. The goal is not to train the model to follow a labeled input-output task, but to improve its domain familiarity and medical-language fluency. AWS security reference guidance also distinguishes continued pre-training from fine-tuning by stating that continued pre-training uses unlabeled data to enhance domain knowledge, while fine-tuning uses labeled data to optimize task-specific performance.

Supervised learning is incorrect because it requires labeled training examples, usually input-output pairs. The question only says the company has medical papers, not labeled prompts and responses.

Reinforcement learning is incorrect because it optimizes behavior based on rewards, feedback, or preference signals. The question does not describe reward modeling or human preference feedback.

Boosting is incorrect because boosting is an ensemble technique that combines weak learners to improve predictive performance. It is not the standard method for adapting an LLM to a specialized knowledge domain.

Because the company wants to familiarize an LLM with medical subject matter through medical papers, the correct technique is continuous pre-training.

Fine-tuning is the process of training a pre-trained LLM with a labeled dataset specific to a desired task—in this case, mapping user messages to JSON outputs. Fine-tuning leverages supervised learning to specialize the model’s outputs.

C is correct:

“Fine-tuning is a supervised learning approach in which a model is further trained on a custom, labeled dataset to adapt to a specific use case.”

(Reference: Amazon Bedrock Fine-Tuning, AWS Certified AI Practitioner Study Guide)

A is incorrect—unsupervised learning does not use labeled data.

B (continued pre-training) uses unlabeled data.

D (RLHF) uses reward signals and human feedback, not direct labeled input/output pairs.

The airline company aims to build a conversational AI assistant using large language models (LLMs) and a knowledge base to create a text-based chatbot with minimal development effort. Retrieval Augmented Generation (RAG) on Amazon Bedrock is an ideal solution because it combines LLMs with a knowledge base to provide accurate, contextually relevant responses without requiring extensive model training or custom development. RAG retrieves relevant information from a knowledge base and uses an LLM to generate responses, simplifying the development process.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Retrieval Augmented Generation (RAG) in Amazon Bedrock enables developers to build conversational AI applications by combining foundation models with external knowledge bases. This approach minimizes development effort by leveraging pre-trained models and integrating them with data sources, such as FAQs or databases, to provide accurate and contextually relevant responses. "

(Source: AWS Bedrock User Guide, Retrieval Augmented Generation)

Detailed Explanation:

Option A: Train models on Amazon SageMaker Autopilot.SageMaker Autopilot is designed for automated machine learning (AutoML) tasks like classification or regression, not for building conversational AI with LLMs and knowledge bases. It requires significant data preparation and is not optimized for chatbot development, making it less suitable.

Option B: Develop a Retrieval Augmented Generation (RAG) agent by using Amazon Bedrock.This is the correct answer. RAG on Amazon Bedrock allows the company to use pre-trained LLMs and integrate them with a knowledge base (e.g., flight schedules or FAQs) to build a chatbot with minimal effort. It avoids the need for extensive training or coding, aligning with the requirement for least development effort.

Option C: Create a Python application by using Amazon Q Developer.While Amazon Q Developer can assist with code generation, building a chatbot from scratch in Python requires significant development effort, including integrating LLMs and a knowledge base manually, which is more complex than using RAG on Bedrock.

Option D: Fine-tune models on Amazon SageMaker Jumpstart.Fine-tuning models on SageMaker Jumpstart requires preparing training data and customizing LLMs, which involves more effort than using a pre-built RAG solution on Bedrock. This option is not the least effort-intensive.

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

Comprehensive and Detailed Explanation From Exact Extract:

The best practice for mitigating bias in AI/ML models, according to AWS and responsible AI frameworks, is to ensure that the training data is representative and diverse. If a model demonstrates bias (such as favoring a particular demographic), the recommended, cost-effective approach is to collect additional data from underrepresented groups and retrain (fine-tune) the model with the improved dataset.

A. Include more diverse training data. Fine-tune the model again by using the new data:

“The most effective method to reduce model bias is to curate and include diverse, representative training data, then retrain or fine-tune the model.”

(Reference: AWS Responsible AI, SageMaker Clarify Bias Mitigation)

B (RAG) is unrelated to model fairness or bias mitigation; it’s for grounding LLMs with external knowledge.

C (AWS Trusted Advisor) is for AWS resource optimization/security—not for ML model bias detection or mitigation.

D (Pre-train a new LLM) would be extremely costly and is unnecessary; fine-tuning with better data is much more efficient.

The average response time is the correct metric for measuring the runtime efficiency of operating AI models.

Average Response Time:

Refers to the time taken by the model to generate an output after receiving an input. It is a key metric for evaluating the performance and efficiency of AI models in production.

A lower average response time indicates a more efficient model that can handle queries quickly.

Why Option C is Correct:

Measures Runtime Efficiency: Directly indicates how fast the model processes inputs and delivers outputs, which is critical for real-time applications.

Performance Indicator: Helps identify potential bottlenecks and optimize model performance.

Why Other Options are Incorrect:

A. Customer satisfaction score (CSAT): Measures customer satisfaction, not model runtime efficiency.

B. Training time for each epoch: Measures training efficiency, not runtime efficiency during model operation.

D. Number of training instances: Refers to data used during training, not operational efficiency.

Temperature is an inference parameter that directly influences the randomness and creativity of content generated by a foundation model.

During text generation, a language model assigns probabilities to potential next tokens. Temperature adjusts this probability distribution, affecting how predictably the model selects subsequent tokens.

A lower temperature generally produces more deterministic, consistent responses, making it useful for factual question answering and structured business applications.

A higher temperature increases the likelihood of selecting less probable tokens, potentially producing more diverse and creative responses.

Token length controls output size, while an end token sequence determines when generation stops.

Top K also affects output diversity by restricting the number of candidate tokens. However, temperature is the standard answer because it directly regulates sampling randomness and creativity.

AWS documents both temperature and Top K as generation-control parameters.

Precision is the metric that measures the proportion of true positives (actual frauds) among all flagged positives (flagged frauds). High precision ensures that most of the flagged cases are truly fraudulent, minimizing the number of false positives employees must review.

C is correct:

" Precision is the ratio of true positives to all predicted positives, and it answers: ‘Of all the cases flagged as fraud, how many were actually fraud?’ High precision means fewer non-fraudulent cases are sent for manual review. "

(Reference: AWS ML Concepts – Precision and Recall, AWS Certified AI Practitioner Study Guide)

A (Recall) measures how many actual frauds are caught, but does not minimize false positives.

B (Accuracy) can be misleading in imbalanced datasets (like fraud detection).