How to audit custom ML models using Amazon SageMaker
An ML research team develops custom ML models. The model artifacts are shared with other teams for integration into products and services. The ML team retains the model training code and data. The ML team wants to build a mechanism that the ML team can use to audit models. Which solution should the ML team use when publishing the custom ML models?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of AWS-specific tools for ML governance; the trap is choosing generic documentation methods (S3/Git) instead of the specialized SageMaker Model Cards feature designed for this purpose.
Amazon SageMaker Model Cards provide a standardized mechanism for documenting model details, intended uses, and training data to facilitate auditing. The community consensus confirms this is the correct solution for transparency and compliance in ML workflows.
Candidates often choose Option A (Amazon S3) because it is a common storage solution, but they fail to recognize that simple file storage does not provide the structured, standardized metadata required for effective model auditing and transparency.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon SageMaker Model Cards are specifically designed to document key aspects of a machine learning model, including its intended use cases, training methodology, evaluation metrics, and ethical considerations. By creating these cards, the ML team establishes a transparent record that facilitates auditing, ensuring that other teams understand how the model was built and its limitations.Why the Other Options Are Wrong
Option A (S3 documents) lacks the structured format and specific fields required for comprehensive model governance. Option B refers to 'AI Service Cards,' which is not a standard AWS product name for custom model documentation. Option D (Git scripts) tracks code versioning but does not document the model's performance, data sources, or ethical implications needed for an audit.Community Comment Notes
Comments [1], [3], and [5] strongly support Option C, highlighting that SageMaker Model Cards provide the necessary standardized documentation for transparency. Comment [4] reinforces that these cards are the specific tool for documenting model details and usage, aligning with the requirement to build an auditing mechanism.Official Reference
Exam Strategy
When encountering questions about ML governance, ethics, or auditing on AWS exams, immediately look for 'Model Cards' as the primary answer. Differentiate between code versioning (Git) and model metadata documentation (Model Cards), as the latter is required for transparency and auditability.
Related Analysis
Practice All AIF-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AIF-C01 Practice Test →