McAfee-Secured Website

Exam 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 Video 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

    Video Course

    106 Video Lectures

    $39.99

Cisco 350-901 Practice Test 96

Question 950

A remote-campus networking team is working on high-latency links and intermittent API access. The team found that a service token can change production routers although it is used only to read inventory. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Crafted interface names are rejected without command execution.
  2. Error logs preserve diagnostic IDs without exposing bearer tokens.
  3. Malicious YAML tags are rejected before object creation.
  4. A write request using the read-only token is denied while inventory lookup works.

Explanation

Correct Answer

D:

This evidence directly verifies the scoped correction, issue a scoped read-only token for inventory queries and separate write identities, for the underlying issue: the assigned API token has excessive permissions and wide resource scope. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a write request using the read-only token is denied while inventory lookup works.

B:

This would confirm recovery from a Python API client prints bearer tokens on each 403 exception, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a write request using the read-only token is denied while inventory lookup works.

C:

This would confirm recovery from a network configuration service allows untrusted YAML tags to instantiate Python objects, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a write request using the read-only token is denied while inventory lookup works.

Question 951

A remote-campus networking team is working on high-latency links and intermittent API access. The team observes that a service token can change production routers although it is used only to read inventory. Which underlying mechanism best explains this failure?

  1. Unsafe YAML deserialization can execute arbitrary constructors.
  2. The assigned API token has excessive permissions and wide resource scope.
  3. Untrusted input is interpolated into a shell command without validation.
  4. Exception handlers serialize unredacted sensitive headers.

Explanation

Correct Answer

B:

This mechanism explains the reported observation, a service token can change production routers although it is used only to read inventory. The targeted response is to issue a scoped read-only token for inventory queries and separate write identities; the expected confirming result is that a write request using the read-only token is denied while inventory lookup works.

Incorrect Answers

A:

That mechanism fits a different symptom: a network configuration service allows untrusted YAML tags to instantiate Python objects. The reported condition instead points to the assigned API token has excessive permissions and wide resource scope.

C:

That mechanism fits a different symptom: an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. The reported condition instead points to the assigned API token has excessive permissions and wide resource scope.

D:

That mechanism fits a different symptom: a Python API client prints bearer tokens on each 403 exception. The reported condition instead points to the assigned API token has excessive permissions and wide resource scope.

Question 952

A remote-campus networking team is working on high-latency links and intermittent API access. A retrospective identifies: a service token can change production routers although it is used only to read inventory. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that a write request using the read-only token is denied while inventory lookup works; flag recurrence if a service token can change production routers although it is used only to read inventory.
  2. Check that malicious YAML tags are rejected before object creation; flag recurrence if a network configuration service allows untrusted YAML tags to instantiate Python objects.
  3. Check that error logs preserve diagnostic IDs without exposing bearer tokens; flag recurrence if a Python API client prints bearer tokens on each 403 exception.
  4. Check that crafted interface names are rejected without command execution; flag recurrence if an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command.

Explanation

Correct Answer

A:

The check tests the restored condition, a write request using the read-only token is denied while inventory lookup works, and explicitly flags a recurrence of a service token can change production routers although it is used only to read inventory.

Incorrect Answers

B:

This guard monitors a different regression trigger: a network configuration service allows untrusted YAML tags to instantiate Python objects. It does not directly validate the recovery condition, a write request using the read-only token is denied while inventory lookup works.

C:

This guard monitors a different regression trigger: a Python API client prints bearer tokens on each 403 exception. It does not directly validate the recovery condition, a write request using the read-only token is denied while inventory lookup works.

D:

This guard monitors a different regression trigger: an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. It does not directly validate the recovery condition, a write request using the read-only token is denied while inventory lookup works.

Question 953

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. During deployment, an internal webhook is vulnerable to replaying a signed old change request. Which action most directly addresses this specific network automation problem?

  1. Enforce server-side tenant authorization and VLAN range constraints.
  2. Require CA-validated TLS with supported hostname checks.
  3. Require timestamps/nonces and deduplicate within a bounded replay window.
  4. Use parameterized database queries with strict input types.

Explanation

Correct Answer

C:

The observed failure is: an internal webhook is vulnerable to replaying a signed old change request. The underlying cause is: signature validation checks authenticity but not freshness or replay identity. Verify that previously consumed signed events cannot trigger repeated configuration writes.

Incorrect Answers

A:

This would address a different condition: a VLAN creation endpoint permits an operator to request arbitrary tenant VLAN IDs. Here, the actual issue is: signature validation checks authenticity but not freshness or replay identity; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: an automation runner accepts TLS with verify=False for every network controller. Here, the actual issue is: signature validation checks authenticity but not freshness or replay identity; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: a network inventory lookup uses string concatenation to build a database query. Here, the actual issue is: signature validation checks authenticity but not freshness or replay identity; it needs a scoped correction rather than this unrelated intervention.

