Free MLA-C01 Practice Test Questions and Answers (2026)

The most efficient solution with the least operational overhead is to use Amazon Macie for identification and AWS Lambda for removal. Amazon Macie is a fully managed data security service specifically designed to discover sensitive data in Amazon S3 using machine learning and pattern matching. This eliminates the need to build and maintain custom identification logic. Macie can publish its findings to Amazon EventBridge, which can then automatically trigger an AWS Lambda function. The Lambda function, being serverless, executes the code to remove or redact the sensitive data without requiring server management, thus minimizing operational overhead.

A: Creating custom Lambda functions to identify sensitive data requires significant development and maintenance effort, which is higher operational overhead compared to using the managed Amazon Macie service.

B: This solution involves custom code within an AWS Batch job and managing an ECS cluster, which introduces more operational complexity and overhead than the serverless Macie and Lambda approach.

D: While Amazon Comprehend can detect PII, Macie is purpose-built for scalable sensitive data discovery in S3. More importantly, using EC2 instances for removal incurs high operational overhead for management, patching, and scaling.

1. Amazon Macie: "Amazon Macie is a data security service that discovers sensitive data by using machine learning and pattern matching... With Macie

you can automate the discovery of sensitive data at scale and lower the cost of protecting your data."

Source: AWS Documentation

"What is Amazon Macie?"

aws.amazon.com/macie/what-is-macie/.

2. Macie and Lambda Integration: "You can configure Amazon Macie to publish findings to Amazon EventBridge as finding events. Then you can use EventBridge to define rules that route the events to targets

such as AWS Lambda functions... for automated remediation."

Source: AWS Macie User Guide

"Monitoring Macie findings with Amazon EventBridge"

docs.aws.amazon.com/macie/latest/user/findings-monitor-events.html.

3. AWS Lambda for Low Overhead: "AWS Lambda is a serverless

event-driven compute service that lets you run code for virtually any type of application or backend service without provisioning or managing servers. You can trigger Lambda from over 200 AWS services..."

Source: AWS Documentation

"AWS Lambda"

aws.amazon.com/lambda/.

Amazon SageMaker endpoints automatically publish operational metrics to Amazon CloudWatch. The Invocations metric specifically counts the number of requests sent to a SageMaker endpoint. This solution directly addresses the requirements by using the native, purpose-built metric for monitoring invocation counts. A CloudWatch dashboard can be used for visualization, and a CloudWatch alarm can be configured on the Invocations metric to send a notification when a specified threshold is breached. This is the most direct and efficient method.

A: SageMaker Debugger is designed to capture and analyze internal model tensors during training or inference for debugging purposes, not for counting external API calls.

B: The tensorvariance rule is a specific SageMaker Debugger feature for monitoring tensor statistics during training, which is irrelevant to counting endpoint API invocations.

C: While AWS CloudTrail logs API calls for auditing, using it for high-frequency operational metrics is less efficient than using the dedicated CloudWatch metrics that SageMaker provides automatically.

1. Amazon SageMaker Developer Guide: "Amazon SageMaker monitors your endpoints and sends metrics to Amazon CloudWatch. For real-time inference

these metrics are by variant... Invocations: The number of invocations of this variant."

Source: AWS Documentation

"Monitor Amazon SageMaker with Amazon CloudWatch

" section on "Endpoint Invocation Metrics."

2. Amazon CloudWatch User Guide: "You can create a CloudWatch alarm that watches a single CloudWatch metric... If the metric breaches the threshold for a specified number of evaluation periods

the alarm performs one or more actions (such as sending a notification to an Amazon SNS topic)."

Source: AWS Documentation

"Using Amazon CloudWatch alarms."

3. Amazon SageMaker Developer Guide (on Debugger): "Amazon SageMaker Debugger provides tools to debug your training scripts in near real time... Debugger gains visibility into the training process by capturing tensors."

Source: AWS Documentation

"Debug and Profile Training Jobs Using Amazon SageMaker Debugger."

