McAfee-Secured Website

Exam Code: AI-300

Exam Name: Operationalizing Machine Learning and Generative AI Solutions

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Machine Learning Operations Engineer Associate

100% Microsoft AI-300 Guaranteed Success With Testking Training Materials

Get Real AI-300 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

213 Questions & Answers with Testing Engine

"Operationalizing Machine Learning and Generative AI Solutions Exam", also known as AI-300 exam, is a Microsoft certification exam.

Pass your tests with the always up-to-date AI-300 Exam Engine. Your AI-300 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Microsoft AI-300 Practice Test 5

Question 40

A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. What should the administrator evaluate?

  1. Use a dedicated federated or managed workload identity with minimal Azure RBAC.
  2. Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner.
  3. Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access.
  4. Give the endpoint deployment's runtime identity the necessary feature-store data permissions.

Explanation

Correct Answer

C:

Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.

Incorrect Answers

A:

Use a dedicated federated or managed workload identity with minimal Azure RBAC. It addresses another case: A GitHub deployment workflow needs access to Azure ML without storing an administrator password. For that case, the distinguishing justification or acceptance check is: Workload identity avoids persistent administrator secrets and can be constrained to the specific resources it deploys. The present case instead states: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. It calls for Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access. Showing success for the other case would not establish: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.

B:

The alternative, Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner, belongs to a different technical condition: A junior operator needs to submit ML training jobs but must not change workspace networking or grant user roles. There the source-specific mechanism or proof is: Least-privilege workspace RBAC permits job operations without broad control over security or billing resources. The condition asked about here is: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. A suitable correction is Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access; the targeted justification or result is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.

D:

Give the endpoint deployment's runtime identity the necessary feature-store data permissions. That operation would be relevant if: A production endpoint can fetch its model but cannot read a secured feature store at inference time. Its corresponding reason or verification is: Production inference uses its execution identity; author privileges do not automatically travel to the deployed container. However the problem in this question is: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. The requirement instead calls for Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access; the question-specific check is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.

Question 41

An ML workspace is accessible through a private endpoint, but a notebook user's access is denied despite the correct network path. What should be diagnosed?

  1. Remove embedded keys and configure data-plane access for the executing managed identity.
  2. Check the user's effective Azure RBAC authorization independently from network connectivity.
  3. Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access.
  4. Give the endpoint deployment's runtime identity the necessary feature-store data permissions.

Explanation

Correct Answer

B:

Private networking controls reachability, not permission to perform workspace operations; both controls must allow the request.

Incorrect Answers

A:

Remove embedded keys and configure data-plane access for the executing managed identity. This is useful for the distinct issue: A revoked storage account key remains in an old training script, although the operator can read storage through their own account. The relevant technical rationale or evidence for that issue is: Interactive user rights cannot rescue a job using revoked credentials; explicit identity-based access is auditable and renewable. Here the reported issue is: An ML workspace is accessible through a private endpoint, but a notebook user's access is denied despite the correct network path. The relevant response is: Check the user's effective Azure RBAC authorization independently from network connectivity. The first result cannot verify this different correction: Private networking controls reachability, not permission to perform workspace operations; both controls must allow the request.

C:

Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access. It addresses another case: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. For that case, the distinguishing justification or acceptance check is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data. The present case instead states: An ML workspace is accessible through a private endpoint, but a notebook user's access is denied despite the correct network path. It calls for Check the user's effective Azure RBAC authorization independently from network connectivity. Showing success for the other case would not establish: Private networking controls reachability, not permission to perform workspace operations; both controls must allow the request.

D:

The alternative, Give the endpoint deployment's runtime identity the necessary feature-store data permissions, belongs to a different technical condition: A production endpoint can fetch its model but cannot read a secured feature store at inference time. There the source-specific mechanism or proof is: Production inference uses its execution identity; author privileges do not automatically travel to the deployed container. The condition asked about here is: An ML workspace is accessible through a private endpoint, but a notebook user's access is denied despite the correct network path. A suitable correction is Check the user's effective Azure RBAC authorization independently from network connectivity; the targeted justification or result is: Private networking controls reachability, not permission to perform workspace operations; both controls must allow the request.

Question 42

Two tenant security teams manage data and models; the platform team should not change model versions. What principle should govern their role assignments?

  1. Split data management and model deployment permissions across scoped security groups.
  2. Check the user's effective Azure RBAC authorization independently from network connectivity.
  3. Use a dedicated federated or managed workload identity with minimal Azure RBAC.
  4. Examine the exact role assignment and scope for the requested compute operation.

