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 18

Question 170

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A Meraki dashboard integration treats HTTP 429 as permanent failure and immediately resubmits hundreds of calls in a tight loop. Which observation would confirm that this exact failure is resolved?

  1. Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.
  2. A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.
  3. Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.
  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

C:

Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm. This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. It checks the technical distinction: HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Applied here, the relevant facts are: A Meraki dashboard integration treats HTTP 429 as permanent failure and immediately resubmits hundreds of calls in a tight loop. 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: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The current case instead depends on: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Confirm that “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. In the current case, the governing reason is: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The direct verification is “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The current case instead depends on: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Confirm that “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

Question 171

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. What is the appropriate response to this network automation condition?

  1. Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.
  2. Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.
  3. Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.
  4. Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations.

Explanation

Correct Answer

D:

Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. This addresses the problem because automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. Confirm success using: The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics.

Incorrect Answers

A:

The offered action targets: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The case facts point instead to: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. Implement “Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations” 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: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The action that directly addresses it is “Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations”.

C:

The proposed action belongs to the mechanism: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Here the stated fault follows a different mechanism: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The corrective choice is “Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations”.

Question 172

At fictional Amberlight Energy, an acceptance review of an AI-assisted code review finds: A conversational assistant intended for route lookup is accidentally granted Terraform apply permissions to all campus workspaces. Which control best prevents this particular failure from recurring?

  1. Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals.
  2. Adopt AI data-classification rules, approved endpoints and automatic prompt redaction checks for developer workflows.
  3. Enforce identity binding, tenant-isolated caches and tool-level audit and RBAC tests for MCP services.
  4. Define permitted AI assistance tiers and required technical approval gates by change risk.

Explanation

Correct Answer

A:

Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals. This prevents the recurrence because the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. A matching immediate correction is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.

Incorrect Answers

B:

The suggested review tracks a different technical risk: aI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure. Here the sustained control must address: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Choose “Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals”.

C:

That safeguard is relevant to: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The current failure instead follows from: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Its prevention measure is “Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals”.

D:

This routine guards against another mechanism: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. The recurring exposure in the current case is: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The matching preventive check is “Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals”.

Question 173

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. Which control best prevents this particular failure from recurring?

  1. Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording.
  2. Implement tool categorization, approval records and run-as identities for every privileged network agent operation.
  3. Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection.
  4. Adopt AI data-classification rules, approved endpoints and automatic prompt redaction checks for developer workflows.

Explanation

Correct Answer

B:

Implement tool categorization, approval records and run-as identities for every privileged network agent operation. This prevents the recurrence because agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. A matching immediate correction is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation.

Incorrect Answers

A:

The suggested review tracks a different technical risk: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. Here the sustained control must address: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Choose “Implement tool categorization, approval records and run-as identities for every privileged network agent operation”.

C:

This routine guards against another mechanism: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The recurring exposure in the current case is: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. The matching preventive check is “Implement tool categorization, approval records and run-as identities for every privileged network agent operation”.

D:

The suggested review tracks a different technical risk: aI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure. Here the sustained control must address: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Choose “Implement tool categorization, approval records and run-as identities for every privileged network agent operation”.

Question 174

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. Which engineering principle explains the described system behavior?

  1. Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination.
  2. Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset.
  3. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  4. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.

Explanation

Correct Answer

A:

Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. Acceptance should show: The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. The reported condition is governed by: The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The two mechanisms should not be conflated.

C:

The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. It does not explain the facts described here, which follow from: The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.

Question 175

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A CI experiment stages a temporary secret-test file but needs to keep it locally while excluding it from the next commit. What mechanism is most directly responsible for these symptoms?

  1. The Git index is the staging area and can be changed independently of the working tree by suitable reset modes.
  2. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  3. Compose networks govern container service reachability, while host port publishing determines external exposure.
  4. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.

Explanation

Correct Answer

A:

The Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. Acceptance should show: The next commit excludes the file, while the local copy remains available for secure handling or deletion. Applied here, the relevant facts are: A CI experiment stages a temporary secret-test file but needs to keep it locally while excluding it from the next commit. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

