McAfee Secure

Cisco 350-901 Bundle

Exam Code: 350-901

Exam Name Designing, Deploying, and Managing Network Automation Systems

Certification Provider: Cisco

Corresponding Certification: DevNet Professional

Cisco 350-901 Bundle $25.00

100% Cisco 350-901 Guaranteed Success With Testking Training Materials

Get Real 350-901 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-901 Questions & Answers

    604 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-901 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-901 Video Course

    350-901 Training Course

    106 Video Lectures

    350-901 Video Course is developed by Cisco Professionals to help you pass the 350-901 exam.

    Description

    This course will improve your knowledge and skills required to pass Designing, Deploying, and Managing Network Automation Systems exam.

Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    604 Questions

    $124.99
  • 350-901 Video Course

    Training Course

    106 Video Lectures

    $39.99

Cisco 350-901 Practice Test 45

Question 440

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. Which result most directly verifies that the proposed correction worked?

  1. A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.
  2. A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms.
  3. A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.
  4. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.

Explanation

Correct Answer

D:

Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data. This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. It checks the technical distinction: Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. Here the stated fault follows a different mechanism: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The corrective choice is “Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data”.

B:

The offered action targets: This directly verifies the related correction: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. The case facts point instead to: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. Implement “Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data” to address that specific condition.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The reported case instead depends on: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The action that directly addresses it is “Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data”.

Question 441

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A network parsing pipeline runs under a clean container and raises ModuleNotFoundError for a local-only tool used by the scripts. What is the appropriate response to this network automation condition?

  1. Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.
  2. Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline.
  3. Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration.
  4. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.

Explanation

Correct Answer

A:

Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. This addresses the problem because cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Confirm success using: A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state.

Incorrect Answers

B:

This alternative is a response to another technical cause: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The reported case instead depends on: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The action that directly addresses it is “Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment”.

C:

That action addresses another technical layer: YANG and JSON schema validation check data types, allowable ranges and required keyed-list fields; this is distinct from successfully completing a later deployment or workflow step. It does not correct this specific failure, which is explained by: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The case-matched action is “Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment”.

D:

The offered action targets: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The case facts point instead to: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Implement “Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment” to address that specific condition.

Question 442

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: An engineer must port one approved RESTCONF bug fix to an older support branch without incorporating unrelated commits. Which result most directly verifies that the proposed correction worked?

  1. The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests.
  2. The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state.
  3. The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results.
  4. The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches.

Explanation

Correct Answer

A:

The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests. This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. It checks the technical distinction: Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Applied here, the relevant facts are: An engineer must port one approved RESTCONF bug fix to an older support branch without incorporating unrelated commits. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

B:

The proposed action belongs to the mechanism: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Here the stated fault follows a different mechanism: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The corrective choice is “The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests”.

C:

The offered action targets: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. The case facts point instead to: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. Implement “The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests” to address that specific condition.

D:

This alternative is a response to another technical cause: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The reported case instead depends on: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The action that directly addresses it is “The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests”.

Question 443

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A vendor-specific CLI string is applied unchanged to several network operating systems and fails on unsupported command syntax. What ongoing engineering assurance should follow the successful fix?

  1. Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate.
  2. Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family.
  3. Record per-platform model support and gate model-specific deploy steps on device capability checks.
  4. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.

Explanation

Correct Answer

B:

Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family. This prevents the recurrence because cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. A matching immediate correction is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. Applied here, the relevant facts are: A vendor-specific CLI string is applied unchanged to several network operating systems and fails on unsupported command syntax. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

The suggested review tracks a different technical risk: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. Here the sustained control must address: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Choose “Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family”.

C:

This routine guards against another mechanism: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The recurring exposure in the current case is: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The matching preventive check is “Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family”.

D:

The suggested review tracks a different technical risk: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Here the sustained control must address: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Choose “Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family”.

Question 444

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A GitLab CI build succeeds on a developer laptop but fails in the runner because the automation package was never declared as a dependency. What ongoing engineering assurance should follow the successful fix?

  1. Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes.
  2. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  3. Review topology fidelity against production design and include adverse link or neighbor failures in CML tests.
  4. Run clean-environment dependency installation tests and enforce dependency lockfile review.

Explanation

Correct Answer

D:

Run clean-environment dependency installation tests and enforce dependency lockfile review. This prevents the recurrence because cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. A matching immediate correction is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. Applied here, the relevant facts are: A GitLab CI build succeeds on a developer laptop but fails in the runner because the automation package was never declared as a dependency. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

That safeguard is relevant to: git revert records an inverse patch in new history rather than moving shared branch pointers backward. The current failure instead follows from: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Its prevention measure is “Run clean-environment dependency installation tests and enforce dependency lockfile review”.

B:

This routine guards against another mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The recurring exposure in the current case is: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The matching preventive check is “Run clean-environment dependency installation tests and enforce dependency lockfile review”.