The described symptoms—high, oscillating training and validation loss—are characteristic of a learning rate that is too high for the given model and data. In stochastic gradient descent (SGD), a high learning rate causes the optimizer to take excessively large steps, overshooting the minimum of the loss function. This leads to the loss value bouncing around the minimum without converging, creating the observed oscillating pattern. Decreasing the learning rate will reduce the step size, allowing the optimizer to descend more smoothly and stably towards a minimum, thereby improving the training process.

A. Introduce early stopping: Early stopping is a regularization technique to prevent overfitting (when validation loss increases while training loss decreases), not to fix a fundamental convergence problem where both losses are high and oscillating.

B. Increase the size of the test set: The test set is used for final model evaluation after training. Its size has no impact on the training dynamics or the convergence of the loss function.

C. Increase the learning rate: The symptoms indicate the learning rate is already too high. Increasing it further would exacerbate the oscillations and likely cause the loss to diverge completely.

1. Goodfellow

I.

Bengio

Y.

& Courville

A. (2016). Deep Learning. MIT Press.

Section 8.3.1

"Learning Rate": The text explains

"If the learning rate is too large

gradient descent can inadvertently increase the value of the objective function... This happens when a step is so large that it steps over the minimum and lands in a region with a higher cost than the starting point." This directly explains the oscillating and increasing loss pattern.

2. Karpathy

A. (n.d.). CS231n: Convolutional Neural Networks for Visual Recognition. Stanford University.

Module 1: Neural Networks Part 3

"Learning and Evaluation" section: The course notes illustrate how a learning rate that is too high causes the loss to "jump" around or diverge. A visual diagram shows the loss curve oscillating wildly when the learning rate is too high

matching the scenario in the question.

3. Amazon Web Services (AWS). (2023). Tune a Model with the SageMaker API. AWS Documentation.

Section: "Learning rate": The documentation identifies the learning rate as a critical hyperparameter that "controls how much to change the model in response to the estimated error each time the model weights are updated." Unstable training

as described

is a primary reason to adjust this hyperparameter

typically by decreasing it.

The Amazon SageMaker Model Registry is the purpose-built service for centrally cataloging, versioning, and managing machine learning models for deployment. The core organizational construct within the Model Registry is the "model package group" (or model group). A model group is used to collect and manage different versions of the same model. By registering each new model iteration as a new version within a specific model group, the company can track lineage, compare performance metrics, and manage the approval status for each version, fulfilling the requirement with the least operational overhead as it is a managed, integrated feature.

A. Create a separate Amazon Elastic Container Registry (Amazon ECR) repository for each model.

Amazon ECR is a registry for container images, not a model registry. This approach lacks the necessary governance, metadata, and versioning features specific to ML models.

B. Use Amazon Elastic Container Registry (Amazon ECR) and unique tags for each model version.

This is also incorrect as ECR is for container images. While tags provide a form of versioning for images, it does not provide the model-centric features of the SageMaker Model Registry.

D. Use the SageMaker Model Registry and unique tags for each model version.

While tags can be applied for metadata, the primary mechanism for cataloging and versioning models in the SageMaker Model Registry is the "model group," not tags. This option is less precise.

1. Amazon SageMaker Developer Guide: "With Amazon SageMaker Model Registry you can catalog models for production

manage model versions

associate metadata... You group model versions that you create in the model registry into model groups."

Source: AWS Documentation

Amazon SageMaker Developer Guide

"SageMaker Model Registry".

URL: https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry.html

2. Amazon SageMaker Feature Page: "Amazon SageMaker Model Registry is a purpose-built tool that allows you to catalog your ML models... You can track model lineage

approve models for deployment

and deploy them from the registry..."

Source: AWS Documentation

Amazon SageMaker Features.

URL: https://aws.amazon.com/sagemaker/model-registry/

3. Amazon SageMaker API Reference: The CreateModelPackageGroup API call is used to "Creates a model package group. A model package group is a collection of model packages." This confirms that the group is the primary collection entity.

Source: AWS Documentation

Amazon SageMaker API Reference.

URL: https://docs.aws.amazon.com/sagemaker/latest/APIReference/APICreateModelPackageGroup.html

