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

The company needs to automatically group similar customers and products based on their characteristics, which is a clustering task. Unsupervised learning is the ML strategy for grouping data without labeled outcomes, making it ideal for this requirement.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

" Unsupervised learning is used to identify patterns or groupings in data without labeled outcomes. Common applications include clustering, such as grouping similar customers or products based on their characteristics, using algorithms like K-means or hierarchical clustering. "

(Source: AWS AI Practitioner Learning Path, Module on Machine Learning Strategies)

Detailed Explanation:

Option A: Unsupervised learningThis is the correct answer. Unsupervised learning, specifically clustering, is designed to group similar entities (e.g., customers or products) based on their characteristics without requiring labeled data.

Option B: Supervised learningSupervised learning requires labeled data to train a model for prediction or classification, which is not applicable here since the task involves grouping without predefined labels.

Option C: Reinforcement learningReinforcement learning involves training an agent to make decisions through rewards and penalties, not for grouping data. This option is irrelevant.

Option D: Semi-supervised learningSemi-supervised learning uses a mix of labeled and unlabeled data, but the task here does not involve any labeled data, making unsupervised learning more appropriate.

Supervised learning is appropriate when the dataset is labeled. The model uses this data to learn patterns and classify images. Unsupervised learning, reinforcement learning, and active learning are not suitable since they either require unlabeled data or different problem settings. References: AWS Machine Learning Best Practices.

AWS documentation recommends exposing deployed machine learning models through secure, managed API endpoints to provide controlled and scalable access for external consumers. Creating a secure API endpoint allows customers to invoke the model using standard HTTPS requests while maintaining strict security boundaries.

AWS services such as Amazon SageMaker support deploying models behind managed endpoints that integrate with AWS security features, including authentication, authorization, encryption in transit, throttling, and monitoring. By using an API-based approach, the company can ensure that external customers interact with the model without gaining direct access to the underlying infrastructure or credentials.

The other options introduce significant security risks. Sharing credentials directly violates AWS security best practices and could lead to unauthorized access. Custom authentication scripts in customer applications are difficult to standardize and maintain. Embedding the model directly into customer applications removes centralized control and makes updates and security management impractical.

AWS positions secure API endpoints as the preferred mechanism for exposing ML inference capabilities to external clients, making this the correct solution.

The verified answers are A. Model evaluation and C. AI model service cards. The question is specifically about explainability and transparency with model selections before a generative AI application goes to production. AWS AI Practitioner guidance identifies model selection as part of the foundation model lifecycle and includes evaluation as a required activity in that lifecycle. AWS also lists model-selection factors such as model type, performance requirements, capabilities, constraints, compliance, modality, latency, model complexity, customization, and input/output length. This means model evaluation directly supports responsible selection because it provides measurable evidence that a model meets the application’s business, technical, and governance requirements.

AI model service cards are also correct because AWS describes AI Service Cards as responsible AI documentation that improves transparency. AWS states that AI Service Cards provide information about intended use cases, limitations, responsible AI design choices, and performance optimization best practices for AWS AI services and models. AWS also links these cards to responsible AI areas such as fairness, bias, explainability, robustness, governance, transparency, privacy, and security. That directly addresses the company’s concern about transparency when choosing models.

Guardrails is not the best answer here. Guardrails are important for safety controls, denied topics, content filtering, and responsible runtime behavior, but the question focuses on explainability and transparency in model selection, not output filtering. Data encryption is incorrect because encryption protects data confidentiality at rest or in transit; it does not explain model behavior or document model limitations. Automated reasoning is also not the best match. It can support formal validation of specific policy-based logic, but it is not the primary AWS tool or technique for transparent model selection. Therefore, model evaluation and AI model service cards are the two techniques/tools that best address the stated requirement.