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 93

Question 920

A multi-tenant hosting operator is working on tenant-isolated device inventory and controller state. A retrospective identifies: a high-availability controller cluster accepts TLS on one node but rejects it on another. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that failover testing preserves trusted TLS to every active cluster endpoint; flag recurrence if a high-availability controller cluster accepts TLS on one node but rejects it on another.
  2. Check that an authorized client establishes authenticated TLS using the approved trust anchors; flag recurrence if a new automation server presents a self-signed certificate in production.
  3. Check that a TLS client validates the chosen address against the SAN successfully; flag recurrence if a certificate request contains an IP address in CN but clients connect by IP and fail validation.
  4. Check that only certificates anchored to trusted CA roots are accepted; flag recurrence if a controller certificate is signed by a CA unknown to the enterprise trust policy.

Explanation

Correct Answer

A:

The check tests the restored condition, failover testing preserves trusted TLS to every active cluster endpoint, and explicitly flags a recurrence of a high-availability controller cluster accepts TLS on one node but rejects it on another.

Incorrect Answers

B:

This guard monitors a different regression trigger: a new automation server presents a self-signed certificate in production. It does not directly validate the recovery condition, failover testing preserves trusted TLS to every active cluster endpoint.

C:

This guard monitors a different regression trigger: a certificate request contains an IP address in CN but clients connect by IP and fail validation. It does not directly validate the recovery condition, failover testing preserves trusted TLS to every active cluster endpoint.

D:

This guard monitors a different regression trigger: a controller certificate is signed by a CA unknown to the enterprise trust policy. It does not directly validate the recovery condition, failover testing preserves trusted TLS to every active cluster endpoint.

Question 921

An airport network operator is working on redundant terminal-core and access infrastructure. During deployment, an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. Which action most directly addresses this specific network automation problem?

  1. Require CA-validated TLS with supported hostname checks.
  2. Require timestamps/nonces and deduplicate within a bounded replay window.
  3. Validate against allowed interface identifiers and use safe argument APIs without a shell.
  4. Redact secret-bearing headers and minimize error payloads before logging.

Explanation

Correct Answer

C:

The observed failure is: an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. The underlying cause is: untrusted input is interpolated into a shell command without validation. Verify that crafted interface names are rejected without command execution.

Incorrect Answers

A:

This would address a different condition: an automation runner accepts TLS with verify=False for every network controller. Here, the actual issue is: untrusted input is interpolated into a shell command without validation; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: an internal webhook is vulnerable to replaying a signed old change request. Here, the actual issue is: untrusted input is interpolated into a shell command without validation; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: a Python API client prints bearer tokens on each 403 exception. Here, the actual issue is: untrusted input is interpolated into a shell command without validation; it needs a scoped correction rather than this unrelated intervention.

Question 922

An airport network operator is working on redundant terminal-core and access infrastructure. The team found that an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Error logs preserve diagnostic IDs without exposing bearer tokens.
  2. Crafted interface names are rejected without command execution.
  3. Previously consumed signed events cannot trigger repeated configuration writes.
  4. MitM test endpoints are rejected and legitimate controllers remain reachable.

Explanation

Correct Answer

B:

This evidence directly verifies the scoped correction, validate against allowed interface identifiers and use safe argument APIs without a shell, for the underlying issue: untrusted input is interpolated into a shell command without validation. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

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: crafted interface names are rejected without command execution.

C:

This would confirm recovery from an internal webhook is vulnerable to replaying a signed old change request, not necessarily from the reported incident. For the specified issue the relevant confirmation is: crafted interface names are rejected without command execution.

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: crafted interface names are rejected without command execution.

Question 923

An airport network operator is working on redundant terminal-core and access infrastructure. The team observes that an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. Which underlying mechanism best explains this failure?

  1. Untrusted input is interpolated into a shell command without validation.
  2. The client disables identity verification in the name of troubleshooting.
  3. Signature validation checks authenticity but not freshness or replay identity.
  4. Exception handlers serialize unredacted sensitive headers.

Explanation

Correct Answer

A:

This mechanism explains the reported observation, an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. The targeted response is to validate against allowed interface identifiers and use safe argument APIs without a shell; the expected confirming result is that crafted interface names are rejected without command execution.

Incorrect Answers

B:

That mechanism fits a different symptom: an automation runner accepts TLS with verify=False for every network controller. The reported condition instead points to untrusted input is interpolated into a shell command without validation.

C:

That mechanism fits a different symptom: an internal webhook is vulnerable to replaying a signed old change request. The reported condition instead points to untrusted input is interpolated into a shell command without validation.

D:

That mechanism fits a different symptom: a Python API client prints bearer tokens on each 403 exception. The reported condition instead points to untrusted input is interpolated into a shell command without validation.

Question 924

An airport network operator is working on redundant terminal-core and access infrastructure. A retrospective identifies: an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. Which ongoing regression check best detects recurrence of this precise failure?

  1. 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.
  2. 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.
  3. 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.
  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

D:

The check tests the restored condition, crafted interface names are rejected without command execution, and explicitly flags a recurrence of an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command.

Incorrect Answers

A:

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, crafted interface names are rejected without command execution.

B:

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, crafted interface names are rejected without command execution.

C:

This guard monitors a different regression trigger: an internal webhook is vulnerable to replaying a signed old change request. It does not directly validate the recovery condition, crafted interface names are rejected without command execution.

Question 925

An education-cloud operations group is working on Git-tracked network simulation and deployment. During deployment, a network inventory lookup uses string concatenation to build a database query. Which action most directly addresses this specific network automation problem?

  1. Enforce server-side tenant authorization and VLAN range constraints.
  2. Pin and test patched dependency versions with automated vulnerability checks.
  3. Use parameterized database queries with strict input types.
  4. Issue a scoped read-only token for inventory queries and separate write identities.