This solution meets the requirements with the least operational overhead by using fully managed AWS services designed for this specific use case. Amazon Kinesis Data Streams is built for ingesting high-volume, real-time data. Amazon Managed Service for Apache Flink is a serverless, real-time processing service that directly integrates with Kinesis. Crucially, it includes the built-in RANDOMCUTFOREST function, which is an unsupervised algorithm specifically for detecting anomalies in streaming data. This combination provides a scalable, real-time anomaly detection pipeline without the need to provision servers, manage clusters, or develop, train, and deploy a separate machine learning model.

B: This approach introduces higher operational overhead by requiring the user to build, train, deploy, and manage a separate Amazon SageMaker endpoint, in addition to developing and managing the AWS Lambda integration code.

C: This option has the highest operational overhead because it involves self-managing an Apache Kafka cluster on Amazon EC2 instances, which requires significant effort for setup, scaling, patching, and maintenance.

D: This solution is incorrect because it uses AWS Glue for batch processing, which does not meet the real-time requirement. Amazon SQS is also less suited for real-time streaming analytics than Kinesis.

1. Amazon Managed Service for Apache Flink

RANDOMCUTFOREST: "The RANDOMCUTFOREST function assigns an anomaly score to each record. Low scores indicate that the record is normal

and high scores indicate the presence of an anomaly in the data." This built-in function is designed for this exact purpose.

Source: AWS Documentation

Amazon Managed Service for Apache Flink Developer Guide

"RANDOMCUTFOREST".

URL: https://docs.aws.amazon.com/managed-flink/latest/apiv2/analytics-sql-reference-random-cut-forest.html

2. Amazon Kinesis Data Streams for Real-Time Processing: "You can use Kinesis Data Streams to collect and process large streams of data records in real time... The processed records can then be sent to dashboards

used to generate alerts

dynamically change pricing and advertising strategies

or send data to a variety of other AWS services."

Source: AWS Documentation

Amazon Kinesis Data Streams Developer Guide

"What Is Amazon Kinesis Data Streams?".

URL: https://docs.aws.amazon.com/streams/latest/dev/introduction.html

3. Operational Overhead of Self-Managed vs. Managed Services: Managed services like Kinesis and Managed Flink reduce operational burden compared to self-managing infrastructure like Apache Kafka on EC2. "Amazon Kinesis is fully managed and runs on a serverless architecture... With Apache Kafka

you are responsible for provisioning servers

managing cluster capacity..."

Source: AWS Documentation

Streaming Data Solutions on AWS with Amazon Kinesis

"Amazon Kinesis versus Apache Kafka".

URL: https://aws.amazon.com/kinesis/streaming-data/kinesis-vs-kafka/

The question requires a solution to resolve class imbalance with the least operational effort before model training. Amazon SageMaker Data Wrangler is specifically designed for preparing data for machine learning within the SageMaker ecosystem. It includes a built-in "Balance Data" transform that allows an engineer to oversample the minority class using techniques like SMOTE or random oversampling through a simple graphical interface. Since the engineer is already developing the model on AWS, using an integrated tool like Data Wrangler within SageMaker Studio provides the most streamlined workflow and thus represents the least operational effort.

A. Use Amazon Athena to identify patterns that contribute to the imbalance. Adjust the dataset accordingly.

Athena is a query service for analysis, not a data transformation tool. Manually adjusting the data after analysis would require significant operational effort.

B. Use Amazon SageMaker Studio Classic built-in algorithms to process the imbalanced dataset.

This addresses the imbalance during training (e.g., using hyperparameters), but the requirement is to resolve the issue before training the model.

C. Use AWS Glue DataBrew built-in features to oversample the minority class.

While DataBrew can perform this task, SageMaker Data Wrangler is more tightly integrated into the SageMaker ML workflow, making it the more direct and lower-effort path.

1. Amazon SageMaker Data Wrangler - Balance Data Transform: The official documentation details the "Balance Data" transform

which supports various oversampling and undersampling techniques. This is a point-and-click feature

minimizing operational effort.

AWS Documentation: Amazon SageMaker Developer Guide

