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 22

Question 210

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. Which explanation best matches the actual broken dependency?

  1. Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed.
  2. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  3. A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects.
  4. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.

Explanation

Correct Answer

A:

Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Acceptance should show: A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons. Applied here, the relevant facts are: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. The question asks which explanation best matches the actual broken dependency.

Incorrect Answers

B:

This alternative is a response to another technical cause: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The reported case instead depends on: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The action that directly addresses it is “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed”.

C:

The proposed action belongs to the mechanism: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Here the stated fault follows a different mechanism: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The corrective choice is “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed”.

D:

The offered action targets: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The case facts point instead to: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Implement “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed” to address that specific condition.

Question 211

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A network automation release branch merges conflicting inventory files and a hurried commit leaves both incompatible configuration blocks in place. 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. The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches.
  3. GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.
  4. The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation.

Explanation

Correct Answer

B:

The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches. This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. It checks the technical distinction: Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.

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: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. Its decisive check is “The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. In the current case, the governing reason is: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The direct verification is “The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The current issue is governed by: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. Its decisive check is “The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches”.

Question 212

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A bad network automation change has already been pushed to a protected shared branch and teammates have based work on it. What ongoing engineering assurance should follow the successful fix?

  1. Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes.
  2. Add secret scanning and explicit staged-diff review before committing automation changes.
  3. Require merge-request review and parse or lint validation after conflicts in network automation files.
  4. Require postchange telemetry and rollback thresholds for network pipeline release completion.

Explanation

Correct Answer

A:

Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes. This prevents the recurrence because git revert records an inverse patch in new history rather than moving shared branch pointers backward. A matching immediate correction is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests.

Incorrect Answers

B:

That safeguard is relevant to: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The current failure instead follows from: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Its prevention measure is “Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes”.

C:

This routine guards against another mechanism: git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. The recurring exposure in the current case is: git revert records an inverse patch in new history rather than moving shared branch pointers backward. The matching preventive check is “Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes”.

D:

The suggested review tracks a different technical risk: deployment command success is not the same as verified service success; operational checks must follow state changes. Here the sustained control must address: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Choose “Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes”.

Question 213

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A critical ACL validation fix is needed in a stable automation release, but merging the full development branch would introduce unfinished feature code. Which control best prevents this particular failure from recurring?

  1. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  2. Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions.
  3. Review Compose network boundaries and port mappings with security tests before any deployment.
  4. Control source updates through review and schedule automated drift detection after deployment.

Explanation

Correct Answer

B:

Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions. This prevents the recurrence because git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. A matching immediate correction is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.

Incorrect Answers

A:

That safeguard is relevant to: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The current failure instead follows from: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Its prevention measure is “Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions”.

C:

The suggested review tracks a different technical risk: compose networks govern container service reachability, while host port publishing determines external exposure. Here the sustained control must address: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Choose “Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions”.

D:

That safeguard is relevant to: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The current failure instead follows from: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Its prevention measure is “Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions”.

Question 214

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: An ACL tool assumes a partial PUT always preserves all omitted siblings, and postchange data shows attributes were removed. What acceptance check would prove the intended behavior was restored?

  1. An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes.
  2. A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.
  3. The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code.
  4. After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value.

Explanation

Correct Answer

D:

After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value. This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. It checks the technical distinction: HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. The current issue is governed by: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. Its decisive check is “After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value”.

B:

The alternative verifies a different condition: 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. The current case instead depends on: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. Confirm that “After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. In the current case, the governing reason is: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. The direct verification is “After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value”.

Question 215

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: An engineer reads a configuration datastore and concludes an OSPF adjacency is healthy even though the operational state shows no neighbor. Which observation would confirm that this exact failure is resolved?

  1. A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target.
  2. Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.
  3. Plans for two independently configured sites show correct separate VLAN IDs or address values while sharing one reviewed module version.
  4. The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment.

Explanation

Correct Answer

D:

The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment. This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. It checks the technical distinction: YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.

Incorrect Answers

A:

The alternative verifies a different condition: 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 current case instead depends on: This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. Confirm that “The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. In the current case, the governing reason is: This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The direct verification is “The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The current issue is governed by: This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. Its decisive check is “The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment”.

