Free Amazon Web Services AIF-C01 Practice Exam with Questions & Answers | Set: 11

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Prompt engineering is the primary method for controlling tone, style, and behavior of foundation model responses.

AWS generative AI guidance explains that:

Prompts can define tone, voice, and response structure

Iterative refinement ensures consistent outputs

Prompt refinement requires no model retraining

Why the other options are incorrect:

Token limits (A) affect length, not tone.

Batch inferencing (B) affects processing mode, not response style.

Higher temperature (D) increases randomness, reducing consistency.

AWS AI document references:

Prompt Engineering Best Practices

Controlling Model Output Tone

Using Prompts with Foundation Models on AWS

Summarization is a natural language processing (NLP) task that condenses long documents into concise, meaningful summaries while retaining the key information.

Regression predicts numerical values.

Clustering groups similar items.

Classification assigns data into predefined categories.

???? Reference:

AWS NLP Use Cases – Summarization

The correct answer is D because autoencoders are an unsupervised machine learning method commonly used for anomaly detection when labeled data is not available.

From AWS documentation:

"Autoencoders learn to compress and reconstruct input data. During anomaly detection, they learn normal patterns in data. Data points that the model cannot accurately reconstruct are flagged as anomalies."

This approach is ideal when there is no labeled data and when patterns must be learned based on normal behavior alone — a common situation in IoT sensor data environments.

Explanation of other options:

A. Linear regression requires labeled data and is used for predicting continuous values.

B. Classification requires labeled data to assign inputs into categories.

C. Decision trees are supervised learning models and also require labeled datasets.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Unsupervised Learning Techniques

Amazon SageMaker Examples – Anomaly Detection Using Autoencoders

The correct answer is B because Amazon CloudWatch provides monitoring capabilities that include tracking usage metrics for Amazon Comprehend endpoints, such as invocation counts. You can configure CloudWatch to collect these metrics and create custom dashboards or alarms to report when an endpoint has zero usage over a period (e.g., 15 days).

From AWS documentation:

"Amazon CloudWatch enables you to collect and track metrics for Comprehend endpoints, create alarms, and automatically react to changes in your AWS resources."

This allows automated reporting and alerting for underused or idle endpoints.

Explanation of other options:

A. AWS Trusted Advisor focuses on general AWS resource optimization, security, and limits but does not track endpoint usage.

C. AWS CloudTrail tracks API calls but does not provide time-based monitoring or usage analysis over time.

D. AWS Config is used to track configuration changes and compliance, not endpoint usage metrics.

Referenced AWS AI/ML Documents and Study Guides:

Amazon CloudWatch Metrics for Amazon Comprehend

AWS Certified Machine Learning Specialty Guide – Monitoring and Logging Section

AWS Cloud Operations Guide – Resource Utilization Monitoring

The company wants an AI application to help employees check open customer claims, identify claim details, and access related documents. Agents for Amazon Bedrock can automate tasks by interacting with external systems, while Amazon Bedrock knowledge bases provide a repository of information (e.g., claim details and documents) that the agent can query to respond to employee requests, making this the best solution.

Exact Extract from AWS AI Documents:

From the AWS Bedrock User Guide:

"Agents for Amazon Bedrock enable developers to build applications that can perform tasks by interacting with external systems and data sources. When paired with Amazon Bedrock knowledge bases, agents can access structured and unstructured data, such as documents or databases, to provide detailed responses for use cases like customer service or claims management."

(Source: AWS Bedrock User Guide, Agents and Knowledge Bases)

Detailed Explanation:

Option A: Use Agents for Amazon Bedrock with Amazon Fraud Detector to build the application.Amazon Fraud Detector is for detecting fraudulent activities, not for managing customer claims or accessing documents. This option is irrelevant.

Option B: Use Agents for Amazon Bedrock with Amazon Bedrock knowledge bases to build the application.This is the correct answer. Agents for Amazon Bedrock can interact with knowledge bases to retrieve claim details and documents, enabling employees to check open claims and access relevant information.

Option C: Use Amazon Personalize with Amazon Bedrock knowledge bases to build the application.Amazon Personalize is for building recommendation systems, not for retrieving claim details or documents. This option does not meet the requirements.

Option D: Use Amazon SageMaker AI to build the application by training a new ML model.Training a new ML model on SageMaker is unnecessary and complex for this use case, as the task can be efficiently handled by Agents and knowledge bases on Amazon Bedrock.

