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

The verified answer is A. Present the model Shapley values. AWS documentation states that SageMaker Clarify provides feature attributions based on Shapley values. These values can determine the contribution each feature made to model predictions and can be provided for individual predictions or at a global level for the model as a whole. That is exactly what stakeholders need when they ask for transparency and explainability: they need to understand which features influenced the model’s decisions and how strongly those features contributed.

AWS also explains that SageMaker Clarify helps explain how ML models make predictions and that transparency is critical for consumers and regulators. Clarify’s explainability uses a model-agnostic feature attribution approach and includes a scalable implementation of SHAP. These explanations answer practical stakeholder questions such as why the model made a prediction, how it makes predictions, and which features have the largest influence on model behavior.

Option B is incorrect because accuracy measures predictive correctness, not explainability. A model can be highly accurate while still being opaque. Accuracy alone does not show why a specific prediction was made.

Option C is incorrect because a confusion matrix summarizes classification performance by showing true positives, false positives, true negatives, and false negatives. It is useful for evaluation, but it does not explain individual feature influence or model reasoning.

Option D is incorrect because a secure inference endpoint protects access to the deployed model. Security is important, but it does not provide transparency or explainability.

Therefore, presenting Shapley values is the correct solution because it directly explains feature contributions to model predictions.

The company wants an AI application to help employees check open customer claims, identify claim details, and access related documents. Agents for Amazon Bedrock can automate tasks by interacting with external systems, while Amazon Bedrock knowledge bases provide a repository of information (e.g., claim details and documents) that the agent can query to respond to employee requests, making this the best solution.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Agents for Amazon Bedrock enable developers to build applications that can perform tasks by interacting with external systems and data sources. When paired with Amazon Bedrock knowledge bases, agents can access structured and unstructured data, such as documents or databases, to provide detailed responses for use cases like customer service or claims management. "

(Source: AWS Bedrock User Guide, Agents and Knowledge Bases)

Detailed Explanation:

Option A: Use Agents for Amazon Bedrock with Amazon Fraud Detector to build the application.Amazon Fraud Detector is for detecting fraudulent activities, not for managing customer claims or accessing documents. This option is irrelevant.

Option B: Use Agents for Amazon Bedrock with Amazon Bedrock knowledge bases to build the application.This is the correct answer. Agents for Amazon Bedrock can interact with knowledge bases to retrieve claim details and documents, enabling employees to check open claims and access relevant information.

Option C: Use Amazon Personalize with Amazon Bedrock knowledge bases to build the application.Amazon Personalize is for building recommendation systems, not for retrieving claim details or documents. This option does not meet the requirements.

Option D: Use Amazon SageMaker AI to build the application by training a new ML model.Training a new ML model on SageMaker is unnecessary and complex for this use case, as the task can be efficiently handled by Agents and knowledge bases on Amazon Bedrock.

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.

The correct answer is A – Create an AI agent. Amazon Bedrock Agents provide autonomous orchestration abilities that allow an AI system to interpret user queries, convert them into structured API calls, retrieve data, generate formatted outputs (like CSVs), and interact with external systems such as Amazon S3. According to AWS documentation, Bedrock Agents combine LLM reasoning with tool use, meaning they execute multi-step workflows such as querying OpenSearch, processing results, generating files, and uploading to storage—all without custom coding. The agent defines actions, APIs, and data transformation steps, making it ideal for automated enterprise workflows. Few-shot prompting (B) only influences text generation and cannot perform external actions like uploading to S3. A hand-coded software application (C) is possible but contradicts the goal of using AI for orchestration and requires more operational effort. A decision tree (D) cannot execute API workflows. Bedrock Agents are explicitly designed to perform multi-step tasks like this.

Referenced AWS Documentation:

Amazon Bedrock Agents – Tool Use and Workflow Automation

AWS Generative AI Best Practices – Agent-Based Architectures

The most cost-effective combination is to perform the managed foundation-model customization through Amazon Bedrock and secure connectivity by using Amazon VPC and AWS PrivateLink .

AWS documentation states that when a Bedrock model-customization job is submitted, Amazon Bedrock accesses the designated training and validation data to fine-tune the selected foundation model. The customization operation is available programmatically through the Amazon Bedrock API.

For network isolation, AWS states: “Using a VPC protects your data” and recommends creating an interface endpoint with AWS PrivateLink so the data does not need to be available over the public internet.

AWS PrivateLink establishes private connectivity between resources in the VPC and Amazon Bedrock without routing application traffic through the public internet. For model customization, AWS supports supplying a VPC configuration containing appropriate subnets and security groups to protect access to training data.

AWS also documents that Bedrock fine-tuning data is used only for the customization process and is not used to train the underlying base model for unrelated customers. Training and validation data provided for fine-tuning is not retained by Bedrock after the job completes.

Option A would introduce unnecessary on-premises infrastructure and hardware costs. Fine-tuning supported Bedrock foundation models does not require deploying the entire service through AWS Outposts.

Option D is invalid because customers do not host the managed Amazon Bedrock service API on premises.

