Free Amazon Web Services AIF-C01 Practice Exam with Questions & Answers | Set: 3

The correct answer is B – Use Amazon Bedrock batch inference, which allows asynchronous generation of large-scale model outputs through APIs without requiring low-latency performance. According to AWS Bedrock documentation, batch inference is ideal for high-volume workloads that can tolerate delay, such as bulk content generation or summarization jobs. Unlike real-time inference, it processes requests in bulk, reducing cost and operational load. AWS handles the queuing, processing, and scaling automatically. Bedrock Agents (option C) are for workflow orchestration, not large-scale generation. AWS Lambda (option D) can automate tasks but is not optimized for high-volume LLM calls. Batch inference provides cost efficiency, scalability, and simplicity for delayed, asynchronous generation needs.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Batch Inference

AWS ML Specialty Study Guide – Scalable Inference Options

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Conversion rate measures the percentage of users who take a desired business action, such as completing a purchase after receiving recommendations.

In the context of:

Personalized product recommendations

Measuring direct impact on sales revenue

Conversion rate is the most relevant business metric, as it directly correlates AI-driven recommendations with revenue-generating outcomes.

Why the other options are incorrect:

Cross-domain performance (A) evaluates generalization across datasets, not revenue.

Solution efficiency (B) focuses on performance and cost, not sales impact.

User satisfaction (C) measures experience quality, not financial outcomes.

AWS AI document references:

AWS Generative AI Use Case Evaluation Guidance

Measuring Business Impact of AI Solutions

AI Metrics and KPIs on AWS

The correct answer is B – Data preprocessing, which involves cleaning, filtering, and transforming raw data before model training. AWS defines preprocessing as the step where irrelevant or poor-quality data (e.g., excessively short or misrecorded audio) is removed or normalized. The described task—filtering recordings by duration and language—is a textbook example of preprocessing since it prepares the dataset for downstream feature extraction. Feature engineering would occur afterward when converting audio signals into numerical representations (like Mel-frequency coefficients). Model training and data collection come after and before preprocessing respectively. Proper preprocessing ensures data consistency, reduces noise, and improves model accuracy, especially in audio-based healthcare models where clarity and consistency are critical.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Data Preprocessing and Cleaning

Amazon SageMaker Data Wrangler Documentation – Data Preparation Best Practices

A confusion matrix is the correct metric for evaluating the performance of a classification model, such as the deep learning model built to classify types of materials in images.

Confusion Matrix:

It is a table used to describe the performance of a classification model by comparing the actual and predicted classifications.

Provides detailed insights into the model’s performance, including true positives, true negatives, false positives, and false negatives.

Why Option A is Correct:

Performance Measurement: Helps measure various performance metrics like accuracy, precision, recall, and F1-score, which are critical for evaluating a classification model.

Comprehensive Evaluation: Allows for a thorough analysis of where the model is making errors and the types of errors being made.

Why Other Options are Incorrect:

B. Correlation matrix: Used to identify relationships between variables, not for evaluating classification performance.

C. R2 score: Used for regression models, not classification.

D. Mean squared error (MSE): Also a metric for regression, measuring the average of the squares of the errors.

When a model is trained on a dataset containing confidential or sensitive data, the model may inadvertently learn patterns from this data, which could then be reflected in its inference responses. To ensure that a model does not generate responses based on confidential data, the most effective approach is to remove the confidential data from the training dataset and then retrain the model.

Explanation of Each Option:

Option A (Correct): " Delete the custom model. Remove the confidential data from the training dataset. Retrain the custom model. " This option is correct because it directly addresses the core issue: the model has been trained on confidential data. The only way to ensure that the model does not produce inferences based on this data is to remove the confidential information from the training dataset and then retrain the model from scratch. Simply deleting the model and retraining it ensures that no confidential data is learned or retained by the model. This approach follows the best practices recommended by AWS for handling sensitive data when using machine learning services like Amazon Bedrock.

Option B: " Mask the confidential data in the inference responses by using dynamic data masking. " This option is incorrect because dynamic data masking is typically used to mask or obfuscate sensitive data in a database. It does not address the core problem of the model beingtrained on confidential data. Masking data in inference responses does not prevent the model from using confidential data it learned during training.

Option C: " Encrypt the confidential data in the inference responses by using Amazon SageMaker. " This option is incorrect because encrypting the inference responses does not prevent the model from generating outputs based on confidential data. Encryption only secures the data at rest or in transit but does not affect the model ' s underlying knowledge or training process.

Option D: " Encrypt the confidential data in the custom model by using AWS Key Management Service (AWS KMS). " This option is incorrect as well because encrypting the data within the model does not prevent the model from generating responses based on the confidential data it learned during training. AWS KMS can encrypt data, but it does not modify the learning that the model has already performed.

AWS AI Practitioner References:

Data Handling Best Practices in AWS Machine Learning: AWS advises practitioners to carefully handle training data, especially when it involves sensitive or confidential information. This includes preprocessing steps like data anonymization or removal of sensitive data before using it to train machine learning models.