Explanation

Correct Answer

C:

The observed failure is: a network inventory lookup uses string concatenation to build a database query. The underlying cause is: user input is injected into SQL syntax instead of bound as data. Verify that injection strings are handled as data and do not alter query logic.

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: user input is injected into SQL syntax instead of bound as data; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: a dependency scanner flags an exploitable version of a network API client used by CI. Here, the actual issue is: user input is injected into SQL syntax instead of bound as data; it needs a scoped correction rather than this unrelated intervention.

D:

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: user input is injected into SQL syntax instead of bound as data; it needs a scoped correction rather than this unrelated intervention.

Question 926

An education-cloud operations group is working on Git-tracked network simulation and deployment. The team found that a network inventory lookup uses string concatenation to build a database query. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Injection strings are handled as data and do not alter query logic.
  2. The patched build passes regression checks and the relevant advisory is resolved.
  3. Cross-tenant requests fail despite well-formed numbers.
  4. A write request using the read-only token is denied while inventory lookup works.

Explanation

Correct Answer

A:

This evidence directly verifies the scoped correction, use parameterized database queries with strict input types, for the underlying issue: user input is injected into SQL syntax instead of bound as data. It should be checked against actual device or pipeline output.

Incorrect Answers

B:

This would confirm recovery from a dependency scanner flags an exploitable version of a network API client used by CI, not necessarily from the reported incident. For the specified issue the relevant confirmation is: injection strings are handled as data and do not alter query logic.

C:

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: injection strings are handled as data and do not alter query logic.

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: injection strings are handled as data and do not alter query logic.

Question 927

An education-cloud operations group is working on Git-tracked network simulation and deployment. The team observes that a network inventory lookup uses string concatenation to build a database query. Which underlying mechanism best explains this failure?

  1. The assigned API token has excessive permissions and wide resource scope.
  2. Validation checks that the field is numeric but not allowed within tenant policy.
  3. Dependency versions are untracked and security advisories are not incorporated.
  4. User input is injected into SQL syntax instead of bound as data.

Explanation

Correct Answer

D:

This mechanism explains the reported observation, a network inventory lookup uses string concatenation to build a database query. The targeted response is to use parameterized database queries with strict input types; the expected confirming result is that injection strings are handled as data and do not alter query logic.

Incorrect Answers

A:

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 user input is injected into SQL syntax instead of bound as data.

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 user input is injected into SQL syntax instead of bound as data.

C:

That mechanism fits a different symptom: a dependency scanner flags an exploitable version of a network API client used by CI. The reported condition instead points to user input is injected into SQL syntax instead of bound as data.

Question 928

An education-cloud operations group is working on Git-tracked network simulation and deployment. A retrospective identifies: a network inventory lookup uses string concatenation to build a database query. Which ongoing regression check best detects recurrence of this precise failure?

  1. 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.
  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 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.

Explanation

Correct Answer

B:

The check tests the restored condition, injection strings are handled as data and do not alter query logic, and explicitly flags a recurrence of a network inventory lookup uses string concatenation to build a database query.

Incorrect Answers

A:

This guard monitors a different regression trigger: a dependency scanner flags an exploitable version of a network API client used by CI. It does not directly validate the recovery condition, injection strings are handled as data and do not alter query logic.

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, injection strings are handled as data and do not alter query logic.

D:

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, injection strings are handled as data and do not alter query logic.

Question 929

A national weather agency is working on resilient remote station telemetry and secure updates. During deployment, a service commits long-lived device passwords in a configuration repository. Which action most directly addresses this specific network automation problem?

  1. Validate against allowed interface identifiers and use safe argument APIs without a shell.
  2. Require timestamps/nonces and deduplicate within a bounded replay window.
  3. Store secrets in an approved vault with scoped identity-based retrieval and rotate exposed keys.
  4. Use safe parsing and schema validation for untrusted YAML documents.

Explanation

Correct Answer

C:

The observed failure is: a service commits long-lived device passwords in a configuration repository. The underlying cause is: credential values are hard-coded instead of retrieved at runtime from a secret manager. Verify that repository and CI logs have no credentials while authorized jobs still authenticate.

Incorrect Answers

A:

This would address a different condition: an automation URL accepts interface names with shell metacharacters and unexpectedly executes a host command. Here, the actual issue is: credential values are hard-coded instead of retrieved at runtime from a secret manager; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: an internal webhook is vulnerable to replaying a signed old change request. Here, the actual issue is: credential values are hard-coded instead of retrieved at runtime from a secret manager; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: a network configuration service allows untrusted YAML tags to instantiate Python objects. Here, the actual issue is: credential values are hard-coded instead of retrieved at runtime from a secret manager; it needs a scoped correction rather than this unrelated intervention.

Question 930

A national weather agency is working on resilient remote station telemetry and secure updates. The team found that a service commits long-lived device passwords in a configuration repository. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Crafted interface names are rejected without command execution.
  2. Repository and CI logs have no credentials while authorized jobs still authenticate.
  3. Malicious YAML tags are rejected before object creation.
  4. Previously consumed signed events cannot trigger repeated configuration writes.

Explanation

Correct Answer

B:

This evidence directly verifies the scoped correction, store secrets in an approved vault with scoped identity-based retrieval and rotate exposed keys, for the underlying issue: credential values are hard-coded instead of retrieved at runtime from a secret manager. 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: repository and CI logs have no credentials while authorized jobs still authenticate.

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: repository and CI logs have no credentials while authorized jobs still authenticate.

D:

This would confirm recovery from an internal webhook is vulnerable to replaying a signed old change request, not necessarily from the reported incident. For the specified issue the relevant confirmation is: repository and CI logs have no credentials while authorized jobs still authenticate.