Question 954

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. The team found that an internal webhook is vulnerable to replaying a signed old change request. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Cross-tenant requests fail despite well-formed numbers.
  2. Previously consumed signed events cannot trigger repeated configuration writes.
  3. Injection strings are handled as data and do not alter query logic.
  4. MitM test endpoints are rejected and legitimate controllers remain reachable.

Explanation

Correct Answer

B:

This evidence directly verifies the scoped correction, require timestamps/nonces and deduplicate within a bounded replay window, for the underlying issue: signature validation checks authenticity but not freshness or replay identity. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from a VLAN creation endpoint permits an operator to request arbitrary tenant VLAN IDs, not necessarily from the reported incident. For the specified issue the relevant confirmation is: previously consumed signed events cannot trigger repeated configuration writes.

C:

This would confirm recovery from a network inventory lookup uses string concatenation to build a database query, not necessarily from the reported incident. For the specified issue the relevant confirmation is: previously consumed signed events cannot trigger repeated configuration writes.

D:

This would confirm recovery from an automation runner accepts TLS with verify=False for every network controller, not necessarily from the reported incident. For the specified issue the relevant confirmation is: previously consumed signed events cannot trigger repeated configuration writes.

Question 955

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. The team observes that an internal webhook is vulnerable to replaying a signed old change request. Which underlying mechanism best explains this failure?

  1. Signature validation checks authenticity but not freshness or replay identity.
  2. Validation checks that the field is numeric but not allowed within tenant policy.
  3. The client disables identity verification in the name of troubleshooting.
  4. User input is injected into SQL syntax instead of bound as data.

Explanation

Correct Answer

A:

This mechanism explains the reported observation, an internal webhook is vulnerable to replaying a signed old change request. The targeted response is to require timestamps/nonces and deduplicate within a bounded replay window; the expected confirming result is that previously consumed signed events cannot trigger repeated configuration writes.

Incorrect Answers

B:

That mechanism fits a different symptom: a VLAN creation endpoint permits an operator to request arbitrary tenant VLAN IDs. The reported condition instead points to signature validation checks authenticity but not freshness or replay identity.

C:

That mechanism fits a different symptom: an automation runner accepts TLS with verify=False for every network controller. The reported condition instead points to signature validation checks authenticity but not freshness or replay identity.

D:

That mechanism fits a different symptom: a network inventory lookup uses string concatenation to build a database query. The reported condition instead points to signature validation checks authenticity but not freshness or replay identity.

Question 956

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. A retrospective identifies: an internal webhook is vulnerable to replaying a signed old change request. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that mitM test endpoints are rejected and legitimate controllers remain reachable; flag recurrence if an automation runner accepts TLS with verify=False for every network controller.
  2. Check that injection strings are handled as data and do not alter query logic; flag recurrence if a network inventory lookup uses string concatenation to build a database query.
  3. Check that cross-tenant requests fail despite well-formed numbers; flag recurrence if a VLAN creation endpoint permits an operator to request arbitrary tenant VLAN IDs.
  4. Check that previously consumed signed events cannot trigger repeated configuration writes; flag recurrence if an internal webhook is vulnerable to replaying a signed old change request.

Explanation

Correct Answer

D:

The check tests the restored condition, previously consumed signed events cannot trigger repeated configuration writes, and explicitly flags a recurrence of an internal webhook is vulnerable to replaying a signed old change request.

Incorrect Answers

A:

This guard monitors a different regression trigger: an automation runner accepts TLS with verify=False for every network controller. It does not directly validate the recovery condition, previously consumed signed events cannot trigger repeated configuration writes.

B:

This guard monitors a different regression trigger: a network inventory lookup uses string concatenation to build a database query. It does not directly validate the recovery condition, previously consumed signed events cannot trigger repeated configuration writes.

C:

This guard monitors a different regression trigger: a VLAN creation endpoint permits an operator to request arbitrary tenant VLAN IDs. It does not directly validate the recovery condition, previously consumed signed events cannot trigger repeated configuration writes.

Question 957

A government service-delivery team is working on segmented infrastructure spanning two departments. During deployment, a dependency scanner flags an exploitable version of a network API client used by CI. Which action most directly addresses this specific network automation problem?

  1. Use safe parsing and schema validation for untrusted YAML documents.
  2. Store secrets in an approved vault with scoped identity-based retrieval and rotate exposed keys.
  3. Issue a scoped read-only token for inventory queries and separate write identities.
  4. Pin and test patched dependency versions with automated vulnerability checks.