Explanation

Correct Answer

A:

Separating duties reduces accidental cross-team changes and makes reviewable, role-specific access boundaries possible.

Incorrect Answers

B:

Check the user's effective Azure RBAC authorization independently from network connectivity. A separate source case supports that approach when: An ML workspace is accessible through a private endpoint, but a notebook user's access is denied despite the correct network path. The supporting rationale or observable result is: Private networking controls reachability, not permission to perform workspace operations; both controls must allow the request. This question describes a different issue: Two tenant security teams manage data and models; the platform team should not change model versions. Address it through Split data management and model deployment permissions across scoped security groups, with the required justification or evidence: Separating duties reduces accidental cross-team changes and makes reviewable, role-specific access boundaries possible.

C:

Use a dedicated federated or managed workload identity with minimal Azure RBAC. This is useful for the distinct issue: A GitHub deployment workflow needs access to Azure ML without storing an administrator password. The relevant technical rationale or evidence for that issue is: Workload identity avoids persistent administrator secrets and can be constrained to the specific resources it deploys. Here the reported issue is: Two tenant security teams manage data and models; the platform team should not change model versions. The relevant response is: Split data management and model deployment permissions across scoped security groups. The first result cannot verify this different correction: Separating duties reduces accidental cross-team changes and makes reviewable, role-specific access boundaries possible.

D:

Examine the exact role assignment and scope for the requested compute operation. It addresses another case: An engineer is able to open the workspace portal but receives authorization failures when trying to edit compute. For that case, the distinguishing justification or acceptance check is: Portal visibility and write permissions are distinct capabilities; the user needs the specific role action at the effective resource scope. The present case instead states: Two tenant security teams manage data and models; the platform team should not change model versions. It calls for Split data management and model deployment permissions across scoped security groups. Showing success for the other case would not establish: Separating duties reduces accidental cross-team changes and makes reviewable, role-specific access boundaries possible.

Question 43

A revoked storage account key remains in an old training script, although the operator can read storage through their own account. What authentication change is necessary?

  1. Give the endpoint deployment's runtime identity the necessary feature-store data permissions.
  2. Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access.
  3. Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner.
  4. Remove embedded keys and configure data-plane access for the executing managed identity.

Explanation

Correct Answer

D:

Interactive user rights cannot rescue a job using revoked credentials; explicit identity-based access is auditable and renewable.

Incorrect Answers

A:

Give the endpoint deployment's runtime identity the necessary feature-store data permissions. That operation would be relevant if: A production endpoint can fetch its model but cannot read a secured feature store at inference time. Its corresponding reason or verification is: Production inference uses its execution identity; author privileges do not automatically travel to the deployed container. However the problem in this question is: A revoked storage account key remains in an old training script, although the operator can read storage through their own account. The requirement instead calls for Remove embedded keys and configure data-plane access for the executing managed identity; the question-specific check is: Interactive user rights cannot rescue a job using revoked credentials; explicit identity-based access is auditable and renewable.

B:

Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access. A separate source case supports that approach when: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. The supporting rationale or observable result is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data. This question describes a different issue: A revoked storage account key remains in an old training script, although the operator can read storage through their own account. Address it through Remove embedded keys and configure data-plane access for the executing managed identity, with the required justification or evidence: Interactive user rights cannot rescue a job using revoked credentials; explicit identity-based access is auditable and renewable.

C:

Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner. This is useful for the distinct issue: A junior operator needs to submit ML training jobs but must not change workspace networking or grant user roles. The relevant technical rationale or evidence for that issue is: Least-privilege workspace RBAC permits job operations without broad control over security or billing resources. Here the reported issue is: A revoked storage account key remains in an old training script, although the operator can read storage through their own account. The relevant response is: Remove embedded keys and configure data-plane access for the executing managed identity. The first result cannot verify this different correction: Interactive user rights cannot rescue a job using revoked credentials; explicit identity-based access is auditable and renewable.

Question 44

A new team member receives the expected workspace role yet still cannot access a separately managed Azure Key Vault. What is missing?

  1. Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner.
  2. Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access.
  3. Assign the appropriate Key Vault data-plane permissions at the secret resource scope.
  4. Replace personal-user dependencies with an approved nonhuman workload identity.

Explanation

Correct Answer

C:

Azure ML role assignments do not automatically authorize secret retrieval in linked services with separate access policies.

Incorrect Answers

