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 11

Question 100

A deployment job succeeds locally but GitHub Actions cannot authenticate because the Azure identity lacks a matching audience claim. Which configuration should be validated?

  1. Verify issuer, audience, and subject on the federated credential against the GitHub-issued token.
  2. Grant only the required workspace or resource-group actions to its deployment identity.
  3. Require an approved protected GitHub environment and reviewers before production deployment jobs.
  4. Remove secrets from source and authenticate using identity federation or an approved secret service.

Explanation

Correct Answer

A:

OIDC federation requires all trust claims to match; resource-group permission changes cannot fix token-claim rejection.

Incorrect Answers

B:

Grant only the required workspace or resource-group actions to its deployment identity. That operation would be relevant if: A GitHub pipeline may update one Azure ML workspace but is currently assigned subscription Owner. Its corresponding reason or verification is: Scoped RBAC limits the blast radius while retaining permissions needed for the authorized ML deployment steps. However the problem in this question is: A deployment job succeeds locally but GitHub Actions cannot authenticate because the Azure identity lacks a matching audience claim. The requirement instead calls for Verify issuer, audience, and subject on the federated credential against the GitHub-issued token; the question-specific check is: OIDC federation requires all trust claims to match; resource-group permission changes cannot fix token-claim rejection.

C:

Require an approved protected GitHub environment and reviewers before production deployment jobs. A separate source case supports that approach when: A pipeline has correct Azure credentials but users can run it manually on unreviewed experimental branches to deploy production models. The supporting rationale or observable result is: GitHub environment protection can gate sensitive workflow jobs independently from possession of a valid Azure deployment identity. This question describes a different issue: A deployment job succeeds locally but GitHub Actions cannot authenticate because the Azure identity lacks a matching audience claim. Address it through Verify issuer, audience, and subject on the federated credential against the GitHub-issued token, with the required justification or evidence: OIDC federation requires all trust claims to match; resource-group permission changes cannot fix token-claim rejection.

D:

Remove secrets from source and authenticate using identity federation or an approved secret service. This is useful for the distinct issue: An ML operations job includes cloud credentials directly in its checked-in YAML for convenience. The relevant technical rationale or evidence for that issue is: Tracked workflow files are widely replicated and reviewed; embedding credentials creates unnecessary exposure beyond the intended deployment run. Here the reported issue is: A deployment job succeeds locally but GitHub Actions cannot authenticate because the Azure identity lacks a matching audience claim. The relevant response is: Verify issuer, audience, and subject on the federated credential against the GitHub-issued token. The first result cannot verify this different correction: OIDC federation requires all trust claims to match; resource-group permission changes cannot fix token-claim rejection.

Question 101

A pipeline uses a shared personal access token to push model configuration changes into a private repository. What alternative improves traceability?

  1. Match the federated subject claim to the exact intended GitHub owner, repository, and reference.
  2. Require an approved protected GitHub environment and reviewers before production deployment jobs.
  3. Configure Microsoft Entra workload identity federation using GitHub OIDC claims.
  4. Use an appropriately scoped GitHub App or workflow token tied to automation.

Explanation

Correct Answer

D:

Automation-owned credentials can be permission-scoped and audited without tying infrastructure changes to one employee's personal account.

Incorrect Answers

A:

The alternative, Match the federated subject claim to the exact intended GitHub owner, repository, and reference, belongs to a different technical condition: A CI job in one repository unexpectedly authenticates as a workload identity intended for another repository. There the source-specific mechanism or proof is: The subject binds the trust relationship to a specific GitHub execution context, not merely a shared Azure tenant. The condition asked about here is: A pipeline uses a shared personal access token to push model configuration changes into a private repository. A suitable correction is Use an appropriately scoped GitHub App or workflow token tied to automation; the targeted justification or result is: Automation-owned credentials can be permission-scoped and audited without tying infrastructure changes to one employee's personal account.

B:

Require an approved protected GitHub environment and reviewers before production deployment jobs. That operation would be relevant if: A pipeline has correct Azure credentials but users can run it manually on unreviewed experimental branches to deploy production models. Its corresponding reason or verification is: GitHub environment protection can gate sensitive workflow jobs independently from possession of a valid Azure deployment identity. However the problem in this question is: A pipeline uses a shared personal access token to push model configuration changes into a private repository. The requirement instead calls for Use an appropriately scoped GitHub App or workflow token tied to automation; the question-specific check is: Automation-owned credentials can be permission-scoped and audited without tying infrastructure changes to one employee's personal account.