Option E provides monitoring and observability, but CloudWatch logging does not establish private network connectivity or isolate model-customization data.

Thus, Amazon Bedrock supplies the managed fine-tuning capability while VPC connectivity and AWS PrivateLink provide the private network path. This combination minimizes infrastructure management while satisfying the stated security requirement.

Therefore, the correct answers are B and C .

===========

The verified answer is A. Compare pre-deployment and post-deployment metrics such as time saved in documentation, number of actionable tasks created, and employee adoption rates. The question is not asking whether the FM produces technically accurate summaries. It is asking whether the FM meets company business objectives, and the stated objective is productivity improvement. AWS AI Practitioner guidance identifies business objective alignment metrics for AI applications, including task completion rate, user satisfaction, and cost per interaction. AWS also identifies business value metrics for generative AI applications such as ROI, efficiency, conversion rate, accuracy, and customer lifetime value. These are business-impact measurements, not just model-quality measurements.

Option A is best because it compares business outcomes before and after deployment. If the tool is intended to improve productivity, the company should measure actual productivity signals: reduced documentation time, more actionable tasks created, higher employee adoption, and other operational improvements. AWS Prescriptive Guidance separates generative AI monitoring into application health, business and user-interaction health, and model quality health. It states that business and user-interaction health evaluates whether the application meets business objectives by tracking adoption, customer satisfaction, productivity improvements, cost savings, and task automation efficiency.

Option B is incomplete because precision, recall, and BLEU are technical evaluation metrics. They can help assess output quality but do not prove productivity improved. Option C may improve the system, but adding RAG does not determine whether the current FM meets business objectives. Option D is also incomplete because employee sentiment alone does not measure actual productivity. Therefore, the correct solution is to compare pre-deployment and post-deployment business metrics.

Retraining or pre-training is costly and unnecessary for just using company policies.

Fine-tuning adapts models but is inefficient for frequently changing company documents.

Retrieval-Augmented Generation (RAG) is the best approach — it retrieves relevant policy documents from a knowledge base and feeds them into the model context in real time, ensuring accurate and up-to-date responses.

???? Reference:

AWS Documentation – RAG with Amazon Bedrock

AWS documentation identifies hallucinations as a known limitation of generative AI models, particularly when used in business and production environments. Hallucinations occur when a model generates outputs that are unrelated, incorrect, fabricated, or unsupported by the input data or provided context. These outputs often appear confident and fluent, which can make them difficult to detect without additional validation.

Generative AI models, including large language models, operate using probabilistic token prediction based on patterns learned during training. AWS explains that these models do not have true reasoning or factual grounding unless explicitly provided with context or external knowledge. As a result, when prompts are ambiguous, incomplete, or outside the model’s training distribution, the model may produce responses that are irrelevant or misleading.

This behavior presents a risk for business use cases such as customer support, reporting, or decision-making systems. AWS highlights hallucinations as a key challenge that must be mitigated through techniques such as Retrieval Augmented Generation (RAG), prompt engineering, human review, and output validation.

The other options are not correct. Interpretability refers to the ability to understand model decisions, not incorrect outputs. Data bias relates to skewed or unfair training data. Nondeterminism refers to variability in outputs, not relevance or correctness.

AWS consistently categorizes hallucinations as a primary disadvantage of generative AI, making this the correct answer.

The correct answer is D – F1 score, which is the harmonic mean of precision and recall. AWS documentation states that the F1 score is the preferred metric when evaluating ML models trained on imbalanced datasets, where one class appears significantly more often than others. Accuracy becomes misleading in these situations because a model can achieve high accuracy simply by predicting the majority class. Precision alone measures correctness of positive predictions, while recall measures completeness—neither fully captures class balancing performance. The F1 score provides a combined measurement that reflects how well the model identifies minority classes while avoiding excessive false positives. AWS’s ML Specialty Guide recommends using F1 for classification tasks where “class distribution is uneven or where both false negatives and false positives matter.” This metric provides a fairer assessment of overall model performance across all class categories.

Referenced AWS Documentation:

AWS Certified Machine Learning Specialty Guide – Metrics for Imbalanced Classes

Amazon SageMaker Developer Guide – Evaluating Classification Models

Model misuse is a key example of output vulnerability, where the output of a model can be intentionally or unintentionally used in ways that create harm or deviate from the model’s intended purpose. According to AWS Responsible AI guidance, output vulnerabilities refer to flaws or weaknesses in how a model’s predictions or generations are interpreted or used by external systems or users. This could involve using a generative model to produce harmful content, manipulate outputs to spread misinformation, or expose private information. AWS recommends that safeguards such as Guardrails, Human-in-the-Loop (HITL) validation, and ethical guidelines be enforced to mitigate these output risks. In contrast, data poisoning and data leakage are input-level vulnerabilities that corrupt model training, and parameter stealing is a model-level attack where internal configurations are extracted. Model misuse specifically reflects how outputs can be abused, making it a textbook example of output vulnerability.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Output Vulnerabilities

Amazon Bedrock Documentation – Guardrails for Responsible Generation