Question 1

Scenario: An email filtering system needs to fine-tune a pre-trained BERT model for spam detection using a labeled email dataset (binary classification). Goal: correctly load the pretrained weights and use them as the initialization point for fine-tuning without full retraining. Question- Which approach will correctly initialize the BERT model to achieve this requirement?. Options:

Accepted Answer

B

Explanation: The standard and most effective method for adapting a pre-trained BERT model to a new classification task, such as spam detection, is through fine-tuning. This process involves loading the weights of the pre-trained model, which has learned general language representations. The original final layer, designed for pre-training tasks (like Masked Language Modeling), is discarded. A new, randomly initialized classification layer (the "head") suitable for the specific downstream task (e.g., a linear layer with a sigmoid or softmax function for binary classification) is added. The entire model, including the pre-trained layers and the new classifier, is then trained on the task-specific labeled dataset (e.g., spam emails), allowing all weights to be adjusted to the new domain.

Question 2

Scenario: A customer service assistant needs to handle complex order inquiries, maintain conversation context across sessions, and securely update order records (execute actions). Question- Which solution best satisfies the companyʼs requirements?. Options:

Accepted Answer

D

Explanation: Agents for Amazon Bedrock are specifically designed to create applications that can execute multi-step tasks across company systems and data sources. This solution directly addresses all requirements: the agent uses a foundation model for complex reasoning and planning to handle inquiries; it can execute actions (e.g., update order records) via Action Groups that call APIs; and integrating with Amazon DynamoDB provides a persistent, scalable mechanism to store and retrieve conversation history and context, fulfilling the need to maintain state across multiple sessions. This architecture provides a robust and complete solution for the described scenario.

Question 3

Scenario: An Amazon Lex virtual assistant sometimes fails to recognize variations of its category themes (e.g., mapping "thrill-seeking" to "adventure"). Need an immediate solution to improve recognition without modifying the backend Lambda function or database structure. Question- Which action should the Generative AI Developer take to improve the chatbot’s ability to recognize these user inputs?. Options:

Accepted Answer

C

Explanation: The most effective and immediate solution is to use synonyms within the custom slot type. By defining "thrill-seeking" as a synonym for the existing enumeration value "adventure," you instruct Amazon Lex to map this user input directly to the canonical value. When a user mentions "thrill-seeking," Lex will resolve the slot's value to "adventure" before passing it to the backend. This approach correctly interprets the user's intent without requiring any modifications to the backend Lambda function or database, thus adhering to all constraints of the scenario.

Question 4

Scenario: A data scientist needs to develop a fraud detection model on SageMaker with a severely imbalanced dataset (fraudulent transactions are rare). They must minimize operational overhead and ensure the model is fair and unbiased. Question- Which approach will fulfill the given requirements?. Options:

Accepted Answer

D

Explanation: This approach correctly addresses all requirements of the scenario. Using the Synthetic Minority Oversampling Technique (SMOTE) is a standard and effective method for handling severely imbalanced datasets in classification tasks like fraud detection. Amazon SageMaker Pipelines are designed to automate and orchestrate machine learning workflows, which directly fulfills the requirement to minimize operational overhead. Finally, Amazon SageMaker Clarify is the specific AWS service designed to detect potential bias in data and models before deployment, ensuring the model is fair and unbiased. This combination provides a complete, automated, and responsible AI solution within the SageMaker ecosystem.

Question 5

Scenario: A research team needs a mechanism to represent user queries and internal documents as semantic embeddings to capture contextual relationships. The solution must be fully managed, scalable, and integrate easily with Bedrock AI agents for downstream RAG workflows. Question- Which approach best satisfies these requirements?. Options:

Accepted Answer

B

Explanation: The optimal approach is to use Amazon Titan Text Embeddings via Amazon Bedrock to generate semantic vector representations of the documents and queries. These embeddings are then stored in a managed, scalable vector database like Amazon OpenSearch Service. This architecture directly addresses the core requirement of creating semantic embeddings. It is a standard, fully managed, and scalable pattern for building the retrieval component of a Retrieval-Augmented Generation (RAG) workflow, which integrates natively with Agents for Amazon Bedrock as a knowledge base.

Question 6