A:

The alternative, Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner, belongs to a different technical condition: A junior operator needs to submit ML training jobs but must not change workspace networking or grant user roles. There the source-specific mechanism or proof is: Least-privilege workspace RBAC permits job operations without broad control over security or billing resources. The condition asked about here is: A new team member receives the expected workspace role yet still cannot access a separately managed Azure Key Vault. A suitable correction is Assign the appropriate Key Vault data-plane permissions at the secret resource scope; the targeted justification or result is: Azure ML role assignments do not automatically authorize secret retrieval in linked services with separate access policies.

B:

Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access. That operation would be relevant if: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. Its corresponding reason or verification is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data. However the problem in this question is: A new team member receives the expected workspace role yet still cannot access a separately managed Azure Key Vault. The requirement instead calls for Assign the appropriate Key Vault data-plane permissions at the secret resource scope; the question-specific check is: Azure ML role assignments do not automatically authorize secret retrieval in linked services with separate access policies.

D:

Replace personal-user dependencies with an approved nonhuman workload identity. A separate source case supports that approach when: An access policy depends on an employee's personal account, and the employee leaves the company. The supporting rationale or observable result is: Long-running automation should not rely on a human account whose employment and conditional access status can change. This question describes a different issue: A new team member receives the expected workspace role yet still cannot access a separately managed Azure Key Vault. Address it through Assign the appropriate Key Vault data-plane permissions at the secret resource scope, with the required justification or evidence: Azure ML role assignments do not automatically authorize secret retrieval in linked services with separate access policies.

Question 45

An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. Which asset type best communicates that input contract?

  1. Record the specific registered data asset name and version with each run.
  2. Define and register an MLTable data asset with the intended table paths and transforms.
  3. Use a registered existing data asset version or register the required version before job submission.
  4. Register the input as a versioned uri_file data asset.

Explanation

Correct Answer

D:

A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input.

Incorrect Answers

A:

Record the specific registered data asset name and version with each run. It addresses another case: Two training jobs use different dataset versions but the same run name. For that case, the distinguishing justification or acceptance check is: Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names. The present case instead states: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. It calls for Register the input as a versioned uri_file data asset. Showing success for the other case would not establish: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input.

B:

The alternative, Define and register an MLTable data asset with the intended table paths and transforms, belongs to a different technical condition: An AutoML tabular training job expects an MLTable with schema and transformation rules, but a folder pointer is supplied. There the source-specific mechanism or proof is: An MLTable describes how tabular data is read, including supported schemas and transformations, beyond merely naming a folder. The condition asked about here is: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. A suitable correction is Register the input as a versioned uri_file data asset; the targeted justification or result is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input.

C:

Use a registered existing data asset version or register the required version before job submission. That operation would be relevant if: A CLI submission fails because its input references azureml:customer-data:99 and that data version does not exist. Its corresponding reason or verification is: An asset reference resolves by name and version; the service cannot infer a missing version from the data's display label. However the problem in this question is: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. The requirement instead calls for Register the input as a versioned uri_file data asset; the question-specific check is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input.

Question 46

A training component consumes thousands of images under a common storage prefix and should not list each one individually. Which data asset type should be used?

  1. Register the data location as a governed Azure ML data asset with ownership and version metadata.
  2. Register the input as a versioned uri_file data asset.
  3. Register a uri_folder data asset that points at the image collection.
  4. Register separately versioned data assets for each snapshot and bind jobs to those versions.

Explanation

Correct Answer

C:

A uri_folder supplies the directory location to downstream components, avoiding a separate asset version for every individual image.

Incorrect Answers

A:

Register the data location as a governed Azure ML data asset with ownership and version metadata. This is useful for the distinct issue: A pipeline input points directly to an individual's personal blob URL, which is likely to disappear. The relevant technical rationale or evidence for that issue is: Managed data assets make a training input discoverable and reusable without depending on an employee's transient location. Here the reported issue is: A training component consumes thousands of images under a common storage prefix and should not list each one individually. The relevant response is: Register a uri_folder data asset that points at the image collection. The first result cannot verify this different correction: A uri_folder supplies the directory location to downstream components, avoiding a separate asset version for every individual image.

B:

Register the input as a versioned uri_file data asset. It addresses another case: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. For that case, the distinguishing justification or acceptance check is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input. The present case instead states: A training component consumes thousands of images under a common storage prefix and should not list each one individually. It calls for Register a uri_folder data asset that points at the image collection. Showing success for the other case would not establish: A uri_folder supplies the directory location to downstream components, avoiding a separate asset version for every individual image.

