DP-100 · Question #327
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Creating a data asset does not enable deployment of a locally cloned MLflow model to a batch endpoint - the model itself must be registered as a model asset in the workspace.
Question
Options
- AYes
- BNo
How the community answered
(25 responses)- A24% (6)
- B76% (19)
Why each option
Creating a data asset does not enable deployment of a locally cloned MLflow model to a batch endpoint - the model itself must be registered as a model asset in the workspace.
A data asset registers a dataset reference for use as pipeline input or output, not a model artifact, and the batch endpoint deployment process requires a model asset registration - making this solution insufficient.
A batch endpoint deployment references a registered model asset, not a data asset. To make the local MLflow model deployable, it must be registered in the workspace using ml_client.models.create_or_update with the local path. A data asset represents input datasets, not a deployable model, so creating one does not fulfill the deployment prerequisite.
Concept tested: Deploying local MLflow model to batch endpoint
Source: https://learn.microsoft.com/en-us/azure/machine-learning/how-to-use-batch-model-deployments
Topics
Community Discussion
No community discussion yet for this question.