"Balance Data". (URL: https://docs.aws.amazon.com/sagemaker/latest/dg/data-wrangler-transform-balance-data.html)

2. AWS Glue DataBrew - Balancing Transformations: The DataBrew documentation shows it also has balancing capabilities

confirming the technical validity of option C but highlighting it as a separate service from the core SageMaker workflow.

AWS Documentation: AWS Glue DataBrew Developer Guide

"Creating dataset-balancing transformations". (URL: https://docs.aws.amazon.com/databrew/latest/dg/creating-dataset-balancing-transformations.html)

3. Amazon SageMaker XGBoost Algorithm - Hyperparameters: The documentation for SageMaker's XGBoost algorithm lists scaleposweight as a hyperparameter to handle imbalanced data during training

confirming the mechanism described in option B is a training-time solution.

AWS Documentation: Amazon SageMaker Developer Guide

"XGBoost Hyperparameters". (URL: https://docs.aws.amazon.com/sagemaker/latest/dg/xgboosthyperparameters.html)

The most effective and non-disruptive solution is to use tags. Tagging is the standard AWS method for applying custom metadata to resources for organization and discovery. By creating a custom tag (e.g., a key named ML-Category with values like Computer-Vision or NLP) and applying it to the appropriate model packages, the data scientists can easily search and filter models. This method adds a layer of organization without altering the model artifacts or changing their membership in existing model groups, thereby satisfying all the requirements of the scenario.

B. Create a model group for each category. Move the existing models into these category model groups.

This is incorrect because it violates the constraint to not affect the models' "existing groupings." Moving a model package to a new model group changes its fundamental grouping.

C. Use SageMaker ML Lineage Tracking to automatically identify and tag which model groups should contain the models.

This is incorrect because SageMaker Lineage Tracking is designed to trace the provenance and relationships between ML artifacts (e.g., data, jobs, models), not for applying high-level business categorization for discovery.

D. Create a Model Registry collection for each of the three categories. Move the existing model groups into the collections.

This is incorrect because "Model Registry collection" is not a feature in Amazon SageMaker. The primary organizational construct within the SageMaker Model Registry is the model group.

1. Tagging Model Package Groups: The AWS SageMaker Developer Guide explicitly states

"You can assign your own metadata to model package groups that you create in Amazon SageMaker. Each tag is a label consisting of a user-defined key and value. Tags can help you manage

identify

organize

search for

and filter resources." This directly supports using tags for organization.

Source: AWS SageMaker Developer Guide

"Tagging Model Package Group Resources". (aws.amazon.com/sagemaker/latest/dg/model-registry-model-group-tagging.html)

2. Model Groups Definition: A model group is a container for different versions of a single ML model. Moving a model package would mean changing its primary organizational container

which the prompt forbids.

Source: AWS SageMaker Developer Guide

"Create a Model Group". (aws.amazon.com/sagemaker/latest/dg/model-registry-model-group.html)

3. SageMaker Lineage Tracking Purpose: The documentation defines lineage tracking's purpose as tracing relationships between workflow components

which is different from the requirement of categorical organization for discovery.

Source: AWS SageMaker Developer Guide

"Amazon SageMaker ML Lineage Tracking". (aws.amazon.com/sagemaker/latest/dg/lineage-tracking.html)

With Amazon Data Firehose the only controllable contributor to end-to-end latency is the delivery stream’s buffering hint. Setting the buffer interval to 0 seconds (and using the smallest practical PutRecordBatch size) causes each record to be forwarded to Amazon OpenSearch Service as soon as it is received, eliminating the 60-second wait and allowing sub-second propagation to the dashboard.

B. AWS DataSync is a scheduled bulk-transfer service; it has no concept of streaming or enhanced fan-out consumers, so cannot achieve sub-second latency.

C. Doubling the buffer interval to 120 s increases, not decreases, latency.

D. SQS introduces queue polling latency; a consumer would still need to batch or long-poll messages, so sub-second delivery is not guaranteed.

1. Amazon Kinesis Data Firehose Developer Guide – “BufferingHints: … you can set IntervalInSeconds to 0 to disable buffering and have records delivered immediately.” https://docs.aws.amazon.com/firehose/latest/dev/create-destination.html#es-buffering

2. AWS Big Data Blog – “Design patterns for near-real-time analytics using Amazon Kinesis Data Firehose and Amazon OpenSearch Service” (section: ‘Reducing latency with zero-second buffering’). https://aws.amazon.com/blogs/big-data/design-patterns-for-near-real-time-analytics-using-amazon-kinesis-data-firehose-and-amazon-opensearch-service/

• Embedding – converts words or passages into high-dimensional vectors that capture semantic meaning, letting the model compare related concepts numerically.

• Retrieval Augmented Generation (RAG) – a pattern that first retrieves relevant external documents and then supplies them as additional context to the LLM, enriching its generated answer with up-to-date or domain-specific knowledge.

• Temperature – a decoding parameter that scales the soft-max distribution during generation; higher values increase randomness/creativity while lower values make output more deterministic.

1. AWS

“Use Amazon Titan Embeddings to create vector embeddings for text

” Amazon Bedrock Developer Guide

§ Model overview. https://docs.aws.amazon.com/bedrock/latest/userguide/embeddings-titan.html

2. AWS

“Build a Retrieval-Augmented Generation (RAG) system with Amazon Bedrock

” AWS GenAI Workshop

Steps 1-2 (concept definition). https://catalog.workshops.aws/generative-ai/en-US/rag-bedrock

3. Stanford University

CS224N: Natural Language Processing with Deep Learning

Lecture 10 “Language Modeling & Generation

” slide 32 (temperature parameter in softmax sampling). https://web.stanford.edu/class/cs224n/slides/cs224n-2023-lecture10.pdf

The workflow for using Amazon SageMaker Feature Store follows a logical sequence. First, a feature group must be created; this acts as a container and defines the schema for the features. Second, data records are populated into this feature group through an ingestion process, typically using the PutRecord API. Finally, once the feature group contains data, it can be accessed to retrieve features and assemble a dataset for model training or to serve features for real-time inference. This sequence ensures the data structure exists before data is added, and data is present before it is used.

1. Amazon SageMaker Developer Guide, "Get Started with Amazon SageMaker Feature Store": This official guide explicitly outlines the process in this order. It details "Step 1: Create a Feature Group," followed by "Step 2: Ingest Data into your Feature Group," and concludes with "Step 3: Create a Dataset for ML."

URL: https://docs.aws.amazon.com/sagemaker/latest/dg/feature-store-getting-started.html

Section: Steps 1, 2, and 3 in the "Get Started with Amazon SageMaker Feature Store" tutorial.

2. Amazon SageMaker Developer Guide, "Amazon SageMaker Feature Store": The conceptual overview page reinforces this workflow. It states, "You create a feature group... After you have created a feature group, you can add features to it... You can then use the features in the online or offline store for training or inference."

URL: https://docs.aws.amazon.com/sagemaker/latest/dg/feature-store.html

Section: "How It Works".

The most logical and efficient workflow begins with understanding the data's structure. AWS Glue crawlers are designed specifically to scan data stores like Amazon S3, automatically infer schemas from unstructured or semi-structured data (like the described .csv files), and populate the AWS Glue Data Catalog. Once the schema is defined, AWS Glue DataBrew provides a visual interface to clean, normalize, and perform feature engineering on the dataset. It is the ideal tool for handling sparse, unlabeled data without writing extensive code. Finally, the prepared, clean dataset must be stored. Amazon S3 is the standard and most integrated storage service for machine learning workflows on AWS, making the processed data readily available for model training with services like Amazon SageMaker.

1. AWS Glue Crawlers: The AWS Glue Developer Guide states, "You can use a crawler to populate the AWS Glue Data Catalog with tables. This is the primary method used by most AWS Glue users." A crawler automatically discovers the schema of your data.

Source: AWS Glue Developer Guide, "Defining Crawlers".

URL: https://docs.aws.amazon.com/glue/latest/dg/add-crawler.html

2. AWS Glue DataBrew: The AWS Glue DataBrew Developer Guide explains, "AWS Glue DataBrew is a visual data preparation tool that you can use to clean and normalize data... You can then use this prepared data for analytics and machine learning."

Source: AWS Glue DataBrew Developer Guide, "What Is AWS Glue DataBrew?".

URL: https://docs.aws.amazon.com/databrew/latest/dg/what-is-databrew.html

3. Storing Data in Amazon S3: The Amazon SageMaker Developer Guide specifies that for training a model, "You store training data in an Amazon S3 bucket." This establishes S3 as the standard location for storing datasets prepared for ML training.

Source: Amazon SageMaker Developer Guide, "Train a Model with Amazon SageMaker".

URL: https://docs.aws.amazon.com/sagemaker/latest/dg/how-it-works-training.html

The selection of each technique aligns with standard machine learning data preprocessing practices.

City (name) is a nominal categorical feature. One-hot encoding is the appropriate method to convert these non-ordinal categories into a numerical format that an ML model can process, creating a separate binary feature for each city.

Type_year is a composite feature containing two distinct pieces of information: the home type and its construction year. Feature splitting is necessary to separate these into two independent, more useful features (type_of_home and year_built).

Size of the building is a continuous numerical feature. In real estate, features like size and price are often right-skewed. A Logarithmic transformation is used to handle this skewness, making the distribution more symmetric and helping to meet the assumptions of certain models like linear regression.

One-hot encoding: Géron, A. (2022). Hands-On Machine Learning with Scikit-Learn, Keras & TensorFlow (3rd ed.). O'Reilly Media, Inc. In Chapter 2, "Handling Text and Categorical Attributes" (pp. 71-73), the author explains and demonstrates the use of OneHotEncoder for nominal categorical features, which is the exact case for the City (name) feature.

Feature splitting: Stanford University. (n.d.). CS229: Machine Learning - Unsupervised Learning, K-means clustering. In the context of feature engineering, it's a common practice to decompose features. While not a formal named method, splitting a feature like Type_year into Type and Year is a fundamental feature engineering step to create more granular and meaningful inputs for the model. This is conceptually similar to extracting the month or day from a date feature.

Logarithmic transformation: University of California, Berkeley. (n.d.). Data 8: Foundations of Data Science, Chapter 15.2: Transformations. The course material explains that applying transformations like the logarithm is useful when dealing with skewed distributions or non-linear relationships, which is highly characteristic of housing size and price data. Applying a log transform can help linearize the relationship and stabilize variance.

This sequence represents a standard MLOps continuous training and deployment (CI/CD) workflow. The process is initiated by a trigger when new data arrives. An Amazon S3 event notification is the correct mechanism to detect the new data upload and invoke a downstream process like an AWS CodePipeline, typically via Amazon EventBridge. Once triggered, the pipeline's first logical action is to use the new data to retrain the model with a SageMaker training job. After successful retraining and evaluation (an implicit step), the final action is to deploy the updated model artifact to a SageMaker endpoint to make it available for real-time inference, thus completing the automated deployment cycle.

1. AWS SageMaker Developer Guide: Describes using events to automate pipelines. "You can automate the running of your pipelines based on events by using Amazon EventBridge. You can create an EventBridge rule that initiates your pipeline when, for example, the state of a resource changes, such as when a new object is added to an Amazon S3 bucket." This supports Step 1 as the trigger.

Source: AWS SageMaker Developer Guide, "Starting a Pipeline Execution".

URL: https://docs.aws.amazon.com/sagemaker/latest/dg/pipelines-automating-pipelines.html

2. AWS Whitepaper - MLOps Foundation on AWS: This document outlines the MLOps lifecycle, showing that after a trigger, the pipeline executes model building (training) and model deployment stages. "The model build pipeline is triggered automatically... The pipeline gets the latest version of the curated dataset to train the ML model... After the model is validated, the pipeline registers it to the model registry. The model deploy pipeline automatically picks up the new model... and deploys it". This supports the sequence of training (Step 2) followed by deployment (Step 3).

Source: AWS Whitepapers & Guides, "MLOps foundation on AWS", Page 10.

URL: https://d1.awsstatic.com/whitepapers/mlops-foundation-on-aws.pdf

3. AWS SageMaker Developer Guide: Explains the final deployment step. "After you train a model, you can deploy it to get predictions... Amazon SageMaker hosting services deploys your model to a SageMaker endpoint and gives you a secure and scalable endpoint that you can use for inference." This confirms that deploying to an endpoint is the action that makes the model operational for inference.

Source: AWS SageMaker Developer Guide, "Deploy a Model to SageMaker Hosting Services".

URL: https://docs.aws.amazon.com/sagemaker/latest/dg/how-it-works-deployment.html

To minimize communication overhead for distributed training, both compute instances and data should be as close as possible. Placing training instances in the same VPC subnet ensures they reside within a single Availability Zone (AZ). This configuration provides the lowest possible network latency for inter-instance communication, which is critical for synchronizing gradients and model parameters in distributed training. Storing the training data in an Amazon S3 bucket within the same AWS Region and Availability Zone as the instances minimizes data access latency, further reducing the overall training time. This combined strategy is the most effective way to reduce the total communication overhead.

A: Storing data in a different AWS Region introduces significant network latency for data retrieval, which would drastically increase, not minimize, overall overhead.

B: A single VPC subnet cannot span multiple Availability Zones, making this option technically invalid. Furthermore, cross-Region data storage is highly inefficient.

D: Storing data in a different Availability Zone, while better than a different Region, still incurs higher data transfer latency compared to storing it in the same AZ as the instances.

1. AWS VPC User Guide - Subnets: "When you create a subnet

you specify the CIDR block for the subnet and the Availability Zone in which to create the subnet. A subnet must reside entirely within one Availability Zone and cannot span zones." This confirms that placing instances in the same subnet places them in the same AZ.

Source: AWS Documentation

VPC User Guide

"Subnets for your VPC"

Section: "Subnet basics".

2. AWS SageMaker Developer Guide - Best Practices: "To reduce data transfer time

we recommend that you store your data in an Amazon S3 bucket in the same AWS Region that you use for your training job." While this specifies the Region

the principle of data locality extends to the Availability Zone for optimal performance.

Source: AWS Documentation

Amazon SageMaker Developer Guide

"Best Practices for Amazon SageMaker Training"

Section: "Prepare the Data".

3. AWS Documentation - Regions and Availability Zones: Availability Zones within a Region are connected with low-latency networking

but latency is lowest for resources within the same AZ. For high-performance computing (HPC) workloads like distributed training

co-locating resources in a single AZ is a standard best practice to minimize network latency.

Source: AWS Documentation

AWS Fundamentals: Core Concepts

"Regions and Availability Zones".

The most critical factor for Amazon Athena query performance is minimizing the amount of data scanned. The query pattern is time-based ("past 3 days"). Partitioning the data in Amazon S3 by a date-based prefix (e.g., s3://bucket/year=YYYY/month=MM/day=DD/) allows Athena to use partition pruning. This means Athena's query engine can directly access and scan only the folders corresponding to the last three days, ignoring all other data. This dramatically reduces query latency and cost, providing the highest performance. Using S3 Lifecycle policies to transition older partitions (prefixes) to S3 Glacier Flexible Retrieval is an efficient, automated way to meet the 30-day archiving requirement.

A: Not partitioning the data forces Athena to perform a full table scan for every query, resulting in the lowest possible performance and highest cost.

B: This option introduces unnecessary complexity with AWS Lambda functions for copying data and does not explicitly mention partitioning, which is the primary performance driver for Athena.

D: Creating a separate S3 bucket for each day is operationally complex and difficult to manage. Querying across multiple buckets is more cumbersome than querying partitions within a single table.

1. Amazon Athena Documentation - Partitioning Data: "Partitioning divides your table into parts and keeps the related data together based on column values such as date... Partitioning restricts the amount of data scanned by a query

thus improving performance and reducing costs."

Source: AWS Documentation

Partitioning data in Athena. https://docs.aws.amazon.com/athena/latest/ug/partitioning-data.html

2. Amazon Athena Documentation - Performance Tuning: The number one performance tuning tip for Athena is to partition data. "By partitioning your data

you can restrict the amount of data scanned by each query

thus improving performance and reducing cost."

Source: AWS Documentation

Top 10 performance tuning tips for Amazon Athena

Tip 1. https://aws.amazon.com/blogs/big-data/top-10-performance-tuning-tips-for-amazon-athena/

3. Amazon S3 Documentation - Lifecycle Management: S3 Lifecycle policies can be configured to act on objects based on their key prefix

which directly aligns with archiving date-based partitions. "You can create rules to define actions that you want Amazon S3 to take during an object's lifetime... The action is based on the object's age or creation date."

Source: AWS Documentation

Managing your storage lifecycle. https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html