Scenario: SageMaker notebook instances are deployed inside an isolated VPC with interface endpoints, yet unauthorized external users can still access them through the internet. Question- How can the team limit access to the SageMaker notebook instances, ensuring only authorized VPC users can connect?. Options:

Accepted Answer

C

Explanation: The most effective and specific method to ensure only users within the VPC can access the SageMaker notebook is to control the generation of the access URL itself. By applying an IAM policy that restricts the sagemaker:CreatePresignedNotebookInstanceUrl action with the aws:sourceVpce condition key, you ensure that the presigned URL required to access the notebook's interface can only be created when the request originates from the VPC interface endpoint. This directly links the authorization to connect with the user's network location, effectively preventing anyone outside the VPC from initiating an access session, which is the core of the requirement. Why Incorrect Options are Wrong: A. Set up VPC Traffic Mirroring to capture traffic to and from the notebook instances and identify unauthorized access attempts, enabling enhanced monitoring. VPC Traffic Mirroring is a passive monitoring tool for inspecting network traffic. It does not block or prevent access, making it a detective control, not a preventative one. B. Apply VPC Endpoint Policies to control which IAM users or services can access SageMaker AI through the VPC interface endpoint, providing more granular access control for interactions with SageMaker AI. VPC Endpoint Policies govern which principals can use the endpoint to make API calls. This does not control the network path to the notebook's web UI or prevent a user from using a presigned URL from outside the VPC. D. Update the security group for the notebook instances to restrict incoming traffic to only the CIDR blocks associated with the VPC. Apply this security group across all interfaces linked to the SageMaker notebook instances. While a necessary network-level control, this is less precise than option C. It doesn't prevent a user inside the VPC from sharing a valid presigned URL with an external party who could potentially use it if any other network path exists. Option C prevents the URL's creation from outside the VPC entirely. --- References: 1. Amazon SageMaker Developer Guide - Connect to a Notebook Instance Through a VPC Interface Endpoint: This official guide explicitly recommends the solution in option C. It states, "To ensure that users can access the notebook instance only when they are in your private VPC, create an IAM policy that allows the sagemaker:CreatePresignedNotebookInstanceUrl operation only from a specific VPC endpoint..." This directly supports using an IAM policy with a condition key as the primary mechanism. 2. AWS Identity and Access Management User Guide - AWS global condition context keys: This document details the aws:sourceVpce condition key, explaining that it is used to "check if the request is coming from a specific VPC endpoint." This is the technical foundation for the policy described in option C. 3. Amazon SageMaker API Reference - CreatePresignedNotebookInstanceUrl: The documentation for this API action confirms that it is the function used to "get a URL that you can use to connect to your notebook instance." Therefore, controlling this specific action is the most direct way to manage access to the notebook's UI.

Question 7

Scenario: An AI developer needs a scalable, secure way to collect telemetry data (temperature, pressure) from devices in remote locations with unstable connectivity, store it in Amazon S3, and minimize infrastructure management. Question- Which solution meets the given requirements?. Options:

Accepted Answer

A

Explanation: This solution provides a fully managed, serverless, and highly scalable pipeline for IoT data ingestion. Message Queuing Telemetry Transport (MQTT) is a lightweight protocol ideal for devices with constrained resources and unreliable network connectivity, as it supports different Quality of Service (QoS) levels to ensure message delivery. AWS IoT Core securely handles device communication at scale. The IoT Core rule engine can directly forward messages to an Amazon Data Firehose stream without any custom code. Firehose is a fully managed service that automatically batches, compresses, and encrypts the data before reliably delivering it to Amazon S3, perfectly aligning with the requirement to minimize infrastructure management.

Question 8

Scenario: A publishing company uses a text-to-text foundation model (FM) on Amazon Bedrock for summarization. The model misinterprets casual language, local expressions, and abbreviations in customer feedback, leading to inaccurate summaries. Question- Which solution provides the most efficient and cost-effective approach to improve the model's understanding of customer feedback? Options:

Accepted Answer

B

