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 12

Question 110

A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. Which Bicep feature exposes it?

  1. Reference resource symbols and their IDs instead of copying fixed resource-ID strings.
  2. Define a Bicep output for the workspace resource ID and consume the deployment output.
  3. Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets.
  4. Use Azure deployment what-if against the target scope and parameter set.

Explanation

Correct Answer

B:

Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.

Incorrect Answers

A:

Reference resource symbols and their IDs instead of copying fixed resource-ID strings. A separate source case supports that approach when: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. The supporting rationale or observable result is: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change. This question describes a different issue: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. Address it through Define a Bicep output for the workspace resource ID and consume the deployment output, with the required justification or evidence: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.

C:

Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets. This is useful for the distinct issue: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. The relevant technical rationale or evidence for that issue is: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code. Here the reported issue is: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. The relevant response is: Define a Bicep output for the workspace resource ID and consume the deployment output. The first result cannot verify this different correction: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.

D:

Use Azure deployment what-if against the target scope and parameter set. It addresses another case: A team must preview resource changes before a production Azure ML workspace update. For that case, the distinguishing justification or acceptance check is: What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment. The present case instead states: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. It calls for Define a Bicep output for the workspace resource ID and consume the deployment output. Showing success for the other case would not establish: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.

Question 111

A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. What is the secure alternative?

  1. Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets.
  2. Use Azure deployment what-if against the target scope and parameter set.
  3. Declare resource dependencies and reference the storage resource symbolically in the workspace definition.
  4. Keep a shared Bicep module and use environment-specific parameter files in the deployment.

Explanation

Correct Answer

A:

Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code.

Incorrect Answers

B:

Use Azure deployment what-if against the target scope and parameter set. That operation would be relevant if: A team must preview resource changes before a production Azure ML workspace update. Its corresponding reason or verification is: What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment. However the problem in this question is: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. The requirement instead calls for Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets; the question-specific check is: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code.

C:

Declare resource dependencies and reference the storage resource symbolically in the workspace definition. A separate source case supports that approach when: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. The supporting rationale or observable result is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail. This question describes a different issue: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. Address it through Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets, with the required justification or evidence: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code.

D:

Keep a shared Bicep module and use environment-specific parameter files in the deployment. This is useful for the distinct issue: A team wants to deploy the same infrastructure with one isolated parameter file per region and immutable source templates. The relevant technical rationale or evidence for that issue is: Separate parameter values from reusable modules reduce drift and make regional configuration decisions explicit in review. Here the reported issue is: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. The relevant response is: Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets. The first result cannot verify this different correction: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code.

Question 112

An engineer gets a Bicep validation error about an unknown property before any Azure resources change. What is the first useful step?

  1. Reference resource symbols and their IDs instead of copying fixed resource-ID strings.
  2. Set the Bicep target scope and deployment command to the intended Azure hierarchy level.
  3. Declare resource dependencies and reference the storage resource symbolically in the workspace definition.
  4. Run Bicep build and deployment validation against the resource type's supported schema.

Explanation

Correct Answer

D:

Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources.

Incorrect Answers

A:

The alternative, Reference resource symbols and their IDs instead of copying fixed resource-ID strings, belongs to a different technical condition: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. There the source-specific mechanism or proof is: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change. The condition asked about here is: An engineer gets a Bicep validation error about an unknown property before any Azure resources change. A suitable correction is Run Bicep build and deployment validation against the resource type's supported schema; the targeted justification or result is: Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources.

B:

Set the Bicep target scope and deployment command to the intended Azure hierarchy level. That operation would be relevant if: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. Its corresponding reason or verification is: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template. However the problem in this question is: An engineer gets a Bicep validation error about an unknown property before any Azure resources change. The requirement instead calls for Run Bicep build and deployment validation against the resource type's supported schema; the question-specific check is: Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources.

C:

Declare resource dependencies and reference the storage resource symbolically in the workspace definition. A separate source case supports that approach when: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. The supporting rationale or observable result is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail. This question describes a different issue: An engineer gets a Bicep validation error about an unknown property before any Azure resources change. Address it through Run Bicep build and deployment validation against the resource type's supported schema, with the required justification or evidence: Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources.

Question 113

A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. What needs adjustment?

  1. Keep a shared Bicep module and use environment-specific parameter files in the deployment.
  2. Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets.
  3. Set the Bicep target scope and deployment command to the intended Azure hierarchy level.
  4. Declare resource dependencies and reference the storage resource symbolically in the workspace definition.

Explanation

Correct Answer

C:

Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template.

Incorrect Answers

A:

Keep a shared Bicep module and use environment-specific parameter files in the deployment. It addresses another case: A team wants to deploy the same infrastructure with one isolated parameter file per region and immutable source templates. For that case, the distinguishing justification or acceptance check is: Separate parameter values from reusable modules reduce drift and make regional configuration decisions explicit in review. The present case instead states: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. It calls for Set the Bicep target scope and deployment command to the intended Azure hierarchy level. Showing success for the other case would not establish: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template.

