Correct Answer:

Explanation:
Because you want to reference all blobs in a container rather than a single file, the correct asset type is AssetTypes.URI_FOLDER. This type points to a directory-level URI, allowing Azure ML to traverse all files within it. For a publicly accessible Azure Blob Storage container, the URI follows the pattern
https://storage_account.blob.core.windows.net/container_name/. You then create the Data object with the correct type, path, name, and version parameters, and register it in the workspace using ml_client.data.
create_or_update. Do not use AssetTypes.URI_FILE, which references a single file. Do not use AssetTypes.
MLTABLE unless you have an MLTable YAML descriptor. URI_FOLDER is the correct choice for referencing a collection of CSV blobs in an Azure Blob Storage container, allowing Azure ML to discover and process all files within the specified path.
Microsoft Learn Reference Topic: Create and manage data assets in Azure Machine Learning Python SDK v2
- URI_FOLDER

Correct Answer:

Explanation:
Azure Machine Learning infrastructure can be described as Infrastructure as Code using ARM templates, Bicep, or Terraform. To make provisioning fully automated, two separate concerns must be addressed. First, the trigger: a CI/CD system like GitHub Actions or Azure DevOps Pipelines must detect changes to IaC template files in the repository, configured through a branch-push or pull-request trigger. Second, the execution: the CI/CD pipeline runs the provisioning commands such as az ml workspace create or bicep deploy non-interactively using a service principal or managed identity, eliminating the need for a human to run scripts manually. Together, these two mechanisms deliver the GitOps-style automation that modern MLOps practices require, ensuring every template change automatically results in a consistent, auditable infrastructure update.
Microsoft Learn Reference Topic: Automate Azure Machine Learning with GitHub Actions - CI/CD for ML infrastructure

Correct Answer: D  🗳️

Correct Answer: B,D  🗳️

Explanation: Only visible for PassTorrent members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
Define how features are retrieved at inference: Feature retrieval specification Ensure feature consistency between training and inference: Feature retrieval specification Enable automated feature lookup in production: Feature retrieval specification The feature retrieval specification is the key model-level contract for all three requirements. Microsoft defines it as a portable specification containing the exact list of features associated with a model, including the relevant feature store, feature set, and feature-set version . The same specification participates in both training and inference, making it the connective artifact across the model lifecycle.
During training, the feature retrieval specification is used to obtain the required feature values and generate training data. Microsoft requires the specification to be packaged with the model artifact when the model depends on feature-store features. At online inference time, the scoring script loads this packaged specification, resolves the feature list, and initializes online feature lookup before calling the feature store to retrieve current values.
This also prevents training-serving inconsistencies because the deployed model carries the feature dependencies and specific feature-set versions established during training, rather than relying on manually reconstructed production configuration. Microsoft explicitly states that packaging the retrieval specification with the model minimizes changes between training and inference workflows.
A feature set specification defines feature sources and transformations, a feature set asset provides managed versioning, and materialization precomputes feature values. None of those alone defines the model ' s complete retrieval contract at inference.
Study Guide Reference: Implement machine learning model lifecycle and operations - package a feature retrieval specification with the model artifact and operationalize feature-store-backed models.