Microsoft AI-300 Dumps
Microsoft AI-300 Practice Test 39
Question 380
A medical analytics bot must survive a model endpoint outage while keeping structured clinical summaries within its reviewed schema and retention boundaries. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A medical analytics bot must survive a model endpoint outage while keeping structured clinical summaries within its reviewed schema and retention boundaries. 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. Confirm it through this test: 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. 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.
This action/test pair addresses “Provision Foundry token throughput capacity for stable peak inference”. Estimate requests per second, token input-output mix, rate limits and desired service latency, then configure supported provisioned throughput capacity or other appropriate deployment quota for a high-volume model. Run load tests with realistic prompt and output lengths, measure tokens per minute, throttling and p95 latency, then verify the selected quota meets the traffic SLO. The case instead calls for: 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.
The action is applicable: 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. But its proposed test—Send a fixed regression set through current and candidate deployments, inspect quality and latency, switch a small permitted traffic cohort and successfully restore the previous route.—addresses “Pin model versions and use staged rollout for Foundry production endpoints”. This requirement is confirmed instead by: 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.
The test would be relevant: 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. But the offered implementation—Record exact foundation model identifiers and deployment versions, use a controlled candidate deployment or routing layer, and promote after regression tests while retaining a supported prior version for rollback.—addresses “Pin model versions and use staged rollout for Foundry production endpoints”. The action needed here is: 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.
Question 381
A banking chatbot changes customer support instructions weekly and auditors need to know which approved prompt version produced a disputed answer. Which Azure AI operations action best addresses this requirement?
Answer & Explanations
Correct answer: D
Create deliberate prompt variants for the same task, evaluate them on identical representative inputs and rubric-based quality or safety metrics, then select only a statistically and operationally suitable improvement. This addresses “Evaluate prompt variants using a fixed and versioned comparison corpus”, where the governing principle is: Different prompt instructions can trade answer clarity for hallucination risk or token cost, so judging one attractive demonstration response is not reliable evidence of improvement. The stated case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
Store model service authentication and other sensitive connection details in supported secret or managed identity infrastructure, while versioning prompt content and nonsecret deployment references independently in source control. This addresses “Keep secrets and deployment configuration outside versioned prompts”, where the governing principle is: A prompt template is easily logged, evaluated and shared across environments; placing reusable API keys inside it leaks credential material through debugging and source histories. The stated case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
Estimate requests per second, token input-output mix, rate limits and desired service latency, then configure supported provisioned throughput capacity or other appropriate deployment quota for a high-volume model. This addresses “Provision Foundry token throughput capacity for stable peak inference”, where the governing principle is: Model serving capacity is consumed by tokens and request processing rather than just the number of subscribed users, and underprovisioned resources can throttle requests despite healthy application hosts. The stated case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change. Verify the result with this test: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
Question 382
A banking chatbot changes customer support instructions weekly and auditors need to know which approved prompt version produced a disputed answer. The engineer proposes the following change: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
Model serving capacity is consumed by tokens and request processing rather than just the number of subscribed users, and underprovisioned resources can throttle requests despite healthy application hosts. That explains “Provision Foundry token throughput capacity for stable peak inference”, not the mechanism behind the described change. The relevant principle is: Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
Different prompt instructions can trade answer clarity for hallucination risk or token cost, so judging one attractive demonstration response is not reliable evidence of improvement. That explains “Evaluate prompt variants using a fixed and versioned comparison corpus”, not the mechanism behind the described change. The relevant principle is: Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change. The corresponding implementation is: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
A prompt template is easily logged, evaluated and shared across environments; placing reusable API keys inside it leaks credential material through debugging and source histories. That explains “Keep secrets and deployment configuration outside versioned prompts”, not the mechanism behind the described change. The relevant principle is: Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
Question 383
A banking chatbot changes customer support instructions weekly and auditors need to know which approved prompt version produced a disputed answer. After implementing this change—Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version. This check is decisive because prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
Run load tests with realistic prompt and output lengths, measure tokens per minute, throttling and p95 latency, then verify the selected quota meets the traffic SLO. That would help test “Provision Foundry token throughput capacity for stable peak inference”, not the outcome required in this scenario. The relevant acceptance check is: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
Review the Git prompt history and application traces to confirm no secret literal appears, then rotate a disposable credential and verify the app works through its approved identity or vault reference. That would help test “Keep secrets and deployment configuration outside versioned prompts”, not the outcome required in this scenario. The relevant acceptance check is: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
Run paired prompt evaluations over a blinded test set with the same deployed model version, report quality differences and check latency, cost and harmful content before approval. That would help test “Evaluate prompt variants using a fixed and versioned comparison corpus”, not the outcome required in this scenario. The relevant acceptance check is: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
Question 384
A banking chatbot changes customer support instructions weekly and auditors need to know which approved prompt version produced a disputed answer. Which proposed shortcut most directly risks untraceable generative AI regressions after uncontrolled prompt changes and should therefore be rejected?
Answer & Explanations
Correct answer: B
Adopt a new production prompt after one fluent example without comparing it against existing prompts on a shared evaluation dataset. That shortcut risks lower real-world answer quality after a prompt revision chosen from a cherry-picked example. Here the specific shortcut is: Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident.
Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident. The foreseeable failure is untraceable generative AI regressions after uncontrolled prompt changes. The safer response is: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
Buy capacity based solely on a count of application users and claim large-context generations cannot exhaust provisioned token throughput. That shortcut risks rate limiting and latency spikes after misestimating peak model token workloads. Here the specific shortcut is: Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident.
Paste a production model API key into the prompt's instruction block and commit the file so every developer can reproduce its exact environment. That shortcut risks reusable model credentials leaked through prompt-version history and evaluation logs. Here the specific shortcut is: Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident.
Question 385
A banking chatbot changes customer support instructions weekly and auditors need to know which approved prompt version produced a disputed answer. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. But its proposed test—Review the Git prompt history and application traces to confirm no secret literal appears, then rotate a disposable credential and verify the app works through its approved identity or vault reference.—addresses “Keep secrets and deployment configuration outside versioned prompts”. This requirement is confirmed instead by: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
This action/test pair addresses “Evaluate prompt variants using a fixed and versioned comparison corpus”. Create deliberate prompt variants for the same task, evaluate them on identical representative inputs and rubric-based quality or safety metrics, then select only a statistically and operationally suitable improvement. Run paired prompt evaluations over a blinded test set with the same deployed model version, report quality differences and check latency, cost and harmful content before approval. The case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
The test would be relevant: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version. But the offered implementation—Store model service authentication and other sensitive connection details in supported secret or managed identity infrastructure, while versioning prompt content and nonsecret deployment references independently in source control.—addresses “Keep secrets and deployment configuration outside versioned prompts”. The action needed here is: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. Confirm it through this test: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version. Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
Question 386
A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Which Azure AI operations action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change. Verify the result with this test: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Store model service authentication and other sensitive connection details in supported secret or managed identity infrastructure, while versioning prompt content and nonsecret deployment references independently in source control. This addresses “Keep secrets and deployment configuration outside versioned prompts”, where the governing principle is: A prompt template is easily logged, evaluated and shared across environments; placing reusable API keys inside it leaks credential material through debugging and source histories. The stated case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
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: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Create deliberate prompt variants for the same task, evaluate them on identical representative inputs and rubric-based quality or safety metrics, then select only a statistically and operationally suitable improvement. This addresses “Evaluate prompt variants using a fixed and versioned comparison corpus”, where the governing principle is: Different prompt instructions can trade answer clarity for hallucination risk or token cost, so judging one attractive demonstration response is not reliable evidence of improvement. The stated case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
Question 387
A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. The engineer proposes the following change: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. Which mechanism explains why it works?
Answer & Explanations
Correct answer: 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: Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. A prompt template is easily logged, evaluated and shared across environments; placing reusable API keys inside it leaks credential material through debugging and source histories. That explains “Keep secrets and deployment configuration outside versioned prompts”, not the mechanism behind the described change. The relevant principle is: Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change. The corresponding implementation is: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Different prompt instructions can trade answer clarity for hallucination risk or token cost, so judging one attractive demonstration response is not reliable evidence of improvement. That explains “Evaluate prompt variants using a fixed and versioned comparison corpus”, not the mechanism behind the described change. The relevant principle is: Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
Question 388
A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. After implementing this change—Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: 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: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version. This check is decisive because prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Run paired prompt evaluations over a blinded test set with the same deployed model version, report quality differences and check latency, cost and harmful content before approval. That would help test “Evaluate prompt variants using a fixed and versioned comparison corpus”, not the outcome required in this scenario. The relevant acceptance check is: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Review the Git prompt history and application traces to confirm no secret literal appears, then rotate a disposable credential and verify the app works through its approved identity or vault reference. That would help test “Keep secrets and deployment configuration outside versioned prompts”, not the outcome required in this scenario. The relevant acceptance check is: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
Question 389
A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Which proposed shortcut most directly risks untraceable generative AI regressions after uncontrolled prompt changes and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident. The foreseeable failure is untraceable generative AI regressions after uncontrolled prompt changes. The safer response is: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Adopt a new production prompt after one fluent example without comparing it against existing prompts on a shared evaluation dataset. That shortcut risks lower real-world answer quality after a prompt revision chosen from a cherry-picked example. Here the specific shortcut is: Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Paste a production model API key into the prompt's instruction block and commit the file so every developer can reproduce its exact environment. That shortcut risks reusable model credentials leaked through prompt-version history and evaluation logs. Here the specific shortcut is: Edit the system prompt in production by hand and expect the team to reconstruct its prior wording from the model's chat history during an incident.
Question 390
A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. Confirm it through this test: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version. Prompt text and variables are part of an AI application's behavior, so untracked instruction changes can alter safety and answer quality without any model binary change.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. This action/test pair addresses “Evaluate prompt variants using a fixed and versioned comparison corpus”. Create deliberate prompt variants for the same task, evaluate them on identical representative inputs and rubric-based quality or safety metrics, then select only a statistically and operationally suitable improvement. Run paired prompt evaluations over a blinded test set with the same deployed model version, report quality differences and check latency, cost and harmful content before approval. The case instead calls for: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. The test would be relevant: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version. But the offered implementation—Store model service authentication and other sensitive connection details in supported secret or managed identity infrastructure, while versioning prompt content and nonsecret deployment references independently in source control.—addresses “Keep secrets and deployment configuration outside versioned prompts”. The action needed here is: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI.
The question is set in this situation: A university library assistant is migrating prompt development to Git and wants an easy way to compare new instructions with a tested previous release. The action is applicable: Commit prompt templates, parameter names, model deployment references and evaluation dataset identifiers to a reviewed Git repository, assigning immutable release identifiers rather than editing only in a live chat UI. But its proposed test—Review the Git prompt history and application traces to confirm no secret literal appears, then rotate a disposable credential and verify the app works through its approved identity or vault reference.—addresses “Keep secrets and deployment configuration outside versioned prompts”. This requirement is confirmed instead by: Restore a previous tagged prompt release in staging, rerun its evaluation fixtures and confirm production traces identify the exact active prompt version.
Operationalizing Machine Learning and Generative AI Solutions (AI-300) Practice Tests
- Microsoft AI-300 Practice Test 37 - 10 Questions (Last Reviewed 16-Oct-2026)
- Microsoft AI-300 Practice Test 38 - 10 Questions (Last Reviewed 15-Oct-2026)
- Microsoft AI-300 Practice Test 39 - 10 Questions (Last Reviewed 14-Oct-2026)
- Microsoft AI-300 Practice Test 40 - 10 Questions (Last Reviewed 13-Oct-2026)
- Microsoft AI-300 Practice Test 41 - 10 Questions (Last Reviewed 12-Oct-2026)