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 40

Question 390

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A one-time diagnostic query is forced through the same slow infrastructure apply workflow used for persistent configuration changes. What should the team add to its network automation operating process?

  1. Record per-platform model support and gate model-specific deploy steps on device capability checks.
  2. Require validated backups, staged batches and executable rollback procedures in approved network playbooks.
  3. Make architecture reviews explicitly compare blast radius, recovery, security and long-term ownership.
  4. Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews.

Explanation

Correct Answer

C:

Make architecture reviews explicitly compare blast radius, recovery, security and long-term ownership. This prevents the recurrence because automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. A matching immediate correction is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Applied here, the relevant facts are: A one-time diagnostic query is forced through the same slow infrastructure apply workflow used for persistent configuration changes. The question asks what should the team add to its network automation operating process.

Incorrect Answers

A:

The offered statement is true for this other mechanism: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. It does not explain the facts described here, which follow from: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.

B:

This principle describes a separate cause: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The reported condition is governed by: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The two mechanisms should not be conflated.

D:

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: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.

Question 391

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A device-automation client repeatedly sends expired OAuth bearer tokens and interprets 401 as permission to retry unchanged forever. What should the engineer change first to resolve this specific issue?

  1. Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses.
  2. Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.
  3. Refresh managed state and review a generated Terraform plan before applying only the intended network changes.
  4. Use inventory capability detection and platform-specific adapters behind a common validated intent model.

Explanation

Correct Answer

A:

Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. This addresses the problem because an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. Confirm success using: The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately. Applied here, the relevant facts are: A device-automation client repeatedly sends expired OAuth bearer tokens and interprets 401 as permission to retry unchanged forever. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

B:

terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. That explanation applies to a different technical failure. Here the controlling principle is: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them.

C:

The offered statement is true for this other mechanism: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. It does not explain the facts described here, which follow from: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them.

D:

This principle describes a separate cause: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The reported condition is governed by: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. The two mechanisms should not be conflated.

Question 392

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A configuration collector overloads a shared Cisco API budget during a morning audit and starves other authorized automation. What underlying technical distinction accounts for this failure?

  1. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.
  2. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  3. Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination.
  4. Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook.

Explanation

Correct Answer

A:

HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Acceptance should show: Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.

Incorrect Answers

B:

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

C:

This principle describes a separate cause: The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The reported condition is governed by: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The two mechanisms should not be conflated.

D:

The corresponding repair is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.

Question 393

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A FastMCP tool hides a Cisco API timeout and fabricates an empty device interface list that the agent treats as a successful snapshot. Which observation would confirm that this exact failure is resolved?

  1. A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials.
  2. Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.
  3. Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results.
  4. Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads.

Explanation

Correct Answer

C:

Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results. 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. It checks the technical distinction: Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. In the current case, the governing reason is: 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. The direct verification is “Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results”.

B:

This observation would test a different technical dependency: 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 issue is governed by: 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. Its decisive check is “Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. In the current case, the governing reason is: 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. The direct verification is “Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results”.

Question 394

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: An overnight VLAN automation rerun blindly adds another copy of a port setting and leaves several switches with divergent repeated statements. What should the team add to its network automation operating process?

  1. Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate.
  2. Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow.
  3. Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout.
  4. Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces.

Explanation

Correct Answer

A:

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. Applied here, the relevant facts are: An overnight VLAN automation rerun blindly adds another copy of a port setting and leaves several switches with divergent repeated statements. The question asks what should the team add to its network automation operating process.

Incorrect Answers

B:

The proposed action belongs to the mechanism: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. 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”.

C:

The offered action targets: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The case facts point instead to: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. Implement “Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate” to address that specific condition.

D:

This alternative is a response to another technical cause: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. 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 395

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A controller-integration container loses its collected audit results whenever the Compose project is recreated. Which observation would confirm that this exact failure is resolved?

  1. Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation.
  2. A schema validator accepts the final YAML or JSON representation and device reads show distinct keyed entries with correct types.
  3. A recreated container reads the expected persistent audit or inventory records from the configured volume.
  4. The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.

Explanation

Correct Answer

C:

A recreated container reads the expected persistent audit or inventory records from the configured volume. This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. It checks the technical distinction: Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Applied here, the relevant facts are: A controller-integration container loses its collected audit results whenever the Compose project is recreated. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

A:

The alternative verifies a different condition: 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 case instead depends on: This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. Confirm that “A recreated container reads the expected persistent audit or inventory records from the configured volume”.

B:

The suggested test “A schema validator accepts the final YAML or JSON representation and device reads show distinct keyed entries with correct types” would establish a separate fact: 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. The evidence requested here must reflect: This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. The direct acceptance check is “A recreated container reads the expected persistent audit or inventory records from the configured volume”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The current case instead depends on: This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. Confirm that “A recreated container reads the expected persistent audit or inventory records from the configured volume”.

Question 396

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A generated network JSON body sends a numeric VLAN ID as an invalid free-form string outside the modeled range. What underlying technical distinction accounts for this failure?

  1. Model-based configuration encoding is constrained by YANG leaf types, ranges and required list keys, not arbitrary YAML structure.
  2. Container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap.
  3. Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes.
  4. Git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback.

Explanation

Correct Answer

A:

Model-based configuration encoding is constrained by YANG leaf types, ranges and required list keys, not arbitrary YAML structure. The corresponding repair is: Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration. Acceptance should show: A schema validator accepts the final YAML or JSON representation and device reads show distinct keyed entries with correct types.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. The reported condition is governed by: The corresponding repair is: Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration. The two mechanisms should not be conflated.

C:

The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. It does not explain the facts described here, which follow from: The corresponding repair is: Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration.

Question 397

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A local branch includes a mistaken last commit with invalid Terraform test output, and no one else has fetched the commit. What mechanism is most directly responsible for these symptoms?

  1. Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.
  2. A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures.
  3. Git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history.
  4. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.

Explanation

Correct Answer

C:

Git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. Acceptance should show: The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The reported condition is governed by: The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The two mechanisms should not be conflated.

B:

The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.

D:

This principle describes a separate cause: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The reported condition is governed by: The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The two mechanisms should not be conflated.

Question 398

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A controller API call is occasionally slow during large inventory updates, but aggregated success logs hide its tail latency. Which result most directly verifies that the proposed correction worked?

  1. The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability.
  2. Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate.
  3. pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.
  4. A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests.

Explanation

Correct Answer

B:

Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate. This directly verifies the related correction: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. It checks the technical distinction: Latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. Applied here, the relevant facts are: A controller API call is occasionally slow during large inventory updates, but aggregated success logs hide its tail latency. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. Here the stated fault follows a different mechanism: This directly verifies the related correction: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. The corrective choice is “Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate”.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. The reported case instead depends on: This directly verifies the related correction: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. The action that directly addresses it is “Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate”.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. Here the stated fault follows a different mechanism: This directly verifies the related correction: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. The corrective choice is “Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate”.

Question 399

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. Which explanation best matches the actual broken dependency?

  1. RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model.
  2. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  3. HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type.
  4. Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook.

Explanation

Correct Answer

D:

Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The corresponding repair is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Acceptance should show: 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 which explanation best matches the actual broken dependency.

Incorrect Answers

A:

The offered action targets: The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The case facts point instead to: The corresponding repair is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Implement “Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook” to address that specific condition.

B:

This alternative is a response to another technical cause: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The reported case instead depends on: The corresponding repair is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The action that directly addresses it is “Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook”.

C:

The proposed action belongs to the 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. Here the stated fault follows a different mechanism: The corresponding repair is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The corrective choice is “Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook”.

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”.