Question 216

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. Which implementation action best meets the observed technical requirement?

  1. Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.
  2. Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.
  3. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  4. Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Explanation

Correct Answer

D:

Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. This addresses the problem because generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Confirm success using: Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices.

Incorrect Answers

A:

The offered action targets: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The case facts point instead to: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Implement “Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval” to address that specific condition.

B:

This alternative is a response to another technical cause: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The reported case instead depends on: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The action that directly addresses it is “Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval”.

C:

The proposed action belongs to the mechanism: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Here the stated fault follows a different mechanism: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The corrective choice is “Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval”.

Question 217

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A Docker Compose stack places its internal database and externally reachable web API on an unrestricted shared network. What should the team add to its network automation operating process?

  1. Add merge topology review and a dry-run diff approval for complex revert operations.
  2. Review Compose network boundaries and port mappings with security tests before any deployment.
  3. Add dependency-impact review and target-branch CI validation to hotfix backport procedures.
  4. Add secret scanning and explicit staged-diff review before committing automation changes.

Explanation

Correct Answer

B:

Review Compose network boundaries and port mappings with security tests before any deployment. This prevents the recurrence because compose networks govern container service reachability, while host port publishing determines external exposure. A matching immediate correction is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed.

Incorrect Answers

A:

This alternative is a response to another technical cause: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The reported case instead depends on: compose networks govern container service reachability, while host port publishing determines external exposure. The action that directly addresses it is “Review Compose network boundaries and port mappings with security tests before any deployment”.

C:

The offered action targets: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The case facts point instead to: compose networks govern container service reachability, while host port publishing determines external exposure. Implement “Review Compose network boundaries and port mappings with security tests before any deployment” to address that specific condition.

D:

This alternative is a response to another technical cause: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The reported case instead depends on: compose networks govern container service reachability, while host port publishing determines external exposure. The action that directly addresses it is “Review Compose network boundaries and port mappings with security tests before any deployment”.

Question 218

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A backup collector hangs during an IOS XE API session because a socket read never completes, delaying all subsequent devices. What should the engineer change first to resolve this specific issue?

  1. Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.
  2. Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.
  3. Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.
  4. Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks.

Explanation

Correct Answer

A:

Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. This addresses the problem because python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Confirm success using: A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others. Applied here, the relevant facts are: A backup collector hangs during an IOS XE API session because a socket read never completes, delaying all subsequent devices. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

B:

The offered action targets: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The case facts point instead to: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Implement “Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely” to address that specific condition.

C:

This alternative is a response to another technical cause: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The reported case instead depends on: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The action that directly addresses it is “Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely”.

D:

The proposed action belongs to the mechanism: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Here the stated fault follows a different mechanism: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The corrective choice is “Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely”.

Question 219

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A build runner silently upgrades its Terraform Cisco provider and begins planning previously unseen resource replacements. What mechanism is most directly responsible for these symptoms?

  1. RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model.
  2. HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type.
  3. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  4. Terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior.

Explanation

Correct Answer

D:

Terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. The corresponding repair is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. Acceptance should show: Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.

Incorrect Answers

A:

The offered statement is true for this other mechanism: 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. It does not explain the facts described here, which follow from: The corresponding repair is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs.

B:

This principle describes a separate cause: The corresponding repair is: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. The reported condition is governed by: The corresponding repair is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. 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: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs.

Question 220

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A network inventory web worker starts before its database is healthy and crashes during initialization. What ongoing engineering assurance should follow the successful fix?

  1. Version lab topology artifacts and run automated readiness verification before configuration tests.
  2. Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes.
  3. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  4. Add secret scanning and explicit staged-diff review before committing automation changes.

Explanation

Correct Answer

C:

Test slow dependency startup and review Compose healthchecks for all network automation support services. This prevents the recurrence because container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. A matching immediate correction is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior.

Incorrect Answers

A:

This routine guards against another mechanism: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The recurring exposure in the current case is: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The matching preventive check is “Test slow dependency startup and review Compose healthchecks for all network automation support services”.

B:

The suggested review tracks a different technical risk: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Here the sustained control must address: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Choose “Test slow dependency startup and review Compose healthchecks for all network automation support services”.

D:

This routine guards against another mechanism: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The recurring exposure in the current case is: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The matching preventive check is “Test slow dependency startup and review Compose healthchecks for all network automation support services”.