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 15

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.

Question 141

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A developer accidentally stages a generated credentials fixture in an unpushed commit and needs to revise local commit history before review. Which observation would confirm that this exact failure is resolved?

  1. The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation.
  2. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  3. The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.
  4. GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.

Explanation

Correct Answer

A:

The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation. This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. It checks the technical distinction: Git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history.

Incorrect Answers

B:

This observation would test a different technical dependency: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The current issue is governed by: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. Its decisive check is “The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation”.

C:

The alternative verifies a different condition: 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 case instead depends on: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. Confirm that “The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. In the current case, the governing reason is: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The direct verification is “The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation”.

Question 142

During a production change postcheck at fictional Marble Bay Software, the change record states: An engineer approves an OSPF automation change after configuration diff alone even though neighbor states have changed unexpectedly. Which explanation best matches the actual broken dependency?

  1. Authentication proves identity but each network resource action requires separate policy-based authorization controls.
  2. CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication.
  3. Untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations.
  4. pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs.

Explanation

Correct Answer

D:

pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. Acceptance should show: pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.

Incorrect Answers

A:

This observation would test a different technical dependency: The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. The current issue is governed by: The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. Its decisive check is “pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs”.

B:

The alternative verifies a different condition: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The current case instead depends on: The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. Confirm that “pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs”.

C:

That test belongs to another control with this basis: The corresponding repair is: Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation. In the current case, the governing reason is: The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. The direct verification is “pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs”.

Question 143

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A controller-integration container loses its collected audit results whenever the Compose project is recreated. Which implementation action best meets the observed technical requirement?

  1. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.
  2. Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.
  3. Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation.
  4. Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.

Explanation

Correct Answer

C:

Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. This addresses the problem because ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Confirm success using: A recreated container reads the expected persistent audit or inventory records from the configured volume.

Incorrect Answers

A:

The proposed action belongs to the mechanism: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Here the stated fault follows a different mechanism: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The corrective choice is “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation”.

B:

The offered action targets: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The case facts point instead to: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Implement “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation” to address that specific condition.

D:

The proposed action belongs to the mechanism: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Here the stated fault follows a different mechanism: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The corrective choice is “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation”.

Question 144

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A merge introduces a network policy defect and a developer tries to revert the merge without identifying its mainline parent. What should the team add to its network automation operating process?

  1. Add merge topology review and a dry-run diff approval for complex revert operations.
  2. Add dependency-impact review and target-branch CI validation to hotfix backport procedures.
  3. Version lab topology artifacts and run automated readiness verification before configuration tests.
  4. Review Compose network boundaries and port mappings with security tests before any deployment.

Explanation

Correct Answer

A:

Add merge topology review and a dry-run diff approval for complex revert operations. This prevents the recurrence because reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. A matching immediate correction is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. Applied here, the relevant facts are: A merge introduces a network policy defect and a developer tries to revert the merge without identifying its mainline parent. The question asks what should the team add to its network automation operating process.

Incorrect Answers

B:

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: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The action that directly addresses it is “Add merge topology review and a dry-run diff approval for complex revert operations”.

C:

The proposed action belongs to the mechanism: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Here the stated fault follows a different mechanism: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The corrective choice is “Add merge topology review and a dry-run diff approval for complex revert operations”.

D:

The offered action targets: compose networks govern container service reachability, while host port publishing determines external exposure. The case facts point instead to: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. Implement “Add merge topology review and a dry-run diff approval for complex revert operations” to address that specific condition.

Question 145

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A controller API call is occasionally slow during large inventory updates, but aggregated success logs hide its tail latency. What should the team add to its network automation operating process?

  1. Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals.
  2. Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls.
  3. Review telemetry label schemas, retention and cardinality budgets before enabling new collectors.
  4. Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows.

Explanation

Correct Answer

B:

Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls. This prevents the recurrence because latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. A matching immediate correction is: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction.

Incorrect Answers

A:

This alternative is a response to another technical cause: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The reported case instead depends on: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The action that directly addresses it is “Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls”.

C:

The offered action targets: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The case facts point instead to: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. Implement “Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls” to address that specific condition.

D:

This alternative is a response to another technical cause: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The reported case instead depends on: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The action that directly addresses it is “Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls”.

Question 146

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: After a controller load-balancer migration, an HTTPS client fails hostname verification because the certificate SAN lists the old hostname. What is the appropriate response to this network automation condition?

  1. Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts.
  2. Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.
  3. Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport.
  4. Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities.

Explanation

Correct Answer

D:

Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. This addresses the problem because modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. Confirm success using: TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification. Applied here, the relevant facts are: After a controller load-balancer migration, an HTTPS client fails hostname verification because the certificate SAN lists the old hostname. The question asks what is the appropriate response to this network automation condition.

Incorrect Answers

A:

The alternative verifies a different condition: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The current case instead depends on: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. Confirm that “Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities”.

B:

That test belongs to another control with this basis: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. In the current case, the governing reason is: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. The direct verification is “Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities”.

C:

This observation would test a different technical dependency: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. The current issue is governed by: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. Its decisive check is “Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities”.

Question 147

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A team builds a custom Python service for straightforward ticket-triggered device tagging already supported by an approved audited low-code connector. Which result most directly verifies that the proposed correction worked?

  1. Plans for two independently configured sites show correct separate VLAN IDs or address values while sharing one reviewed module version.
  2. A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.
  3. Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval.
  4. The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails.

Explanation

Correct Answer

B:

A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach. This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. It checks the technical distinction: Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics.

Incorrect Answers

A:

The offered action targets: This directly verifies the related correction: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The case facts point instead to: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. Implement “A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach” to address that specific condition.

C:

The proposed action belongs to the mechanism: 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. Here the stated fault follows a different mechanism: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. The corrective choice is “A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach”.

D:

The offered action targets: This directly verifies the related correction: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. The case facts point instead to: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. Implement “A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach” to address that specific condition.

Question 148

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A pipeline skips a failing YANG schema check because the deploy stage is not explicitly dependent on prevalidation success. Which control best prevents this particular failure from recurring?

  1. Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations.
  2. Require clean-worktree status checks when CI or operators switch network automation release branches.
  3. Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks.
  4. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.

Explanation

Correct Answer

C:

Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks. This prevents the recurrence because prevalidation is a safety boundary before changing network state, separate from checks after a change completes. A matching immediate correction is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. Applied here, the relevant facts are: A pipeline skips a failing YANG schema check because the deploy stage is not explicitly dependent on prevalidation success. The question asks which control best prevents this particular failure from recurring.

Incorrect Answers

A:

This routine guards against another mechanism: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The recurring exposure in the current case is: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The matching preventive check is “Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks”.

B:

The suggested review tracks a different technical risk: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Here the sustained control must address: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Choose “Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks”.

D:

This routine guards against another mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The recurring exposure in the current case is: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The matching preventive check is “Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks”.

Question 149

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A network parsing pipeline runs under a clean container and raises ModuleNotFoundError for a local-only tool used by the scripts. What mechanism is most directly responsible for these symptoms?

  1. Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.
  2. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
  3. CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.
  4. Git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback.

Explanation

Correct Answer

C:

CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. Acceptance should show: A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state. Applied here, the relevant facts are: A network parsing pipeline runs under a clean container and raises ModuleNotFoundError for a local-only tool used by the scripts. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. It does not explain the facts described here, which follow from: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.

D:

The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.

Question 150

While investigating a telemetry quality investigation for fictional Sable Valley Power, the team reports: A time-series database stores each raw API request ID as a permanent metric label, causing explosive series cardinality. Which engineering principle explains the described system behavior?

  1. Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource.
  2. CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication.
  3. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.
  4. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.

Explanation

Correct Answer

D:

Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. Acceptance should show: The series count remains bounded while operators can still filter reliably by site, device and interface.

Incorrect Answers

A:

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: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.

B:

This principle describes a separate cause: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The reported condition is governed by: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. The two mechanisms should not be conflated.

C:

The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.