C:

Configure Microsoft Entra workload identity federation using GitHub OIDC claims. A separate source case supports that approach when: A GitHub Actions workflow deploys to Azure ML using a service principal secret stored in repository settings. Security wants to eliminate long-lived secrets. The supporting rationale or observable result is: Federated credentials exchange trusted workflow identity tokens for Azure access without storing a reusable client secret in GitHub. This question describes a different issue: A pipeline uses a shared personal access token to push model configuration changes into a private repository. Address it through Use an appropriately scoped GitHub App or workflow token tied to automation, with the required justification or evidence: Automation-owned credentials can be permission-scoped and audited without tying infrastructure changes to one employee's personal account.

Question 102

An ML operations job includes cloud credentials directly in its checked-in YAML for convenience. How should the integration be redesigned?

  1. Grant the runtime Azure identity the required storage data-plane role on that container.
  2. Use distinct federated workload identities and scopes for staging and production environments.
  3. Remove secrets from source and authenticate using identity federation or an approved secret service.
  4. Verify issuer, audience, and subject on the federated credential against the GitHub-issued token.

Explanation

Correct Answer

C:

Tracked workflow files are widely replicated and reviewed; embedding credentials creates unnecessary exposure beyond the intended deployment run.

Incorrect Answers

A:

Grant the runtime Azure identity the required storage data-plane role on that container. It addresses another case: GitHub runners authenticate successfully but cannot access artifacts from a private storage container used by the deployment. For that case, the distinguishing justification or acceptance check is: Authentication alone is not authorization to data; Azure RBAC on storage can be required in addition to workspace roles. The present case instead states: An ML operations job includes cloud credentials directly in its checked-in YAML for convenience. It calls for Remove secrets from source and authenticate using identity federation or an approved secret service. Showing success for the other case would not establish: Tracked workflow files are widely replicated and reviewed; embedding credentials creates unnecessary exposure beyond the intended deployment run.

B:

The alternative, Use distinct federated workload identities and scopes for staging and production environments, belongs to a different technical condition: A production deployment uses the same federated identity as experimental workflows and cannot attribute risky changes to a distinct release context. There the source-specific mechanism or proof is: Environment-specific workload identities improve isolation, auditability, and rollback investigation without spreading shared deployment credentials. The condition asked about here is: An ML operations job includes cloud credentials directly in its checked-in YAML for convenience. A suitable correction is Remove secrets from source and authenticate using identity federation or an approved secret service; the targeted justification or result is: Tracked workflow files are widely replicated and reviewed; embedding credentials creates unnecessary exposure beyond the intended deployment run.

D:

Verify issuer, audience, and subject on the federated credential against the GitHub-issued token. That operation would be relevant if: A deployment job succeeds locally but GitHub Actions cannot authenticate because the Azure identity lacks a matching audience claim. Its corresponding reason or verification is: OIDC federation requires all trust claims to match; resource-group permission changes cannot fix token-claim rejection. However the problem in this question is: An ML operations job includes cloud credentials directly in its checked-in YAML for convenience. The requirement instead calls for Remove secrets from source and authenticate using identity federation or an approved secret service; the question-specific check is: Tracked workflow files are widely replicated and reviewed; embedding credentials creates unnecessary exposure beyond the intended deployment run.

Question 103

GitHub runners authenticate successfully but cannot access artifacts from a private storage container used by the deployment. What additional permission is missing?

  1. Use distinct federated workload identities and scopes for staging and production environments.
  2. Grant the runtime Azure identity the required storage data-plane role on that container.
  3. Constrain the federated credential subject and issuer to the approved repository and protected workflow context.
  4. Remove secrets from source and authenticate using identity federation or an approved secret service.

Explanation

Correct Answer

B:

Authentication alone is not authorization to data; Azure RBAC on storage can be required in addition to workspace roles.

Incorrect Answers

A:

Use distinct federated workload identities and scopes for staging and production environments. This is useful for the distinct issue: A production deployment uses the same federated identity as experimental workflows and cannot attribute risky changes to a distinct release context. The relevant technical rationale or evidence for that issue is: Environment-specific workload identities improve isolation, auditability, and rollback investigation without spreading shared deployment credentials. Here the reported issue is: GitHub runners authenticate successfully but cannot access artifacts from a private storage container used by the deployment. The relevant response is: Grant the runtime Azure identity the required storage data-plane role on that container. The first result cannot verify this different correction: Authentication alone is not authorization to data; Azure RBAC on storage can be required in addition to workspace roles.

