Microsoft AI-300 Practice Test 47 - Prepaway
Practice Exams:

Pass Microsoft AI-300 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

AI-300 Premium ETE File


  • Premium File 213 Questions & Answers. Last Update: Nov 12, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft AI-300 Practice Test 47

Question 460

At a municipal government agency, an AI model release board examines a failure affecting citizen service search and permitting workflow: An online deployment repeatedly restarts because it cannot retrieve the model from the registered source. The proposed fix is to grant the minimum required model-artifact data access to the actual serving identity and redeploy. The proposed response must be supported by the recorded incident and observable evidence. Which observation most decisively establishes the stated root cause?

  1. Deployment audit shows deletion of blue before green reaches validated response and error metrics
  2. Endpoint traffic weights remain blue 100 percent and no direct deployment override is present in the test request
  3. Notebook execution history references a local path and interactive in-memory state outside the committed pipeline
  4. Endpoint diagnostics show access-denied for the storage asset under the deployment's assigned identity

Explanation

Correct Answer

D:

Endpoint diagnostics show access-denied for the storage asset under the deployment's assigned identity. At a municipal government agency, an online deployment repeatedly restarts because it cannot retrieve the model from the registered source. Grant the minimum required model-artifact data access to the actual serving identity and redeploy.

Incorrect Answers

A:

Deployment audit shows deletion of blue before green reaches validated response and error metrics. Endpoint diagnostics show access-denied for the storage asset under the deployment's assigned identity. Grant the minimum required model-artifact data access to the actual serving identity and redeploy.

B:

Endpoint traffic weights remain blue 100 percent and no direct deployment override is present in the test request. Endpoint diagnostics show access-denied for the storage asset under the deployment's assigned identity. Grant the minimum required model-artifact data access to the actual serving identity and redeploy.

C:

Notebook execution history references a local path and interactive in-memory state outside the committed pipeline. Grant the minimum required model-artifact data access to the actual serving identity and redeploy.

Question 461

While operating project planning and safety documentation at a construction project firm, administrators verify this issue: A production assistant switches to a customized model but the release manifest omits the baseline and tuning job identifiers. Investigators found: Deployment metadata lacks reference to training dataset version, tuning parameters and previous validated model. They propose to register the tuned artifact with dataset, model and training lineage and retain a tested baseline rollback endpoint. Which technical principle most directly justifies the plan?

  1. Fine-tuning release governance spans data, base model, training job, evaluation and deployment
  2. Model fine-tuning creates lasting data handling risk and requires dataset governance before training
  3. Customization improvement requires evaluation on truly independent task examples
  4. Fine-tuning artifacts are coupled to supported base model versions and customization frameworks

Explanation

Correct Answer

A:

Fine-tuning release governance spans data, base model, training job, evaluation and deployment. Deployment metadata lacks reference to training dataset version, tuning parameters and previous validated model.

Incorrect Answers

B:

Model fine-tuning creates lasting data handling risk and requires dataset governance before training. Deployment metadata lacks reference to training dataset version, tuning parameters and previous validated model. Fine-tuning release governance spans data, base model, training job, evaluation and deployment.

C:

Customization improvement requires evaluation on truly independent task examples. Deployment metadata lacks reference to training dataset version, tuning parameters and previous validated model. For the documented incident, the condition is: While operating project planning and safety documentation at a construction project firm, administrators verify this issue: A production assistant switches to a customized model but the release manifest omits the baseline and tuning job identifiers.

D:

Fine-tuning artifacts are coupled to supported base model versions and customization frameworks. Fine-tuning release governance spans data, base model, training job, evaluation and deployment.

Question 462

A controlled Azure AI systems audit at a legal services network focuses on case research and contract analysis. It confirms that An operations team deploys a new Foundry project but production policies are inherited from the wrong parent environment. Diagnostic evidence: Project resource hierarchy and deployment audit identify the project attached to a development resource rather than the approved production boundary. Preserve sensitive data, approved model artifacts and least-privilege controls during the test. Which action together with its verification criterion is most appropriate?

  1. Revoke and rotate the leaked credential and use a supported managed identity or secured secret reference — verification: Pipelines deploy with authorized identity and scans find no active credential in repository or build output
  2. Create or migrate the project using the supported production Foundry resource and correct scoped governance and identities — verification: A project audit shows the expected resource linkage, policy boundaries and model permissions without developer access leakage
  3. Set reviewed per-environment Foundry endpoint and resource IDs with protected GitHub environment configuration — verification: A production-tagged release reaches only the approved production project and a sandbox test remains isolated
  4. Apply supported authentication and network access controls and rotate compromised keys with approved client identity changes — verification: Approved managed clients can infer while denied credentials and source networks fail access tests

