Free Amazon Web Services AIF-C01 Practice Exam with Questions & Answers

Providing labeled data with both a prompt field and a completion field is the correct strategy for fine-tuning a foundation model (FM) on Amazon Bedrock.

Fine-Tuning Strategy:

To fine-tune a model, labeled data that pairs input prompts with the correct outputs (completions) is necessary.

This allows the model to learn the desired behavior or response style based on the provided examples.

Why Option A is Correct:

Proper Training Format: The prompt-completion pairs provide the necessary format for training the model to produce accurate outputs.

Customization: Ensures that the model is fine-tuned to the specific requirements of the company’s data and desired outputs.

Why Other Options are Incorrect:

B. Prepare a .txt file in .csv format: This does not align with the specific need for labeled data with prompts and completions.

C. Purchase Provisioned Throughput: Relates to read/write capacity in databases, not to model fine-tuning.

D. Train on journals and textbooks: Lacks the specific format and labeling required for fine-tuning.

The correct answer is B, because AWS recommends that any generative AI initiative begin with use-case clarification, stakeholder alignment, and measurable business objectives. According to the AWS Generative AI Adoption Framework and the AWS Machine Learning Journey guidelines, successful AI projects start with defining specific business outcomes—such as revenue growth, reduced time-to-market, or improved campaign efficiency. Conducting stakeholder interviews ensures the organization identifies the highest-value marketing use cases, such as personalized campaigns or content generation, and sets KPIs to measure revenue impact within the target timeframe. AWS documentation emphasizes avoiding premature model training (option A), which is costly and unnecessary without validated requirements. Implementing a prebuilt assistant (option C) may help operations but does not guarantee alignment with the core revenue objective. Replicating competitor features (option D) may lack strategic alignment. Therefore, refining use cases and measurable goals is the foundational AWS-recommended approach for a targeted revenue-driven generative AI initiative.

Referenced AWS Documentation:

AWS Generative AI Adoption Framework

AWS ML Business Value and Use-Case Identification Guidelines

The verified answer is C. Use the LLM-as-a-judge approach with a rubric across prompts to compare model outputs. The question asks for a scalable way to compare two foundation models for chat summarization based on correctness and completeness. AWS documentation for Amazon Bedrock model evaluation states that an evaluation job using a judge model uses an LLM to score another model’s responses and provide an explanation of how it scored each prompt and response pair. This is specifically designed to compare model outputs across prompt datasets at scale, without requiring every output to be manually scored by humans.

AWS Bedrock documentation also lists built-in metrics for model evaluation jobs that use an LLM as a judge. The valid built-in metrics include Correctness and Completeness, which directly match the evaluation criteria in the question. Therefore, using LLM-as-a-judge with a rubric across prompts is the best fit because it evaluates the actual summaries produced by each model against the desired quality dimensions.

Option A is partially valid as an evaluation method, but it is not the most scalable approach. Human reviewers can provide high-quality judgments, but manual review becomes expensive and slow when comparing many prompts, outputs, and models. Option B is incorrect because latency and throughput measure operational performance, not whether a summary is correct or complete. A fast model can still produce incomplete or inaccurate summaries. Option D is incorrect because external benchmark rankings are generic. They do not prove that a model performs best on the company’s specific chat summarization workload.

The decisive terms are “scalable,” “correctness,” and “completeness.” Amazon Bedrock LLM-as-a-judge evaluation directly supports those dimensions, so option C is correct.

The correct answer is C – Test the AI solution to ensure that it does not discriminate against any protected groups. According to AWS Responsible AI principles, fairness and bias mitigation are essential when AI is used for high-impact decisions such as hiring. AWS documentation emphasizes evaluating datasets, model outputs, and demographic performance to ensure that AI systems do not reinforce or reproduce discriminatory patterns. Services such as Amazon SageMaker Clarify support automated bias detection and explainability, helping teams identify and mitigate unwanted correlations in training data or model predictions. Option A violates AWS guidance, as human-in-the-loop review is required for sensitive decisions. Option B risks amplifying historical bias because training on only “successful” hires can create feedback loops. Option D contradicts transparency principles, which AWS states are crucial for accountability in regulated or ethical decision-making domains. Therefore, rigorous fairness testing aligns with AWS’s recommended practices for responsible AI in hiring workflows.

Referenced AWS Documentation:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation

The goal is to prevent a fine-tuned large language model (LLM) on Amazon Bedrock from revealing private customer data. Let’s analyze the options:

A. Amazon Bedrock Guardrails: Guardrails in Amazon Bedrock allow users to define policies to filter harmful or sensitive content in model inputs and outputs. While useful for real-time content moderation, they do not address the risk of private data being embedded in the model during fine-tuning, as the model could still memorize sensitive information.