Amazon Bedrock and Model Training Security: Amazon Bedrock provides foundational models and customization capabilities, but any training involving sensitive data should follow best practices, such as removing or anonymizing confidential data to prevent unintended data leakage.

The correct answer is A because ensuring responsibility and fairness in ML begins with bias detection in the training data. Including a balanced representation of all demographics ensures the model learns fairly across different groups, which is critical in regulated industries like finance.

From AWS documentation:

" A key principle of responsible AI is building models that do not propagate or amplify bias. Fairness begins with training data. Reviewing and augmenting data for representation is essential. "

Explanation of other options:

B. The number of hidden layers doesn’t inherently improve fairness or responsibility.

C. Keeping decisions opaque violates explainability principles in responsible AI.

D. A static dataset can become outdated and may not reflect real-world shifts, which limits fairness assessment over time.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker Clarify Documentation – Bias Detection and Explainability

AWS Responsible AI Guidelines

AWS ML Specialty Study Guide – Fairness and Governance

The verified answer is C. Faithfulness. The company is evaluating foundation models for a summarization task by using an LLM-as-a-judge evaluation job in Amazon Bedrock. AWS documentation states that with a model evaluation job that uses a judge model, Amazon Bedrock uses one LLM to score another model’s responses and provide an explanation of how it scored each prompt and response pair. AWS also states that Amazon Bedrock provides built-in metrics that can be selected for these judge-based evaluation jobs.

Among the answer choices, Faithfulness is the only valid built-in metric for an Amazon Bedrock LLM-as-a-judge model evaluation job. AWS API documentation lists the valid built-in metric names for LLM-as-a-judge evaluation jobs, including Correctness, Completeness, Faithfulness, Helpfulness, Coherence, Relevance, FollowingInstructions, ProfessionalStyleAndTone, and responsible AI metrics such as Harmfulness, Stereotyping, and Refusal. The same documentation identifies Summarization as a valid task type for model evaluation jobs. Therefore, Faithfulness is a valid built-in metric for evaluating whether generated summaries remain grounded in the source input rather than introducing unsupported claims.

Option A. Context relevance and option B. Context coverage are incorrect for this question because AWS lists those as metrics for knowledge base retrieval-only evaluation jobs, not general LLM-as-a-judge model evaluation of foundation model summarization output. These metrics evaluate retrieved context, not the quality of a summarization model’s generated response. Option D. RMSE is also incorrect because root mean square error is a regression metric. It is not a built-in LLM-as-a-judge metric for summarization in Amazon Bedrock.

Because the task is summarization and the evaluation job is LLM-as-a-judge, the correct built-in evaluation metric from the available choices is Faithfulness.

The evaluation stage of the generative AI model lifecycle involves testing the model to assess its performance, including accuracy, coherence, and other metrics. This stage ensures the model meets the desired quality standards before deployment.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

" The evaluation phase in the machine learning lifecycle involves testing the model against validation or test datasets to measure its performance metrics, such as accuracy, precision, recall, or task-specific metrics for generative AI models. "

(Source: AWS AI Practitioner Learning Path, Module on Machine Learning Lifecycle)

Detailed Explanation:

Option A: DeploymentDeployment involves making the model available for use in production. While monitoring occurs post-deployment, accuracy testing is performed earlier in the evaluation stage.

Option B: Data selectionData selection involves choosing and preparing data for training, not testing the model’s accuracy.

Option C: Fine-tuningFine-tuning adjusts a pre-trained model to improve performance for a specific task, but it is not the stage where accuracy is formally tested.

Option D: EvaluationThis is the correct answer. The evaluation stage is where tests are conducted to examine the model’s accuracy and other performance metrics, ensuring it meets requirements.

Generative Pre-trained Transformers (GPT) are suitable for building an AI-based application that can generate SQL queries from natural language input provided by employees.

GPT for Natural Language Processing:

GPT models are designed for understanding and generating human-like text based on natural language input.

They can be fine-tuned to interpret specific tasks, such as converting natural language queries into SQL queries.

Why Option A is Correct:

Natural Language Understanding: GPT is highly effective for tasks that require understanding of human language and generating structured outputs like SQL.

User-Friendly: Requires minimal technology experience from employees, as they provide simple text input.

Why Other Options are Incorrect:

B. Residual neural network: Typically used in computer vision tasks, not for natural language-to-SQL conversion.

C. Support vector machine: Used for classification tasks, not for generating structured queries from text.

D. WaveNet: A deep generative model for audio data, unrelated to text-to-SQL tasks.

The correct answer is A, as the most effective way to ensure fairness in AI systems is to audit and diversify training data. AWS Responsible AI documentation stresses that bias originates primarily from unbalanced or incomplete datasets. By including samples from all demographic groups, the model learns patterns that generalize fairly across populations. AWS SageMaker Clarify supports data bias detection and offers fairness metrics like demographic parity and equal opportunity difference. Deeper models (option B) or secrecy (option C) do not mitigate bias and may worsen transparency. Static test datasets (option D) fail to capture evolving data distributions. Therefore, ongoing bias reviews and diverse datasets form the foundation of responsible generative AI for financial use cases.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation – Bias Detection