Free AWS MLA-C01 Actual Exam Questions - Question 14 Discussion
A company is building a web-based AI application by using Amazon SageMaker. The application will provide the following capabilities and features: ML experimentation, training, a central model registry, model deployment, and model monitoring. The application must ensure secure and isolated use of training data during the ML lifecycle. The training data is stored in Amazon S3. The company needs to use the central model registry to manage different versions of models in the application. Which action will meet this requirement with the LEAST operational overhead?
C imo, model groups in SageMaker Model Registry are designed to organize models and versions efficiently, which cuts down on manual tracking and operational work compared to just tagging versions.
Maybe D makes more sense here. The question emphasizes versioning within a central registry, and using unique tags for each version is straightforward without adding complexity from managing model groups. Model groups are good for big catalogs, but if the setup is simpler, tagging alone might keep things leaner. Plus, both C and D use SageMaker Model Registry, so the core requirement is met either way, but D could minimize overhead by avoiding extra organization layers.
It’s C because model groups in SageMaker Model Registry naturally organize different models and their versions, reducing manual work compared to just tagging versions. That cuts overhead better than D.
D imo, using unique tags for model versions in the SageMaker Model Registry still keeps it centralized and secure, but avoids the extra layer of managing model groups, which might be overkill here.
C/D? I’d skip ECR options since they focus on containers, not models. Between C and D, model groups in C help automate organizing versions, which cuts down manual tagging hassles in D. So C feels smoother.
Makes sense to ditch A and B quickly since ECR handles containers, not model versioning or central registry. Between C and D, C stands out because model groups are built for organizing different model versions neatly. Using model groups (C) means less manual tagging or tracking, so it fits the “least operational overhead” bit better than D. So yeah, C feels like the cleaner, more native way to meet the requirement here.
Actually, I’d rule out A and B right away since those deal mainly with container registries, not model versioning or centralized model management. Managing separate ECR repos or tags for each model version adds a lot of manual work and complexity. SageMaker’s Model Registry is built to handle version control and organization smoothly. Between C and D, C is better because model groups explicitly group models by project or functionality, making it easier to track different versions without relying on manual tagging. It’s the most straightforward way to meet the requirement with minimal overhead.
C/D? I’m thinking C because model groups are designed specifically to handle versioning and organization in SageMaker, which keeps things tidy without extra tagging effort. D could work too, but managing unique tags manually sounds like more admin work and higher overhead. ECR options (A/B) feel off since they’re more about container images, not model lifecycle management. The question focuses on model registry and versioning with low overhead, so using the built-in Model Registry with groups looks like the best fit to me.
Totally agree with going for C here. Model groups in SageMaker's registry keep everything neat and automate version tracking way better than tagging manually. Definitely the lowest overhead. C
Makes sense to go with C here. The model groups in the SageMaker Model Registry really cut down on manual tracking of versions and keep everything organized automatically. That should lower operational overhead compared to relying on just tags like in D. Plus, it fits the requirement to manage different model versions centrally and securely without extra hassle.
Probably D here. Using the SageMaker Model Registry with unique tags for each model version still leverages the built-in registry features but gives fine-grained control over versions without adding the extra step of managing model groups. It might be simpler when you just need to track versions rather than organize models into groups, so less setup and overhead. C feels like it adds more structure but might not be necessary if the company just wants straightforward version management.
It’s C since model groups automate version management better than manual tagging in D.
C vs D but C is better for grouping models, less manual tagging needed.
C imo, since the SageMaker Model Registry with model groups is designed for organizing and managing model versions efficiently, which fits the need for low operational overhead better than just tagging.
Option D