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

Comprehensive and Detailed Explanation (AWS AI documents):

AWS recommends Amazon SageMaker Feature Store as a centralized, managed repository for storing, discovering, and reusing features and datasets across teams and projects. Feature Store enables:

Feature discovery through searchable metadata

Reusability of curated datasets and features by future practitioners

Consistency between training and inference datasets

Governance and lineage, supporting responsible AI practices

Why the other options are incorrect:

A is intended for retrieval-augmented generation, not dataset sharing.

B does not provide discoverability, governance, or long-term reuse.

D is designed for sharing data with external subscribers, not internal ML teams.

AWS AI Study Guide References:

Amazon SageMaker Feature Store overview

AWS best practices for feature management and reuse

The verified answer is A. AWS Audit Manager. The requirement is recurring compliance assessments with documented evidence mapped to regulatory frameworks. AWS documentation states that AWS Audit Manager helps customers continually audit AWS usage to simplify risk and compliance management. It automates evidence collection so customers can assess whether policies, procedures, and controls are operating effectively. AWS also states that Audit Manager provides prebuilt frameworks that structure and automate assessments for compliance standards and regulations.

The key phrase is “documented evidence mapped to regulatory frameworks.” AWS Audit Manager creates assessments from frameworks, automatically runs resource assessments, collects data from in-scope AWS accounts, transforms that data into audit-friendly evidence, and attaches it to relevant controls. That is the exact service function being tested. AWS also explains that Audit Manager can generate reports for auditors and supports prebuilt frameworks for standards such as PCI DSS, GDPR, HIPAA, SOC 2, and AWS operational best practices.

AWS Trusted Advisor is incorrect because Trusted Advisor provides recommendations for cost optimization, performance, security, fault tolerance, service quotas, and operational excellence. It is not a compliance-evidence automation service.

AWS Secrets Manager is incorrect because it stores, rotates, and manages secrets such as database credentials and API keys. It does not automate compliance assessments.

Amazon Inspector is incorrect because it scans workloads for software vulnerabilities and unintended network exposure. It is security-focused, but it does not create recurring evidence-mapped compliance assessments.

Therefore, the correct service is AWS Audit Manager.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

The correct technique is fine-tuning, which is explicitly supported by Amazon Bedrock for customizing foundation models using high-quality labeled datasets.

Fine-tuning involves:

Starting with a pre-trained foundation model

Training it further using domain-specific, labeled data

Improving accuracy for specialized tasks, such as product classification, image-based understanding, and specification extraction

In this use case:

The company has labeled data

They want to customize model behavior

They require high accuracy and domain adaptation

These conditions match the definition of fine-tuning, not prompt-only methods.

Why the other options are incorrect:

A. Continued pre-training typically requires massive unlabeled datasets and is not the standard customization method exposed in Amazon Bedrock.

B. Creating an agent orchestrates model interactions and tools but does not customize the model’s learned parameters.

D. Prompt engineering improves responses through prompt design but does not modify the underlying model weights, making it insufficient for deep domain adaptation.

AWS AI document references (for exact extracts):

Amazon Bedrock Documentation — section on Model customization and fine-tuning

AWS Generative AI Study Guide — comparison of prompt engineering vs fine-tuning

Foundation Models on AWS — explanation of fine-tuning with labeled datasets

The correct answer is B because K-means is an unsupervised learning algorithm used for clustering data points into groups (clusters) based on feature similarity. It is ideal for customer segmentation use cases where the goal is to discover natural groupings based on buying behavior and demographics without pre-labeled data.

From AWS documentation:

" K-means is a clustering algorithm that assigns data points to one of K groups based on feature similarity. It is commonly used in marketing and customer segmentation to group users with similar characteristics. "

Explanation of other options:

A. K-nearest neighbors is a supervised classification algorithm, not intended for clustering.

C. Decision tree is also a supervised learning method used for classification or regression tasks.

D. Support vector machine is used for classification and regression, not unsupervised clustering.

Referenced AWS AI/ML Documents and Study Guides:

AWS ML Specialty Guide – Unsupervised Learning and Clustering

AWS ML Algorithm Selection Guide

Amazon SageMaker Built-in Algorithms – K-means Clustering