Microsoft AI-300 Practice Test 23
Question 220
During a Foundry generative AI quality and observability incident, the following condition occurs: A public-facing GenAI service is cleared for launch after English safety checks, but hostile user requests in supported non-English languages bypass the tested safety evaluator. The fix must preserve evaluation validity and avoid unnecessary user-data collection. What approved correction resolves the failure without modifying unrelated healthy services?
- Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
- Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
- Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
- Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
Explanation
Correct Answer
C:Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content. This targets harmful content probe set excludes multilingual input. Safety evaluation quality depends on representative inputs; English-only coverage cannot establish protection for a multilingual product. Verify the failure through: Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. Validate success with: Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable.
Incorrect Answers
A:Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This could address custom evaluator silently changes its scoring rubric, but it does not solve the specified harmful content probe set excludes multilingual input failure. The matching remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
B:Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This could address debug traces leak secrets and retrieved personal records, but it does not solve the specified harmful content probe set excludes multilingual input failure. The matching remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
D:Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution. This could address content safety evaluation omits prompt injection tests, but it does not solve the specified harmful content probe set excludes multilingual input failure. The matching remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
Question 221
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A high-volume assistant deployment repeatedly hits throughput saturation during business-hour spikes because its provisioned throughput units were selected from average rather than peak token load. The deployment must retain governed identities, endpoint contracts and auditable release history. What approved correction resolves the failure without modifying unrelated healthy services?
- Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.
- Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.
- Build and test a compatible version-pinned serving environment and promote the corrected managed model deployment.
- Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.
Explanation
Correct Answer
B:Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits. This targets provisioned throughput capacity insufficient at peak traffic. Provisioned model throughput constrains admitted tokens and request demand; average daily request counts cannot establish a safe peak capacity allocation. Verify the failure through: Inspect input/output token volume, peak concurrent requests, provisioned throughput allocation, throttling codes and deployment latency percentiles. Validate success with: Peak requests meet approved latency and throttling targets under a representative load test while capacity costs remain documented. This matters here because a high-volume assistant deployment repeatedly hits throughput saturation during business-hour spikes because its….
Incorrect Answers
A:Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review. This could address prompt repository references secret customer examples, but it does not solve the specified provisioned throughput capacity insufficient at peak traffic failure. The matching remediation is: Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.
C:Build and test a compatible version-pinned serving environment and promote the corrected managed model deployment. This could address managed foundation model deployment lacks compatible runtime image, but it does not solve the specified provisioned throughput capacity insufficient at peak traffic failure. The matching remediation is: Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.
D:Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow. This could address prompt contract rollback ignores associated model version, but it does not solve the specified provisioned throughput capacity insufficient at peak traffic failure. The matching remediation is: Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.
Question 222
As an AI operations team checks production agent evaluation evidence, the following condition occurs: A tool-enabled finance agent passes harmful-text screening but executes instructions inside a hostile retrieved web page because its safety suite contains no prompt-injection or tool-misuse cases. The workflow must produce measurable quality, safety and performance evidence. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
- Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records.
- Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence.
- Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
Explanation
Correct Answer
A:Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. This is the most relevant evidence for content safety evaluation omits prompt injection tests. Harmful-content detection alone does not test whether an agent obeys malicious instructions inserted into lower-trust retrieved material. The matching controlled remediation is: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
Incorrect Answers
B:Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records. This would investigate evaluation workflow fails to block degraded agent deployment rather than the documented content safety evaluation omits prompt injection tests issue. The relevant investigation is: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
C:Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. This would investigate harmful content probe set excludes multilingual input rather than the documented content safety evaluation omits prompt injection tests issue. The relevant investigation is: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
D:Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. This would investigate prompt truncation strategy increases generated-token spend rather than the documented content safety evaluation omits prompt injection tests issue. The relevant investigation is: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
Question 223
During a Foundry generative AI quality and observability incident, the following condition occurs: A Foundry agent evaluation job runs against a CSV whose expected_answer column was mapped as user_query, so relevance and groundedness results are invalid. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which production-safe remediation should the engineer apply to this AI workflow?
- Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
- Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.
- Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
- Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.
Explanation
Correct Answer
B:Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run. This targets genai evaluation dataset lacks expected answer column mapping. Generative evaluation depends on the semantic role of each dataset field; a syntactically valid CSV is not necessarily an evaluable response set. Verify the failure through: Inspect evaluation dataset field names, input-output column mapping, evaluator requirements, row samples and failed scoring logs. Validate success with: Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.
Incorrect Answers
A:Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content. This could address harmful content probe set excludes multilingual input, but it does not solve the specified genai evaluation dataset lacks expected answer column mapping failure. The matching remediation is: Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.
C:Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change. This could address generation latency spike blamed on retrieval without breakdown, but it does not solve the specified genai evaluation dataset lacks expected answer column mapping failure. The matching remediation is: Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.
D:Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections. This could address multi-turn agent evaluation uses isolated last message only, but it does not solve the specified genai evaluation dataset lacks expected answer column mapping failure. The matching remediation is: Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.
Question 224
During a retrieval or model-customization performance review, the following condition occurs: A synthetic data workflow for complaint classification injects real support tickets verbatim as prompts and emits generated examples still containing customer names and account details. The change must keep citations, privacy and previously approved behavior intact. What approved correction resolves the failure without modifying unrelated healthy services?
- Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.
- Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
- Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.
- Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.
Explanation
Correct Answer
C:Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content. This targets synthetic training examples copy private customer identifiers. Generated data is not automatically privacy-safe; a model can reproduce sensitive source details when the generation prompt includes them. Verify the failure through: Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals. Validate success with: Synthetic examples cover the intended complaint categories with no detected customer identifiers or unacceptable near copies. This matters here because a synthetic data workflow for complaint classification injects real support tickets verbatim as prompts and emits….
Incorrect Answers
A:Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions. This could address fine-tuned candidate bypasses promotion review after training, but it does not solve the specified synthetic training examples copy private customer identifiers failure. The matching remediation is: Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.
B:Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise. This could address rag similarity threshold filters all relevant evidence, but it does not solve the specified synthetic training examples copy private customer identifiers failure. The matching remediation is: Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.
D:Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This could address fine-tune evaluation lacks drift checks for new customer terminology, but it does not solve the specified synthetic training examples copy private customer identifiers failure. The matching remediation is: Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.
Question 225
While preparing a secure Foundry model or agent release, the following condition occurs: A customer assistant must handle Turkish and Arabic queries, yet the chosen model is approved based only on English benchmark scores and performs poorly in the required languages. The remediation must meet enterprise access and reliability requirements without a broad bypass. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
- Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
- Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
- Deploy the governed Foundry resource and project in a supported compliant region with an available model option.
- Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
Explanation
Correct Answers
A:Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. This is the most relevant evidence for multilingual model selection fails target-language quality. Model selection for a multilingual workload requires evaluation in the actual languages and use cases rather than generic model rankings. The matching controlled remediation is: Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A customer assistant must….
C:Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates. This targets multilingual model selection fails target-language quality. Model selection for a multilingual workload requires evaluation in the actual languages and use cases rather than generic model rankings. Verify the failure through: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. Validate success with: The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A customer assistant must….
Incorrect Answers
B:Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step. This is associated with vision input sent to text-only foundation model, not the essential evidence-and-fix pair for multilingual model selection fails target-language quality. First examine: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. Then correct: Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A customer assistant must….
D:Deploy the governed Foundry resource and project in a supported compliant region with an available model option. This is associated with foundry project created in mismatched resource location, not the essential evidence-and-fix pair for multilingual model selection fails target-language quality. First examine: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. Then correct: Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
E:Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. This is associated with provisioned model update exceeds regional capacity ceiling, not the essential evidence-and-fix pair for multilingual model selection fails target-language quality. First examine: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. Then correct: Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
Question 226
During a retrieval or model-customization performance review, the following condition occurs: A fine-tuned model endpoint cannot be recreated during disaster recovery because the training checkpoint and tokenizer artifacts were deleted after deployment. The change must keep citations, privacy and previously approved behavior intact. Which TWO complementary choices identify the issue and correct it? Select TWO.
- Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy.
- Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together.
- Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior.
- Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
- Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.
Explanation
Correct Answers
A:Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. This is the most relevant evidence for fine-tune production endpoint references deleted training artifact. Custom model lifecycle management includes training lineage and artifact retention; an online endpoint alone is not a durable source of the full fine-tuned model package. The matching controlled remediation is: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
D:Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This targets fine-tune production endpoint references deleted training artifact. Custom model lifecycle management includes training lineage and artifact retention; an online endpoint alone is not a durable source of the full fine-tuned model package. Verify the failure through: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. Validate success with: A disaster-recovery deployment loads the reviewed customized model with matching tokenizer and runtime without repeating unrecoverable training.
Incorrect Answers
B:Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together. This is associated with rag retrieval chunks truncate critical policy exception, not the essential evidence-and-fix pair for fine-tune production endpoint references deleted training artifact. First examine: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. Then correct: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
C:Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. This is associated with supervised fine-tuning dataset includes conflicting assistant behaviors, not the essential evidence-and-fix pair for fine-tune production endpoint references deleted training artifact. First examine: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. Then correct: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
E:Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions. This is associated with fine-tuned candidate bypasses promotion review after training, not the essential evidence-and-fix pair for fine-tune production endpoint references deleted training artifact. First examine: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. Then correct: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
Question 227
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A withdrawn credit-risk model is marked deprecated in a wiki but remains exposed as an active registry version and continues to be selected by automated deployment tools. The operator must safeguard training reproducibility and serving continuity. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
- Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
- Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook.
- Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification.
Explanation
Correct Answer
A:Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This is the most relevant evidence for retired model kept active as discoverable deployment candidate. Model lifecycle management must reflect state in the model registry and deployment references, not just informal documentation. The matching controlled remediation is: Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
Incorrect Answers
B:Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This would investigate run comparison uses incompatible validation populations rather than the documented retired model kept active as discoverable deployment candidate issue. The relevant investigation is: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
C:Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. This would investigate incident rollback artifact was deleted instead of archived rather than the documented retired model kept active as discoverable deployment candidate issue. The relevant investigation is: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
D:Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification. This would investigate online feature retrieval pulls values from after prediction time rather than the documented retired model kept active as discoverable deployment candidate issue. The relevant investigation is: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
Question 228
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A developer changes a production agent prompt directly in the Foundry portal without committing it, so a later regression cannot be tied to the release history. The deployment must retain governed identities, endpoint contracts and auditable release history. Which investigation best verifies the cause before changing production configuration?
- Inspect the prompt template, target JSON schema, model output examples, parser exceptions and current evaluation dataset.
- Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.
- Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes.
- Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
Explanation
Correct Answer
D:Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions. This is the most relevant evidence for prompt hotfix bypasses git review and loses rollback history. Prompt text is production code-like configuration; untracked edits undermine provenance, collaboration and controlled rollback. The matching controlled remediation is: Store reviewed prompt templates and configuration in version control and deploy immutable approved revisions through the release workflow.
Incorrect Answers
A:Inspect the prompt template, target JSON schema, model output examples, parser exceptions and current evaluation dataset. This would investigate prompt omits explicit structured answer schema rather than the documented prompt hotfix bypasses git review and loses rollback history issue. The relevant investigation is: Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
B:Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. This would investigate prompt variant comparison measures fluency not task success rather than the documented prompt hotfix bypasses git review and loses rollback history issue. The relevant investigation is: Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
C:Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes. This would investigate foundry project created in mismatched resource location rather than the documented prompt hotfix bypasses git review and loses rollback history issue. The relevant investigation is: Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
Question 229
As an AI operations team checks production agent evaluation evidence, the following condition occurs: A team upgrades a custom evaluator prompt and compares this month's agent scores to last month's, even though the grading rubric and baseline model changed. The workflow must produce measurable quality, safety and performance evidence. What measured outcome validates the solution while preserving the stated constraints?
- An intentionally degraded candidate fails before production promotion and a passing candidate proceeds with an auditable evaluation receipt.
- Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports.
- Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately.
- An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.
Explanation
Correct Answer
C:Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately. Evaluation metrics are outputs of versioned assessment logic; changing a judge or rubric can change scores without any underlying agent change. a direct corrective action is to version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
Incorrect Answers
A:An intentionally degraded candidate fails before production promotion and a passing candidate proceeds with an auditable evaluation receipt. That addresses a different configuration issue rather than the main requirement. Verify instead: Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately.
B:Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports. That addresses a different configuration issue rather than the main requirement. Verify instead: Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately.
D:An adversarial document cannot cause unapproved transactions while authorized research questions still succeed. That addresses a different configuration issue rather than the main requirement. Verify instead: Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately.
Question 230
During a regulated Azure ML workspace infrastructure review, the following condition occurs: An engineer runs an Azure CLI setup script that creates the model workspace in the CLI's current default subscription rather than the approved production subscription. The team must preserve approved access, model provenance and private network constraints. Which acceptance test shows the AI operations defect is corrected?
- A validation job loads the intended features with the declared schema and rejects incompatible input files.
- Authorized registry models load in the isolated environment and unrelated external destinations remain blocked.
- A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence.
- Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources.
Explanation
Correct Answer
D:Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources. Azure CLI context is stateful; an otherwise valid infrastructure command can target the wrong subscription when scope is not explicitly established. a direct corrective action is to require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.
Incorrect Answers
A:A validation job loads the intended features with the declared schema and rejects incompatible input files. That addresses a different configuration issue rather than the main requirement. Verify instead: Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources.
B:Authorized registry models load in the isolated environment and unrelated external destinations remain blocked. That addresses a different configuration issue rather than the main requirement. Verify instead: Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources.
C:A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence. That addresses a different configuration issue rather than the main requirement. Verify instead: Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources.