Amazon Web Services Updated AIF-C01 Exam Questions and Answers by inayah

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

The correct answer is C because in image generation tasks using foundation models like Stable Diffusion on Amazon Bedrock, the number of generation steps directly influences the fidelity and level of detail of the generated image. Fewer steps can produce more abstract or less defined images, while more steps allow the model to refine details, resulting in higher realism.

From AWS documentation:

"In diffusion-based image generation models, the number of inference steps (generation steps) determines how refined the final image is. Lower steps produce faster but less detailed outputs. Increasing steps results in more detailed and higher-quality images."

Explanation of other options:

A. Model checkpoint refers to saved versions of the model during training, not inference-time generation settings.

B. Batch size affects training/inference throughput, not image detail.

D. Token length is relevant for text models, not image generation.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Model Parameters for Image Generation

Stable Diffusion on Amazon Bedrock – Developer Guide

AWS ML Specialty Guide – Generative AI Configuration

The correct answer is B, because AWS recommends that any generative AI initiative begin with use-case clarification, stakeholder alignment, and measurable business objectives. According to the AWS Generative AI Adoption Framework and the AWS Machine Learning Journey guidelines, successful AI projects start with defining specific business outcomes—such as revenue growth, reduced time-to-market, or improved campaign efficiency. Conducting stakeholder interviews ensures the organization identifies the highest-value marketing use cases, such as personalized campaigns or content generation, and sets KPIs to measure revenue impact within the target timeframe. AWS documentation emphasizes avoiding premature model training (option A), which is costly and unnecessary without validated requirements. Implementing a prebuilt assistant (option C) may help operations but does not guarantee alignment with the core revenue objective. Replicating competitor features (option D) may lack strategic alignment. Therefore, refining use cases and measurable goals is the foundational AWS-recommended approach for a targeted revenue-driven generative AI initiative.

Referenced AWS Documentation:

AWS Generative AI Adoption Framework

AWS ML Business Value and Use-Case Identification Guidelines

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