Explanation

Correct Answer

B:

Create or migrate the project using the supported production Foundry resource and correct scoped governance and identities. A project audit shows the expected resource linkage, policy boundaries and model permissions without developer access leakage. Project resource hierarchy and deployment audit identify the project attached to a development resource rather than the approved production boundary. Foundry project boundaries and their parent resources determine available model connections and policy inheritance.

Incorrect Answers

A:

Revoke and rotate the leaked credential and use a supported managed identity or secured secret reference. Pipelines deploy with authorized identity and scans find no active credential in repository or build output. Create or migrate the project using the supported production Foundry resource and correct scoped governance and identities; A project audit shows the expected resource linkage, policy boundaries and model permissions without developer access leakage.

C:

Set reviewed per-environment Foundry endpoint and resource IDs with protected GitHub environment configuration. A production-tagged release reaches only the approved production project and a sandbox test remains isolated. This pair concerns a different control or outcome, leaving the recorded fault unresolved. Create or migrate the project using the supported production Foundry resource and correct scoped governance and identities; A project audit shows the expected resource linkage, policy boundaries and model permissions without developer access leakage.

D:

Apply supported authentication and network access controls and rotate compromised keys with approved client identity changes. Approved managed clients can infer while denied credentials and source networks fail access tests. Create or migrate the project using the supported production Foundry resource and correct scoped governance and identities; A project audit shows the expected resource linkage, policy boundaries and model permissions without developer access leakage.

Question 463

While operating demand forecasting and customer support automation at a retail operations group, administrators verify this issue: An assistant scales based on calls per second while long prompts saturate context processing capacity. The proposed fix is to capacity-plan using measured token throughput and context distributions, with guardrails on oversized inputs. Do not grant broader model, dataset, or infrastructure permissions than the approved operation requires. Which observation most decisively establishes the stated root cause?

  1. Version comparison evaluation shows significantly worse relevant-language responses despite improved English score
  2. Metrics show provisioned capacity saturation and 429 responses rise as parallel token demand increases
  3. Request logs show rising input and output token lengths even though request count remains stable
  4. Prompt renderer errors identify a missing template variable after an SDK integration change

Explanation

Correct Answer

C:

Request logs show rising input and output token lengths even though request count remains stable. While operating demand forecasting and customer support automation at a retail operations group, an assistant scales based on calls per second while long prompts saturate context processing capacity. Capacity-plan using measured token throughput and context distributions, with guardrails on oversized inputs.

Incorrect Answers

A:

Version comparison evaluation shows significantly worse relevant-language responses despite improved English score. Request logs show rising input and output token lengths even though request count remains stable. Capacity-plan using measured token throughput and context distributions, with guardrails on oversized inputs.

B:

Metrics show provisioned capacity saturation and 429 responses rise as parallel token demand increases. Request logs show rising input and output token lengths even though request count remains stable. Capacity-plan using measured token throughput and context distributions, with guardrails on oversized inputs.

D:

Prompt renderer errors identify a missing template variable after an SDK integration change. Request logs show rising input and output token lengths even though request count remains stable. Capacity-plan using measured token throughput and context distributions, with guardrails on oversized inputs.

Question 464

During an approved Azure AI operations review at a regulated banking division, the engineering team supporting account monitoring and customer service discovers that A new evaluation pipeline works only after an administrator grants its service principal Owner over the subscription. The evidence is: IAM role audit shows that the evaluation task only needs scoped project and dataset rights but has excessive broad privileges. Keep changes within the authorized Azure ML or Foundry project and its data access boundaries. Which corrective action most directly addresses the failure?

  1. Add preflight model quota and region availability checks with a reviewed deployment fallback plan
  2. Isolate evaluation datasets and storage permissions and version promotion of reviewed knowledge sources
  3. Retain the last validated version and gate traffic shifts on schema and agent integration tests
  4. Replace the Owner grant with documented least-privilege Foundry and data roles and retest the workflow

Explanation