C:

Constrain the federated credential subject and issuer to the approved repository and protected workflow context. It addresses another case: A workflow from a public fork can request a deployment identity because the federation subject allows all branches. For that case, the distinguishing justification or acceptance check is: Narrow matching conditions prevent an untrusted branch or repository event from assuming the production deployment identity. The present case instead states: GitHub runners authenticate successfully but cannot access artifacts from a private storage container used by the deployment. It calls for Grant the runtime Azure identity the required storage data-plane role on that container. Showing success for the other case would not establish: Authentication alone is not authorization to data; Azure RBAC on storage can be required in addition to workspace roles.

D:

The alternative, Remove secrets from source and authenticate using identity federation or an approved secret service, belongs to a different technical condition: An ML operations job includes cloud credentials directly in its checked-in YAML for convenience. There the source-specific mechanism or proof is: Tracked workflow files are widely replicated and reviewed; embedding credentials creates unnecessary exposure beyond the intended deployment run. The condition asked about here is: GitHub runners authenticate successfully but cannot access artifacts from a private storage container used by the deployment. A suitable correction is Grant the runtime Azure identity the required storage data-plane role on that container; the targeted justification or result is: Authentication alone is not authorization to data; Azure RBAC on storage can be required in addition to workspace roles.

Question 104

A production deployment uses the same federated identity as experimental workflows and cannot attribute risky changes to a distinct release context. How should identity be separated?

  1. Use distinct federated workload identities and scopes for staging and production environments.
  2. Explicitly set the GITHUB_TOKEN job permissions to read-only except where write is required.
  3. Use an appropriately scoped GitHub App or workflow token tied to automation.
  4. Verify issuer, audience, and subject on the federated credential against the GitHub-issued token.

Explanation

Correct Answer

A:

Environment-specific workload identities improve isolation, auditability, and rollback investigation without spreading shared deployment credentials.

Incorrect Answers

B:

Explicitly set the GITHUB_TOKEN job permissions to read-only except where write is required. A separate source case supports that approach when: A GitHub workflow uses the default token with broad write privileges even though its job only reads source. The supporting rationale or observable result is: Job-scoped permissions reduce the actions a compromised CI step can perform against repository contents and releases. This question describes a different issue: A production deployment uses the same federated identity as experimental workflows and cannot attribute risky changes to a distinct release context. Address it through Use distinct federated workload identities and scopes for staging and production environments, with the required justification or evidence: Environment-specific workload identities improve isolation, auditability, and rollback investigation without spreading shared deployment credentials.

C:

Use an appropriately scoped GitHub App or workflow token tied to automation. This is useful for the distinct issue: A pipeline uses a shared personal access token to push model configuration changes into a private repository. The relevant technical rationale or evidence for that issue is: Automation-owned credentials can be permission-scoped and audited without tying infrastructure changes to one employee's personal account. Here the reported issue is: A production deployment uses the same federated identity as experimental workflows and cannot attribute risky changes to a distinct release context. The relevant response is: Use distinct federated workload identities and scopes for staging and production environments. The first result cannot verify this different correction: Environment-specific workload identities improve isolation, auditability, and rollback investigation without spreading shared deployment credentials.

D:

Verify issuer, audience, and subject on the federated credential against the GitHub-issued token. It addresses another case: A deployment job succeeds locally but GitHub Actions cannot authenticate because the Azure identity lacks a matching audience claim. For that case, the distinguishing justification or acceptance check is: OIDC federation requires all trust claims to match; resource-group permission changes cannot fix token-claim rejection. The present case instead states: A production deployment uses the same federated identity as experimental workflows and cannot attribute risky changes to a distinct release context. It calls for Use distinct federated workload identities and scopes for staging and production environments. Showing success for the other case would not establish: Environment-specific workload identities improve isolation, auditability, and rollback investigation without spreading shared deployment credentials.

Question 105

A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. What should be added?

  1. Select the intended Azure subscription and deployment scope before running IaC.
  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. Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets.

Explanation

Correct Answer

C:

Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail.

Incorrect Answers

A:

