Question 100An engineer executes an Azure Machine Learning setup script from a laptop and accidentally creates compute in the wrong subscription. What change-management control best protects this workflow? Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. Review private DNS links, routing, and dependency access whenever workspace network policies change. Restrict workflow permissions, protected environments, and review of infrastructure changes before production deployment. Review datastore references, storage-network restrictions, and execution identity permissions together during change approval. ExplanationCorrect Answer A:Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. This reduces the failure risk because Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. Immediate action: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. Other Answers B:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The preventive control that addresses this condition is: Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. C:OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. The preventive control that addresses this condition is: Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. D:A datastore records a connection to external storage; the job execution identity still requires permission to access the underlying data. The preventive control that addresses this condition is: Validate target subscriptions, parameter files, and changed resources in a pre-deployment review.
Question 101A nightly bootstrap script creates duplicate workspace resources whenever it is rerun after a partial failure. What is the most defensible change for the stated failure? Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. Define Machine Learning workspace resources and their supporting infrastructure as reviewed Bicep templates rather than manual portal clicks. Request supported regional compute quota and select an appropriately sized managed cluster before scheduling a parallel training workload. ExplanationCorrect Answer A:Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. This is appropriate because Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. Verify with: Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. Other Answers B:OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. The required action here is: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. C:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The required action here is: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. D:Compute jobs may remain queued when Azure subscription quota or available regional capacity cannot satisfy their requested VM sizes. The required action here is: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection.
Question 102A nightly bootstrap script creates duplicate workspace resources whenever it is rerun after a partial failure. Why does the recommended approach address the observed issue? Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. An Azure Machine Learning workspace organizes experiments, jobs, models, and attached resources within an Azure subscription and region. ExplanationCorrect Answer B:Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. This explains the relevant intervention: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. Confirm by: Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. Other Answers A:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The more specific mechanism behind the reported outcome is: Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. C:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The more specific mechanism behind the reported outcome is: Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. D:An Azure Machine Learning workspace organizes experiments, jobs, models, and attached resources within an Azure subscription and region. The more specific mechanism behind the reported outcome is: Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments.
Question 103A nightly bootstrap script creates duplicate workspace resources whenever it is rerun after a partial failure. What observable evidence should the engineering team collect? Deploy the template into a disposable environment and compare the resulting resource properties with the approved baseline. Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. From authorized compute, resolve the private service names and complete a small data-access and job-submission test. Confirm that an authorized project identity can open the workspace and submit a small test job in the approved region. ExplanationCorrect Answer B:Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. This directly tests whether the intervention works: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. The technical reason is: Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. Other Answers A:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The applicable evidence for this requirement is: Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. C:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The applicable evidence for this requirement is: Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. D:An Azure Machine Learning workspace organizes experiments, jobs, models, and attached resources within an Azure subscription and region. The applicable evidence for this requirement is: Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration.
Question 104A nightly bootstrap script creates duplicate workspace resources whenever it is rerun after a partial failure. Which documented safeguard helps sustain the improvement? Use pull-request review and environment-specific parameters before applying changes to ML infrastructure templates. Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. Review private DNS links, routing, and dependency access whenever workspace network policies change. Review workspace access groups and environment separation as part of every release and staff change. ExplanationCorrect Answer B:Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. This reduces the failure risk because Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. Immediate action: Use Azure CLI commands in an idempotent provisioning workflow with explicit subscription and resource group selection. Other Answers A:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The preventive control that addresses this condition is: Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. C:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The preventive control that addresses this condition is: Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. D:Separating production and development workspaces reduces accidental changes and enables distinct role assignments, networking, and release controls. The preventive control that addresses this condition is: Validate target subscriptions, parameter files, and changed resources in a pre-deployment review.
Question 105A GitHub Actions workflow uses a shared service-principal password that expired and stops deploying Azure ML infrastructure. Which supported solution best fits this production constraint? Configure supported private networking and required private DNS resolution for the Machine Learning workspace and its data dependencies. Define Machine Learning workspace resources and their supporting infrastructure as reviewed Bicep templates rather than manual portal clicks. Create a versioned Azure Machine Learning environment specifying the required base image and package dependencies for the job. Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. ExplanationCorrect Answer D:Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. This is appropriate because OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. Verify with: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. Other Answers A:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The required action here is: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. B:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The required action here is: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. C:A managed environment captures runtime dependencies so training jobs are less dependent on a developer's local Python installation. The required action here is: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment.
Question 106A GitHub Actions workflow uses a shared service-principal password that expired and stops deploying Azure ML infrastructure. Why is the selected configuration more appropriate here? Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. Reproducible ML artifacts depend on a traceable connection between inputs, code, dependencies, and the producing job. ExplanationCorrect Answer B:OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. This explains the relevant intervention: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. Confirm by: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. Other Answers A:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The more specific mechanism behind the reported outcome is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. C:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The more specific mechanism behind the reported outcome is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. D:Reproducible ML artifacts depend on a traceable connection between inputs, code, dependencies, and the producing job. The more specific mechanism behind the reported outcome is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities.
Question 107A GitHub Actions workflow uses a shared service-principal password that expired and stops deploying Azure ML infrastructure. Which controlled test would best verify the outcome? Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. From authorized compute, resolve the private service names and complete a small data-access and job-submission test. Run the same deployment safely twice in a test subscription and inspect the resulting resource identities and configuration. Run the same small training script on fresh compute with the registered environment version and compare dependency resolution. ExplanationCorrect Answer A:Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. This directly tests whether the intervention works: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. The technical reason is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. Other Answers B:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The applicable evidence for this requirement is: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. C:Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. The applicable evidence for this requirement is: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. D:A managed environment captures runtime dependencies so training jobs are less dependent on a developer's local Python installation. The applicable evidence for this requirement is: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret.
Question 108A GitHub Actions workflow uses a shared service-principal password that expired and stops deploying Azure ML infrastructure. What governance control should accompany this configuration? Validate target subscriptions, parameter files, and changed resources in a pre-deployment review. Restrict workflow permissions, protected environments, and review of infrastructure changes before production deployment. Review private DNS links, routing, and dependency access whenever workspace network policies change. Pin tested package and image versions and scan environment updates before promoting training jobs. ExplanationCorrect Answer B:Restrict workflow permissions, protected environments, and review of infrastructure changes before production deployment. This reduces the failure risk because OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. Immediate action: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. Other Answers A:Explicit scopes and repeatable CLI commands reduce accidental resource creation in the wrong subscription or inconsistent environments. The preventive control that addresses this condition is: Restrict workflow permissions, protected environments, and review of infrastructure changes before production deployment. C:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The preventive control that addresses this condition is: Restrict workflow permissions, protected environments, and review of infrastructure changes before production deployment. D:A managed environment captures runtime dependencies so training jobs are less dependent on a developer's local Python installation. The preventive control that addresses this condition is: Restrict workflow permissions, protected environments, and review of infrastructure changes before production deployment.
Question 109A team wants a repository pipeline to update its staging ML workspace without storing reusable Azure credentials in repository secrets. What should the AI operations engineer do first? Define Machine Learning workspace resources and their supporting infrastructure as reviewed Bicep templates rather than manual portal clicks. Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. Configure supported private networking and required private DNS resolution for the Machine Learning workspace and its data dependencies. Record the trained model's input data version, code commit, environment version, and run identifier alongside its registered artifact. ExplanationCorrect Answer B:Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. This is appropriate because OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. Verify with: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. Other Answers A:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The required action here is: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. C:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The required action here is: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. D:Reproducible ML artifacts depend on a traceable connection between inputs, code, dependencies, and the producing job. The required action here is: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment.
Question 110A team wants a repository pipeline to update its staging ML workspace without storing reusable Azure credentials in repository secrets. Which infrastructure or model-lifecycle behavior is relevant? Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. Reusable components define composable pipeline steps and preserve input and output contracts between jobs. ExplanationCorrect Answer B:OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. This explains the relevant intervention: Configure GitHub Actions to authenticate to Azure with workload identity federation and tightly scoped permissions for infrastructure deployment. Confirm by: Run an authorized pull-request deployment against a test resource group and verify token-based access without a stored client secret. Other Answers A:Private endpoints and network restrictions can keep approved workspace traffic on controlled paths, but DNS and dependency reachability must align. The more specific mechanism behind the reported outcome is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. C:Infrastructure as code produces a repeatable, versioned declaration of Azure resources and configuration differences. The more specific mechanism behind the reported outcome is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities. D:Reusable components define composable pipeline steps and preserve input and output contracts between jobs. The more specific mechanism behind the reported outcome is: OIDC federation avoids storing a long-lived Azure client secret in the CI repository and supports least-privilege deployment identities.