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 5

Question 40

At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: A multi-tenant MCP endpoint reuses a cached privileged token between separate customer sessions, exposing one site's inventory to another. Which targeted correction best addresses the network automation failure?

  1. Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.
  2. Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.
  3. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  4. Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Explanation

Correct Answer

A:

Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. This addresses the problem because an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Confirm success using: Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited.

Incorrect Answers

B:

The proposed action belongs to the mechanism: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Here the stated fault follows a different mechanism: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The corrective choice is “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context”.

C:

The offered action targets: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The case facts point instead to: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Implement “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context” to address that specific condition.

D:

This alternative is a response to another technical cause: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The reported case instead depends on: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The action that directly addresses it is “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context”.

Question 41

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: An engineer adds every file to the index, including a generated device backup that must not be included in a Git commit. Which result most directly verifies that the proposed correction worked?

  1. The revert removes only the intended merge effect and network automation tests pass against the protected mainline.
  2. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  3. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  4. The next commit excludes the file, while the local copy remains available for secure handling or deletion.

Explanation

Correct Answer

D:

The next commit excludes the file, while the local copy remains available for secure handling or deletion. This directly verifies the related correction: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. It checks the technical distinction: The Git index is the staging area and can be changed independently of the working tree by suitable reset modes.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. Here the stated fault follows a different mechanism: This directly verifies the related correction: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. The corrective choice is “The next commit excludes the file, while the local copy remains available for secure handling or deletion”.

B:

The offered action targets: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The case facts point instead to: This directly verifies the related correction: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. Implement “The next commit excludes the file, while the local copy remains available for secure handling or deletion” to address that specific condition.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The reported case instead depends on: This directly verifies the related correction: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. The action that directly addresses it is “The next commit excludes the file, while the local copy remains available for secure handling or deletion”.

Question 42

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. Which implementation action best meets the observed technical requirement?

  1. Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group.
  2. Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.
  3. Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.
  4. Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses.

Explanation

Correct Answer

C:

Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. This addresses the problem because rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Confirm success using: The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value.

Incorrect Answers

A:

The offered action targets: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The case facts point instead to: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Implement “Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths” to address that specific condition.

B:

This alternative is a response to another technical cause: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The reported case instead depends on: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The action that directly addresses it is “Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths”.

D:

The offered action targets: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. The case facts point instead to: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Implement “Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths” to address that specific condition.

Question 43

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: An Ansible network job uses a raw shell command to append the same interface description on every run, producing duplicate configuration lines after retries. What should the team add to its network automation operating process?

  1. Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews.
  2. Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client.
  3. Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate.
  4. Record per-platform model support and gate model-specific deploy steps on device capability checks.

Explanation

Correct Answer

C:

Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate. This prevents the recurrence because ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. A matching immediate correction is: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state.

Incorrect Answers

A:

This alternative is a response to another technical cause: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. The reported case instead depends on: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The action that directly addresses it is “Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate”.

B:

The proposed action belongs to the mechanism: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Here the stated fault follows a different mechanism: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The corrective choice is “Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate”.

D:

This alternative is a response to another technical cause: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The reported case instead depends on: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The action that directly addresses it is “Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate”.

Question 44

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A conversational network assistant is permitted to run a harmless ping but then automatically chains into an unapproved ACL modification. What underlying technical distinction accounts for this failure?

  1. An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions.
  2. Model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action.
  3. Agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated.
  4. Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.

Explanation

Correct Answer

C:

Agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. Acceptance should show: A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms.

Incorrect Answers

A:

The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation.

B:

The offered statement is true for this other 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. It does not explain the facts described here, which follow from: The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation.

D:

The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation.

Question 45

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A Meraki inventory collector reads only the first page of network devices and silently reports dozens of branches missing. What should the team add to its network automation operating process?

  1. Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run.
  2. Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout.
  3. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  4. Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity.

Explanation

Correct Answer

A:

Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run. This prevents the recurrence because many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. A matching immediate correction is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors.