Correct Answer

D:

Replace the Owner grant with documented least-privilege Foundry and data roles and retest the workflow. IAM role audit shows that the evaluation task only needs scoped project and dataset rights but has excessive broad privileges. Approved evaluations still run while unrelated resources cannot be modified by the identity.

Incorrect Answers

A:

Add preflight model quota and region availability checks with a reviewed deployment fallback plan. Replace the Owner grant with documented least-privilege Foundry and data roles and retest the workflow.

B:

Isolate evaluation datasets and storage permissions and version promotion of reviewed knowledge sources. IAM role audit shows that the evaluation task only needs scoped project and dataset rights but has excessive broad privileges. Replace the Owner grant with documented least-privilege Foundry and data roles and retest the workflow.

C:

Retain the last validated version and gate traffic shifts on schema and agent integration tests. IAM role audit shows that the evaluation task only needs scoped project and dataset rights but has excessive broad privileges. Replace the Owner grant with documented least-privilege Foundry and data roles and retest the workflow.

Question 465

During an approved Azure AI operations review at an energy provider, the engineering team supporting load forecasting and field maintenance discovers that An agent's relevant document recall collapses after only its query vectorization model is changed. Diagnostic evidence: Pipeline manifests show document vectors built with one embedding version and live queries vectorized with a different semantic space. Keep changes within the authorized Azure ML or Foundry project and its data access boundaries. Which action together with its verification criterion is most appropriate?

  1. Align indexing and query embeddings to the same approved model version and reindex under controlled rollout — verification: A held-out retrieval test recovers expected relevant documents with comparable scores
  2. Reduce overfitting through curated examples and tuning settings and require balanced factual and style evaluations — verification: A tuned candidate passes domain factual, safety and style thresholds rather than style alone
  3. Enforce document-level access filters during search using the requester's verified authorization context — verification: Authorized users retrieve the right evidence and unauthorized queries never return protected documents to the generator
  4. Tune semantic-aware chunk boundaries and overlap with versioned evaluation of supported answer completeness — verification: Queries needing the exception retrieve both rule and exception and meet groundedness acceptance

Explanation

Correct Answer

A:

Align indexing and query embeddings to the same approved model version and reindex under controlled rollout. A held-out retrieval test recovers expected relevant documents with comparable scores. During an approved Azure AI operations review at an energy provider, pipeline manifests show document vectors built with one embedding version and live queries vectorized with a different semantic space. Vector similarity assumes compatible embedding representations for documents and queries.

Incorrect Answers

B:

Reduce overfitting through curated examples and tuning settings and require balanced factual and style evaluations. A tuned candidate passes domain factual, safety and style thresholds rather than style alone. Align indexing and query embeddings to the same approved model version and reindex under controlled rollout; A held-out retrieval test recovers expected relevant documents with comparable scores.

C:

Enforce document-level access filters during search using the requester's verified authorization context. Authorized users retrieve the right evidence and unauthorized queries never return protected documents to the generator. This pair concerns a different control or outcome, leaving the recorded fault unresolved. Align indexing and query embeddings to the same approved model version and reindex under controlled rollout; A held-out retrieval test recovers expected relevant documents with comparable scores.

D:

Tune semantic-aware chunk boundaries and overlap with versioned evaluation of supported answer completeness. Queries needing the exception retrieve both rule and exception and meet groundedness acceptance. Align indexing and query embeddings to the same approved model version and reindex under controlled rollout; A held-out retrieval test recovers expected relevant documents with comparable scores.

Question 466

During an approved Azure AI operations review at a transport authority, the engineering team supporting timetable reliability and passenger assistance discovers that A remotely executed training script records metrics to a personal experiment rather than the governed production workspace. The proposed fix is to set the approved Azure MLflow tracking URI and experiment name in the supported job execution environment. Keep changes within the authorized Azure ML or Foundry project and its data access boundaries. Which observation most decisively establishes the stated root cause?

  1. AutoML job settings show restrictive allowed model algorithms not supported by the problem selection review
  2. MLflow tracking URI and experiment lookup show the process uses the developer's stale configuration
  3. Notebook execution history references a local path and interactive in-memory state outside the committed pipeline
  4. Pipeline graph connects training completion directly to production deployment and lacks an approval metric step

Explanation

Correct Answer

B:

