Free Practice Questions for Amazon Web Services MLA-C01 Exam

Step 1

Upload the existing models to the same Amazon S3 bucket path.

Multi-model endpoints require all models to be stored under a single S3 prefix so SageMaker can dynamically load them on demand.

Step 2

Create a SageMaker AI model with multi-model endpoints enabled.

This creates a SageMaker model resource that uses a multi-model–capable container (for example, XGBoost, PyTorch, or TensorFlow MME-compatible containers).

Step 3

Create an endpoint configuration that references a multi-model container.

The endpoint configuration defines:

Instance type

Initial instance count

The multi-model container reference

Step 4

Deploy a real-time inference endpoint by using the endpoint configuration.

Real-time endpoints ensure low-latency inference, which is a strict customer requirement.

Step 5

Update the models to use the new endpoint ID. Pass the model IDs to the new endpoint.

Each inference request specifies a model ID so SageMaker knows which model to load from S3.

For real-time anomaly detection on streaming data, AWS recommends using Amazon Managed Service for Apache Flink, which provides serverless, scalable stream processing with built-in ML functions.

Apache Flink includes a native RANDOM_CUT_FOREST (RCF) function for unsupervised anomaly detection. This eliminates the need to deploy, manage, or scale custom ML endpoints. When combined with Amazon Kinesis Data Streams, the solution can process thousands of records per second with very low latency.

Option B introduces multiple services and custom logic, increasing operational overhead. Option C requires managing EC2 infrastructure and Kafka clusters. Option D is batch-oriented and does not meet real-time requirements.

AWS documentation explicitly highlights Kinesis + Managed Flink + RCF as the lowest-overhead solution for real-time anomaly detection.

Therefore, Option A is the correct and AWS-aligned choice.

The target_precision hyperparameter in the Amazon SageMaker linear learner controls the trade-off between precision and recall for the model. Increasing the target_precision prioritizes minimizing false positives by making the model more cautious in its predictions. This approach is effective for use cases where false positives have higher consequences than false negatives.

Scenario: The company needs to run a batch job for 90 minutes every weekend over the next 6 months. The processing can handle interruptions, and cost-effectiveness is a priority.

Why Spot Instances?

Cost-Effective: Spot Instances provide up to 90% savings compared to On-Demand Instances, making them the most cost-effective option for batch processing.

Interruption Tolerance: Since the processing can tolerate interruptions, Spot Instances are suitable for this workload.

Batch-Friendly: Spot Instances can be requested for specific durations or automatically re-requested in case of interruptions.

Steps to Implement:

Create a Spot Instance Request:

Use the EC2 console or CLI to request Spot Instances with desired instance type and duration.

Use Auto Scaling: Configure Spot Instances with an Auto Scaling group to handle instance interruptions and ensure job completion.

Run the Batch Job: Use tools like AWS Batch or custom scripts to manage the processing.

Comparison with Other Options:

Reserved Instances: Suitable for predictable, continuous workloads, but less cost-effective for a job that runs only once a week.

On-Demand Instances: More expensive and unnecessary given the tolerance for interruptions.

Dedicated Instances: Best for isolation and compliance but significantly more costly.

Text representation of basic units of data processed by LLMs: Token

High-dimensional vectors that contain the semantic meaning of text: Embedding

Enrichment of information from additional data sources to improve a generated response: Retrieval Augmented Generation (RAG)

Comprehensive Detailed Explanation

Token:

Description: A token represents the smallest unit of text (e.g., a word or part of a word) that an LLM processes. For example, " running " might be split into two tokens: " run " and " ing. "

Why? Tokens are the fundamental building blocks for LLM input and output processing, ensuring that the model can understand and generate text efficiently.

Embedding:

Description: High-dimensional vectors that encode the semantic meaning of text. These vectors are representations of words, sentences, or even paragraphs in a way that reflects their relationships and meaning.

Why? Embeddings are essential for enabling similarity search, clustering, or any task requiring semantic understanding. They allow the model to " understand " text contextually.

