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 41

Question 400

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A network engineer switches branches with uncommitted interface edits, then mistakenly tests a mixture of two feature versions. What technical evidence should be required before closing this change?

  1. The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit.
  2. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  3. The working tree reports the intended revision and no uncommitted cross-branch edits before test execution.
  4. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.

Explanation

Correct Answer

C:

The working tree reports the intended revision and no uncommitted cross-branch edits before test execution. This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. It checks the technical distinction: Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. The current issue is governed by: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Its decisive check is “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.

B:

The alternative verifies a different condition: 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 current case instead depends on: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Confirm that “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.

D:

This observation would test a different technical dependency: 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 current issue is governed by: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Its decisive check is “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.

Question 401

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A Terraform automation run misses out-of-band interface edits and applies a broad change from stale assumptions. Which implementation action best meets the observed technical requirement?

  1. Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations.
  2. Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation.
  3. Refresh managed state and review a generated Terraform plan before applying only the intended network changes.
  4. Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary.

Explanation

Correct Answer

C:

Refresh managed state and review a generated Terraform plan before applying only the intended network changes. This addresses the problem because terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Confirm success using: The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift. Applied here, the relevant facts are: A Terraform automation run misses out-of-band interface edits and applies a broad change from stale assumptions. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

A:

infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. That explanation applies to a different technical failure. Here the controlling principle is: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply.

B:

The offered statement is true for this other mechanism: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. It does not explain the facts described here, which follow from: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply.

D:

ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. That explanation applies to a different technical failure. Here the controlling principle is: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply.

Question 402

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: An engineer places region-specific ACL variables in a global inventory file, and the wrong region receives the restricted network policy. What should the engineer change first to resolve this specific issue?

  1. Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.
  2. Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group.
  3. Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path.
  4. Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.

Explanation

Correct Answer

B:

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. Applied here, the relevant facts are: An engineer places region-specific ACL variables in a global inventory file, and the wrong region receives the restricted network policy. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

The offered action targets: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The case facts point instead to: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. Implement “Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group” to address that specific condition.

C:

The proposed action belongs to the mechanism: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. 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:

The offered action targets: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The case facts point instead to: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. Implement “Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group” to address that specific condition.

Question 403

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A Terraform workflow change was merged and released, but its logic must be undone without rewriting published branch history. What underlying technical distinction accounts for this failure?

  1. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
  2. Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch.
  3. A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures.
  4. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.

Explanation

Correct Answer

A:

Git revert records an inverse patch in new history rather than moving shared branch pointers backward. The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Acceptance should show: The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state.

Incorrect Answers

B:

The corresponding repair is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. It does not explain the facts described here, which follow from: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests.

D:

This principle describes a separate cause: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The reported condition is governed by: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The two mechanisms should not be conflated.

Question 404

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: A user switches sites in the same session, but the assistant carries the earlier site's tenant scope into a new API query. Which result most directly verifies that the proposed correction worked?

  1. Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results.
  2. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.
  3. A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.
  4. The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved.

Explanation

Correct Answer

C:

A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers. This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. It checks the technical distinction: Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. Here the stated fault follows a different mechanism: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. The corrective choice is “A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers”.

B:

The offered action targets: 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 case facts point instead to: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. Implement “A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers” to address that specific condition.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. Here the stated fault follows a different mechanism: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. The corrective choice is “A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers”.

Question 405

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: A previously hand-managed device interface is added to an infrastructure repository without matching its live resource identity in state. Which engineering principle explains the described system behavior?

  1. HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type.
  2. Ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions.
  3. Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address.
  4. A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects.

Explanation

Correct Answer

C:

Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. Acceptance should show: The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. It does not explain the facts described here, which follow from: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.

B:

This principle describes a separate cause: The corresponding repair is: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. The reported condition is governed by: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The two mechanisms should not be conflated.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. It does not explain the facts described here, which follow from: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.

Question 406

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A Terraform linting job suddenly fails after a GitLab base image pulls an incompatible provider and Python library combination. Which observation would confirm that this exact failure is resolved?

  1. A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.
  2. The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence.
  3. The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds.
  4. Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation.

Explanation

Correct Answer

C:

The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds. This directly verifies the related correction: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. It checks the technical distinction: Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. Applied here, the relevant facts are: A Terraform linting job suddenly fails after a GitLab base image pulls an incompatible provider and Python library combination. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The current issue is governed by: This directly verifies the related correction: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. Its decisive check is “The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The current case instead depends on: This directly verifies the related correction: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. Confirm that “The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The current issue is governed by: This directly verifies the related correction: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. Its decisive check is “The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds”.

Question 407

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A team builds a custom Python service for straightforward ticket-triggered device tagging already supported by an approved audited low-code connector. Which sustainable preventive control most directly avoids a recurrence?

  1. Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow.
  2. Require representative failure-path tests before approving a low-code production integration.
  3. Maintain separate configuration-compliance and operational-state assertions for every network change workflow.
  4. Require validated backups, staged batches and executable rollback procedures in approved network playbooks.

Explanation

Correct Answer

B:

Require representative failure-path tests before approving a low-code production integration. This prevents the recurrence because low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. A matching immediate correction is: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. Applied here, the relevant facts are: A team builds a custom Python service for straightforward ticket-triggered device tagging already supported by an approved audited low-code connector. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

A:

The suggested review tracks a different technical risk: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Here the sustained control must address: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Choose “Require representative failure-path tests before approving a low-code production integration”.

C:

This routine guards against another mechanism: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The recurring exposure in the current case is: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. The matching preventive check is “Require representative failure-path tests before approving a low-code production integration”.

D:

The suggested review tracks a different technical risk: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Here the sustained control must address: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Choose “Require representative failure-path tests before approving a low-code production integration”.

Question 408

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: A network provisioning system assumes every device family exposes identical Terraform provider resources and cannot fulfill a mixed-platform request. What mechanism is most directly responsible for these symptoms?

  1. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.
  2. Terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply.
  3. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  4. API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes.

Explanation

Correct Answer

C:

Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. Acceptance should show: Separate platform acceptance tests reach equivalent approved network intent on each supported operating system without invalid commands.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. It does not explain the facts described here, which follow from: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model.

B:

This principle describes a separate cause: The corresponding repair is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. The reported condition is governed by: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The two mechanisms should not be conflated.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. It does not explain the facts described here, which follow from: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model.

Question 409

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An AI assistant generates a long network automation library, but the team cannot determine licensing obligations for externally reproduced snippets. Which engineering principle explains the described system behavior?

  1. The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors.
  2. AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations.
  3. An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions.
  4. Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.

Explanation

Correct Answer

B:

AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. Acceptance should show: The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved. Applied here, the relevant facts are: An AI assistant generates a long network automation library, but the team cannot determine licensing obligations for externally reproduced snippets. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. The reported condition is governed by: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. It does not explain the facts described here, which follow from: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.

D:

This principle describes a separate cause: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. The reported condition is governed by: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The two mechanisms should not be conflated.

Question 410

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A change board chooses an unreviewed custom deploy script even though the production topology demands staged approval and automated rollback. Which observation would confirm that this exact failure is resolved?

  1. The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.
  2. The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift.
  3. The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics.
  4. The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value.

Explanation

Correct Answer

C:

The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics. This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. It checks the technical distinction: Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. The current case instead depends on: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Confirm that “The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. In the current case, the governing reason is: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. The direct verification is “The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The current case instead depends on: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Confirm that “The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics”.