MLflow tracking URI and experiment lookup show the process uses the developer's stale configuration. During an approved Azure AI operations review at a transport authority, a remotely executed training script records metrics to a personal experiment rather than the governed production workspace. Set the approved Azure MLflow tracking URI and experiment name in the supported job execution environment.

Incorrect Answers

A:

AutoML job settings show restrictive allowed model algorithms not supported by the problem selection review. MLflow tracking URI and experiment lookup show the process uses the developer's stale configuration. Set the approved Azure MLflow tracking URI and experiment name in the supported job execution environment.

C:

Notebook execution history references a local path and interactive in-memory state outside the committed pipeline. Set the approved Azure MLflow tracking URI and experiment name in the supported job execution environment.

D:

Pipeline graph connects training completion directly to production deployment and lacks an approval metric step. MLflow tracking URI and experiment lookup show the process uses the developer's stale configuration. Set the approved Azure MLflow tracking URI and experiment name in the supported job execution environment.

Question 467

During an approved Azure AI operations review at an airport support organization, the engineering team supporting flight support and ground service scheduling discovers that An online classifier dashboard reports stable accuracy despite no production label outcomes being collected. The evidence is: Monitoring configuration captures predictions but lacks actual outcome labels needed for an accuracy calculation. Keep changes within the authorized Azure ML or Foundry project and its data access boundaries. Which corrective action most directly addresses the failure?

  1. Add an independent evaluation and governed promotion gate that compares the candidate to the champion model
  2. Unify versioned transformation components or feature retrieval contracts and validate paired serving inputs
  3. Implement a governed delayed-label join and separate operational health from label-based model performance signals
  4. Keep the known-good deployment and version available until the gated rollout and explicit rollback window complete

Explanation

Correct Answer

C:

Implement a governed delayed-label join and separate operational health from label-based model performance signals. Monitoring configuration captures predictions but lacks actual outcome labels needed for an accuracy calculation. Input and prediction distributions cannot alone prove real model predictive accuracy without ground truth.

Incorrect Answers

A:

Add an independent evaluation and governed promotion gate that compares the candidate to the champion model. Monitoring configuration captures predictions but lacks actual outcome labels needed for an accuracy calculation. Implement a governed delayed-label join and separate operational health from label-based model performance signals.

B:

Unify versioned transformation components or feature retrieval contracts and validate paired serving inputs. Monitoring configuration captures predictions but lacks actual outcome labels needed for an accuracy calculation. Implement a governed delayed-label join and separate operational health from label-based model performance signals.

D:

Keep the known-good deployment and version available until the gated rollout and explicit rollback window complete. Implement a governed delayed-label join and separate operational health from label-based model performance signals.

Question 468

At a national insurance service, an AI model release board examines a failure affecting claims decision support and policy analysis: A document ingestion pipeline stops indexing after the embedding deployment is upgraded to a model with different dimensions. The proposed fix is to version the embedding model and use a compatible index schema with a controlled re-embedding and cutover plan. The proposed response must be supported by the recorded incident and observable evidence. Which observation most decisively establishes the stated root cause?

  1. Tracing reveals reranker time dominates the request and most candidates have negligible relevance
  2. Retrieval traces show keyword-specific identifier queries ranking unrelated conceptually similar content above the exact match
  3. Synthetic-data review shows the same false rule duplicated across generated demonstrations with no human validation
  4. Index update errors report vector field dimension mismatch with generated embedding arrays

Explanation

Correct Answer

D:

Index update errors report vector field dimension mismatch with generated embedding arrays. A document ingestion pipeline stops indexing after the embedding deployment is upgraded to a model with different dimensions. Version the embedding model and use a compatible index schema with a controlled re-embedding and cutover plan.

Incorrect Answers

A:

Tracing reveals reranker time dominates the request and most candidates have negligible relevance. Index update errors report vector field dimension mismatch with generated embedding arrays. Version the embedding model and use a compatible index schema with a controlled re-embedding and cutover plan.

B:

Retrieval traces show keyword-specific identifier queries ranking unrelated conceptually similar content above the exact match. Index update errors report vector field dimension mismatch with generated embedding arrays. Version the embedding model and use a compatible index schema with a controlled re-embedding and cutover plan.

C:

Synthetic-data review shows the same false rule duplicated across generated demonstrations with no human validation. Index update errors report vector field dimension mismatch with generated embedding arrays. Version the embedding model and use a compatible index schema with a controlled re-embedding and cutover plan.

