Practice Exams:

Microsoft AI-300 Dumps

EXAM: Operationalizing Machine Learning and Generative AI Solutions
Verified By Experts
Premium Bundle
$49.99

AI-300 Premium ETE File


  • Premium File 213 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft AI-300 Practice Test 30

Question 290

A biomedical researcher creates a new GenAIOps workspace and must demonstrate its deployed models and project resources remain separate from an unrelated clinical team. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Verify: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.
  2. Implement: Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production. Verify: Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource.
  3. Implement: Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. Verify: Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource.
  4. Implement: Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. Verify: Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.

Answer & Explanations

Correct answer: C

A.

This action/test pair addresses “Use managed identities and RBAC for Foundry application connections”. Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. The case instead calls for: Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations.

B.

The test would be relevant: Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource. But the offered implementation—Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production.—addresses “Separate Foundry project deployments and quota by environment and region”. The action needed here is: Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations.

C.

The question is set in this situation: A biomedical researcher creates a new GenAIOps workspace and must demonstrate its deployed models and project resources remain separate from an unrelated clinical team. Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. Confirm it through this test: Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource. Foundry project-scoped application assets and deployment connections need a valid parent resource and governed identity; creating a generic Azure storage account does not produce a model-operation environment.

D.

The action is applicable: Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. But its proposed test—Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.—addresses “Separate Foundry project deployments and quota by environment and region”. This requirement is confirmed instead by: Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource.

Question 291

A law firm operates a Foundry-based assistant that retrieves approved case excerpts and needs scoped access without hard-coded model service keys in source control. Which Azure AI operations action best addresses this requirement?

  1. Define approved fallback model deployments with compatible inputs, data handling and quality gates, and trigger fallback only on supported operational errors rather than masking every low-quality answer.
  2. Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.
  3. Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations.
  4. Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production.

Answer & Explanations

Correct answer: B

A.

Define approved fallback model deployments with compatible inputs, data handling and quality gates, and trigger fallback only on supported operational errors rather than masking every low-quality answer. This addresses “Design resilient model endpoint fallback without silently changing data policy”, where the governing principle is: A backup model may differ in region, cost, privacy conditions and output schema; blind fallback to an arbitrary public endpoint can violate residency or application validation assumptions. The stated case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

B.

Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service. Verify the result with this test: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

C.

Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. This addresses “Create governed Microsoft Foundry resources and separate development projects”, where the governing principle is: Foundry project-scoped application assets and deployment connections need a valid parent resource and governed identity; creating a generic Azure storage account does not produce a model-operation environment. The stated case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

D.

Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production. This addresses “Separate Foundry project deployments and quota by environment and region”, where the governing principle is: A model listed in a catalog is not necessarily available with the same version, deployment type or token capacity in every region, so staging success alone cannot prove production quota readiness. The stated case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

Question 292

A law firm operates a Foundry-based assistant that retrieves approved case excerpts and needs scoped access without hard-coded model service keys in source control. The engineer proposes the following change: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Which mechanism explains why it works?

  1. A backup model may differ in region, cost, privacy conditions and output schema; blind fallback to an arbitrary public endpoint can violate residency or application validation assumptions.
  2. Foundry project-scoped application assets and deployment connections need a valid parent resource and governed identity; creating a generic Azure storage account does not produce a model-operation environment.
  3. A model listed in a catalog is not necessarily available with the same version, deployment type or token capacity in every region, so staging success alone cannot prove production quota readiness.
  4. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

Answer & Explanations

Correct answer: D

A.

A backup model may differ in region, cost, privacy conditions and output schema; blind fallback to an arbitrary public endpoint can violate residency or application validation assumptions. That explains “Design resilient model endpoint fallback without silently changing data policy”, not the mechanism behind the described change. The relevant principle is: An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

B.

Foundry project-scoped application assets and deployment connections need a valid parent resource and governed identity; creating a generic Azure storage account does not produce a model-operation environment. That explains “Create governed Microsoft Foundry resources and separate development projects”, not the mechanism behind the described change. The relevant principle is: An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

C.

A model listed in a catalog is not necessarily available with the same version, deployment type or token capacity in every region, so staging success alone cannot prove production quota readiness. That explains “Separate Foundry project deployments and quota by environment and region”, not the mechanism behind the described change. The relevant principle is: An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

D.

An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service. The corresponding implementation is: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

Question 293

A law firm operates a Foundry-based assistant that retrieves approved case excerpts and needs scoped access without hard-coded model service keys in source control. After implementing this change—Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.—which test most directly validates its intended outcome?

  1. Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource.
  2. Simulate a primary deployment rate limit in staging, verify only a preapproved compatible endpoint handles the request and confirm the returned format and audit trail remain valid.
  3. Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.
  4. Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

Answer & Explanations

Correct answer: D

A.

Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource. That would help test “Create governed Microsoft Foundry resources and separate development projects”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

B.

