Microsoft AI-300 Dumps
Microsoft AI-300 Practice Test 10
Question 90
A university wants the research infrastructure team to reproduce a Machine Learning workspace after a region migration without relying on screenshots of past portal settings. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The test would be relevant: Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation. But the offered implementation—Configure supported Azure Machine Learning private endpoint and network access settings along with dependent storage and vault connectivity, private DNS and outbound egress requirements before disabling public access.—addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”. The action needed here is: Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers.
The action is applicable: Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers. But its proposed test—From an approved compute subnet run a small training job that reads its private datastore, resolves required service names and writes logs while public network access follows the approved restriction.—addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”. This requirement is confirmed instead by: Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation.
The question is set in this situation: A university wants the research infrastructure team to reproduce a Machine Learning workspace after a region migration without relying on screenshots of past portal settings. Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers. Confirm it through this test: Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation. Infrastructure-as-code reconciles desired resource declarations across deployments, while copying portal clicks by hand leaves undocumented differences in networking, identity and workspace dependencies.
This action/test pair addresses “Use GitHub Actions workload identity federation for secure ML provisioning”. Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. The case instead calls for: Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers.
Question 91
A medical software provider wants GitHub Actions to deploy Azure ML compute and workspace configuration without storing any reusable production password inside its source repository. Which Azure AI operations action best addresses this requirement?
Answer & Explanations
Correct answer: D
Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers. This addresses “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”, where the governing principle is: Infrastructure-as-code reconciles desired resource declarations across deployments, while copying portal clicks by hand leaves undocumented differences in networking, identity and workspace dependencies. The stated case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Grant selected researchers workspace permissions to submit and read experiments while assigning separate scoped storage access to managed job identities that actually need the underlying training data. This addresses “Assign Azure Machine Learning workspace and data access roles separately”, where the governing principle is: Azure resource management permissions and data-plane authorization govern distinct operations, so being able to view a workspace does not automatically imply permission to read its private storage containers. The stated case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Configure supported Azure Machine Learning private endpoint and network access settings along with dependent storage and vault connectivity, private DNS and outbound egress requirements before disabling public access. This addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”, where the governing principle is: Creating a workspace private endpoint alone does not guarantee the compute nodes can resolve or reach every linked artifact service needed for experiment submission and output storage. The stated case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment. Verify the result with this test: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
Question 92
A medical software provider wants GitHub Actions to deploy Azure ML compute and workspace configuration without storing any reusable production password inside its source repository. The engineer proposes the following change: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
Creating a workspace private endpoint alone does not guarantee the compute nodes can resolve or reach every linked artifact service needed for experiment submission and output storage. That explains “Validate private network and DNS dependencies of restricted Azure ML workspaces”, not the mechanism behind the described change. The relevant principle is: OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment. The corresponding implementation is: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Infrastructure-as-code reconciles desired resource declarations across deployments, while copying portal clicks by hand leaves undocumented differences in networking, identity and workspace dependencies. That explains “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”, not the mechanism behind the described change. The relevant principle is: OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
Azure resource management permissions and data-plane authorization govern distinct operations, so being able to view a workspace does not automatically imply permission to read its private storage containers. That explains “Assign Azure Machine Learning workspace and data access roles separately”, not the mechanism behind the described change. The relevant principle is: OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
Question 93
A medical software provider wants GitHub Actions to deploy Azure ML compute and workspace configuration without storing any reusable production password inside its source repository. After implementing this change—Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
From an approved compute subnet run a small training job that reads its private datastore, resolves required service names and writes logs while public network access follows the approved restriction. That would help test “Validate private network and DNS dependencies of restricted Azure ML workspaces”, not the outcome required in this scenario. The relevant acceptance check is: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation. That would help test “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”, not the outcome required in this scenario. The relevant acceptance check is: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
Sign in as a research contributor to submit an allowed test job, verify the job's identity reads its approved dataset and a second reader-only user cannot browse restricted blobs. That would help test “Assign Azure Machine Learning workspace and data access roles separately”, not the outcome required in this scenario. The relevant acceptance check is: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. This check is decisive because openID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
Question 94
A medical software provider wants GitHub Actions to deploy Azure ML compute and workspace configuration without storing any reusable production password inside its source repository. Which proposed shortcut most directly risks unauthorized machine learning infrastructure deployments after long-lived pipeline credentials are exposed and should therefore be rejected?
Answer & Explanations
Correct answer: B
Grant every notebook user subscription Owner because their jobs need to access one dataset stored in a restricted storage account. That shortcut risks excessive Azure privileges with unresolved training data authorization errors. Here the specific shortcut is: Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe.
Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe. The foreseeable failure is unauthorized machine learning infrastructure deployments after long-lived pipeline credentials are exposed. The safer response is: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Disable public access to every Azure ML dependency before adding private DNS and network routes, then assume jobs will still discover all endpoints automatically. That shortcut risks training jobs failing to fetch data or persist outputs after incomplete private networking. Here the specific shortcut is: Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe.
Run an unguarded script that destroys and recreates the workspace and training artifact storage on every deployment to keep the code short. That shortcut risks loss of registered models and unnecessary outages during repeated infrastructure updates. Here the specific shortcut is: Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe.
Question 95
A medical software provider wants GitHub Actions to deploy Azure ML compute and workspace configuration without storing any reusable production password inside its source repository. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The test would be relevant: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. But the offered implementation—Configure supported Azure Machine Learning private endpoint and network access settings along with dependent storage and vault connectivity, private DNS and outbound egress requirements before disabling public access.—addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”. The action needed here is: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
This action/test pair addresses “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”. Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers. Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation. The case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. Confirm it through this test: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
The action is applicable: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. But its proposed test—From an approved compute subnet run a small training job that reads its private datastore, resolves required service names and writes logs while public network access follows the approved restriction.—addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”. This requirement is confirmed instead by: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
Question 96
A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Which Azure AI operations action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment. Verify the result with this test: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers. This addresses “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”, where the governing principle is: Infrastructure-as-code reconciles desired resource declarations across deployments, while copying portal clicks by hand leaves undocumented differences in networking, identity and workspace dependencies. The stated case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Provision the Azure Machine Learning workspace in the approved region with its required storage, Key Vault, monitoring dependencies and project-specific resource ownership, then verify workspace provisioning completes. This addresses “Create an Azure Machine Learning workspace with governed dependent resources”, where the governing principle is: The workspace is the management boundary for jobs and registered ML assets while supporting Azure services hold artifacts, credentials and telemetry; a bare resource-group label does not create working ML dependencies. The stated case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Configure supported Azure Machine Learning private endpoint and network access settings along with dependent storage and vault connectivity, private DNS and outbound egress requirements before disabling public access. This addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”, where the governing principle is: Creating a workspace private endpoint alone does not guarantee the compute nodes can resolve or reach every linked artifact service needed for experiment submission and output storage. The stated case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
Question 97
A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. The engineer proposes the following change: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
The workspace is the management boundary for jobs and registered ML assets while supporting Azure services hold artifacts, credentials and telemetry; a bare resource-group label does not create working ML dependencies. That explains “Create an Azure Machine Learning workspace with governed dependent resources”, not the mechanism behind the described change. The relevant principle is: OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment. The corresponding implementation is: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Infrastructure-as-code reconciles desired resource declarations across deployments, while copying portal clicks by hand leaves undocumented differences in networking, identity and workspace dependencies. That explains “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”, not the mechanism behind the described change. The relevant principle is: OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Creating a workspace private endpoint alone does not guarantee the compute nodes can resolve or reach every linked artifact service needed for experiment submission and output storage. That explains “Validate private network and DNS dependencies of restricted Azure ML workspaces”, not the mechanism behind the described change. The relevant principle is: OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
Question 98
A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. After implementing this change—Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. From an approved compute subnet run a small training job that reads its private datastore, resolves required service names and writes logs while public network access follows the approved restriction. That would help test “Validate private network and DNS dependencies of restricted Azure ML workspaces”, not the outcome required in this scenario. The relevant acceptance check is: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation. That would help test “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”, not the outcome required in this scenario. The relevant acceptance check is: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. This check is decisive because openID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
Create a small experiment in the new workspace, write a disposable data artifact to approved storage and confirm logs and controlled secret references resolve for a nonadministrator test identity. That would help test “Create an Azure Machine Learning workspace with governed dependent resources”, not the outcome required in this scenario. The relevant acceptance check is: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
Question 99
A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Which proposed shortcut most directly risks unauthorized machine learning infrastructure deployments after long-lived pipeline credentials are exposed and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe. The foreseeable failure is unauthorized machine learning infrastructure deployments after long-lived pipeline credentials are exposed. The safer response is: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Run an unguarded script that destroys and recreates the workspace and training artifact storage on every deployment to keep the code short. That shortcut risks loss of registered models and unnecessary outages during repeated infrastructure updates. Here the specific shortcut is: Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Disable public access to every Azure ML dependency before adding private DNS and network routes, then assume jobs will still discover all endpoints automatically. That shortcut risks training jobs failing to fetch data or persist outputs after incomplete private networking. Here the specific shortcut is: Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe.
Create only an empty Azure resource group named MachineLearning and assume the Machine Learning workspace, storage, monitoring and vault services appear implicitly. That shortcut risks unusable workspace operations after a deployment that never provisioned required machine learning resources. Here the specific shortcut is: Commit a service principal client secret into a public workflow YAML file and claim repository branch protection makes leaked permanent credentials safe.
Question 100
A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. But its proposed test—Deploy the template to a disposable resource group twice with unchanged parameters and verify the second execution introduces no unexpected resource replacement or network relaxation.—addresses “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”. This requirement is confirmed instead by: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege.
This action/test pair addresses “Validate private network and DNS dependencies of restricted Azure ML workspaces”. Configure supported Azure Machine Learning private endpoint and network access settings along with dependent storage and vault connectivity, private DNS and outbound egress requirements before disabling public access. From an approved compute subnet run a small training job that reads its private datastore, resolves required service names and writes logs while public network access follows the approved restriction. The case instead calls for: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
The test would be relevant: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. But the offered implementation—Define the approved Machine Learning workspace, network policies and dependent services in parameterized Bicep templates and deploy with Azure CLI using environment-specific configuration and repeatable resource identifiers.—addresses “Provision Azure Machine Learning infrastructure idempotently with Bicep and CLI”. The action needed here is: Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments.
The question is set in this situation: A financial risk-model team separates staging from production deployments and needs to prove that forked pull requests cannot obtain production Azure deployment identities. Configure a trusted GitHub Actions workflow to authenticate to Azure through a narrowly scoped federated identity credential and deploy reviewed ML resources only from authorized repositories or environments. Confirm it through this test: Trigger the permitted deployment workflow in a sandbox, confirm an authorized branch can obtain a token and make intended resource changes, and verify an untrusted pull request lacks equivalent privilege. OpenID Connect federation supplies short-lived tokens conditioned on workflow claims, avoiding a stored long-lived Azure client secret in repository settings and requiring an appropriate Azure role assignment.
Operationalizing Machine Learning and Generative AI Solutions (AI-300) Practice Tests
- Microsoft AI-300 Practice Test 8 - 10 Questions (Last Reviewed 14-Nov-2026)
- Microsoft AI-300 Practice Test 9 - 10 Questions (Last Reviewed 13-Nov-2026)
- Microsoft AI-300 Practice Test 10 - 10 Questions (Last Reviewed 12-Nov-2026)
- Microsoft AI-300 Practice Test 11 - 10 Questions (Last Reviewed 11-Nov-2026)
- Microsoft AI-300 Practice Test 12 - 10 Questions (Last Reviewed 10-Nov-2026)