B. Remove personally identifiable information (PII) from the customer data before fine-tuning the LLM: Removing PII (e.g., names, addresses, account numbers) from the training dataset ensures that the model does not learn or memorize sensitive customer data, reducing the risk of data leakage. This is a proactive and effective approach to data privacy during model training.

C. Increase the Top-K parameter of the LLM: The Top-K parameter controls the randomness of the model’s output by limiting the number of tokens considered during generation. Adjusting this parameter affects output diversity but does not address the privacy of customer data embedded in the model.

D. Store customer data in Amazon S3. Encrypt the data before fine-tuning the LLM: Encrypting data in Amazon S3 protects data at rest and in transit, but during fine-tuning, the data is decrypted and used to train the model. If PII is present, the model could still learn and potentially expose it, so encryption alone does not solve the problem.

Exact Extract Reference: AWS emphasizes data privacy in AI/ML workflows, stating, “To protect sensitive data, you can preprocess datasets to remove personally identifiable information (PII) before using them for model training. This reduces the risk of models inadvertently learning or exposing sensitive information.” (Source: AWS Best Practices for Responsible AI, https://aws.amazon.com/machine-learning/responsible-ai/). Additionally, the Amazon Bedrock documentation notes that users are responsible for ensuring compliance with data privacy regulations during fine-tuning (https://docs.aws.amazon.com/bedrock/latest/userguide/model-customization.html).

Removing PII before fine-tuning is the most direct and effective way to prevent the model from revealing private customer data, making B the correct answer.

When a model performs well on training data but poorly on evaluation/test data, it indicates overfitting.

Overfitting: The model memorizes the training data patterns instead of generalizing.

Underfitting (A) means the model performs poorly on both training and test data.

Bias (C) refers to systemic errors in predictions, not this training/test mismatch.

Prompt engineering (B) applies to generative AI, not general ML training models.

???? Reference:

AWS ML Glossary – Overfitting and Underfitting

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Macie uses machine learning to:

Discover sensitive data such as PII

Classify data stored in Amazon S3

Help prevent unintended data exposure

AWS security guidance recommends Macie before data sharing to ensure compliance and privacy protection.

Why the other options are incorrect:

Kendra (A) is a search service.

Textract (C) extracts text from documents.

Data Exchange (D) shares datasets, not analyzes sensitivity.

AWS AI document references:

Amazon Macie Overview

Protecting Sensitive Data in S3

Data Privacy and Governance on AWS

Clustering is an unsupervised machine learning technique used to group data points based on similarity without requiring labeled data. AWS documentation explains that clustering is commonly used for customer segmentation, where the goal is to discover natural groupings within a dataset.

In this scenario, the dataset is unlabeled and includes behavioral and demographic features. Clustering algorithms analyze patterns and distances between data points to identify distinct customer groups, making this technique ideal for understanding customer segments.

Regression and classification require labeled outputs, and reinforcement learning focuses on sequential decision-making, not grouping. AWS positions clustering as the correct approach for this use case.

Partial dependence plots (PDPs) are visual tools used to show the relationship between a feature (or a set of features) in the data and the predicted outcome of a machine learning model. They are highly effective for providing transparency and explainability of the model ' s behavior to stakeholders by illustrating how different input variables impact the model ' s predictions.

Option B (Correct): " Partial dependence plots (PDPs) " : This is the correct answer because PDPs help to interpret how the model ' s predictions change with varying values of input features, providing stakeholders with a clearer understanding of the model ' s decision-making process.

Option A: " Code for model training " is incorrect because providing the raw code for model training may not offer transparency or explainability to non-technical stakeholders.

Option C: " Sample data for training " is incorrect as sample data alone does not explain how the model works or its decision-making process.

Option D: " Model convergence tables " is incorrect. While convergence tables can show the training process, they do not provide insights into how input features affect the model ' s predictions.

AWS AI Practitioner References:

Explainability in AWS Machine Learning: AWS provides various tools for model explainability, such as Amazon SageMaker Clarify, which includes PDPs to help explain the impact of different features on the model’s predictions.

Comprehensive and Detailed Explanation (AWS AI documents):

According to AWS Generative AI and Foundation Model guidance, foundation models are pre-trained on very large and diverse datasets, enabling them to perform a wide range of tasks such as classification, summarization, labeling, and content generation without task-specific training.

For labeling online news articles, a foundation model can be used out of the box or with minimal prompt engineering, whereas a conventional ML model would typically require:

Task-specific labeled training data

Model training and validation cycles

Ongoing retraining as content evolves

Why the other options are incorrect:

B. Smaller and faster – Foundation models are generally larger, not smaller, than conventional ML models.

C. More transparent – FMs are often less transparent due to their size and complexity.

D. Not biased – Foundation models can still inherit biases from training data; bias mitigation is required.

AWS AI Study Guide References:

AWS Generative AI fundamentals

AWS Foundation Model characteristics and benefits