D:

The alternative, Register separately versioned data assets for each snapshot and bind jobs to those versions, belongs to a different technical condition: A model retraining run must compare outcomes from data collected this week and last week without overwriting either snapshot. There the source-specific mechanism or proof is: Independent snapshot versions allow fair temporal comparison and avoid silent changes in data during reruns. The condition asked about here is: A training component consumes thousands of images under a common storage prefix and should not list each one individually. A suitable correction is Register a uri_folder data asset that points at the image collection; the targeted justification or result is: A uri_folder supplies the directory location to downstream components, avoiding a separate asset version for every individual image.

Question 47

An AutoML tabular training job expects an MLTable with schema and transformation rules, but a folder pointer is supplied. How should the input be corrected?

  1. Define an MLTable asset specifying the CSV sources and parsing information.
  2. Define and register an MLTable data asset with the intended table paths and transforms.
  3. Record the specific registered data asset name and version with each run.
  4. Register the input as a versioned uri_file data asset.

Explanation

Correct Answer

B:

An MLTable describes how tabular data is read, including supported schemas and transformations, beyond merely naming a folder.

Incorrect Answers

A:

Define an MLTable asset specifying the CSV sources and parsing information. A separate source case supports that approach when: A batch processing component reads a folder data asset successfully but needs to consume its structured CSV records as a table. The supporting rationale or observable result is: A folder URI identifies files only; MLTable metadata can express their structured tabular interpretation for supported consumers. This question describes a different issue: An AutoML tabular training job expects an MLTable with schema and transformation rules, but a folder pointer is supplied. Address it through Define and register an MLTable data asset with the intended table paths and transforms, with the required justification or evidence: An MLTable describes how tabular data is read, including supported schemas and transformations, beyond merely naming a folder.

C:

Record the specific registered data asset name and version with each run. This is useful for the distinct issue: Two training jobs use different dataset versions but the same run name. The relevant technical rationale or evidence for that issue is: Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names. Here the reported issue is: An AutoML tabular training job expects an MLTable with schema and transformation rules, but a folder pointer is supplied. The relevant response is: Define and register an MLTable data asset with the intended table paths and transforms. The first result cannot verify this different correction: An MLTable describes how tabular data is read, including supported schemas and transformations, beyond merely naming a folder.

D:

Register the input as a versioned uri_file data asset. It addresses another case: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. For that case, the distinguishing justification or acceptance check is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input. The present case instead states: An AutoML tabular training job expects an MLTable with schema and transformation rules, but a folder pointer is supplied. It calls for Define and register an MLTable data asset with the intended table paths and transforms. Showing success for the other case would not establish: An MLTable describes how tabular data is read, including supported schemas and transformations, beyond merely naming a folder.

Question 48

The same dataset name is reused after a schema change, and historical experiments can no longer reproduce old results. What governance feature should the team use?

  1. Create a new immutable data asset version and reference explicit versions in jobs.
  2. Record the specific registered data asset name and version with each run.
  3. Register the input as a versioned uri_file data asset.
  4. Register separately versioned data assets for each snapshot and bind jobs to those versions.

Explanation

Correct Answer

A:

Version references preserve historical input identity; overwriting an unversioned path hides the data used for earlier training.

Incorrect Answers

B:

Record the specific registered data asset name and version with each run. That operation would be relevant if: Two training jobs use different dataset versions but the same run name. Its corresponding reason or verification is: Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names. However the problem in this question is: The same dataset name is reused after a schema change, and historical experiments can no longer reproduce old results. The requirement instead calls for Create a new immutable data asset version and reference explicit versions in jobs; the question-specific check is: Version references preserve historical input identity; overwriting an unversioned path hides the data used for earlier training.

C:

Register the input as a versioned uri_file data asset. A separate source case supports that approach when: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. The supporting rationale or observable result is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input. This question describes a different issue: The same dataset name is reused after a schema change, and historical experiments can no longer reproduce old results. Address it through Create a new immutable data asset version and reference explicit versions in jobs, with the required justification or evidence: Version references preserve historical input identity; overwriting an unversioned path hides the data used for earlier training.

D:

