AIF-C01 Exam Dumps - AWS Certified AI Practitioner Exam

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.

The correct responsible AI dimension is Explainability . AWS defines explainability in its Responsible AI framework as “Having mechanisms to understand system behavior.” The AWS Generative AI Lens similarly characterizes explainability as “Understanding and evaluating system outputs.”

The wording of the question directly matches this AWS definition. The organization wants to understand and evaluate outputs produced by its generative AI system. Explainability concerns the mechanisms, methods, and information that allow developers, operators, auditors, customers, and other stakeholders to understand why an AI system produces particular behavior or outputs.

Explainability can involve examining influential features, reasoning about model behavior, analyzing response patterns, providing evidence or supporting information, and using interpretability techniques appropriate to the model architecture. For generative AI systems, the goal is not necessarily to expose every internal mathematical operation of a foundation model. Instead, organizations establish mechanisms that make system behavior sufficiently understandable for the intended use case and associated risks.

Controllability is different. AWS defines controllability as having mechanisms to monitor and steer AI system behavior. Examples include configuring guardrails, adjusting system behavior, establishing user controls, or restricting what an AI application can do.

Safety focuses on blocking or reducing harmful outputs and preventing misuse. It addresses risks where AI behavior might cause harm to users or other stakeholders.

Fairness concerns the different effects that an AI system can have on groups of stakeholders and seeks to detect or mitigate unwanted disparities or bias.

AWS recommends identifying responsible AI risks and selecting appropriate evaluation metrics for the relevant dimensions throughout development and deployment. Explainability is specifically measured when teams need to assess whether stakeholders can understand system behavior.

Because the requirement explicitly centers on understanding and evaluating AI-generated outputs , A. Explainability is the exact AWS-aligned answer.

===========

Sentiment analysis is the task of determining the emotional tone or intent behind a body of text (positive, negative, neutral).

This falls under Natural Language Processing (NLP) because it deals with understanding and processing human language.

Computer vision relates to images, robotics to autonomous machines, and time series forecasting to predicting values from sequential data.

📖 Reference:

AWS ML Glossary – NLP

The attack is specifically prompt leakage because the user ' s objective is to obtain confidential system-level instructions or configuration information from the AI application. AWS defines prompt leakage as user prompts designed to “extract or reveal the system prompt, developer instructions, or other confidential configuration details.”

The scenario precisely matches this definition. The user asks the assistant to disclose the guidelines used to configure it and to reproduce the complete initial setup. The assistant then reveals its system prompt. The defining outcome is therefore unauthorized disclosure of protected prompt instructions.

Prompt leakage is related to the broader category of prompt attacks , and a leakage attempt can involve prompt-injection techniques. However, when AWS asks for the specific type of attack and the attacker is intentionally trying to expose the hidden system prompt or developer instructions, prompt leakage is the more precise classification.

A jailbreak generally attempts to bypass model safeguards or restrictions so the model performs behavior that would normally be prohibited. Although jailbreaks and prompt leakage can overlap, the core purpose in this scenario is disclosure of system configuration rather than simply bypassing a safety policy.

Prompt injection is the broader technique of introducing malicious instructions designed to override or manipulate existing instructions. For example, an attacker might tell the application to ignore previous instructions. AWS includes jailbreaks, prompt injections, and prompt leakages within its prompt-attack filtering capabilities.

A denied topic violation occurs when content concerns a topic explicitly configured as prohibited in Amazon Bedrock Guardrails. It does not describe system-prompt disclosure.

AWS recommends protecting generative AI applications by using Bedrock Guardrails prompt-attack detection, clearly defined system instructions, controlled access to tools and resources, input evaluation, output validation, and security testing.

Because confidential system instructions were explicitly requested and subsequently disclosed, the exact AWS-aligned classification is B. Prompt leakage .

===========

The context window determines how much information can fit into a single prompt when using a large language model (LLM) like those on Amazon Bedrock.

Context Window:

The context window is the maximum amount of text (measured in tokens) that a language model can process in a single pass.

For LLM applications, the size of the context window limits how much input data, such as text for sentiment analysis, can be fed into the model at once.

Why Option B is Correct:

Determines Prompt Size: The context window size directly informs how much information (e.g., words or sentences) can fit in one prompt.

Model Capacity: The larger the context window, the more information the model can consider for generating outputs.

Why Other Options are Incorrect:

A. Temperature: Controls randomness in model outputs but does not affect the prompt size.

C. Batch size: Refers to the number of training samples processed in one iteration, not the amount of information in a prompt.

D. Model size: Refers to the number of parameters in the model, not the input size for a single prompt.

The verified selections are Few-shot prompting, Chain-of-thought prompting, and Zero-shot prompting. The first description matches few-shot prompting because AWS describes few-shot prompting as a technique that includes example outputs or demonstrations in the initial prompt so the model can understand the expected pattern before generating a response. The phrase “provide a small number of examples” is the key indicator. A few-shot prompt gives the model limited examples of the desired task, format, or reasoning style, and the model uses those examples as context for the next output.

The second description matches chain-of-thought prompting. AWS describes chain-of-thought prompting as a technique that helps a model solve a problem by following a series of intermediate reasoning steps before reaching the final answer. The wording “break down the step-by-step process” directly points to chain-of-thought prompting. This method is commonly associated with reasoning, arithmetic, logic, planning, and multi-step problem solving because the prompt encourages the model to work through intermediate steps rather than immediately outputting a final answer.

The third description matches zero-shot prompting because AWS describes zero-shot prompting as asking the model to perform a task without providing examples in the prompt. The model relies only on the instruction and its pre-trained knowledge. The phrase “without providing examples” is the decisive clue.

Role-based prompting is not used here because none of the descriptions asks the model to act as a specific persona, job role, or domain expert, such as “Act as a financial analyst” or “You are a security engineer.” Single-shot prompting is also not used because the first description says a “small number of examples,” which indicates few-shot prompting, not exactly one example. Therefore, the three correct hotspot mappings are Few-shot prompting, Chain-of-thought prompting, and Zero-shot prompting.

Retrieval Augmented Generation (RAG) combines information retrieval with foundation model inference to generate contextually relevant answers.

Instead of requiring extensive labeled training datasets, RAG retrieves relevant information from existing enterprise data sources and supplies that information to a foundation model as contextual input.

For this scenario, the product database already contains the information needed to answer customer questions. A RAG architecture can retrieve relevant product descriptions during inference without retraining the foundation model.

Amazon Bedrock Knowledge Bases offers managed retrieval capabilities that simplify implementing this architecture.

Fine-tuning requires additional model customization and maintenance. Deploying separate models increases operational complexity, while training a foundation model from scratch requires substantial computational resources and expertise.

RAG therefore provides the most practical solution with comparatively low implementation effort, particularly when product information changes frequently.