Simulate a primary deployment rate limit in staging, verify only a preapproved compatible endpoint handles the request and confirm the returned format and audit trail remain valid. That would help test “Design resilient model endpoint fallback without silently changing data policy”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

C.

Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput. That would help test “Separate Foundry project deployments and quota by environment and region”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

D.

Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. This check is decisive because an Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

Question 294

A law firm operates a Foundry-based assistant that retrieves approved case excerpts and needs scoped access without hard-coded model service keys in source control. Which proposed shortcut most directly risks overprivileged generative AI workloads and credential leakage through application artifacts and should therefore be rejected?

  1. Create a public blob container named Foundry and assume it automatically supplies project management, model deployment rights and identity-scoped AI connections.
  2. Assume a foundation model in a development region automatically provides unrestricted throughput and identical capability in every production Azure region.
  3. Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.
  4. When a Foundry deployment is throttled, send sensitive prompts to any public consumer chat API without checking location, model compatibility or approved data usage.

Answer & Explanations

Correct answer: C

A.

Create a public blob container named Foundry and assume it automatically supplies project management, model deployment rights and identity-scoped AI connections. That shortcut risks unmanaged generative AI deployments after confusing a storage container with a Foundry project. Here the specific shortcut is: Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.

B.

Assume a foundation model in a development region automatically provides unrestricted throughput and identical capability in every production Azure region. That shortcut risks deployment failures and throttled service due to unverified regional model availability and quota. Here the specific shortcut is: Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.

C.

Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models. The foreseeable failure is overprivileged generative AI workloads and credential leakage through application artifacts. The safer response is: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

D.

When a Foundry deployment is throttled, send sensitive prompts to any public consumer chat API without checking location, model compatibility or approved data usage. That shortcut risks confidential data exposure and corrupted responses during model service failover. Here the specific shortcut is: Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.

Question 295

A law firm operates a Foundry-based assistant that retrieves approved case excerpts and needs scoped access without hard-coded model service keys in source control. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Verify: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.
  2. Implement: Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production. Verify: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.
  3. Implement: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Verify: Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.
  4. Implement: Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. Verify: Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource.

Answer & Explanations

Correct answer: A

A.

Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Confirm it through this test: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

B.

The test would be relevant: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. But the offered implementation—Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production.—addresses “Separate Foundry project deployments and quota by environment and region”. The action needed here is: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

C.

The action is applicable: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. But its proposed test—Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.—addresses “Separate Foundry project deployments and quota by environment and region”. This requirement is confirmed instead by: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

D.

This action/test pair addresses “Create governed Microsoft Foundry resources and separate development projects”. Create an appropriate Microsoft Foundry resource and project environment in the supported region, assign project owners, configure linked model access and separate nonproduction from production configurations. Open a test project with a nonadmin identity, resolve its approved model deployment and confirm unauthorized project members cannot modify a separate production resource. The case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

Question 296

A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Which Azure AI operations action best addresses this requirement?

  1. Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production.
  2. Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.
  3. Compare candidate Foundry foundation models using representative prompts, grounded domain tasks, output safety measures, latency and expected token cost before choosing a production deployment.
  4. Implement parameterized Bicep and Azure CLI provisioning for supported Foundry resources, project configuration, identities, required model capacity and connections, with separate environment settings and approval gates.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production. This addresses “Separate Foundry project deployments and quota by environment and region”, where the governing principle is: A model listed in a catalog is not necessarily available with the same version, deployment type or token capacity in every region, so staging success alone cannot prove production quota readiness. The stated case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

B.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service. Verify the result with this test: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

C.

Compare candidate Foundry foundation models using representative prompts, grounded domain tasks, output safety measures, latency and expected token cost before choosing a production deployment. This addresses “Select foundation models using task-specific quality latency safety and cost evaluation”, where the governing principle is: Model size or catalog popularity alone does not determine fit; task success and operational limits depend on input context, evaluation criteria and workload-specific performance. The stated case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

D.

Implement parameterized Bicep and Azure CLI provisioning for supported Foundry resources, project configuration, identities, required model capacity and connections, with separate environment settings and approval gates. This addresses “Automate Foundry deployment foundations using Bicep and Azure CLI”, where the governing principle is: Infrastructure templates record the required foundations reproducibly while manually creating model deployments in a portal can produce version and access drift between test and production. The stated case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

Question 297

A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. The engineer proposes the following change: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Which mechanism explains why it works?

  1. Model size or catalog popularity alone does not determine fit; task success and operational limits depend on input context, evaluation criteria and workload-specific performance.
  2. A model listed in a catalog is not necessarily available with the same version, deployment type or token capacity in every region, so staging success alone cannot prove production quota readiness.
  3. Infrastructure templates record the required foundations reproducibly while manually creating model deployments in a portal can produce version and access drift between test and production.
  4. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

Answer & Explanations

Correct answer: D

A.

Model size or catalog popularity alone does not determine fit; task success and operational limits depend on input context, evaluation criteria and workload-specific performance. That explains “Select foundation models using task-specific quality latency safety and cost evaluation”, not the mechanism behind the described change. The relevant principle is: An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

