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 25

Question 240

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A Terraform linting job suddenly fails after a GitLab base image pulls an incompatible provider and Python library combination. Which engineering principle explains the described system behavior?

  1. Git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history.
  2. A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access.
  3. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.
  4. Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged.

Explanation

Correct Answer

D:

Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. Acceptance should show: The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. It does not explain the facts described here, which follow from: The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.

B:

This principle describes a separate cause: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The reported condition is governed by: The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. The two mechanisms should not be conflated.

C:

The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.

Question 241

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. What underlying technical distinction accounts for this failure?

  1. Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed.
  2. Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes.
  3. RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model.
  4. API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes.

Explanation

Correct Answer

C:

RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. Acceptance should show: The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The reported condition is governed by: The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The two mechanisms should not be conflated.

B:

The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.

D:

This principle describes a separate cause: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The reported condition is governed by: The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The two mechanisms should not be conflated.

Question 242

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A configuration client sends PUT with only one interface leaf and unintentionally replaces other fields in the addressed YANG data resource. Which observation would confirm that this exact failure is resolved?

  1. The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code.
  2. Unchanged reruns cause no service restart, while an approved changed configuration invokes its handler exactly once.
  3. The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately.
  4. After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value.

Explanation

Correct Answer

D:

After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value. This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. It checks the technical distinction: HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. Applied here, the relevant facts are: A configuration client sends PUT with only one interface leaf and unintentionally replaces other fields in the addressed YANG data resource. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The current case instead depends on: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. Confirm that “After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. In the current case, the governing reason is: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. The direct verification is “After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. The current issue is governed by: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. Its decisive check is “After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value”.

Question 243

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A support operator attempts to inspect a historical release while untracked temporary config overlays contaminate the working directory. What ongoing engineering assurance should follow the successful fix?

  1. Use reproducible lockfiles, container digest pinning and scheduled compatibility tests before updating dependencies.
  2. Require clean-worktree status checks when CI or operators switch network automation release branches.
  3. Add merge topology review and a dry-run diff approval for complex revert operations.
  4. Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks.

Explanation

Correct Answer

B:

Require clean-worktree status checks when CI or operators switch network automation release branches. This prevents the recurrence because git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. A matching immediate correction is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.

Incorrect Answers

A:

That safeguard is relevant to: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The current failure instead follows from: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Its prevention measure is “Require clean-worktree status checks when CI or operators switch network automation release branches”.

C:

The suggested review tracks a different technical risk: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. Here the sustained control must address: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Choose “Require clean-worktree status checks when CI or operators switch network automation release branches”.

D:

That safeguard is relevant to: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The current failure instead follows from: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Its prevention measure is “Require clean-worktree status checks when CI or operators switch network automation release branches”.

Question 244

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 mechanism is most directly responsible for these symptoms?

  1. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
  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. A squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry.

Explanation

Correct Answer

D:

A squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. Acceptance should show: The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.

Incorrect Answers

A:

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: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. The two mechanisms should not be conflated.

B:

The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.

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: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.

Question 245

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: Parallel infrastructure pipelines apply conflicting ACL changes because state locking was disabled in a shared backend. Which result most directly verifies that the proposed correction worked?

  1. A second playbook run reports no unnecessary changes, and captured device configuration contains one intended interface setting on each target.
  2. The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately.
  3. The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment.
  4. The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment.

Explanation

Correct Answer

C:

The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment. This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. It checks the technical distinction: Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. Here the stated fault follows a different mechanism: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The corrective choice is “The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment”.

B:

The offered action targets: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. The case facts point instead to: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. Implement “The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment” to address that specific condition.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. Here the stated fault follows a different mechanism: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The corrective choice is “The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment”.

Question 246

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A BGP peering project legitimately changes neighbor count while a baseline assertion requires exact old inventory values. What acceptance check would prove the intended behavior was restored?

  1. An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage.
  2. A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.
  3. The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability.
  4. Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain.

Explanation

Correct Answer

C:

The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability. This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. It checks the technical distinction: Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination. In the current case, the governing reason is: This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The direct verification is “The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The current issue is governed by: This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. Its decisive check is “The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability”.

D:

That test belongs to another control with this basis: 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. In the current case, the governing reason is: This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The direct verification is “The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability”.

Question 247

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A Cisco asset API returns a continuation link, but a script ignores it and stops after the default page size. Which explanation best matches the actual broken dependency?

  1. Ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions.
  2. Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset.
  3. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  4. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.

Explanation

Correct Answer

B:

Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The corresponding repair is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. Acceptance should show: The final inventory count includes all pages and a test endpoint with three pages is retrieved without duplicates.

Incorrect Answers

A:

This alternative is a response to another technical cause: The corresponding repair is: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. The reported case instead depends on: The corresponding repair is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. The action that directly addresses it is “Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset”.

C:

The offered action targets: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The case facts point instead to: The corresponding repair is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. Implement “Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset” to address that specific condition.

D:

This alternative is a response to another technical cause: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The reported case instead depends on: The corresponding repair is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. The action that directly addresses it is “Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset”.

Question 248

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 underlying technical distinction accounts for this failure?

  1. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  2. Latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient.
  3. Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert.
  4. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.

Explanation

Correct Answer

C:

Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Acceptance should show: TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification.

Incorrect Answers

A:

The alternative verifies a different condition: 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 current case instead depends on: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Confirm that “Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert”.

B:

That test belongs to another control with this basis: The corresponding repair is: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. In the current case, the governing reason is: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. The direct verification is “Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert”.

D:

The alternative verifies a different condition: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The current case instead depends on: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Confirm that “Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert”.

Question 249

At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: A multi-tenant MCP endpoint reuses a cached privileged token between separate customer sessions, exposing one site's inventory to another. What underlying technical distinction accounts for this failure?

  1. Agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated.
  2. AI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure.
  3. The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors.
  4. An MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials.

Explanation

Correct Answer

D:

An MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The corresponding repair is: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. Acceptance should show: Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited. Applied here, the relevant facts are: A multi-tenant MCP endpoint reuses a cached privileged token between separate customer sessions, exposing one site's inventory to another. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. It does not explain the facts described here, which follow from: The corresponding repair is: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.

B:

This principle describes a separate cause: The corresponding repair is: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. The reported condition is governed by: The corresponding repair is: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. The two mechanisms should not be conflated.

C:

The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.

Question 250

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A GitLab job is marked failed after a network policy unit test, but the operator reruns deployment without inspecting the failing assertion. What acceptance check would prove the intended behavior was restored?

  1. A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates.
  2. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  3. A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.
  4. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.

Explanation

Correct Answer

A:

A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates. This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. It checks the technical distinction: A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.

Incorrect Answers

B:

The alternative verifies a different condition: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The current case instead depends on: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. Confirm that “A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. In the current case, the governing reason is: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The direct verification is “A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates”.

D:

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: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. Its decisive check is “A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates”.