B:

The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. It does not explain the facts described here, which follow from: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.

D:

This principle describes a separate cause: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The reported condition is governed by: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. The two mechanisms should not be conflated.

Question 176

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A network configuration generator uses cached YAML values while the approved source of truth has changed VLAN ownership. What underlying technical distinction accounts for this failure?

  1. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  2. Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline.
  3. A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures.
  4. YANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure.

Explanation

Correct Answer

A:

A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. Acceptance should show: Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation.

Incorrect Answers

B:

The offered statement is true for this other mechanism: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. It does not explain the facts described here, which follow from: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.

C:

This principle describes a separate cause: The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. The reported condition is governed by: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The two mechanisms should not be conflated.

D:

The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.

Question 177

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. Which observation would confirm that this exact failure is resolved?

  1. Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.
  2. A GET of the specific keyed list entry shows only the authorized VLAN or interface changed, with sibling entries intact.
  3. The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift.
  4. A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target.

Explanation

Correct Answer

D:

A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target. This directly verifies the related correction: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. It checks the technical distinction: Ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. In the current case, the governing reason is: This directly verifies the related correction: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. The direct verification is “A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The current issue is governed by: This directly verifies the related correction: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. Its decisive check is “A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. The current case instead depends on: This directly verifies the related correction: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. Confirm that “A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target”.

Question 178

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A network configuration generator uses cached YAML values while the approved source of truth has changed VLAN ownership. What is the appropriate response to this network automation condition?

  1. Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.
  2. Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.
  3. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  4. Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin.

Explanation

Correct Answer

A:

Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. This addresses the problem because a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. Confirm success using: Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation. Applied here, the relevant facts are: A network configuration generator uses cached YAML values while the approved source of truth has changed VLAN ownership. The question asks what is the appropriate response to this network automation condition.

Incorrect Answers

B:

The proposed action belongs to the mechanism: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. Here the stated fault follows a different mechanism: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The corrective choice is “Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path”.

C:

The offered action targets: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The case facts point instead to: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. Implement “Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path” to address that specific condition.

D:

This alternative is a response to another technical cause: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The reported case instead depends on: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The action that directly addresses it is “Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path”.

Question 179

At fictional Amberlight Energy, an acceptance review of an AI-assisted code review finds: A generated Ansible task uses a nonexistent Cisco module parameter yet passes a superficial prose review by the engineer. What technical evidence should be required before closing this change?

  1. Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices.
  2. Authorization tests show route queries succeed but unapproved configuration changes are rejected before reaching Cisco APIs.
  3. Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results.
  4. The validation crosschecks observed interface or VLAN state before accepting a proposed operation and flags missing telemetry as uncertainty.

Explanation

Correct Answer

A:

Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices. This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. It checks the technical distinction: Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.

Incorrect Answers

B:

That test belongs to another control with this basis: This directly verifies the related correction: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. In the current case, the governing reason is: This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. The direct verification is “Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices”.

C:

This observation would test a different technical dependency: 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 current issue is governed by: This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. Its decisive check is “Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. The current case instead depends on: This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. Confirm that “Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices”.

Question 180

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: An API integration disables certificate verification after a controller rotates its TLS certificate, exposing management traffic to interception. Which control best prevents this particular failure from recurring?

  1. Maintain tested parser/device version matrices and fail clearly when collection contracts change.
  2. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.
  3. Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases.
  4. Monitor certificate expirations and trust-chain changes with automated predeployment verification.

Explanation

Correct Answer

D:

Monitor certificate expirations and trust-chain changes with automated predeployment verification. This prevents the recurrence because tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. A matching immediate correction is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. Applied here, the relevant facts are: An API integration disables certificate verification after a controller rotates its TLS certificate, exposing management traffic to interception. The question asks which control best prevents this particular failure from recurring.

Incorrect Answers

A:

That test belongs to another control with this basis: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. In the current case, the governing reason is: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The direct verification is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.

B:

This observation would test a different technical dependency: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The current issue is governed by: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Its decisive check is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.

C:

The alternative verifies a different condition: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. The current case instead depends on: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Confirm that “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.