Orchestrating SageMaker ML Workflows as DAGs in Studio with ML Lineage Tracking for Governance
A company is using Amazon SageMaker to create ML models. The company's data scientists need fine-grained control of the ML workflows that they orchestrate. The data scientists also need the ability to visualize SageMaker jobs and workflows as a directed acyclic graph (DAG). The data scientists must keep a running history of model discovery experiments and must establish model governance for auditing and compliance verifications. Which solution will meet these requirements?
Community Votes
67% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
SageMaker Pipelines orchestrates the workflows and renders them as DAGs inside SageMaker Studio, while SageMaker ML Lineage Tracking records the lineage of datasets, models, and artifacts to provide the experiment history and the audit and compliance evidence.
Data scientists need fine-grained control of the ML workflows they orchestrate, must visualize SageMaker jobs and workflows as a directed acyclic graph, and must keep a running history of model discovery experiments plus establish model governance for auditing and compliance. The answer has to satisfy all three needs at once.
Substituting SageMaker Experiments for ML Lineage Tracking, or AWS CodePipeline for SageMaker Pipelines. Experiments manages experiment runs and statistics but is not the lineage and governance mechanism, and CodePipeline is a general CI/CD service rather than the SageMaker-native workflow orchestrator that integrates with Studio.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The three requirements map onto specific SageMaker features. SageMaker Pipelines is the SageMaker-native workflow orchestrator and its integration with SageMaker Studio provides the fine-grained control and the directed acyclic graph visualization of jobs and workflows. For the running history of model discovery experiments and for model governance that supports auditing and compliance verification, SageMaker ML Lineage Tracking is the dedicated feature, because it tracks lineage across datasets, models, and artifacts. Option C is the only choice that satisfies all three requirements together. The vote was 67 for C, with khchan123, Saransundar, fnuuu, and aws_Tamilan all selecting C and citing the official define-pipeline and lineage-tracking documentation, while GiorgioGss pointed out that the entire ML flow is managed through Studio.Why the Other Options Are Wrong
Options B and D both use SageMaker Experiments where the question requires the running experiment history and governance. Experiments tracks experiment runs, hyperparameters, and metrics, but it is not the lineage and governance mechanism that captures artifact lineage for auditing and compliance, as khchan123 argued. Options A and C are the correct lineage pairing, but option A uses AWS CodePipeline, which is a general-purpose CI/CD service for building and deploying software, not the SageMaker-native pipeline orchestrator that integrates with Studio to render ML workflows as DAGs.Community Comment Notes
The community split 67 for C and 33 for D. a4002bd, who voted D, credited SageMaker Pipelines for DAG visualization and SageMaker Experiments for tracking experiment history, but did not address the governance and compliance requirement that specifically calls for lineage tracking. jackzhang846 addressed both sides in the same thread, citing the Experiments page for D and noting in Chinese that SageMaker ML Lineage Tracking supplies model and data lineage for audit and compliance, which points back to C.Official Reference
Related Analysis
Practice All MLA-C01 Questions
Access 115 questions with complete answers and detailed explanations.
View Full MLA-C01 Practice Test →