Register separately versioned data assets for each snapshot and bind jobs to those versions. This is useful for the distinct issue: A model retraining run must compare outcomes from data collected this week and last week without overwriting either snapshot. The relevant technical rationale or evidence for that issue is: Independent snapshot versions allow fair temporal comparison and avoid silent changes in data during reruns. Here the reported issue is: The same dataset name is reused after a schema change, and historical experiments can no longer reproduce old results. The relevant response is: Create a new immutable data asset version and reference explicit versions in jobs. The first result cannot verify this different correction: Version references preserve historical input identity; overwriting an unversioned path hides the data used for earlier training.

Question 49

A pipeline input points directly to an individual's personal blob URL, which is likely to disappear. What should be improved for reproducibility?

  1. Change the component input to a compatible uri_folder asset for the required directory structure.
  2. Register the input as a versioned uri_file data asset.
  3. Register a uri_folder data asset that points at the image collection.
  4. Register the data location as a governed Azure ML data asset with ownership and version metadata.

Explanation

Correct Answer

D:

Managed data assets make a training input discoverable and reusable without depending on an employee's transient location.

Incorrect Answers

A:

The alternative, Change the component input to a compatible uri_folder asset for the required directory structure, belongs to a different technical condition: A training task expects a directory containing nested subfolders, but its input asset uses uri_file and points to one manifest. There the source-specific mechanism or proof is: An input's asset type must match the component's expected file-versus-folder contract, not merely share a similar path name. The condition asked about here is: A pipeline input points directly to an individual's personal blob URL, which is likely to disappear. A suitable correction is Register the data location as a governed Azure ML data asset with ownership and version metadata; the targeted justification or result is: Managed data assets make a training input discoverable and reusable without depending on an employee's transient location.

B:

Register the input as a versioned uri_file data asset. That operation would be relevant if: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. Its corresponding reason or verification is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input. However the problem in this question is: A pipeline input points directly to an individual's personal blob URL, which is likely to disappear. The requirement instead calls for Register the data location as a governed Azure ML data asset with ownership and version metadata; the question-specific check is: Managed data assets make a training input discoverable and reusable without depending on an employee's transient location.

C:

Register a uri_folder data asset that points at the image collection. A separate source case supports that approach when: A training component consumes thousands of images under a common storage prefix and should not list each one individually. The supporting rationale or observable result is: A uri_folder supplies the directory location to downstream components, avoiding a separate asset version for every individual image. This question describes a different issue: A pipeline input points directly to an individual's personal blob URL, which is likely to disappear. Address it through Register the data location as a governed Azure ML data asset with ownership and version metadata, with the required justification or evidence: Managed data assets make a training input discoverable and reusable without depending on an employee's transient location.

Question 50

Two training jobs use different dataset versions but the same run name. Which metadata should link predictions to the actual source data?

  1. Change the component input to a compatible uri_folder asset for the required directory structure.
  2. Register the data location as a governed Azure ML data asset with ownership and version metadata.
  3. Record the specific registered data asset name and version with each run.
  4. Register the input as a versioned uri_file data asset.

Explanation

Correct Answer

C:

Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names.

Incorrect Answers

A:

The alternative, Change the component input to a compatible uri_folder asset for the required directory structure, belongs to a different technical condition: A training task expects a directory containing nested subfolders, but its input asset uses uri_file and points to one manifest. There the source-specific mechanism or proof is: An input's asset type must match the component's expected file-versus-folder contract, not merely share a similar path name. The condition asked about here is: Two training jobs use different dataset versions but the same run name. A suitable correction is Record the specific registered data asset name and version with each run; the targeted justification or result is: Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names.

B:

Register the data location as a governed Azure ML data asset with ownership and version metadata. That operation would be relevant if: A pipeline input points directly to an individual's personal blob URL, which is likely to disappear. Its corresponding reason or verification is: Managed data assets make a training input discoverable and reusable without depending on an employee's transient location. However the problem in this question is: Two training jobs use different dataset versions but the same run name. The requirement instead calls for Record the specific registered data asset name and version with each run; the question-specific check is: Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names.

D:

Register the input as a versioned uri_file data asset. A separate source case supports that approach when: An Azure ML pipeline needs to pass one versioned parquet file rather than an entire mounted directory. The supporting rationale or observable result is: A uri_file represents a single addressed file; treating it as an unrestricted directory would misstate the component's expected input. This question describes a different issue: Two training jobs use different dataset versions but the same run name. Address it through Record the specific registered data asset name and version with each run, with the required justification or evidence: Explicit source versions make downstream predictions traceable even when experiment labels or models share friendly names.

Operationalizing Machine Learning and Generative AI Solutions (AI-300) Practice Tests