Select the intended Azure subscription and deployment scope before running IaC. That operation would be relevant if: A team's Bicep deployment changes subscription settings unexpectedly because a CLI script targets the engineer's personal Azure context. Its corresponding reason or verification is: Explicit deployment context prevents resources from appearing in whatever subscription the operator authenticated to most recently. However the problem in this question is: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. The requirement instead calls for Declare resource dependencies and reference the storage resource symbolically in the workspace definition; the question-specific check is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail.

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 Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. Address it through Declare resource dependencies and reference the storage resource symbolically in the workspace definition, with the required justification or evidence: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail.

D:

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 Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. The relevant response is: Declare resource dependencies and reference the storage resource symbolically in the workspace definition. The first result cannot verify this different correction: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail.

Question 106

A team's Bicep deployment changes subscription settings unexpectedly because a CLI script targets the engineer's personal Azure context. What should the script specify?

  1. Pass environment-specific resource names and locations through declared Bicep parameters.
  2. Select the intended Azure subscription and deployment scope before running IaC.
  3. Define a Bicep output for the workspace resource ID and consume the deployment output.
  4. Set the Bicep target scope and deployment command to the intended Azure hierarchy level.

Explanation

Correct Answer

B:

Explicit deployment context prevents resources from appearing in whatever subscription the operator authenticated to most recently.

Incorrect Answers

A:

The alternative, Pass environment-specific resource names and locations through declared Bicep parameters, belongs to a different technical condition: An ML team hard-codes a storage account name into each copy of a workspace template. Different regions now require manual edits. There the source-specific mechanism or proof is: Parameters keep the template reusable while allowing approved environment differences without modifying core infrastructure logic. The condition asked about here is: A team's Bicep deployment changes subscription settings unexpectedly because a CLI script targets the engineer's personal Azure context. A suitable correction is Select the intended Azure subscription and deployment scope before running IaC; the targeted justification or result is: Explicit deployment context prevents resources from appearing in whatever subscription the operator authenticated to most recently.

C:

Define a Bicep output for the workspace resource ID and consume the deployment output. That operation would be relevant if: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. Its corresponding reason or verification is: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values. However the problem in this question is: A team's Bicep deployment changes subscription settings unexpectedly because a CLI script targets the engineer's personal Azure context. The requirement instead calls for Select the intended Azure subscription and deployment scope before running IaC; the question-specific check is: Explicit deployment context prevents resources from appearing in whatever subscription the operator authenticated to most recently.

D:

Set the Bicep target scope and deployment command to the intended Azure hierarchy level. A separate source case supports that approach when: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. The supporting rationale or observable result is: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template. This question describes a different issue: A team's Bicep deployment changes subscription settings unexpectedly because a CLI script targets the engineer's personal Azure context. Address it through Select the intended Azure subscription and deployment scope before running IaC, with the required justification or evidence: Explicit deployment context prevents resources from appearing in whatever subscription the operator authenticated to most recently.

Question 107

A repeat infrastructure deployment recreates workspace dependencies because each environment template contains random suffixes. What design best supports idempotency?

  1. Use deterministic names and declarative Bicep resources with parameterized environment values.
  2. Run Bicep build and deployment validation against the resource type's supported schema.
  3. Define a Bicep output for the workspace resource ID and consume the deployment output.
  4. Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs.

Explanation

Correct Answer

A:

Stable resource identifiers allow repeat provisioning to reconcile the intended deployment instead of creating duplicates on every run.

Incorrect Answers

B:

Run Bicep build and deployment validation against the resource type's supported schema. It addresses another case: An engineer gets a Bicep validation error about an unknown property before any Azure resources change. For that case, the distinguishing justification or acceptance check is: Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources. The present case instead states: A repeat infrastructure deployment recreates workspace dependencies because each environment template contains random suffixes. It calls for Use deterministic names and declarative Bicep resources with parameterized environment values. Showing success for the other case would not establish: Stable resource identifiers allow repeat provisioning to reconcile the intended deployment instead of creating duplicates on every run.

C:

The alternative, Define a Bicep output for the workspace resource ID and consume the deployment output, belongs to a different technical condition: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. There the source-specific mechanism or proof is: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values. The condition asked about here is: A repeat infrastructure deployment recreates workspace dependencies because each environment template contains random suffixes. A suitable correction is Use deterministic names and declarative Bicep resources with parameterized environment values; the targeted justification or result is: Stable resource identifiers allow repeat provisioning to reconcile the intended deployment instead of creating duplicates on every run.