B:

The alternative, Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets, belongs to a different technical condition: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. There the source-specific mechanism or proof is: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code. The condition asked about here is: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. A suitable correction is Set the Bicep target scope and deployment command to the intended Azure hierarchy level; the targeted justification or result is: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template.

D:

Declare resource dependencies and reference the storage resource symbolically in the workspace definition. That operation would be relevant if: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. Its corresponding reason or verification is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail. However the problem in this question is: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. The requirement instead calls for Set the Bicep target scope and deployment command to the intended Azure hierarchy level; the question-specific check is: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template.

Question 114

A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. What should be installed?

  1. Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets.
  2. Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs.
  3. Define a Bicep output for the workspace resource ID and consume the deployment output.
  4. Reference resource symbols and their IDs instead of copying fixed resource-ID strings.

Explanation

Correct Answer

B:

Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands.

Incorrect Answers

A:

Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets. This is useful for the distinct issue: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. The relevant technical rationale or evidence for that issue is: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code. Here the reported issue is: A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. The relevant response is: Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs. The first result cannot verify this different correction: Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands.

C:

Define a Bicep output for the workspace resource ID and consume the deployment output. It addresses another case: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. For that case, the distinguishing justification or acceptance check is: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values. The present case instead states: A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. It calls for Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs. Showing success for the other case would not establish: Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands.

D:

The alternative, Reference resource symbols and their IDs instead of copying fixed resource-ID strings, belongs to a different technical condition: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. There the source-specific mechanism or proof is: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change. The condition asked about here is: A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. A suitable correction is Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs; the targeted justification or result is: Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands.

Question 115

A team wants to deploy the same infrastructure with one isolated parameter file per region and immutable source templates. Which approach supports this?

  1. Keep a shared Bicep module and use environment-specific parameter files in the deployment.
  2. Select the intended Azure subscription and deployment scope before running IaC.
  3. Declare resource dependencies and reference the storage resource symbolically in the workspace definition.
  4. Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs.

Explanation

Correct Answer

A:

Separate parameter values from reusable modules reduce drift and make regional configuration decisions explicit in review.

Incorrect Answers

B:

Select the intended Azure subscription and deployment scope before running IaC. A separate source case supports that approach when: A team's Bicep deployment changes subscription settings unexpectedly because a CLI script targets the engineer's personal Azure context. The supporting rationale or observable result is: Explicit deployment context prevents resources from appearing in whatever subscription the operator authenticated to most recently. This question describes a different issue: A team wants to deploy the same infrastructure with one isolated parameter file per region and immutable source templates. Address it through Keep a shared Bicep module and use environment-specific parameter files in the deployment, with the required justification or evidence: Separate parameter values from reusable modules reduce drift and make regional configuration decisions explicit in review.

C:

Declare resource dependencies and reference the storage resource symbolically in the workspace definition. This is useful for the distinct issue: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. The relevant technical rationale or evidence for that issue is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail. Here the reported issue is: A team wants to deploy the same infrastructure with one isolated parameter file per region and immutable source templates. The relevant response is: Keep a shared Bicep module and use environment-specific parameter files in the deployment. The first result cannot verify this different correction: Separate parameter values from reusable modules reduce drift and make regional configuration decisions explicit in review.

D:

Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs. It addresses another case: A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. For that case, the distinguishing justification or acceptance check is: Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands. The present case instead states: A team wants to deploy the same infrastructure with one isolated parameter file per region and immutable source templates. It calls for Keep a shared Bicep module and use environment-specific parameter files in the deployment. Showing success for the other case would not establish: Separate parameter values from reusable modules reduce drift and make regional configuration decisions explicit in review.

Question 116

A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. How can Bicep avoid stale references?

  1. Run Bicep build and deployment validation against the resource type's supported schema.
  2. Pass environment-specific resource names and locations through declared Bicep parameters.
  3. Declare resource dependencies and reference the storage resource symbolically in the workspace definition.
  4. Reference resource symbols and their IDs instead of copying fixed resource-ID strings.

Explanation

Correct Answer

D:

Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change.

Incorrect Answers

A:

Run Bicep build and deployment validation against the resource type's supported schema. That operation would be relevant if: An engineer gets a Bicep validation error about an unknown property before any Azure resources change. Its corresponding reason or verification is: Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources. However the problem in this question is: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. The requirement instead calls for Reference resource symbols and their IDs instead of copying fixed resource-ID strings; the question-specific check is: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change.

B:

