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 34

Question 330

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A temporary network automation API container is unintentionally published to every host interface with privileged management endpoints exposed. What acceptance check would prove the intended behavior was restored?

  1. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  2. A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates.
  3. Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API.
  4. The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results.

Explanation

Correct Answer

C:

Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API. This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. It checks the technical distinction: Compose networks govern container service reachability, while host port publishing determines external exposure. Applied here, the relevant facts are: A temporary network automation API container is unintentionally published to every host interface with privileged management endpoints exposed. The question asks what acceptance check would prove the intended behavior was restored.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. In the current case, the governing reason is: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The direct verification is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The current issue is governed by: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. Its decisive check is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. In the current case, the governing reason is: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The direct verification is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.

Question 331

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 targeted correction best addresses the network automation failure?

  1. Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.
  2. Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors.
  3. Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state.
  4. Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.

Explanation

Correct Answer

C:

Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. This addresses the problem because ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. Confirm success using: A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target. 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 which targeted correction best addresses the network automation failure.

Incorrect Answers

A:

This alternative is a response to another technical cause: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. 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 “Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state”.

B:

The proposed action belongs to the mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Here the stated fault follows a different mechanism: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The corrective choice is “Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state”.

D:

This alternative is a response to another technical cause: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. 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 “Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state”.

Question 332

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A GitLab job is marked failed after a network policy unit test, but the operator reruns deployment without inspecting the failing assertion. What should the engineer change first to resolve this specific issue?

  1. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  2. Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result.
  3. Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline.
  4. Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.

Explanation

Correct Answer

A:

Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. This addresses the problem because a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Confirm success using: A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates.

Incorrect Answers

B:

The offered action targets: git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. The case facts point instead to: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Implement “Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix” to address that specific condition.

C:

This alternative is a response to another technical cause: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The reported case instead depends on: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The action that directly addresses it is “Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix”.

D:

The proposed action belongs to the mechanism: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Here the stated fault follows a different mechanism: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The corrective choice is “Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix”.

Question 333

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: A service integrator copies model-generated code into a commercial network product without reviewing third-party dependency or attribution terms. What ongoing engineering assurance should follow the successful fix?

  1. Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions.
  2. Expire cached network context, confirm target scope and revalidate resources before agent actions.
  3. Require provenance review, software composition analysis and approved dependencies for generated network automation components.
  4. Use egress firewall allowlists, response sanitization, credential isolation and canary tests against tool-output injection.

Explanation

Correct Answer

C:

Require provenance review, software composition analysis and approved dependencies for generated network automation components. This prevents the recurrence because aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. A matching immediate correction is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.

Incorrect Answers

A:

That safeguard is relevant to: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. The current failure instead follows from: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Its prevention measure is “Require provenance review, software composition analysis and approved dependencies for generated network automation components”.

B:

This routine guards against another mechanism: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The recurring exposure in the current case is: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. The matching preventive check is “Require provenance review, software composition analysis and approved dependencies for generated network automation components”.

D:

That safeguard is relevant to: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. The current failure instead follows from: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Its prevention measure is “Require provenance review, software composition analysis and approved dependencies for generated network automation components”.

Question 334

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: A previously hand-managed device interface is added to an infrastructure repository without matching its live resource identity in state. What technical evidence should be required before closing this change?

  1. The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement.
  2. The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately.
  3. The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.
  4. Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval.

Explanation

Correct Answer

A:

The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement. This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. It checks the technical distinction: Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address.

Incorrect Answers

B:

The alternative verifies a different condition: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. The current case instead depends on: This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. Confirm that “The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. In the current case, the governing reason is: This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The direct verification is “The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. The current issue is governed by: This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. Its decisive check is “The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement”.

Question 335

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A network library hotfix is copied as one commit although it depends on a prior schema refactor absent from the release branch. What acceptance check would prove the intended behavior was restored?

  1. A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.
  2. The target branch builds and tests cleanly with only the required backported changes and no missing dependency references.
  3. The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.
  4. The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.

Explanation

Correct Answer

B:

