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 14

Question 130

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A network automation feature branch contains many intermediate repair commits that obscure the single approved change being deployed. What should the engineer change first to resolve this specific issue?

  1. Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.
  2. Define service dependencies with appropriate health checks and resilient application startup or retry behavior.
  3. Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.
  4. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.

Explanation

Correct Answer

D:

Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. This addresses the problem because a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Confirm success using: The protected target branch contains one reviewed release commit whose diff matches the approved feature changes. Applied here, the relevant facts are: A network automation feature branch contains many intermediate repair commits that obscure the single approved change being deployed. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

This alternative is a response to another technical cause: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The reported case instead depends on: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The action that directly addresses it is “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content”.

B:

The proposed action belongs to the mechanism: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Here the stated fault follows a different mechanism: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The corrective choice is “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content”.

C:

The offered action targets: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The case facts point instead to: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Implement “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content” to address that specific condition.

Question 131

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: A network assistant relies on a week-old device inventory from chat history and recommends changing a retired switch. 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. Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary.
  3. Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values.
  4. Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.

Explanation

Correct Answer

D:

Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. This addresses the problem because conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. Confirm success using: A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.

Incorrect Answers

A:

The proposed action belongs to the mechanism: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. Here the stated fault follows a different mechanism: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The corrective choice is “Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls”.

B:

The offered action targets: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The case facts point instead to: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. Implement “Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls” to address that specific condition.

C:

This alternative is a response to another technical cause: tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The reported case instead depends on: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The action that directly addresses it is “Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls”.

Question 132

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: During a fabric-wide link flap, a subscriber's ingestion queue overflows while dashboards continue displaying incomplete metrics as if current. What underlying technical distinction accounts for this failure?

  1. Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions.
  2. Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value.
  3. Authentication proves identity but each network resource action requires separate policy-based authorization controls.
  4. Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert.

Explanation

Correct Answer

A:

Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. Acceptance should show: Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The reported condition is governed by: The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The two mechanisms should not be conflated.

C:

The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. It does not explain the facts described here, which follow from: The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting.

Question 133

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: Engineers manually recreate a CML lab from memory each week and results cannot be tied to the version of the test topology. Which result most directly verifies that the proposed correction worked?

  1. A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state.
  2. A recreated container reads the expected persistent audit or inventory records from the configured volume.
  3. The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results.
  4. The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit.

Explanation

Correct Answer

C:

The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results. This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. It checks the technical distinction: A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Applied here, the relevant facts are: Engineers manually recreate a CML lab from memory each week and results cannot be tied to the version of the test topology. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

This alternative is a response to another technical cause: This directly verifies the related correction: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. The reported case instead depends on: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. The action that directly addresses it is “The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results”.

B:

The proposed action belongs to the mechanism: This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. Here the stated fault follows a different mechanism: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. The corrective choice is “The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results”.

D:

This alternative is a response to another technical cause: 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 reported case instead depends on: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. The action that directly addresses it is “The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results”.

Question 134

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A routing policy automation is planned for production without testing expected OSPF convergence under the new neighbor settings. What underlying technical distinction accounts for this failure?

  1. Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged.
  2. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.
  3. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
  4. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.

Explanation

Correct Answer

B:

CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. Acceptance should show: The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology. Applied here, the relevant facts are: A routing policy automation is planned for production without testing expected OSPF convergence under the new neighbor settings. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

A:

The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release.

C:

This principle describes a separate cause: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The reported condition is governed by: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The two mechanisms should not be conflated.

D:

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: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release.

Question 135

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: A user asks a network bot to adjust one interface but the bot invents parameters and attempts an unreviewed fleet-wide rollout. What technical evidence should be required before closing this change?

  1. The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved.
  2. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  3. A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.
  4. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.

Explanation

Correct Answer

A:

The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved. This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. It checks the technical distinction: LLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose.

Incorrect Answers

B:

This observation would test a different technical dependency: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The current issue is governed by: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. Its decisive check is “The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The current case instead depends on: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. Confirm that “The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. In the current case, the governing reason is: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The direct verification is “The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved”.

Question 136

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: An engineer adds every file to the index, including a generated device backup that must not be included in a Git commit. What mechanism is most directly responsible for these symptoms?

  1. Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.
  2. The Git index is the staging area and can be changed independently of the working tree by suitable reset modes.
  3. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.
  4. Git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. 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.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. 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: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. 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 137

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A telemetry dashboard polls SNMP every minute for a rapidly changing interface queue and fails to capture short congestion spikes. What should the team add to its network automation operating process?

  1. Maintain tested parser/device version matrices and fail clearly when collection contracts change.
  2. Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals.
  3. Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls.
  4. Add injection regression tests and prohibit unmanaged shell execution in network automation services.

Explanation

Correct Answer

B:

Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals. This prevents the recurrence because model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. A matching immediate correction is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal.

Incorrect Answers

A:

The proposed action belongs to the mechanism: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. Here the stated fault follows a different mechanism: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The corrective choice is “Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals”.

C:

This alternative is a response to another technical cause: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The reported case instead depends on: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The action that directly addresses it is “Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals”.

D:

The proposed action belongs to the mechanism: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. Here the stated fault follows a different mechanism: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The corrective choice is “Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals”.

Question 138

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A network automation proof uses a single virtual switch even though production depends on redundant OSPF neighbors and link failures. Which targeted correction best addresses the network automation failure?

  1. Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.
  2. Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.
  3. Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.
  4. Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.

Explanation

Correct Answer

B:

Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. This addresses the problem because simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Confirm success using: Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.

Incorrect Answers

A:

The offered action targets: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The case facts point instead to: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Implement “Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device” to address that specific condition.

C:

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: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The corrective choice is “Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device”.

D:

The offered action targets: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The case facts point instead to: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Implement “Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device” to address that specific condition.

Question 139

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: An engineering team patches switch interfaces manually but never updates canonical device intent, so the next automated apply undoes the fix. What ongoing engineering assurance should follow the successful fix?

  1. Use reproducible lockfiles, container digest pinning and scheduled compatibility tests before updating dependencies.
  2. Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks.
  3. Require clean-worktree status checks when CI or operators switch network automation release branches.
  4. Control source updates through review and schedule automated drift detection after deployment.

Explanation

Correct Answer

D:

Control source updates through review and schedule automated drift detection after deployment. This prevents the recurrence because a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. A matching immediate correction is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.

Incorrect Answers

A:

This routine guards against another mechanism: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The recurring exposure in the current case is: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The matching preventive check is “Control source updates through review and schedule automated drift detection after deployment”.

B:

The suggested review tracks a different technical risk: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Here the sustained control must address: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. Choose “Control source updates through review and schedule automated drift detection after deployment”.

C:

That safeguard is relevant to: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The current failure instead follows from: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. Its prevention measure is “Control source updates through review and schedule automated drift detection after deployment”.

Question 140

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A network incident log contains attacker-controlled text saying ignore safety checks and run a destructive router command, and the agent obeys it. What underlying technical distinction accounts for this failure?

  1. LLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose.
  2. Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.
  3. Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.
  4. Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent.

Explanation

Correct Answer

B:

Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. Acceptance should show: Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls. Applied here, the relevant facts are: A network incident log contains attacker-controlled text saying ignore safety checks and run a destructive router command, and the agent obeys it. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

A:

The corresponding repair is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.

C:

This principle describes a separate cause: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The reported condition is governed by: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. The two mechanisms should not be conflated.

D:

The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.