AIF-C01 Dumps with Practice Exam Questions Answers

Amazon Textract (E) automatically extracts text and structured data from scanned documents, such as PDFs.

Amazon Bedrock (B) offers access to LLMs (such as Amazon Titan or Anthropic Claude) for tasks like summarization and generating embeddings for search.

Workflow:

Amazon Textract extracts text from PDFs in S3.

Amazon Bedrock LLMs summarize the extracted text.

(Optional: Summaries can be indexed using Amazon OpenSearch or another search solution.)

A (Translate) is for language translation, not extraction or summarization.

C (Transcribe) is for audio to text, not PDFs.

D (Polly) is for text-to-speech.

“Amazon Textract extracts text, forms, and tables from scanned documents... Bedrock provides generative AI models to perform summarization and other text generation tasks.”

(Reference: Amazon Textract, Amazon Bedrock, AWS GenAI RAG Reference)

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 Amazon Bedrock Guardrails provides out-of-the-box configurable safety mechanisms to control the behavior of LLMs in generative AI applications. Guardrails can be configured with denylists, content filters, sensitive topics, and tone enforcement, all without retraining the model.

From AWS documentation:

" Amazon Bedrock Guardrails allows developers to define safety and responsible AI policies directly in the model inference layer, making it easy to prevent harmful, biased, or unsafe outputs with minimal configuration. "

Explanation of other options:

A. Bedrock playgrounds are interactive environments for testing prompts and models but do not provide production-grade safety enforcement.

B. SageMaker Clarify focuses on bias detection and explainability for supervised ML models — it does not directly apply guardrails to LLM outputs.

D. SageMaker JumpStart is for model fine-tuning and deployment, not for enforcing safety policies on LLM responses.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – Guardrails Overview

AWS Responsible AI Whitepaper

AWS Certified ML Specialty Study Guide – Safety in Generative AI

The company is building a chatbot using an LLM to answer questions about HR policies, with access to a large digital documentation base. Retrieval Augmented Generation (RAG) optimizes the LLM’s responses by retrieving relevant information from the documentation base and using it to generate accurate, contextually grounded answers, reducing hallucinations and improving response quality.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

" Retrieval Augmented Generation (RAG) enhances the performance of large language models by retrieving relevant information from external knowledge bases, such as documentation or databases, and incorporating it into the generation process. This technique ensures responses are accurate and grounded in the provided data, making it ideal for applications like policy chatbots. "

(Source: AWS Bedrock User Guide, Retrieval Augmented Generation)

Detailed Explanation:

Option A: Use Retrieval Augmented Generation (RAG).This is the correct answer. RAG leverages the documentation base to provide the LLM with relevant HR policy information, optimizing the chatbot’s responses for accuracy and relevance.

Option B: Use few-shot prompting.Few-shot prompting provides a few examples in the prompt to guide the LLM, but it is less effective than RAG for large documentation bases, as it cannot dynamically retrieve specific policy details.

Option C: Set the temperature to 1.Setting the temperature to 1 controls the randomness of the LLM’s output but does not optimize responses using external documentation. This option is unrelated to the documentation base.

Option D: Decrease the token size.Decreasing token size (likely referring to limiting input/output tokens) may reduce response length but does not optimize the quality of responses using the documentation base.

The correct answer is C – Amazon Kendra, AWS’s enterprise search service designed for organizations with large, diverse document repositories. Kendra uses machine learning and natural language understanding (NLU) to provide semantic search, meaning it retrieves results based on meaning rather than keyword matching. According to AWS documentation, Kendra is ideal for educational, enterprise, and knowledge-management scenarios where users need fast, accurate retrieval across PDFs, HTML, Office documents, FAQs, and multimedia transcripts. Kendra connectors can index content from S3, SharePoint, LMS platforms, and internal databases, making it perfect for large volumes of training materials. Amazon Comprehend (A) is for NLP tasks like entity extraction, not enterprise search. Amazon Textract (B) extracts text from PDFs and scanned materials but does not provide search capabilities. Amazon Personalize (D) is for personalized recommendations, not document retrieval. Kendra is purpose-built for enterprise search and aligns directly with the company ' s needs.

Referenced AWS Documentation:

Amazon Kendra Developer Guide – Enterprise Search

AWS ML Specialty Guide – Intelligent Search Systems