DP-100 · Question #542
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. Deploying an MLflow PyFunc model to a managed online endpoint without egress connectivity requires more than a single parameter addition; the proposed solution does not meet the no-egress requirement.
Question
Exhibit
Options
- AYes
- BNo
How the community answered
(25 responses)- A24% (6)
- B76% (19)
Why each option
Deploying an MLflow PyFunc model to a managed online endpoint without egress connectivity requires more than a single parameter addition; the proposed solution does not meet the no-egress requirement.
Accepting the solution as sufficient ignores that MLflow PyFunc models with external dependencies will fail environment setup when outbound internet access is blocked on the managed endpoint.
The proposed solution does not satisfy the no-egress deployment requirement because deploying an MLflow model with PyFunc flavor may trigger external package downloads at runtime to resolve conda/pip dependencies, which fail when egress connectivity is disabled. To deploy successfully without egress, the model environment must be pre-built and all dependencies must be bundled into a custom Docker image or environment, not simply addressed by a ManagedOnlineDeployment parameter alone.
Concept tested: Azure ML managed online endpoint no-egress deployment
Source: https://learn.microsoft.com/en-us/azure/machine-learning/how-to-secure-online-endpoint
Topics
Community Discussion
No community discussion yet for this question.