The target branch builds and tests cleanly with only the required backported changes and no missing dependency references. This directly verifies the related correction: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. It checks the technical distinction: A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The current case instead depends on: This directly verifies the related correction: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. Confirm that “The target branch builds and tests cleanly with only the required backported changes and no missing dependency references”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. The current issue is governed by: This directly verifies the related correction: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. Its decisive check is “The target branch builds and tests cleanly with only the required backported changes and no missing dependency references”.

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: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. Confirm that “The target branch builds and tests cleanly with only the required backported changes and no missing dependency references”.

Question 336

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A teammate wants to compare one previous inventory template but accidentally resets unrelated new workflow files to older versions. Which engineering principle explains the described system behavior?

  1. Git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback.
  2. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  3. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.
  4. Deployment command success is not the same as verified service success; operational checks must follow state changes.

Explanation

Correct Answer

A:

Git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. Acceptance should show: Only the selected file matches the approved historical content, and unrelated working files remain unchanged.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The reported condition is governed by: The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. The two mechanisms should not be conflated.

C:

The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. It does not explain the facts described here, which follow from: The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.

Question 337

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A network library hotfix is copied as one commit although it depends on a prior schema refactor absent from the release branch. 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. A squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry.
  3. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  4. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.

Explanation

Correct Answer

C:

A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. Acceptance should show: The target branch builds and tests cleanly with only the required backported changes and no missing dependency references. Applied here, the relevant facts are: A network library hotfix is copied as one commit although it depends on a prior schema refactor absent from the release branch. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration. The reported condition is governed by: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. The two mechanisms should not be conflated.

B:

The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline.

D:

This principle describes a separate cause: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The reported condition is governed by: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. The two mechanisms should not be conflated.

Question 338

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A developer sends an interface configuration as a flat JSON object without the model container and module prefix expected by the RESTCONF endpoint. What ongoing engineering assurance should follow the successful fix?

  1. Add merge topology review and a dry-run diff approval for complex revert operations.
  2. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  3. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  4. Version lab topology artifacts and run automated readiness verification before configuration tests.

Explanation

Correct Answer

B:

Generate payload fixtures from reviewed YANG modules and test schema validation before any live update. This prevents the recurrence because yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. A matching immediate correction is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. Applied here, the relevant facts are: A developer sends an interface configuration as a flat JSON object without the model container and module prefix expected by the RESTCONF endpoint. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

The suggested review tracks a different technical risk: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. Here the sustained control must address: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Choose “Generate payload fixtures from reviewed YANG modules and test schema validation before any live update”.

C:

This routine guards against another mechanism: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The recurring exposure in the current case is: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The matching preventive check is “Generate payload fixtures from reviewed YANG modules and test schema validation before any live update”.

D:

The suggested review tracks a different technical risk: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Here the sustained control must address: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Choose “Generate payload fixtures from reviewed YANG modules and test schema validation before any live update”.

Question 339

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: A malformed response from one Cisco API causes a network inventory loop to discard successful results from 200 devices. Which explanation best matches the actual broken dependency?

  1. Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes.
  2. Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed.
  3. Terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior.
  4. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.

Explanation

Correct Answer

A:

Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. Acceptance should show: The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails. Applied here, the relevant facts are: A malformed response from one Cisco API causes a network inventory loop to discard successful results from 200 devices. 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: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The reported case instead depends on: The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. The action that directly addresses it is “Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes”.

C:

The proposed action belongs to the mechanism: The corresponding repair is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. Here the stated fault follows a different mechanism: The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. The corrective choice is “Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes”.

D:

The offered action targets: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The case facts point instead to: The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. Implement “Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes” to address that specific condition.

Question 340

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A pipeline declares success when configuration API calls return 200 despite OSPF sessions remaining down on edge routers. What should the engineer change first to resolve this specific issue?

  1. Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.
  2. Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.
  3. Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.
  4. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.

Explanation

Correct Answer

B:

Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. This addresses the problem because deployment command success is not the same as verified service success; operational checks must follow state changes. Confirm success using: The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence.

Incorrect Answers

A:

This alternative is a response to another technical cause: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The reported case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. The action that directly addresses it is “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent”.

C:

The offered action targets: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The case facts point instead to: deployment command success is not the same as verified service success; operational checks must follow state changes. Implement “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent” to address that specific condition.

D:

This alternative is a response to another technical cause: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The reported case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. The action that directly addresses it is “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent”.