D:

Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs. That operation would be relevant if: A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. Its corresponding reason or verification is: Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands. However the problem in this question is: A repeat infrastructure deployment recreates workspace dependencies because each environment template contains random suffixes. The requirement instead calls for Use deterministic names and declarative Bicep resources with parameterized environment values; the question-specific check is: Stable resource identifiers allow repeat provisioning to reconcile the intended deployment instead of creating duplicates on every run.

Question 108

A team must preview resource changes before a production Azure ML workspace update. Which command family serves this review?

  1. Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs.
  2. Declare resource dependencies and reference the storage resource symbolically in the workspace definition.
  3. Set the Bicep target scope and deployment command to the intended Azure hierarchy level.
  4. Use Azure deployment what-if against the target scope and parameter set.

Explanation

Correct Answer

D:

What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment.

Incorrect Answers

A:

Use the Azure CLI machine-learning ml extension compatible with Azure ML v2 assets and jobs. This is useful for the distinct issue: A build agent is using the obsolete v1 AML extension command syntax while its pipeline definitions use Azure ML v2. The relevant technical rationale or evidence for that issue is: Current v2 command forms require the matching CLI extension rather than deprecated v1 workspace and experiment commands. Here the reported issue is: A team must preview resource changes before a production Azure ML workspace update. The relevant response is: Use Azure deployment what-if against the target scope and parameter set. The first result cannot verify this different correction: What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment.

B:

Declare resource dependencies and reference the storage resource symbolically in the workspace definition. It addresses another case: A Bicep template creates an Azure ML workspace but deploys its dependent storage account after the workspace without resource dependencies. For that case, the distinguishing justification or acceptance check is: Bicep dependencies establish creation order when one resource needs another's identifier; parallel deployment without ordering can fail. The present case instead states: A team must preview resource changes before a production Azure ML workspace update. It calls for Use Azure deployment what-if against the target scope and parameter set. Showing success for the other case would not establish: What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment.

C:

The alternative, Set the Bicep target scope and deployment command to the intended Azure hierarchy level, belongs to a different technical condition: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. There the source-specific mechanism or proof is: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template. The condition asked about here is: A team must preview resource changes before a production Azure ML workspace update. A suitable correction is Use Azure deployment what-if against the target scope and parameter set; the targeted justification or result is: What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment.

Question 109

An ML team hard-codes a storage account name into each copy of a workspace template. Different regions now require manual edits. How should the template be improved?

  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. Pass environment-specific resource names and locations through declared Bicep parameters.
  4. Run Bicep build and deployment validation against the resource type's supported schema.

Explanation

Correct Answer

C:

Parameters keep the template reusable while allowing approved environment differences without modifying core infrastructure logic.

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: An ML team hard-codes a storage account name into each copy of a workspace template. Different regions now require manual edits. Address it through Pass environment-specific resource names and locations through declared Bicep parameters, with the required justification or evidence: Parameters keep the template reusable while allowing approved environment differences without modifying core infrastructure logic.

B:

Set the Bicep target scope and deployment command to the intended Azure hierarchy level. This is useful for the distinct issue: A project includes multiple resource groups and incorrectly uses a resource-group-level deployment for subscription-scoped resources. The relevant technical rationale or evidence for that issue is: Subscription and resource-group deployment operations differ; the scope must match the resources declared by the template. Here the reported issue is: An ML team hard-codes a storage account name into each copy of a workspace template. Different regions now require manual edits. The relevant response is: Pass environment-specific resource names and locations through declared Bicep parameters. The first result cannot verify this different correction: Parameters keep the template reusable while allowing approved environment differences without modifying core infrastructure logic.

D:

Run Bicep build and deployment validation against the resource type's supported schema. It addresses another case: An engineer gets a Bicep validation error about an unknown property before any Azure resources change. For that case, the distinguishing justification or acceptance check is: Syntax and resource-provider schema validation catch malformed property names before the deployment attempts to create resources. The present case instead states: An ML team hard-codes a storage account name into each copy of a workspace template. Different regions now require manual edits. It calls for Pass environment-specific resource names and locations through declared Bicep parameters. Showing success for the other case would not establish: Parameters keep the template reusable while allowing approved environment differences without modifying core infrastructure logic.

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.

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