AIF-C01 Exam Dumps - Amazon Web Services AWS Certified AI Practitioner Questions and Answers

Comprehensive and Detailed Explanation From Exact AWS AI documents:

To secure data in Amazon Q Business, AWS recommends:

AWS KMS (A) to encrypt data at rest and manage encryption keys.

AWS IAM (E) to control authentication and authorization for users and services.

Together, these services ensure:

Strong access control

Data confidentiality

Compliance with enterprise security requirements

Why the other options are incorrect:

Cross-account access (B) does not inherently ensure privacy.

Amazon Inspector (C) is for vulnerability scanning, not authentication.

Public access (D) violates security best practices.

AWS AI document references:

Amazon Q Business Security Overview

Data Protection with AWS KMS

Access Control with AWS IAM

Unsupervised learning is the correct methodology for classifying customers into tiers when the data is unlabeled, as it does not require predefined labels or outputs.

Unsupervised Learning:

This type of machine learning is used when the data has no labels or pre-defined categories. The goal is to identify patterns, clusters, or associations within the data.

In this case, the company has petabytes of unlabeled customer data and needs to classify customers into different tiers. Unsupervised learning techniques like clustering (e.g., K-Means, Hierarchical Clustering) can group similar customers based on various attributes without any prior knowledge or labels.

Why Option B is Correct:

Handling Unlabeled Data: Unsupervised learning is specifically designed to work with unlabeled data, making it ideal for the company’s need to classify customer data.

Customer Segmentation: Techniques in unsupervised learning can be used to find natural groupings within customer data, such as identifying high-value vs. low-value customers or segmenting based on purchasing behavior.

Why Other Options are Incorrect:

A. Supervised learning: Requires labeled data with input-output pairs to train the model, which is not suitable since the company's data is unlabeled.

C. Reinforcement learning: Focuses on training an agent to make decisions by maximizing some notion of cumulative reward, which does not align with the company's need for customer classification.

D. Reinforcement learning from human feedback (RLHF): Similar to reinforcement learning but involves human feedback to refine the model’s behavior; it is also not appropriate for classifying unlabeled customer data.

The company is building a chatbot using an LLM on Amazon Bedrock, and the chatbot needs to use content from previous customer messages to resolve requests. Adding previous messages to the model prompt (also known as providing conversation history) enables the LLM to maintain context across interactions, allowing it to respond coherently based on the ongoing conversation.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"To enable a large language model (LLM) to maintain context in a conversation, you can include previous messages in the model prompt. This approach, often referred to as providing conversation history, allows the LLM to generate responses that are contextually relevant toprior interactions."

(Source: AWS Bedrock User Guide, Building Conversational Applications)

Detailed Explanation:

Option A: Turn on model invocation logging to collect messages.Model invocation logging records interactions for auditing or debugging but does not provide the LLM with access to previous messages during inference to maintain conversation context.

Option B: Add messages to the model prompt.This is the correct answer. Including previous messages in the prompt gives the LLM the conversation history it needs to respond appropriately, a common practice for chatbots on Amazon Bedrock.

Option C: Use Amazon Personalize to save conversation history.Amazon Personalize is for building recommendation systems, not for managing conversation history in a chatbot. This option is irrelevant.

Option D: Use Provisioned Throughput for the LLM.Provisioned Throughput in Amazon Bedrock ensures consistent performance for model inference but does not address the need to use previous messages in the conversation.

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

The correct answer is Amazon Bedrock, AWS’s fully managed service for building and scaling generative AI applications using foundation models (FMs). Bedrock gives developers access to models from leading providers such as Anthropic (Claude), Meta (Llama), Mistral, Cohere, and Amazon Titan. Users can invoke these models via API without managing infrastructure or model training. According to AWS documentation, Bedrock supports tasks such as text generation, summarization, question answering, image generation, and RAG workflows with minimal setup. It supports both on-demand and provisioned throughput modes and integrates with features like Guardrails, Knowledge Bases, and Agents for secure, enterprise-grade applications. Amazon Q Developer is a generative AI tool for developers, but it doesn’t host or scale models. Amazon Kendra is an intelligent search engine, and Amazon Comprehend is used for NLP tasks like entity extraction—not foundation model access.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Foundation Models and Use Cases

AWS Certified ML Specialty Guide – Generative AI on AWS

The correct answers are A and E because both directly align with AWS best practices for securing generative AI services and data privacy in enterprise applications.

From the AWS Amazon Q Business documentation:

"AWS Key Management Service (KMS) integrates with Amazon Q Business to encrypt sensitive data at rest. You can use customer-managed KMS keys to meet compliance requirements."

And:

"You must configure IAM access controls to manage which users and applications can access Amazon Q Business indexes, ensuring that only authorized users can retrieve information."

Explanation of other options:

B. Cross-account access is not a common requirement for internal enterprise use of Amazon Q Business unless explicitly sharing data across organizations. It’s not a requirement for securing access.

C. Amazon Inspector is a vulnerability management tool for EC2 and containers. It is unrelated to Amazon Q authentication or security.

D. Allowing public access would violate security and privacy principles and directly contradict the stated requirement.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Q Business Developer Guide – Security and Identity Management

AWS KMS Documentation – Integration with Bedrock and Amazon Q

AWS Certified Machine Learning Specialty Guide – Responsible AI and Governance Section

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 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.

Accuracy is the most appropriate metric to measure the performance of an image classification model. It indicates the percentage of correctly classified images out of the total number of images. In the context of classifying plant diseases from images, accuracy will help the company determine how well the model is performing by showing how many images were correctly classified.

Option B (Correct): "Accuracy": This is the correct answer because accuracy measures the proportion of correct predictions made by the model, which is suitable for evaluating the performance of a classification model.

Option A: "R-squared score" is incorrect as it is used for regression analysis, not classification tasks.

Option C: "Root mean squared error (RMSE)" is incorrect because it is also used for regression tasks to measure prediction errors, not for classification accuracy.

Option D: "Learning rate" is incorrect as it is a hyperparameter for training, not a performance metric.

AWS AI Practitioner References:

Evaluating Machine Learning Models on AWS: AWS documentation emphasizes the use of appropriate metrics, like accuracy, for classification tasks.

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI best practices emphasize that bias should be detected, measured, mitigated, and monitored throughout the ML lifecycle, especially for sensitive domains such as healthcare. When biased outcomes are observed, AWS guidance recommends addressing bias at the data and model level, not only at the output level.

Using Amazon SageMaker Clarify aligns directly with AWS Responsible AI principles because it is designed to:

Detect and quantify bias in datasets and model predictions across sensitive attributes such as demographic groups

Provide pre-training and post-training bias metrics, allowing practitioners to identify where bias originates

Support data-centric mitigation, including improving dataset balance and representativeness

After identifying bias with SageMaker Clarify, collecting additional balanced training data and retraining the model helps ensure that:

The model learns from a more representative dataset

Disparate treatment recommendations based on demographics are reduced

Fairness is improved while maintaining clinical accuracy

Why the other options are not sufficient or aligned with AWS best practices:

B. Prompt engineering can influence outputs but does not address underlying data or model bias and is not sufficient for regulated, high-risk domains like healthcare.

C. Content filtering removes outputs after generation but does not prevent biased decision-making by the model itself.

D. Separate FM endpoints by demographic group increases the risk of reinforcing bias and violates fairness principles rather than mitigating them.

AWS AI Study Guide References:

AWS Responsible AI principles: Fairness and Governance

Amazon SageMaker Clarify: bias detection and mitigation

AWS best practices for ML in high-risk domains such as healthcare