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

Amazon Comprehend Medical is designed for processing medical records and extracting key clinical entities, useful for summaries. Per the AWS Comprehend Medical documentation:

“Amazon Comprehend Medical enables extraction of relevant medical information from unstructured clinical text such as medications, conditions, and relationships, making it ideal for summarization tasks.”

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

The correct answer is B because Amazon Augmented AI (Amazon A2I) allows developers to integrate human review workflows into ML systems. It supports defining confidence thresholds, such that only low-confidence predictions are sent to human reviewers.

From AWS documentation:

"Amazon A2I provides built-in human review workflows for ML predictions. You can configure confidence thresholds to determine when human review is triggered, enabling continual adjustment based on accuracy needs."

This supports use cases where business decisions (like financial approvals) require manual oversight for edge cases.

Explanation of other options:

A. Amazon Personalize is used for recommendation systems, not human review.

C. Amazon Inspector is for security assessment and vulnerability scanning.

D. AWS Audit Manager is used for compliance audits, not ML prediction reviews.

Referenced AWS AI/ML Documents and Study Guides:

Amazon A2I Developer Guide – Confidence Threshold Configuration

AWS ML Specialty Guide – Human-in-the-Loop Systems

AWS Responsible AI Documentation – Review and Escalation Workflows

The correct answer is A, as the most effective way to ensure fairness in AI systems is to audit and diversify training data. AWS Responsible AI documentation stresses that bias originates primarily from unbalanced or incomplete datasets. By including samples from all demographic groups, the model learns patterns that generalize fairly across populations. AWS SageMaker Clarify supports data bias detection and offers fairness metrics like demographic parity and equal opportunity difference. Deeper models (option B) or secrecy (option C) do not mitigate bias and may worsen transparency. Static test datasets (option D) fail to capture evolving data distributions. Therefore, ongoing bias reviews and diverse datasets form the foundation of responsible generative AI for financial use cases.

Referenced AWS AI/ML Documents and Study Guides:

AWS Responsible AI Whitepaper – Fairness and Bias Mitigation

Amazon SageMaker Clarify Documentation – Bias Detection

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Clarify is designed to detect and explain bias in ML models and datasets.

AWS Responsible AI guidance recommends Clarify to:

Identify bias in predictions

Analyze feature attribution

Support fairness and ethical AI practices

Why the other options are incorrect:

Rekognition (A) analyzes images, not recommendation bias.

Amazon Q Developer (B) assists developers with code.

Comprehend (C) performs NLP tasks, not bias analysis.

AWS AI document references:

Amazon SageMaker Clarify Documentation

Detecting Bias in AI Systems

Responsible AI on AWS

The scenario involves analyzing customer feedback and automatically classifying it into categories such as product quality, customer service, and delivery experience. This task requires processing and understanding textual data, which is a core application of natural language processing (NLP). NLP encompasses techniques for analyzing, interpreting, and generating human language, including tasks like text classification, sentiment analysis, and topic modeling, all of which are relevant to this use case.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"Natural Language Processing (NLP) enables machines to understand and process human language. Common NLP tasks include text classification, sentiment analysis, named entity recognition, and topic modeling. Services like Amazon Comprehend can be used to classify text into predefined categories based on content."

(Source: AWS AI Practitioner Learning Path, Module on AI and ML Concepts)

Detailed Explanation:

Option A: Computer visionComputer vision involves processing and analyzing visual data, such as images or videos. Since the scenario deals with textual customer feedback, computer vision is not applicable.

Option B: Natural language processing (NLP)This is the correct answer. The task of classifying customer feedback into categories requires understanding and processing text, which is an NLP task. AWS services like Amazon Comprehend are specifically designed for such text classification tasks.

Option C: Recommendation systemsRecommendation systems suggest items or content based on user preferences or behavior. The scenario does not involve recommending products or services but rather classifying feedback, so this option is incorrect.

Option D: Fraud detectionFraud detection involves identifying anomalous or fraudulent activities, typically in financial or transactional data. The scenario focuses on text classification, not anomaly detection, making this option irrelevant.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Data residency refers to requirements that dictate where data is physically stored and processed, often to meet regulatory, legal, or organizational policies.

AWS governance guidance emphasizes that:

PII data may be legally required to remain within a specific geographic region

Customers can control data location by selecting AWS Regions

Data residency is a core component of data governance and compliance

Why the other options are incorrect:

Data mining (A) refers to extracting insights from data.

Pre-training bias (C) relates to model training data, not storage location.

Geolocation routing (D) concerns request routing, not data governance.

AWS AI document references:

AWS Data Governance and Residency

Responsible AI and Data Management on AWS

Security and Compliance in AWS Regions

Comprehensive and Detailed Explanation From Exact AWS AI documents:

AWS PrivateLink enables private connectivity between AWS services through VPC endpoints, ensuring traffic does not traverse the public internet.

AWS guidance recommends PrivateLink for:

Secure, private service access

Regulatory and compliance requirements

VPC-based architecture

Why the other options are incorrect:

IAM (A) controls access, not network routing.

Macie (B) is a data security service.

VPC peering (D) is not required for Bedrock access.

AWS AI document references:

Amazon Bedrock Networking and Security

Private Connectivity with AWS PrivateLink

Secure AI Architectures on AWS

Amazon SageMaker Model Cards provide a standardized way to document important details about an AI model, such as its purpose, performance, intended usage, and known limitations. This enables transparency and compliance while fostering better communication between stakeholders. It does not store models physically or optimize computational requirements. References: AWS SageMaker Model Cards Documentation.

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.