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

BLEU (Bilingual Evaluation Understudy) is a metric used to evaluate the accuracy of machine-generated translations by comparing them against reference translations. It is commonly used for translation tasks to measure how close the generated output is to professional human translations.

Option A (Correct): " Bilingual Evaluation Understudy (BLEU) " : This is the correct answer because BLEU is specifically designed to evaluate the quality of translations, making it suitable for the company ' s use case.

Option B: " Root mean squared error (RMSE) " is incorrect because RMSE is used for regression tasks to measure prediction errors, not translation quality.

Option C: " Recall-Oriented Understudy for Gisting Evaluation (ROUGE) " is incorrect as it is used to evaluate text summarization, not translation.

Option D: " F1 score " is incorrect because it is typically used for classification tasks, not for evaluating translation accuracy.

AWS AI Practitioner References:

Model Evaluation Metrics on AWS: AWS supports various metrics like BLEU for specific use cases, such as evaluating machine translation models.

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 D because autoencoders are an unsupervised machine learning method commonly used for anomaly detection when labeled data is not available.

From AWS documentation:

" Autoencoders learn to compress and reconstruct input data. During anomaly detection, they learn normal patterns in data. Data points that the model cannot accurately reconstruct are flagged as anomalies. "

This approach is ideal when there is no labeled data and when patterns must be learned based on normal behavior alone — a common situation in IoT sensor data environments.

Explanation of other options:

A. Linear regression requires labeled data and is used for predicting continuous values.

B. Classification requires labeled data to assign inputs into categories.

C. Decision trees are supervised learning models and also require labeled datasets.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Unsupervised Learning Techniques

Amazon SageMaker Examples – Anomaly Detection Using Autoencoders

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Feature engineering focuses on:

Creating new features

Selecting the most relevant existing features

Improving model signal and accuracy

AWS ML best practices identify feature engineering as a key driver of predictive performance.

Why the other options are incorrect:

Visualization (A) helps understanding, not feature creation.

Hyperparameter tuning (B) optimizes models, not features.

Data collection (D) expands datasets but does not engineer features.

AWS AI document references:

Feature Engineering Best Practices

Improving Model Accuracy on AWS

ML Model Development Lifecycle

A prompt template defines how the model is structured and guided (system prompts, roles, guardrails).

An attack that reveals or leaks this prompt template is known as a prompt extraction attack.

The other options (persona switching, exploiting friendliness, ignoring prompts) describe adversarial techniques but do not directly expose the internal configured behavior.

???? Reference:

AWS Responsible AI – Prompt Injection & Extraction Attacks

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.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Bedrock is the managed AWS service designed specifically to develop, customize, and deploy foundation models with minimal effort.

Amazon Bedrock:

Provides direct access to multiple foundation models

Eliminates infrastructure management

Supports customization, evaluation, and deployment

Why the other options are incorrect:

SageMaker AI (B) requires more setup and ML expertise.

PartyRock (C) is for experimentation, not deployment.

Amazon Q Developer (D) is a productivity assistant.

AWS AI document references:

Amazon Bedrock Overview

Foundation Model Deployment on AWS

Reducing Development Effort with Managed AI Services

AWS HealthScribe provides speech-to-text and medical documentation generation, specifically designed for healthcare applications.

Amazon Polly is text-to-speech, not speech-to-text.

Amazon Rekognition is computer vision.

Amazon Q Developer is a generative AI assistant for developers, not healthcare.

???? Reference:

AWS Documentation – AWS HealthScribe

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

Amazon Personalize – Evaluating recommendation effectiveness

AWS ML Business Metrics