C:

The suggested review tracks a different technical risk: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Here the sustained control must address: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Choose “Run clean-environment dependency installation tests and enforce dependency lockfile review”.

Question 445

At fictional Amberlight Energy, an acceptance review of an AI-assisted code review finds: A generated Ansible task uses a nonexistent Cisco module parameter yet passes a superficial prose review by the engineer. What should the team add to its network automation operating process?

  1. Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence.
  2. Expire cached network context, confirm target scope and revalidate resources before agent actions.
  3. Tag provenance and document freshness, test poisoned retrieval cases, and gate device changes on deterministic validation.
  4. Use egress firewall allowlists, response sanitization, credential isolation and canary tests against tool-output injection.

Explanation

Correct Answer

A:

Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence. This prevents the recurrence because generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. A matching immediate correction is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Incorrect Answers

B:

The proposed action belongs to the mechanism: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. Here the stated fault follows a different mechanism: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The corrective choice is “Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence”.

C:

The offered action targets: retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. The case facts point instead to: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Implement “Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence” to address that specific condition.

D:

This alternative is a response to another technical cause: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. The reported case instead depends on: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The action that directly addresses it is “Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence”.

Question 446

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. Which explanation best matches the actual broken dependency?

  1. AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations.
  2. High aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes.
  3. Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.
  4. Model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action.

Explanation

Correct Answer

C:

Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. Acceptance should show: Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data. Applied here, the relevant facts are: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. The question asks which explanation best matches the actual broken dependency.

Incorrect Answers

A:

The proposed action belongs to the mechanism: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. Here the stated fault follows a different mechanism: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The corrective choice is “Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call”.

B:

The offered action targets: The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. The case facts point instead to: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. Implement “Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call” to address that specific condition.

D:

The proposed action belongs to the mechanism: The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. Here the stated fault follows a different mechanism: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The corrective choice is “Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call”.

Question 447

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An AI network diagnostic tool receives a malicious API description instructing it to send secrets to an external webhook. Which observation would confirm that this exact failure is resolved?

  1. A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.
  2. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.
  3. A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials.
  4. Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.

Explanation

Correct Answer

C:

A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials. This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. It checks the technical distinction: Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. Applied here, the relevant facts are: An AI network diagnostic tool receives a malicious API description instructing it to send secrets to an external webhook. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. In the current case, the governing reason is: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. The direct verification is “A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The current issue is governed by: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. Its decisive check is “A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. In the current case, the governing reason is: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. The direct verification is “A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials”.

Question 448

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A Python FastMCP service exposes a broad execute-command tool to an agent that only needs interface status snapshots. What technical evidence should be required before closing this change?

  1. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  2. Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.
  3. A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations.
  4. Authorization tests show route queries succeed but unapproved configuration changes are rejected before reaching Cisco APIs.

Explanation

Correct Answer

C:

A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations. This directly verifies the related correction: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. It checks the technical distinction: An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. Applied here, the relevant facts are: A Python FastMCP service exposes a broad execute-command tool to an agent that only needs interface status snapshots. The question asks what technical evidence should be required before closing this change.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The current issue is governed by: This directly verifies the related correction: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. Its decisive check is “A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. The current case instead depends on: This directly verifies the related correction: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. Confirm that “A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. The current issue is governed by: This directly verifies the related correction: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. Its decisive check is “A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations”.

Question 449

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: An Ansible network workflow deploys source directly from a mutable branch without a versioned build artifact. What should the engineer change first to resolve this specific issue?

  1. Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.
  2. Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed.
  3. Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment.
  4. Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.

Explanation

Correct Answer

C:

Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. This addresses the problem because a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. Confirm success using: The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit. Applied here, the relevant facts are: An Ansible network workflow deploys source directly from a mutable branch without a versioned build artifact. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

The proposed action belongs to the mechanism: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Here the stated fault follows a different mechanism: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The corrective choice is “Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment”.

B:

The offered action targets: compose networks govern container service reachability, while host port publishing determines external exposure. The case facts point instead to: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. Implement “Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment” to address that specific condition.

D:

The proposed action belongs to the mechanism: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. Here the stated fault follows a different mechanism: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The corrective choice is “Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment”.

Question 450

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: An AI chat assistant translates free-text "fix routing" into unbounded commands rather than requiring a precise change proposal. What acceptance check would prove the intended behavior was restored?

  1. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  2. The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved.
  3. Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.
  4. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.

Explanation

Correct Answer

B:

The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved. This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. It checks the technical distinction: LLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. Applied here, the relevant facts are: An AI chat assistant translates free-text "fix routing" into unbounded commands rather than requiring a precise change proposal. The question asks what acceptance check would prove the intended behavior was restored.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. In the current case, the governing reason is: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The direct verification is “The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. The current case instead depends on: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. Confirm that “The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. In the current case, the governing reason is: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The direct verification is “The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved”.