Pass environment-specific resource names and locations through declared Bicep parameters. A separate source case supports that approach when: An ML team hard-codes a storage account name into each copy of a workspace template. Different regions now require manual edits. The supporting rationale or observable result is: Parameters keep the template reusable while allowing approved environment differences without modifying core infrastructure logic. This question describes a different issue: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. Address it through Reference resource symbols and their IDs instead of copying fixed resource-ID strings, with the required justification or evidence: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change.

C:

Declare resource dependencies and reference the storage resource symbolically in the workspace definition. This is useful for the distinct issue: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. The relevant technical rationale or evidence for that issue is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail. Here the reported issue is: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. The relevant response is: Reference resource symbols and their IDs instead of copying fixed resource-ID strings. The first result cannot verify this different correction: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change.

Question 117

A GitHub Actions workflow deploys infrastructure on every push, including documentation edits to feature branches. What trigger policy avoids unintended deployments?

  1. Use OIDC federation and avoid emitting access tokens or secret values in job logs.
  2. Restrict deployment jobs to approved branches, paths, or explicit workflow dispatch events.
  3. Deploy from a pinned approved release commit or immutable artifact rather than an uncontrolled moving branch.
  4. Use an explicit matrix strategy with approved region and parameter combinations.

Explanation

Correct Answer

B:

Targeted events prevent unrelated repository activity from initiating resource changes while retaining repeatable automation.

Incorrect Answers

A:

The alternative, Use OIDC federation and avoid emitting access tokens or secret values in job logs, belongs to a different technical condition: A workflow reads an Azure deployment token and accidentally logs it in step output. There the source-specific mechanism or proof is: Short-lived identity exchange and secret-safe logging reduce exposure during repeatable provisioning workflows. The condition asked about here is: A GitHub Actions workflow deploys infrastructure on every push, including documentation edits to feature branches. A suitable correction is Restrict deployment jobs to approved branches, paths, or explicit workflow dispatch events; the targeted justification or result is: Targeted events prevent unrelated repository activity from initiating resource changes while retaining repeatable automation.

C:

Deploy from a pinned approved release commit or immutable artifact rather than an uncontrolled moving branch. That operation would be relevant if: A nightly infrastructure workflow changes a workspace even when no reviewed manifest update exists. Its corresponding reason or verification is: Release pinning ensures scheduled automation applies reviewed configuration instead of whatever code happens to be newest. However the problem in this question is: A GitHub Actions workflow deploys infrastructure on every push, including documentation edits to feature branches. The requirement instead calls for Restrict deployment jobs to approved branches, paths, or explicit workflow dispatch events; the question-specific check is: Targeted events prevent unrelated repository activity from initiating resource changes while retaining repeatable automation.

D:

Use an explicit matrix strategy with approved region and parameter combinations. A separate source case supports that approach when: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. The supporting rationale or observable result is: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set. This question describes a different issue: A GitHub Actions workflow deploys infrastructure on every push, including documentation edits to feature branches. Address it through Restrict deployment jobs to approved branches, paths, or explicit workflow dispatch events, with the required justification or evidence: Targeted events prevent unrelated repository activity from initiating resource changes while retaining repeatable automation.

Question 118

Two simultaneous GitHub jobs update the same Azure ML production workspace and race to replace configuration. How can the workflow serialize them?

  1. Configure a GitHub Actions concurrency group for the shared deployment target.
  2. Pin external GitHub Actions to reviewed immutable commit SHAs.
  3. Publish build artifacts or versioned model assets and download them in dependent jobs.
  4. Record the Git commit SHA, parameter values, deployment ID, and outcome as release evidence.

Explanation

Correct Answer

A:

Concurrency controls prevent overlapping deployment runs from applying conflicting infrastructure changes to one environment.

Incorrect Answers

B:

Pin external GitHub Actions to reviewed immutable commit SHAs. It addresses another case: A GitHub Actions script downloads an unpinned third-party action on every deployment. Supply-chain reviewers object. For that case, the distinguishing justification or acceptance check is: Pinning reduces the possibility that a changed upstream action runs unexpected code in a privileged deployment pipeline. The present case instead states: Two simultaneous GitHub jobs update the same Azure ML production workspace and race to replace configuration. It calls for Configure a GitHub Actions concurrency group for the shared deployment target. Showing success for the other case would not establish: Concurrency controls prevent overlapping deployment runs from applying conflicting infrastructure changes to one environment.

C:

The alternative, Publish build artifacts or versioned model assets and download them in dependent jobs, belongs to a different technical condition: An engineer checks in generated model binaries as workflow source to pass them between training and deployment jobs. There the source-specific mechanism or proof is: Artifact transfer preserves the exact build output without inflating source history or recreating it in each deployment job. The condition asked about here is: Two simultaneous GitHub jobs update the same Azure ML production workspace and race to replace configuration. A suitable correction is Configure a GitHub Actions concurrency group for the shared deployment target; the targeted justification or result is: Concurrency controls prevent overlapping deployment runs from applying conflicting infrastructure changes to one environment.

D:

Record the Git commit SHA, parameter values, deployment ID, and outcome as release evidence. That operation would be relevant if: A failed production infrastructure deployment should leave evidence identifying the exact Bicep commit. Its corresponding reason or verification is: Immutable source and deployment identifiers make it possible to reconstruct which configuration produced the deployed state. However the problem in this question is: Two simultaneous GitHub jobs update the same Azure ML production workspace and race to replace configuration. The requirement instead calls for Configure a GitHub Actions concurrency group for the shared deployment target; the question-specific check is: Concurrency controls prevent overlapping deployment runs from applying conflicting infrastructure changes to one environment.

Question 119

A GitHub Actions job deploys to production before its Bicep validation step finishes because the jobs have no dependency relation. What should be declared?

  1. Use an explicit matrix strategy with approved region and parameter combinations.
  2. Split region deployments into independently addressable workflow jobs or matrix legs.
  3. Pin external GitHub Actions to reviewed immutable commit SHAs.
  4. Use needs dependencies so the deployment job waits for successful validation.

Explanation

Correct Answer

D:

Explicit job dependencies enforce validation gates before resource changes instead of relying on incidental job timing.

Incorrect Answers

A:

Use an explicit matrix strategy with approved region and parameter combinations. This is useful for the distinct issue: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. The relevant technical rationale or evidence for that issue is: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set. Here the reported issue is: A GitHub Actions job deploys to production before its Bicep validation step finishes because the jobs have no dependency relation. The relevant response is: Use needs dependencies so the deployment job waits for successful validation. The first result cannot verify this different correction: Explicit job dependencies enforce validation gates before resource changes instead of relying on incidental job timing.

B:

Split region deployments into independently addressable workflow jobs or matrix legs. It addresses another case: A new ML resource deployment fails in one environment, while three regions succeed. The team wants isolated reruns rather than rerunning all environments. For that case, the distinguishing justification or acceptance check is: Per-environment jobs isolate failures and let authorized operators rerun a affected region without replaying healthy deployments. The present case instead states: A GitHub Actions job deploys to production before its Bicep validation step finishes because the jobs have no dependency relation. It calls for Use needs dependencies so the deployment job waits for successful validation. Showing success for the other case would not establish: Explicit job dependencies enforce validation gates before resource changes instead of relying on incidental job timing.

C:

The alternative, Pin external GitHub Actions to reviewed immutable commit SHAs, belongs to a different technical condition: A GitHub Actions script downloads an unpinned third-party action on every deployment. Supply-chain reviewers object. There the source-specific mechanism or proof is: Pinning reduces the possibility that a changed upstream action runs unexpected code in a privileged deployment pipeline. The condition asked about here is: A GitHub Actions job deploys to production before its Bicep validation step finishes because the jobs have no dependency relation. A suitable correction is Use needs dependencies so the deployment job waits for successful validation; the targeted justification or result is: Explicit job dependencies enforce validation gates before resource changes instead of relying on incidental job timing.

Question 120

The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. What GitHub Actions feature fits?

  1. Make deployment depend on successful test and build jobs and halt on failures.
  2. Publish build artifacts or versioned model assets and download them in dependent jobs.
  3. Use an explicit matrix strategy with approved region and parameter combinations.
  4. Record the Git commit SHA, parameter values, deployment ID, and outcome as release evidence.

Explanation

Correct Answer

C:

A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.

Incorrect Answers

A:

Make deployment depend on successful test and build jobs and halt on failures. This is useful for the distinct issue: A workflow has test, build, and deploy jobs but continues deploying when integration tests fail. The relevant technical rationale or evidence for that issue is: Gated job dependencies ensure unverified artifacts do not advance to environments that serve production ML traffic. Here the reported issue is: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. The relevant response is: Use an explicit matrix strategy with approved region and parameter combinations. The first result cannot verify this different correction: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.

B:

Publish build artifacts or versioned model assets and download them in dependent jobs. It addresses another case: An engineer checks in generated model binaries as workflow source to pass them between training and deployment jobs. For that case, the distinguishing justification or acceptance check is: Artifact transfer preserves the exact build output without inflating source history or recreating it in each deployment job. The present case instead states: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. It calls for Use an explicit matrix strategy with approved region and parameter combinations. Showing success for the other case would not establish: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.

D:

The alternative, Record the Git commit SHA, parameter values, deployment ID, and outcome as release evidence, belongs to a different technical condition: A failed production infrastructure deployment should leave evidence identifying the exact Bicep commit. There the source-specific mechanism or proof is: Immutable source and deployment identifiers make it possible to reconstruct which configuration produced the deployed state. The condition asked about here is: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. A suitable correction is Use an explicit matrix strategy with approved region and parameter combinations; the targeted justification or result is: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.

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