Crush the AWS AIF-C01 AI Practitioner Exam Without the Fluff

Generative AI models are used to create new content based on existing data. One common use case is generating photorealistic images from text descriptions, which is particularly useful in digital marketing, where visual content is key to engaging potential customers.

Option B (Correct): " Creating photorealistic images from text descriptions for digital marketing " : This is the correct answer because generative AI models, like those offered by Amazon Bedrock, can create images based on text descriptions, making them highly valuable for generating marketing materials.

Option A: " Improving network security by using intrusion detection systems " is incorrect because this is a use case for traditional machine learning models, not generative AI.

Option C: " Enhancing database performance by using optimized indexing " is incorrect as it is unrelated to generative AI.

Option D: " Analyzing financial data to forecast stock market trends " is incorrect because it typically involves predictive modeling rather than generative AI.

AWS AI Practitioner References:

Use Cases for Generative AI Models on AWS: AWS highlights the use of generative AI for creative content generation, including image creation, text generation, and more, which is suited for digital marketing applications.

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.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

AWS CloudTrail Lake provides:

Immutable (tamper-proof) storage of API activity

Advanced querying across multiple AWS services

Long-term retention for audit and compliance

AWS governance guidance recommends CloudTrail Lake for centralized, queryable audit logs.

Why the other options are incorrect:

Trusted Advisor (A) gives recommendations.

Macie (B) discovers sensitive data.

Inspector (D) performs vulnerability scans.

AWS AI document references:

AWS CloudTrail Lake Overview

Auditing AI Workloads on AWS

Centralized Compliance Logging

Comprehensive and Detailed Explanation From Exact AWS AI documents:

In Amazon Bedrock evaluations, Completeness measures how thoroughly a model or agent response addresses all aspects of the user prompt.

AWS evaluation guidance for LLM-as-a-judge explains that:

Completeness focuses on coverage of prompt requirements

It is especially useful for evaluating multi-part questions

It is a built-in qualitative metric in agent evaluation workflows

Why the other options are incorrect:

ROUGE (A) measures text overlap, mainly for summarization.

Following instructions (C) evaluates adherence, not coverage.

Refusal (D) measures appropriate refusal behavior.

AWS AI document references:

Amazon Bedrock Model Evaluation

LLM-as-a-Judge Metrics

Evaluating Agent Responses on AWS

Comprehensive and Detailed Explanation From Exact AWS AI documents:

This scenario describes prompt injection, which is a well-documented security and safety risk in generative AI systems.

Prompt injection occurs when a user intentionally crafts input prompts to override, manipulate, or bypass system instructions, guardrails, or safety policies defined by the AI application developer. The user’s instruction explicitly attempts to override prior system instructions and force the model into unrestricted behavior.

AWS Responsible AI and Generative AI security guidance describe prompt injection as:

An attempt to alter model behavior through malicious or manipulative user input

A risk that can lead to policy violations, unsafe outputs, or data misuse

A key concern when deploying large language models (LLMs) in production systems

Why the other options are incorrect:

Data bias (B) refers to skewed or unrepresentative training data, not user manipulation at inference time.

Hallucination (C) refers to the model generating incorrect or fabricated information.

Data exposure (D) involves leaking sensitive or private data, not instruction hijacking.

AWS AI document references (for exact extracts):

AWS Responsible AI Overview — section on Generative AI risks

Amazon Bedrock Security Best Practices — section on prompt injection and input validation

AWS Generative AI Governance Guidance — discussion of instruction hierarchy and guardrails

Explainability refers to the ability of an AI system to make its decision-making process clear and understandable to humans.

A is correct:

" Explainability is crucial for human-centered AI, especially in healthcare, to ensure that doctors and patients understand the rationale behind AI-driven recommendations. "

(Reference: AWS Responsible AI)

B relates to protecting data, not explanations.

C is about treating groups equally.

D is about managing data lifecycle, not providing rationales.

Artificial Intelligence (AI) is the broad field focused on simulating human problem-solving and cognitive abilities, including reasoning, perception, and decision-making.

(Reference: AWS Certified AI Practitioner Official Study Guide)

Machine Learning (ML) is a subset of AI that uses data-driven algorithms to identify patterns and make predictions without explicit programming for each specific task.

(Reference: AWS Machine Learning Overview)

Deep learning is a subset of ML that uses neural networks with many layers (deep neural networks) to process complex data and extract high-level features.

(Reference: AWS Deep Learning on AWS)

Underfitting occurs when a machine learning model is too simple to capture the underlying patterns in the training data. AWS documentation explains that an underfit model performs poorly on both training and test datasets, which directly matches the scenario described.

In this case, the model shows low accuracy during training and evaluation, indicating that it has not learned sufficient relationships from the data. AWS identifies common causes of underfitting as insufficient model complexity, inadequate feature representation, overly aggressive regularization, or insufficient training time.

Underfitting is different from overfitting. Overfitting occurs when a model performs well on training data but poorly on test data, which is not the situation here. Hallucination applies to generative AI outputs, not supervised ML model accuracy. Cross-validation is a model evaluation technique, not a cause of poor performance.

AWS emphasizes the importance of diagnosing underfitting early in the model development lifecycle. Remedies include increasing model complexity, adding relevant features, reducing regularization, or selecting a more expressive algorithm. These steps allow the model to better learn from the data and improve accuracy across both training and test sets.

AWS machine learning best practices clearly associate low performance on both datasets with underfitting, making this the most likely cause of the problem described.