Processing, training, a metric condition, and registration are still run as four notebook cells. The team needs a repeatable DAG that builds the model when invoked. Which service automates that build?
Select an answer to reveal the explanation.
Short Explanation
Processing, training, a metric condition, and registration are still four notebook cells. SageMaker Pipelines automates that as one DAG. Notebook cells are not a DAG, and the Model Registry is not the pipeline.
Full Explanation
SageMaker Pipelines automates model building as a DAG (processing, training, condition, register). That is orchestration of the build, not Task 3.1 orchestrator selection and not the Domain 2 registry definition. Notebook cells are not that DAG.