MLA-C01 Exam Dumps : AWS Certified Machine Learning Engineer - Associate

The AWS::SageMaker::Model resource in AWS CloudFormation is used to create an ML model in Amazon SageMaker. This model can then be hosted on an endpoint by using the AWS::SageMaker::Endpoint resource. The model resource defines the container or algorithm to use for hosting and the S3 location of the model artifacts.

The correct answer is B. Use the Amazon SageMaker Model Registry to catalog the models. Create model groups for each model to manage the model versions and to maintain associated metadata.

The Amazon SageMaker Model Registry is a managed repository within SageMaker designed specifically for production-grade ML model lifecycle management. It allows organizations to catalog models, track multiple versions of a model, associate rich metadata, and manage deployment workflows in a scalable, controlled manner. Each model can belong to a model group, which acts as a container for all versions of that particular model. Versions can store training metrics, hyperparameters, model artifacts, and other key metadata, enabling reproducibility, auditing, and automated promotion between stages (e.g., Staging → Production).

Option A, while using the Model Registry, relies on manually tagging versions and creating key-value pairs to store metadata. This approach is error-prone, lacks structured versioning, and does not integrate with SageMaker’s deployment pipelines.

Options C and D suggest using Amazon ECR repositories. While ECR can store containerized model artifacts, it is not designed for ML-specific metadata, versioning, or automated model stage transitions. Using ECR alone would require custom-built solutions for metadata management, auditing, and version tracking, adding unnecessary operational overhead.

By leveraging the Model Registry with model groups, organizations can automate promotions, apply approval workflows, and track lineage efficiently, fully aligning with AWS best practices for ML model development and production readiness. This ensures compliance, reproducibility, and reduces operational complexity in enterprise AI platforms.

Using the Model Registry and model groups is the standard AWS-recommended approach for enterprise-scale model cataloging and version control, enabling teams to focus on model improvement rather than infrastructure management.

Int8 quantization

Low-rank adaptation (LoRA)

Fully Sharded Data Parallel (FSDP)

These three mappings align with AWS documentation for large-model training and optimization in SageMaker AI.

For 1, the correct answer is Int8 quantization. AWS documentation explains that quantization reduces hardware and memory requirements by using a less precise data type for weights and activations, including INT8 formats. AWS Prescriptive Guidance also states that quantization reduces memory footprint by converting higher-precision weights to lower-precision formats such as FP16 to INT8. That matches the description of reducing memory usage by representing model weights with lower precision.

For 2, the correct answer is Low-rank adaptation (LoRA). In practice, LoRA is a standard parameter-efficient fine-tuning (PEFT) method that updates only a small subset of trainable parameters instead of full-model fine-tuning. In SageMaker JumpStart workflows for large language models, LoRA is used specifically to make fine-tuning large models more efficient by training adapter-style low-rank updates rather than all original model weights. This matches the description of a PEFT technique that trains only a subset of model parameters.

For 3, the correct answer is Fully Sharded Data Parallel (FSDP). AWS documentation states that SageMaker model parallelism integrates with PyTorch FSDP, which shards model states across GPUs and supports large-scale distributed training. That directly matches the description of a distributed training technique used to share or shard model parameters across GPUs.