Azure Machine Learning environment versions are effectively immutable with respect to their runtime definition . Microsoft documents that after an environment version has been registered, properties such as the Docker image, build context, and Conda dependencies cannot be modified. Only metadata properties such as the description and tags can be updated. Therefore, when a newer Docker image must be used, the correct approach is to define an Environment object representing a new environment version and register it with Azure Machine Learning.

For example, the new environment version can retain the existing environment name while specifying the updated image URI/tag and a new version. Registering an environment with the same name creates another version, preserving reproducibility for jobs that depend on the previous version.

Option A changes only descriptive metadata and has no effect on the execution image. Option B is incorrect because conda_file defines Python/Conda package dependencies rather than the Docker image version. Option C incorrectly implies that an existing registered environment ' s image tag can be modified through create_or_update; Microsoft explicitly states that the image is immutable after registration.

Study Guide Reference: Implement machine learning model lifecycle and operations — Azure Machine Learning environments, versioned assets, reproducible training environments, and SDK v2 asset management.

Enabling tracing via the prompt flow SDK alone does not guarantee that all four required dimensions — inputs, outputs, token usage, and latencies — are captured and surfaced in the Microsoft Foundry portal ' s trace viewer in a way that allows manual comparison across runs. While the prompt flow SDK does support tracing configuration, the portal-based Tracing activation is the complete, supported path for this specific capture requirement. The correct and complete solution as confirmed by the next question in this series is to use the Tracing toggle directly in the Microsoft Foundry portal for the project, then execute test runs. This portal-side Tracing feature is purpose-built to instrument all four dimensions and store them in a queryable trace store accessible through the Foundry interface.

Microsoft Learn Reference Topic: Enable tracing for prompt flows in Microsoft Foundry portal – Capturing run telemetry

Navigate to the Microsoft Foundry project in the Azure portal or Foundry portal and open the prompt flow for which you want to capture telemetry. Locate the Tracing toggle in the project or flow settings and enable it — this single action instructs the Foundry runtime to instrument every LLM call within the flow. Execute test runs of the prompt flow through the portal ' s test interface or via the CLI. Open the Traces view in Microsoft Foundry: each run appears as a trace with a tree of spans, where each span corresponds to one LLM call or tool invocation. Every span captures the exact input sent to the model, the model ' s output, token counts including prompt tokens and completion tokens, and wall-clock latency. Compare runs across prompt variants by examining individual traces side-by-side. This solution directly satisfies all four capture requirements.

Microsoft Learn Reference Topic: Enable and use tracing in Microsoft Foundry – Capturing LLM call telemetry for evaluation

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