Incorrect Answers

B:

This alternative is a response to another technical cause: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The reported case instead depends on: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The action that directly addresses it is “Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run”.

C:

The proposed action belongs to the mechanism: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. Here the stated fault follows a different mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The corrective choice is “Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run”.

D:

The offered action targets: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The case facts point instead to: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Implement “Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run” to address that specific condition.

Question 46

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A support operator attempts to inspect a historical release while untracked temporary config overlays contaminate the working directory. Which targeted correction best addresses the network automation failure?

  1. Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.
  2. Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.
  3. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.
  4. Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.

Explanation

Correct Answer

C:

Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. This addresses the problem because git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Confirm success using: The working tree reports the intended revision and no uncommitted cross-branch edits before test execution.

Incorrect Answers

A:

This alternative is a response to another technical cause: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The reported case instead depends on: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The action that directly addresses it is “Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree”.

B:

The proposed action belongs to the mechanism: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Here the stated fault follows a different mechanism: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The corrective choice is “Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree”.

D:

This alternative is a response to another technical cause: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The reported case instead depends on: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The action that directly addresses it is “Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree”.

Question 47

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: Two automation jobs modify the same Cisco network resource inventory from separate local Terraform state files, each unaware of the other's last apply. What should the engineer change first to resolve this specific issue?

  1. Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors.
  2. Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.
  3. Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.
  4. Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses.

Explanation

Correct Answer

C:

Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. This addresses the problem because terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Confirm success using: The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment.

Incorrect Answers

A:

The proposed action belongs to the mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Here the stated fault follows a different mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corrective choice is “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state”.

B:

The offered action targets: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The case facts point instead to: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Implement “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state” to address that specific condition.

D:

The proposed action belongs to the mechanism: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. Here the stated fault follows a different mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corrective choice is “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state”.

Question 48

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A GitLab network release uses an overly privileged runner that applies Terraform changes to unauthorized production workspaces. Which targeted correction best addresses the network automation failure?

  1. Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.
  2. Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.
  3. Create a reviewed Git revert commit for the offending change and run the full network automation release tests.
  4. Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.

Explanation

Correct Answer

D:

Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. This addresses the problem because a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Confirm success using: GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.

Incorrect Answers

A:

The offered action targets: deployment command success is not the same as verified service success; operational checks must follow state changes. The case facts point instead to: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Implement “Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout” to address that specific condition.

B:

This alternative is a response to another technical cause: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The reported case instead depends on: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The action that directly addresses it is “Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout”.

C:

The proposed action belongs to the mechanism: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Here the stated fault follows a different mechanism: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The corrective choice is “Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout”.

Question 49

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A playbook selects the entire production inventory even though a new OSPF policy is approved only for one distribution switch group. What is the appropriate response to this network automation condition?

  1. Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.
  2. Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.
  3. Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group.
  4. Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models.

Explanation

Correct Answer

C:

Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. This addresses the problem because ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. Confirm success using: The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy.

Incorrect Answers

A:

This alternative is a response to another technical cause: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The reported case instead depends on: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The action that directly addresses it is “Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group”.

B:

The proposed action belongs to the mechanism: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Here the stated fault follows a different mechanism: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The corrective choice is “Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group”.

D:

This alternative is a response to another technical cause: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The reported case instead depends on: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The action that directly addresses it is “Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group”.

Question 50

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A Python network maintenance loop calls requests.get without a timeout and blocks indefinitely when a switch management plane stops responding. Which result most directly verifies that the proposed correction worked?

  1. A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others.
  2. The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment.
  3. The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment.
  4. The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy.

Explanation

Correct Answer

A:

A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others. This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. It checks the technical distinction: Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts.

Incorrect Answers

B:

The offered action targets: This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The case facts point instead to: This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. Implement “A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others” to address that specific condition.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The reported case instead depends on: This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The action that directly addresses it is “A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others”.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Here the stated fault follows a different mechanism: This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The corrective choice is “A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others”.