Explanation: Fine-tuning is the most appropriate technique for adapting a pre-trained foundation model to a specific domain, style, or vocabulary. The core problem is the model's inability to understand specific linguistic nuances (casual language, local expressions). By fine-tuning the existing Bedrock model with a labeled dataset of customer feedback, the model's weights are adjusted to learn these specific patterns. This directly improves its comprehension and summarization accuracy for this type of text. This method is significantly more efficient and cost-effective than training a new model from scratch and more robust than preprocessing or multi-step inference approaches. Amazon Bedrock provides built-in support for fine-tuning, making it the standard and recommended solution for this use case. Why Incorrect Options are Wrong: A. Training a new large-scale model from scratch is prohibitively expensive and time-consuming, making it the least efficient and cost-effective solution for this specific adaptation task. C. Removing slang and abbreviations via preprocessing would eliminate important context and nuance from the customer feedback, likely resulting in less accurate and incomplete summaries. D. This proposes a complex, two-step inference process (first CER, then Bedrock). It is less efficient due to increased latency, and the mechanism of using "metadata inputs" is not a standard, direct feature for influencing Bedrock's summarization logic. --- References: 1. Amazon Bedrock User Guide - Fine-tuning models: The official documentation states, "Fine-tuning improves model accuracy by providing your own task-specific labeled training data... Use fine-tuning to further specialize your model on a particular domain or task that is important to your business." This scenario of adapting to customer feedback language is a primary use case for domain adaptation. Source: Amazon Bedrock User Guide, Section: "Fine-tuning models". 2. Stanford University CS224N: NLP with Deep Learning - Lecture on Transfer Learning and Pre-training: Course materials explain that fine-tuning is the standard approach to adapt large pre-trained models (like those on Bedrock) to specific downstream tasks or data distributions. It is presented as a highly effective method that requires far fewer resources than pre-training from scratch. Source: Stanford University, CS224N Course Materials, Winter 2023, Lecture 12: "Pre-training and Transfer Learning". 3. Raffel, C., et al. (2020). Exploring the limits of transfer learning with a unified text-to-text transformer. This foundational paper on the T5 model, a text-to-text architecture similar to what's used for summarization, establishes fine-tuning as the primary method for adapting a single pre-trained model to a wide variety of downstream tasks, demonstrating its effectiveness and efficiency. Source: Journal of Machine Learning Research, 21(140), 1-67. Section 3.2 "Fine-tuning on a downstream task".

Question 9

Scenario: An ML engineer uses Amazon SageMaker Data Wrangler to explore a numerical feature
(image brightness) before applying normalization, as it affects model convergence.
Question- Which action should the engineer take to best understand the range and distribution of the
brightness feature values before transformation?.
Options:

Accepted Answer

D

Explanation: Amazon SageMaker Data Wrangler is designed for data preparation and includes powerful built-in analysis and visualization capabilities. A histogram is a standard and effective tool for exploratory data analysis of a single numerical feature. It visually represents the distribution of data, making it easy to understand the range, identify the central tendency, observe the spread, and spot potential outliers or skewness. Using the histogram feature directly within Data Wrangler is the most efficient and appropriate action for an engineer to understand the 'image brightness' feature before applying transformations like normalization.

Question 10

Scenario: A manufacturer needs to forecast weekly sales for a brand-new product variant that has no sales history (cold-start problem). The model must learn shared patterns across existing SKUs. Question- Which approach best satisfies these requirements?. Options:

Accepted Answer

C

Explanation: The scenario describes a classic cold-start forecasting problem where a model must be trained on existing product data to predict sales for a new product with no history. The Amazon SageMaker DeepAR algorithm is specifically designed for this use case. DeepAR trains a single model on multiple related time series (all SKUs), learning global patterns such as seasonality and trends. It can incorporate item metadata (e.g., brand, category) as features, allowing it to generate accurate forecasts for new items by associating them with patterns learned from existing, similar SKUs.

Question 11

Scenario: An ML pipeline uses a SageMaker Service API VPC interface endpoint in a public subnet. The team must ensure that only specific Amazon EC2 instances and IAM users can invoke SageMaker API operations through that endpoint. Question- Which combination of actions should the team take to secure the traffic to the SageMaker Service API? (Select TWO.) Options:

Accepted Answer

C, D

