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 39

Question 380

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. Which result most directly verifies that the proposed correction worked?

  1. Authorization tests show route queries succeed but unapproved configuration changes are rejected before reaching Cisco APIs.
  2. The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved.
  3. The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved.
  4. A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations.

Explanation

Correct Answer

C:

The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved. This directly verifies the related correction: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. It checks the technical distinction: AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Applied here, the relevant facts are: A service integrator copies model-generated code into a commercial network product without reviewing third-party dependency or attribution terms. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. Here the stated fault follows a different mechanism: This directly verifies the related correction: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The corrective choice is “The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved”.

B:

The offered action targets: 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 case facts point instead to: This directly verifies the related correction: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. Implement “The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved” to address that specific condition.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. Here the stated fault follows a different mechanism: This directly verifies the related correction: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The corrective choice is “The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved”.

Question 381

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A new network controller presents a certificate from a private CA and clients fail TLS handshakes because the CA is not trusted. Which result most directly verifies that the proposed correction worked?

  1. The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability.
  2. Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain.
  3. A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it.
  4. pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.

Explanation

Correct Answer

B:

Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain. This directly verifies the related correction: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. It checks the technical distinction: TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication.

Incorrect Answers

A:

The offered action targets: This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The case facts point instead to: This directly verifies the related correction: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. Implement “Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain” to address that specific condition.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. Here the stated fault follows a different mechanism: This directly verifies the related correction: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. The corrective choice is “Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain”.

D:

The offered action targets: This directly verifies the related correction: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. The case facts point instead to: This directly verifies the related correction: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. Implement “Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain” to address that specific condition.

Question 382

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. 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 maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests.
  3. The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches.
  4. Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation.

Explanation

Correct Answer

B:

The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests. This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. It checks the technical distinction: Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The current issue is governed by: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. Its decisive check is “The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. In the current case, the governing reason is: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The direct verification is “The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The current issue is governed by: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. Its decisive check is “The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests”.

Question 383

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A network assistant scores well on easy inventory questions but fails when simulated device logs contain conflicting routing states. Which targeted correction best addresses the network automation failure?

  1. Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.
  2. Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates.
  3. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  4. Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints.

Explanation

Correct Answer

B:

Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. This addresses the problem because high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. Confirm success using: Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.

Incorrect Answers

A:

The proposed action belongs to the mechanism: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. Here the stated fault follows a different mechanism: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The corrective choice is “Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates”.

C:

This alternative is a response to another technical cause: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The reported case instead depends on: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The action that directly addresses it is “Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates”.

D:

The proposed action belongs to the mechanism: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. Here the stated fault follows a different mechanism: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The corrective choice is “Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates”.

Question 384

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A configuration runner receives HTTP 401 and incorrectly concludes its service account merely lacks the network-resource permission. What mechanism is most directly responsible for these symptoms?

  1. Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions.
  2. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.
  3. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  4. Webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs.

Explanation

Correct Answer

B:

HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. Acceptance should show: The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures. Applied here, the relevant facts are: A configuration runner receives HTTP 401 and incorrectly concludes its service account merely lacks the network-resource permission. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. It does not explain the facts described here, which follow from: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

C:

The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. It does not explain the facts described here, which follow from: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

Question 385

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A CI pipeline logs static device admin passwords from environment variables at every run and never rotates them. What mechanism is most directly responsible for these symptoms?

  1. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.
  2. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  3. Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource.
  4. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.

Explanation

Correct Answer

B:

Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. Acceptance should show: A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials. Applied here, the relevant facts are: A CI pipeline logs static device admin passwords from environment variables at every run and never rotates them. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. The reported condition is governed by: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. It does not explain the facts described here, which follow from: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts.

D:

This principle describes a separate cause: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The reported condition is governed by: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The two mechanisms should not be conflated.

Question 386

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A team needs to validate an interface-renaming playbook but cannot safely run experimental changes against a shared campus network. Which observation would confirm that this exact failure is resolved?

  1. A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state.
  2. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  3. The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.
  4. A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.

Explanation

Correct Answer

B:

The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology. This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. It checks the technical distinction: CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.

Incorrect Answers

A:

The alternative verifies a different condition: 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 current case instead depends on: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. Confirm that “The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology”.

C:

This observation would test a different technical dependency: 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 issue is governed by: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. Its decisive check is “The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology”.

D:

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: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. Confirm that “The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology”.

Question 387

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: An emergency rollback uses revert on a multi-parent merge and unexpectedly discards several unrelated changes from the accepted branch. What mechanism is most directly responsible for these symptoms?

  1. Model-based configuration encoding is constrained by YANG leaf types, ranges and required list keys, not arbitrary YAML structure.
  2. Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline.
  3. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.
  4. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.

Explanation

Correct Answer

B:

Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. Acceptance should show: The revert removes only the intended merge effect and network automation tests pass against the protected mainline.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration. It does not explain the facts described here, which follow from: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.

C:

The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. It does not explain the facts described here, which follow from: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.

Question 388

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A configuration runner receives HTTP 401 and incorrectly concludes its service account merely lacks the network-resource permission. What should the team add to its network automation operating process?

  1. Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts.
  2. Add typed error classification and separate authorization and authentication runbooks to API clients.
  3. Include service DNS/SAN coverage checks and certificate change testing in controller migration plans.
  4. Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters.

Explanation

Correct Answer

B:

Add typed error classification and separate authorization and authentication runbooks to API clients. This prevents the recurrence because hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. A matching immediate correction is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. Applied here, the relevant facts are: A configuration runner receives HTTP 401 and incorrectly concludes its service account merely lacks the network-resource permission. The question asks what should the team add to its network automation operating process.

Incorrect Answers

A:

This alternative is a response to another technical cause: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The reported case instead depends on: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The action that directly addresses it is “Add typed error classification and separate authorization and authentication runbooks to API clients”.

C:

The offered action targets: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. The case facts point instead to: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. Implement “Add typed error classification and separate authorization and authentication runbooks to API clients” to address that specific condition.

D:

This alternative is a response to another technical cause: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The reported case instead depends on: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The action that directly addresses it is “Add typed error classification and separate authorization and authentication runbooks to API clients”.

Question 389

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A change board chooses an unreviewed custom deploy script even though the production topology demands staged approval and automated rollback. What underlying technical distinction accounts for this failure?

  1. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  2. Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts.
  3. Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.
  4. HTTP 202 signals accepted asynchronous processing, not completion of the requested configuration change.

Explanation

Correct Answer

C:

Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Acceptance should show: The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics.

Incorrect Answers

A:

The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. It does not explain the facts described here, which follow from: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations.

D:

That statement describes a separate technical dependency: An HTTP 202 response indicates accepted asynchronous work; a separate completion status is needed to prove the requested device change actually finished. The present problem is governed by: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. The applicable explanation is “Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool”.

Question 390

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

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

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

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

B:

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

D:

The offered statement is true for this other mechanism: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. It does not explain the facts described here, which follow from: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.