Question 469

While operating timetable reliability and passenger assistance at a transport authority, administrators verify this issue: An operator assumes archiving a model version will immediately stop a production endpoint still pinned to that model artifact. Diagnostic evidence: Registry lifecycle state changed but endpoint deployment configuration continues pointing to the same model version. Preserve sensitive data, approved model artifacts and least-privilege controls during the test. Which action together with its verification criterion is most appropriate?

  1. Update the supported endpoint deployment reference through a reviewed rollback while managing registry lifecycle separately — verification: The endpoint serves the approved replacement version and archive metadata reflects the intended policy
  2. Define and verify an approved MLflow signature and example input contract with the registered model — verification: Valid payloads score successfully while invalid feature types are rejected with actionable errors
  3. Package the approved feature retrieval definition and input contract with the model version before registration — verification: A fresh deployment reconstructs feature lookup and passes train-versus-serve feature parity tests
  4. Unify versioned transformation components or feature retrieval contracts and validate paired serving inputs — verification: Canary inference uses the same unit definition as training and regression tests flag future divergence

Explanation

Correct Answer

A:

Update the supported endpoint deployment reference through a reviewed rollback while managing registry lifecycle separately. The endpoint serves the approved replacement version and archive metadata reflects the intended policy. While operating timetable reliability and passenger assistance at a transport authority, registry lifecycle state changed but endpoint deployment configuration continues pointing to the same model version. Model asset lifecycle status and deployment traffic or artifact references are distinct controls.

Incorrect Answers

B:

Define and verify an approved MLflow signature and example input contract with the registered model. While operating timetable reliability and passenger assistance at a transport authority, valid payloads score successfully while invalid feature types are rejected with actionable errors. Update the supported endpoint deployment reference through a reviewed rollback while managing registry lifecycle separately; The endpoint serves the approved replacement version and archive metadata reflects the intended policy.

C:

Package the approved feature retrieval definition and input contract with the model version before registration. A fresh deployment reconstructs feature lookup and passes train-versus-serve feature parity tests. Update the supported endpoint deployment reference through a reviewed rollback while managing registry lifecycle separately; The endpoint serves the approved replacement version and archive metadata reflects the intended policy.

D:

Unify versioned transformation components or feature retrieval contracts and validate paired serving inputs. Canary inference uses the same unit definition as training and regression tests flag future divergence. This pair concerns a different control or outcome, leaving the recorded fault unresolved. Update the supported endpoint deployment reference through a reviewed rollback while managing registry lifecycle separately; The endpoint serves the approved replacement version and archive metadata reflects the intended policy.

Question 470

At a media production company, an AI model release board examines a failure affecting content catalog and creative workflow: An on-call engineer modifies the live prompt in a portal and the source-controlled deployment no longer reproduces its answers. The approved change is to store and deploy prompts from reviewed immutable Git revisions and record prompt version alongside model deployment. Avoid an unrelated subscription-wide identity, networking or model change. Which post-change measurable result best validates success?

  1. Approved requests render the intended prompt and missing fields fail validation before model invocation
  2. A clean release reproduces the approved prompt and an unreviewed portal edit is detected
  3. Approved test prompts preserve expected behavior without personal records in shared source control
  4. Latency and error telemetry remains usable but sampled logs contain no unauthorized customer content

Explanation

Correct Answer

B:

A clean release reproduces the approved prompt and an unreviewed portal edit is detected. At a media production company, an on-call engineer modifies the live prompt in a portal and the source-controlled deployment no longer reproduces its answers. Prompt text is deployable software configuration and should receive source control and change governance.

Incorrect Answers

A:

Approved requests render the intended prompt and missing fields fail validation before model invocation. A clean release reproduces the approved prompt and an unreviewed portal edit is detected.

C:

Approved test prompts preserve expected behavior without personal records in shared source control. An on-call engineer modifies the live prompt in a portal and the source-controlled deployment no longer reproduces its answers. A clean release reproduces the approved prompt and an unreviewed portal edit is detected.

D:

Latency and error telemetry remains usable but sampled logs contain no unauthorized customer content. An on-call engineer modifies the live prompt in a portal and the source-controlled deployment no longer reproduces its answers. A clean release reproduces the approved prompt and an unreviewed portal edit is detected.

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