Ace Your AI-300 Microsoft Certified: Machine Learning Operations (MLOps) Engineer Exam

In Azure Machine Learning, a workspace is the top-level resource that acts as a centralized hub for every ML activity. It stores experiments, pipelines, datasets, models, environments, and compute targets all in one place. Before you can register assets or deploy endpoints, the workspace itself must exist and be shared across the team. Fabrikam ' s core challenge is inconsistent experiment tracking, ad-hoc versioning, and no standardized deployment path — all symptoms of the absence of a single, governed workspace. Option A (registering assets) is a subsequent action only possible after the workspace exists. Option C (online endpoint) is a deployment concern, not an asset-management foundation. Option D (Foundry project) is appropriate for generative AI workloads, not for the traditional ML pipeline standardization described here. The workspace is the prerequisite that makes every other governance action possible.

Microsoft Learn Reference Topic: Azure Machine Learning workspaces – Microsoft Learn: Manage Azure Machine Learning workspaces

Imagine a hospital analytics firm with data scientists who kick off dozens of training jobs throughout the week. During peak hours, five jobs compete for the same GPU cluster and fail or queue for hours. On quiet nights, that cluster sits completely idle, burning money. Managed compute targets with autoscaling solve both problems: the cluster scales out automatically when multiple jobs arrive simultaneously and scales back to zero when idle. Option A (single shared cluster) is exactly the resource-contention problem Fabrikam already has. Option B (fixed-size cluster) wastes money during off-peak hours. Option C (dedicated per-experiment clusters) eliminates contention but is prohibitively expensive for a cost-conscious healthcare firm. Autoscaling managed compute is the cloud-native answer to variable workload demand.

Microsoft Learn Reference Topic: Azure Machine Learning compute targets – Configure autoscale for compute clusters

Data Zone Standard deployment routes requests to multiple datacenters within a defined geographic zone such as the US data zone, providing lower latency by using zone-level load balancing while maintaining data within a broad compliance boundary. This makes it suitable for enterprise internal applications where multiple business units need low-latency access without strict single-region data residency requirements. Developer deployment (option A) is a low-quota, unguaranteed tier designed for prototype testing, not production workloads serving multiple business units. Data Zone Batch (option B) is designed for high-volume asynchronous batch processing, not interactive low-latency real-time requests. Global Batch (option D) is optimized for scheduled bulk inference across all global regions but adds latency and is inappropriate for synchronous interactive use cases.

Microsoft Learn Reference Topic: Foundation model deployment types in Microsoft Foundry – Data Zone Standard for low-latency internal use

The correct parameter is image . In Azure Machine Learning Python SDK v2, the Environment entity supports defining an execution environment directly from an existing Docker image by specifying the image URI through the image parameter . Microsoft provides the explicit SDK v2 pattern:

Environment(image= " pytorch/pytorch:latest " , ...)

The resulting environment can then be registered by using ml_client.environments.create_or_update().

The image value can reference an image hosted in a supported container registry such as Docker Hub or Azure Container Registry. Azure Machine Learning then uses that image as the container environment for training or deployment workloads.

build is different: it is used when Azure Machine Learning must build a Docker image from a Docker build context , typically a directory containing a Dockerfile and related files. Microsoft specifies that image and build represent alternative environment-definition approaches.

conda_file specifies Python and Conda dependencies layered on top of a base Docker image; it does not identify the Docker image itself. properties stores arbitrary metadata and cannot define the execution container.

Therefore, to create an SDK v2 environment directly from an existing Docker image, use image .

Study Guide Reference: Design and implement an MLOps infrastructure — Azure Machine Learning environments, Python SDK v2, Docker images, reusable execution environments, and dependency management.