SageMaker Model Registry, SageMaker Serverless interference

This question requires selecting the appropriate Amazon SageMaker feature for two distinct steps in the AI model lifecycle. Let’s break down each step and evaluate the options:

Step 1: Managing different versions of the model

The goal here is to identify a SageMaker feature that supports version control and management of machine learning models. Let’s analyze the options:

SageMaker Clarify: This feature is used to detect bias in models and explain model predictions, helping with fairness and interpretability. It does not provide functionality for managing model versions.

SageMaker Model Registry: This is a centralized repository in Amazon SageMaker that allows users to catalog, manage, and track different versions of machine learning models. It supports model versioning, approval workflows, and deployment tracking, making it ideal for managing different versions of a model.

SageMaker Serverless Inference: This feature enables users to deploy models for inference without managing servers, automatically scaling based on demand. It is focused on inference (predictions), not on managing model versions.

Conclusion for Step 1: The SageMaker Model Registry is the correct choice for managing different versions of the model.

Exact Extract Reference: According to the AWS SageMaker documentation, “The SageMaker Model Registry allows you to catalog models for production, manage model versions, associate metadata, and manage approval status for deployment.” (Source: AWS SageMaker Documentation - Model Registry, https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry.html).

Step 2: Using the current model to make predictions

The goal here is to identify a SageMaker feature that facilitates making predictions (inference) with a deployed model. Let’s evaluate the options:

SageMaker Clarify: As mentioned, this feature focuses on bias detection and explainability, not on performing inference or making predictions.

SageMaker Model Registry: While the Model Registry helps manage and catalog models, it is not used directly for making predictions. It can store models, but the actual inference process requires a deployment mechanism.

SageMaker Serverless Inference: This feature allows users to deploy models for inference without managing infrastructure. It automatically scales based on traffic and is specifically designed for making predictions in a cost-efficient, serverless manner.

Conclusion for Step 2: SageMaker Serverless Inference is the correct choice for using the current model to make predictions.

Exact Extract Reference: The AWS documentation states, “SageMaker Serverless Inference is a deployment option that allows you to deploy machine learning models for inference without configuring or managing servers. It automatically scales to handle inference requests, making it ideal for workloads with intermittent or unpredictable traffic.” (Source: AWS SageMaker Documentation - Serverless Inference, https://docs.aws.amazon.com/sagemaker/latest/dg/serverless-inference.html).

Why Not Use the Same Feature Twice?

The question specifies that each SageMaker feature or resource should be selected one time or not at all. Since SageMaker Model Registry is used for version management and SageMaker Serverless Inference is used for predictions, each feature is selected exactly once. SageMaker Clarify is not applicable to either step, so it is not selected at all, fulfilling the question’s requirements.

Regression predicts continuous numerical values (e.g., stock prices, temperatures).

A is classification (genre selection).

B is clustering.

D is generative AI/computer vision.

???? Reference:

AWS ML Glossary – Regression

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Inference latency measures the time it takes for a model to:

Receive an input request

Process the request

Return an output

AWS performance guidance emphasizes inference latency as a critical metric for real-time and user-facing AI applications.

Why the other options are incorrect:

Model size (A) refers to number of parameters.

Context window (C) defines input length capacity.

Fine-tuning (D) is a customization process.

AWS AI document references:

Foundation Model Performance Metrics

Latency Considerations for AI Applications

Optimizing Inference on AWS

The evaluation stage of the generative AI model lifecycle involves testing the model to assess its performance, including accuracy, coherence, and other metrics. This stage ensures the model meets the desired quality standards before deployment.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

"The evaluation phase in the machine learning lifecycle involves testing the model against validation or test datasets to measure its performance metrics, such as accuracy, precision, recall, or task-specific metrics for generative AI models."

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

Detailed Explanation:

Option A: DeploymentDeployment involves making the model available for use in production. While monitoring occurs post-deployment, accuracy testing is performed earlier in the evaluation stage.

Option B: Data selectionData selection involves choosing and preparing data for training, not testing the model’s accuracy.

Option C: Fine-tuningFine-tuning adjusts a pre-trained model to improve performance for a specific task, but it is not the stage where accuracy is formally tested.

Option D: EvaluationThis is the correct answer. The evaluation stage is where tests are conducted to examine the model’s accuracy and other performance metrics, ensuring it meets requirements.