Microsoft AI-300 - Operationalizing Machine Learning and Generative AI Solutions

Azure Private Endpoints are network interfaces that connect your Azure ML workspace to your Virtual Network using a private IP address from the VNet ' s address space. Once a private endpoint is created and DNS is configured, all traffic to the workspace — including the Studio UI, REST API, and SDK calls — travels entirely over Microsoft ' s private backbone rather than the public internet. The workspace ' s public endpoint can then be completely disabled. Azure Firewall (option A) filters traffic at the network layer but still requires the workspace to have a public IP. Network Security Groups (option C) control traffic within VNets but cannot block the public endpoint of a PaaS service. Service endpoints (option D) keep traffic on the Azure backbone but the workspace still has a public-facing address. Private endpoints are the only option that fully removes the public network presence.

Microsoft Learn Reference Topic: Configure a private endpoint for Azure Machine Learning workspace

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

Azure Monitor is valuable for production observability , but it is not the appropriate mechanism for the stated development-time requirement: manually inspecting individual prompt-flow executions and comparing prompt variants with their inputs, outputs, token consumption, and latency.

Prompt flow provides purpose-built run outputs and tracing . Microsoft documents that after a flow execution, the Outputs experience exposes detailed flow inputs and outputs. When tracing is enabled, the Trace view provides execution duration and token information and lets the developer expand individual steps to inspect their inputs and execution details.

Prompt flow also directly supports variants and batch/evaluation runs. Multiple variants can be executed and compared, while the run details expose per-test-case inputs, outputs, token counts, duration, and evaluation results. Microsoft explicitly states that multiple runs can be selected to compare their metrics and outputs.

Azure Monitor/Application Insights can collect operational metrics such as token consumption and flow or node latency for deployed applications, but that telemetry is primarily intended for monitoring and troubleshooting rather than the interactive prompt-variant evaluation workflow described here.

Therefore, the proposed solution does not meet the goal .

Study Guide Reference: Implement generative AI quality assurance and observability — prompt evaluation, tracing, debugging, token consumption, latency, and prompt-variant comparison.

===============