Retrieval Augmented Generation (RAG):

Description: A technique where information is enriched or retrieved from external data sources (e.g., knowledge bases or document stores) to improve the accuracy and relevance of a model ' s generated responses.

Why? RAG enhances the generative capabilities of LLMs by grounding their responses in factual and up-to-date information, reducing hallucinations in generated text.

By matching these terms to their respective descriptions, the ML engineer can effectively leverage these concepts to build robust and contextually aware generative AI applications on Amazon Bedrock.

Partitioning the time-series data by date prefix in the S3 bucket significantly improves query performance in Amazon Athena by reducing the amount of data that needs to be scanned during queries. This allows the ML engineers to efficiently analyze trends over specific time periods, such as the past 3 days. Applying S3 Lifecycle policies to archive partitions older than 30 days to S3 Glacier Flexible Retrieval ensures cost-effective data retention and storage management while maintaining high performance for recent data retrieval.

Amazon SageMaker Data Wrangler supports both direct and cataloged connections. To ensure data is always up to date, AWS recommends using cataloged connections backed by AWS Glue Data Catalog.

Cataloged connections allow Data Wrangler to reference the source systems dynamically, ensuring that each import reflects the latest data changes without manual reconfiguration. This approach supports Amazon S3, Amazon Redshift, and Snowflake and integrates securely using managed credentials.

Direct connections are point-in-time imports and do not automatically reflect schema or data updates. Glue and Lambda-based solutions introduce unnecessary complexity and operational overhead.

Therefore, using cataloged connections in Data Wrangler is the correct solution.

AWS best practices recommend event-driven architectures to automate ML workflows with minimal operational overhead. Amazon EventBridge natively integrates with Amazon S3 and Amazon SageMaker Pipelines, making it the most efficient solution for triggering retraining when new data arrives.

Amazon S3 automatically emits object creation events. By creating an EventBridge rule that listens for these events and targets a SageMaker Pipeline execution, the pipeline can start immediately when new training data is uploaded. This solution requires no custom code, no polling, and no infrastructure management.

Option A is incorrect because S3 lifecycle rules manage storage transitions, not workflow execution. Option B introduces custom code and periodic scanning, which increases operational complexity and cost. Option D (MWAA) is powerful but requires maintaining an Airflow environment and is unnecessary for a simple event-based trigger.

AWS documentation explicitly highlights EventBridge + SageMaker Pipelines as the recommended pattern for automated retraining workflows triggered by data arrival.

Therefore, Option C is the correct and AWS-verified answer.

Amazon Kendra is an AI-powered search service designed for semantic search use cases. It allows ingestion of documents from an Amazon S3 bucket using the Amazon Kendra S3 connector. Once the documents are ingested, Kendra enables semantic searches with its built-in capabilities, removing the need to manually generate embeddings or manage a vector database. This approach is efficient, requires minimal operational effort, and meets the requirements for a Retrieval Augmented Generation (RAG) application.

In regression problems such as house price prediction, extreme values can significantly distort model learning. In this dataset, the presence of a large mansion and an extremely small apartment represents clear outliers in the Square Meters feature. According to AWS Machine Learning best practices, outliers can disproportionately influence loss functions (such as mean squared error), leading to poor predictions for the majority of typical data points.

Removing these outliers helps the model focus on learning patterns that apply to the majority of houses and apartments, which aligns with the requirement to produce accurate predictions for typical properties. After removing outliers, applying a log transformation to the Square Meters feature further improves model performance by reducing skewness and stabilizing variance. Log transformations are commonly recommended in AWS and general ML documentation when numerical features span multiple orders of magnitude.

Option B is incorrect because normalization alone does not address the undue influence of extreme outliers. Option C and D are incorrect because one-hot encoding is intended for categorical variables, not continuous numerical features such as square meters.

Therefore, removing outliers and applying a log transformation is the most statistically sound preprocessing approach.