Explanation

Correct Answer

D:

The observed failure is: a dependency scanner flags an exploitable version of a network API client used by CI. The underlying cause is: dependency versions are untracked and security advisories are not incorporated. Verify that the patched build passes regression checks and the relevant advisory is resolved.

Incorrect Answers

A:

This would address a different condition: a network configuration service allows untrusted YAML tags to instantiate Python objects. Here, the actual issue is: dependency versions are untracked and security advisories are not incorporated; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: a service commits long-lived device passwords in a configuration repository. Here, the actual issue is: dependency versions are untracked and security advisories are not incorporated; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a service token can change production routers although it is used only to read inventory. Here, the actual issue is: dependency versions are untracked and security advisories are not incorporated; it needs a scoped correction rather than this unrelated intervention.

Question 958

A government service-delivery team is working on segmented infrastructure spanning two departments. The team found that a dependency scanner flags an exploitable version of a network API client used by CI. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Repository and CI logs have no credentials while authorized jobs still authenticate.
  2. Malicious YAML tags are rejected before object creation.
  3. The patched build passes regression checks and the relevant advisory is resolved.
  4. A write request using the read-only token is denied while inventory lookup works.

Explanation

Correct Answer

C:

This evidence directly verifies the scoped correction, pin and test patched dependency versions with automated vulnerability checks, for the underlying issue: dependency versions are untracked and security advisories are not incorporated. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from a service commits long-lived device passwords in a configuration repository, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the patched build passes regression checks and the relevant advisory is resolved.

B:

This would confirm recovery from a network configuration service allows untrusted YAML tags to instantiate Python objects, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the patched build passes regression checks and the relevant advisory is resolved.

D:

This would confirm recovery from a service token can change production routers although it is used only to read inventory, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the patched build passes regression checks and the relevant advisory is resolved.

Question 959

A government service-delivery team is working on segmented infrastructure spanning two departments. The team observes that a dependency scanner flags an exploitable version of a network API client used by CI. Which underlying mechanism best explains this failure?

  1. Dependency versions are untracked and security advisories are not incorporated.
  2. Credential values are hard-coded instead of retrieved at runtime from a secret manager.
  3. The assigned API token has excessive permissions and wide resource scope.
  4. Unsafe YAML deserialization can execute arbitrary constructors.

Explanation

Correct Answer

A:

This mechanism explains the reported observation, a dependency scanner flags an exploitable version of a network API client used by CI. The targeted response is to pin and test patched dependency versions with automated vulnerability checks; the expected confirming result is that the patched build passes regression checks and the relevant advisory is resolved.

Incorrect Answers

B:

That mechanism fits a different symptom: a service commits long-lived device passwords in a configuration repository. The reported condition instead points to dependency versions are untracked and security advisories are not incorporated.

C:

That mechanism fits a different symptom: a service token can change production routers although it is used only to read inventory. The reported condition instead points to dependency versions are untracked and security advisories are not incorporated.

D:

That mechanism fits a different symptom: a network configuration service allows untrusted YAML tags to instantiate Python objects. The reported condition instead points to dependency versions are untracked and security advisories are not incorporated.

Question 960

A government service-delivery team is working on segmented infrastructure spanning two departments. A retrospective identifies: a dependency scanner flags an exploitable version of a network API client used by CI. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that a write request using the read-only token is denied while inventory lookup works; flag recurrence if a service token can change production routers although it is used only to read inventory.
  2. Check that the patched build passes regression checks and the relevant advisory is resolved; flag recurrence if a dependency scanner flags an exploitable version of a network API client used by CI.
  3. Check that repository and CI logs have no credentials while authorized jobs still authenticate; flag recurrence if a service commits long-lived device passwords in a configuration repository.
  4. Check that malicious YAML tags are rejected before object creation; flag recurrence if a network configuration service allows untrusted YAML tags to instantiate Python objects.

Explanation

Correct Answer

B:

The check tests the restored condition, the patched build passes regression checks and the relevant advisory is resolved, and explicitly flags a recurrence of a dependency scanner flags an exploitable version of a network API client used by CI.

Incorrect Answers

A:

This guard monitors a different regression trigger: a service token can change production routers although it is used only to read inventory. It does not directly validate the recovery condition, the patched build passes regression checks and the relevant advisory is resolved.

C:

This guard monitors a different regression trigger: a service commits long-lived device passwords in a configuration repository. It does not directly validate the recovery condition, the patched build passes regression checks and the relevant advisory is resolved.

D:

This guard monitors a different regression trigger: a network configuration service allows untrusted YAML tags to instantiate Python objects. It does not directly validate the recovery condition, the patched build passes regression checks and the relevant advisory is resolved.