B.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. A model listed in a catalog is not necessarily available with the same version, deployment type or token capacity in every region, so staging success alone cannot prove production quota readiness. That explains “Separate Foundry project deployments and quota by environment and region”, not the mechanism behind the described change. The relevant principle is: An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

C.

Infrastructure templates record the required foundations reproducibly while manually creating model deployments in a portal can produce version and access drift between test and production. That explains “Automate Foundry deployment foundations using Bicep and Azure CLI”, not the mechanism behind the described change. The relevant principle is: An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

D.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service. The corresponding implementation is: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

Question 298

A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. After implementing this change—Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.—which test most directly validates its intended outcome?

  1. Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.
  2. Deploy the same reviewed template twice into a disposable environment, compare resource properties and verify the production approval step prevents unreviewed model quota or network changes.
  3. Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.
  4. Run a blind paired evaluation on a fixed representative set, record quality and risk metrics alongside measured p95 latency and token cost and approve the best feasible candidate.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput. That would help test “Separate Foundry project deployments and quota by environment and region”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

B.

Deploy the same reviewed template twice into a disposable environment, compare resource properties and verify the production approval step prevents unreviewed model quota or network changes. That would help test “Automate Foundry deployment foundations using Bicep and Azure CLI”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

C.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. This check is decisive because an Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

D.

Run a blind paired evaluation on a fixed representative set, record quality and risk metrics alongside measured p95 latency and token cost and approve the best feasible candidate. That would help test “Select foundation models using task-specific quality latency safety and cost evaluation”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

Question 299

A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Which proposed shortcut most directly risks overprivileged generative AI workloads and credential leakage through application artifacts and should therefore be rejected?

  1. Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.
  2. Assume a foundation model in a development region automatically provides unrestricted throughput and identical capability in every production Azure region.
  3. Choose the largest and newest advertised foundation model by name and claim it is always the cheapest safest and most accurate option for every workload.
  4. Treat an old screenshot of a Foundry model deployment as an automated production provisioning plan and recreate settings manually for every release.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models. The foreseeable failure is overprivileged generative AI workloads and credential leakage through application artifacts. The safer response is: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

B.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Assume a foundation model in a development region automatically provides unrestricted throughput and identical capability in every production Azure region. That shortcut risks deployment failures and throttled service due to unverified regional model availability and quota. Here the specific shortcut is: Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.

C.

Choose the largest and newest advertised foundation model by name and claim it is always the cheapest safest and most accurate option for every workload. That shortcut risks high serving expense or poor task-specific results after selecting a model without evaluation. Here the specific shortcut is: Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.

D.

Treat an old screenshot of a Foundry model deployment as an automated production provisioning plan and recreate settings manually for every release. That shortcut risks unreproducible generative AI environments and unauthorized capacity changes from drift. Here the specific shortcut is: Paste a global administrator service principal secret into every prompt template and assume the secret is required for the project to call models.

Question 300

A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Verify: Deploy the same reviewed template twice into a disposable environment, compare resource properties and verify the production approval step prevents unreviewed model quota or network changes.
  2. Implement: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Verify: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.
  3. Implement: Implement parameterized Bicep and Azure CLI provisioning for supported Foundry resources, project configuration, identities, required model capacity and connections, with separate environment settings and approval gates. Verify: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.
  4. Implement: Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production. Verify: Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput.

Answer & Explanations

Correct answer: B

A.

The action is applicable: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. But its proposed test—Deploy the same reviewed template twice into a disposable environment, compare resource properties and verify the production approval step prevents unreviewed model quota or network changes.—addresses “Automate Foundry deployment foundations using Bicep and Azure CLI”. This requirement is confirmed instead by: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt.

B.

The question is set in this situation: A university's GenAI evaluation service must call one Foundry deployment but should not gain the power to alter model deployments for all campus research teams. Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services. Confirm it through this test: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. An Azure managed identity receives time-limited resource tokens without embedded reusable application secrets, but those tokens still require data-plane role assignments for the specific service.

C.

The test would be relevant: Run a harmless test application under its deployed identity, verify the model or storage call succeeds and an unrelated resource rejects the same identity's attempt. But the offered implementation—Implement parameterized Bicep and Azure CLI provisioning for supported Foundry resources, project configuration, identities, required model capacity and connections, with separate environment settings and approval gates.—addresses “Automate Foundry deployment foundations using Bicep and Azure CLI”. The action needed here is: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

D.

This action/test pair addresses “Separate Foundry project deployments and quota by environment and region”. Plan supported model region availability, subscription quota, deployment limits and environment-specific ownership before promoting a high-throughput Foundry workload to production. Deploy a small supported model in the target region, check quota and limits and run a pilot using its intended credentials before committing production throughput. The case instead calls for: Assign the supported Azure managed identity and scoped RBAC roles for Foundry projects or deployed application workloads to access only intended model endpoints and backing services.

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