Explanation: To secure a VPC interface endpoint according to the principle of least privilege, a layered security approach is required, combining network-level and identity-level controls. 1. Network-Level Control: Security groups act as a stateful firewall for the endpoint's Elastic Network Interface (ENI). By configuring the security group (Option C) to only allow inbound traffic from the security group associated with the approved EC2 instances, you restrict network access to only those specific instances. 2. Identity-Level Control: VPC endpoint policies are IAM resource policies that control which principals (users, roles) can use the endpoint. Attaching a custom policy (Option D) that explicitly lists the ARNs of the allowed IAM users and roles ensures that only authorized identities can perform SageMaker API operations through the endpoint, regardless of their network location (within the allowed set). Combining these two controls effectively enforces the requirement that only specific users from specific instances can access the API.

Question 12

Scenario: Visualize recommendation results across four dimensions in SageMaker Canvas: X-axis (interest score), Y-axis (conversion rate), Color (product category), and Size (number of impressions). Question- Which approach best satisfies the given requirements? Options:

Accepted Answer

A

Explanation: A scatter plot is the most appropriate visualization for this scenario. It is specifically designed to show the relationship between two continuous numerical variables, which are mapped to the X-axis (interest score) and Y-axis (conversion rate). To incorporate additional dimensions, standard visualization techniques involve using other visual attributes. SageMaker Canvas scatter plots support mapping a third, categorical dimension (product category) to the color of the data points and a fourth, numerical dimension (number of impressions) to the size of the data points. This approach effectively and intuitively represents all four required dimensions in a single chart.

Question 13

Scenario: A recommendation endpoint experiences significant delays during predictable high-traffic sales events, resulting in poor user experience. The goal is to adjust the target tracking scaling policy to proactively ensure sufficient capacity and prevent latency issues during these peak periods. Question- Which solution will best meet the requirements?. Options:

Accepted Answer

B

Explanation: The scenario describes a predictable, recurring high-traffic event (a sales event). The goal is to proactively scale capacity before the event begins to prevent latency. Scheduled scaling is the only proactive scaling policy designed for this exact use case. It allows you to set a schedule to increase the number of instances at a specific time, ensuring the endpoint is prepared for the anticipated load increase. This directly addresses the requirement to prevent delays during predictable peaks by having sufficient capacity ready in advance.

Question 14

Scenario: Autonomous vehicle model training experiences slow startup times and low GPU utilization because the training job downloads data sequentially from S3. Goal: improve data access performance and training throughput while maintaining the S3 repository and avoiding data duplication. Question- Which solution should be implemented to optimize SageMaker AI training performance while maintaining the existing S3-based workflow?. Options:

Accepted Answer

A

Explanation: Amazon FSx for Lustre is a high-performance file system optimized for workloads like machine learning training. By creating an FSx for Lustre file system linked to the S3 bucket, the training data is presented to the SageMaker job through a high-throughput, POSIX-compliant file system interface. This architecture utilizes lazy loading, meaning data is fetched from S3 on-demand as it is first accessed. This dramatically reduces the training job's startup time because it doesn't need to wait for the entire dataset to be downloaded. The high-speed cache and parallel access capabilities of FSx for Lustre ensure that the GPUs are not starved for data, thus increasing utilization and overall training throughput, while S3 remains the persistent data repository.

Question 15

Scenario: Multiple recommendation models must be evaluated using A/B testing in production. The system must route live inference traffic, monitor real-time engagement metrics, and seamlessly direct 100% of traffic to the best-performing model with minimal operational overhead. Question- Which solution will meet these requirements in the most operationally efficient way?. Options:

Accepted Answer

A

Explanation: Amazon SageMaker multi-variant endpoints are the purpose-built, fully managed solution for this use case. They allow multiple models (variants) to be deployed behind a single endpoint, simplifying the client application. SageMaker handles the weighted distribution of live inference traffic to each variant for A/B testing. Performance metrics for each variant are emitted to Amazon CloudWatch automatically. Once the best-performing model is identified through engagement metrics, the endpoint configuration can be updated via a single API call to route 100% of the traffic to that variant. This approach abstracts away the underlying infrastructure management, offering the highest operational efficiency.

Free AWS AIP-C01 Actual Exam Questions