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

To determine customer sentiments based on written customer reviews, the company can use Amazon Comprehend and Amazon Bedrock.

Amazon Comprehend:

A natural language processing (NLP) service that uses machine learning to uncover insights and relationships in text.

Can analyze customer reviews to detect sentiments (positive, negative, neutral, or mixed) automatically.

Amazon Bedrock:

Provides access to foundational models (FMs) from multiple AI companies for tasks such as text generation, summarization, and sentiment analysis.

The company can use a pre-trained sentiment analysis model available on Amazon Bedrock for processing customer reviews.

Why Other Options are Incorrect:

A. Amazon Lex: Used for building conversational interfaces like chatbots, not for sentiment analysis.

C. Amazon Polly: Converts text to speech; it doesn't analyze sentiment.

E. Amazon Rekognition: Analyzes images and videos, not text.

The manufacturing company needs to create product descriptions in multiple languages, which requires automated language translation. Amazon Translate is a fully managed service that uses machine learning to provide high-quality translation between languages, making it the ideal solution for this task.

Exact Extract from AWS AI Documents:

From the Amazon Translate Developer Guide:

"Amazon Translate is a neural machine translation service that delivers fast, high-quality, and affordable language translation. It can be used to automatically translate text, such as product descriptions, into multiple languages to reach a global audience."

(Source: Amazon Translate Developer Guide, Introduction to Amazon Translate)

Detailed Explanation:

Option A: Amazon TranslateThis is the correct answer. Amazon Translate automates the translation of text into multiple languages, directly addressing the company’s need to create product descriptions in different languages.

Option B: Amazon TranscribeAmazon Transcribe converts speech to text, which is unrelated to translating text into multiple languages. This option is incorrect.

Option C: Amazon KendraAmazon Kendra is an intelligent search service that uses machine learning to provide answers from documents, not for translating text. This option is irrelevant.

Option D: Amazon PollyAmazon Polly is a text-to-speech service that generates spoken audio from text, not for translating text into other languages. This option does not meet the requirements.

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.

The requirement is to deploy a customized machine learning (ML) model and monitor its quality for potential drift over time in a production environment. Let’s evaluate each option:

A. Amazon Rekognition: This service is designed for image and video analysis, such as object detection, facial recognition, and text extraction. It is not suited for deploying custom ML models or monitoring model quality drift.

B. Amazon SageMaker Clarify: This feature helps detect bias in ML models and explains model predictions. While it addresses fairness and interpretability, it does not specifically focus on monitoring model quality drift over time in production.

C. Amazon Comprehend: This is a natural language processing (NLP) service for extracting insights from text, such as sentiment analysis or entity recognition. It does not support deploying custom ML models or monitoring model performance drift.

D. Amazon SageMaker Model Monitor: This feature is part of Amazon SageMaker and is specifically designed to monitor ML models in production. It tracks metrics such as data drift, model drift, and performance degradation over time, alerting users when issues are detected.

Exact Extract Reference: According to the AWS documentation on Amazon SageMaker, “Amazon SageMaker Model Monitor allows you to detect and remediate data and model quality issues in production. It continuously monitors the performance of deployed models, capturing data and model predictions to detect deviations from expected behavior, such as data drift or model performance degradation.” (Source: AWS SageMaker Documentation - Model Monitoring, https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor.html).

This directly aligns with the requirement to observe model quality drift, making Amazon SageMaker Model Monitor the correct choice.

To use a custom model that has been trained to improve summarization quality, the company must deploy the model on an Amazon SageMaker endpoint. This allows the model to be used for real-time inference through Amazon Bedrock or other AWS services. By deploying the model in SageMaker, the custom model can be accessed programmatically via API calls, enabling integration with Amazon Bedrock.

Option B (Correct): "Deploy the custom model in an Amazon SageMaker endpoint for real-time inference": This is the correct answer because deploying the model on SageMaker enables it to serve real-time predictions and be integrated with Amazon Bedrock.

Option A: "Purchase Provisioned Throughput for the custom model" is incorrect because provisioned throughput is related to database or storage services, not model deployment.

Option C: "Register the model with the Amazon SageMaker Model Registry" is incorrect because while the model registry helps with model management, it does not make the model accessible for real-time inference.

Option D: "Grant access to the custom model in Amazon Bedrock" is incorrect because Bedrock does not directly manage custom model access; it relies on deployed endpoints like those in SageMaker.

AWS AI Practitioner References:

Amazon SageMaker Endpoints: AWS recommends deploying models to SageMaker endpoints to use them for real-time inference in various applications.

Experimenting and refining the prompt is the best approach to ensure that the chatbot using a foundation model (FM) produces responses that adhere to the company's tone.

Prompt Engineering:

Adjusting and refining the prompt allows for better control over the FM's outputs, ensuring they align with the desired tone and style.

This iterative process involves testing different prompts and modifying them based on the model's responses to achieve the desired outcome.

Why Option C is Correct:

Directly Influences Output Quality: Allows for fine-tuning of the model’s responses to match the company's tone.

Cost-Effective: Does not require modifying the model itself, only the inputs to it.

Why Other Options are Incorrect:

A. Low limit on tokens: Limits response length but not the adherence to company tone.

B. Batch inferencing: Relates to processing multiple inputs, not controlling response tone.

D. Higher temperature: Increases randomness in responses, which could deviate from the desired tone.

Real-time inference is designed to provide immediate, low-latency predictions, which is necessary when the company requires near real-time latency for its ML models. This option is optimal when there is a need for fast responses, even with large input data sizes and substantial processing times.

Option A (Correct): "Real-time inference": This is the correct answer because it supports low-latency requirements, which are essential for real-time applications where quick response times are needed.

Option B: "Serverless inference" is incorrect because it is more suited for intermittent, small-scale inference workloads, not for continuous, large-scale, low-latency needs.

Option C: "Asynchronous inference" is incorrect because it is used for workloads that do not require immediate responses.

Option D: "Batch transform" is incorrect as it is intended for offline, large-batch processing where immediate response is not necessary.

AWS AI Practitioner References:

Amazon SageMaker Inference Options: AWS documentation describes real-time inference as the best solution for applications that require immediate prediction results with low latency.

The correct answer is C – Use a negative prompt. Negative prompts instruct a generative image model to avoid certain features, objects, or styles in the output. This technique is fully supported by models like Amazon Nova Canvas on Bedrock, which are based on diffusion or image generation architectures. According to AWS documentation, negative prompts refine output control by telling the model what not to include, thereby improving brand alignment, compliance, or creative direction. A higher temperature increases randomness, not control. A detailed prompt helps, but without exclusion instructions, the model may still include unwanted elements. Changing the model may yield better output but doesn’t directly solve this control requirement. Negative prompts are purpose-built for this scenario.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Prompt Engineering for Image Models

AWS Generative AI Guide – Controlled Generation with Negative Prompts

The scenario where a student copies content from generative AI to write essays represents the challenge of plagiarism in responsible AI use.

Plagiarism:

Occurs when someone uses content generated by AI (or any source) without proper attribution, claiming it as their own.

This is a key challenge with generative AI models, which can produce human-like text that might be misused for academic or other purposes.

Why Option C is Correct:

Represents Unauthorized Use: Copying content directly from AI without attribution is a clear case of plagiarism.

Ethical Concern: Highlights the ethical considerations around using AI-generated content responsibly.

Why Other Options are Incorrect:

A. Toxicity: Refers to harmful or offensive content generation, not content copying.

B. Hallucinations: When AI generates incorrect or nonsensical information, not plagiarism.

D. Privacy: Involves the misuse or exposure of personal information, not copying content.

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.