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 15

Question 140

A financial services platform team is working on regional data-center and branch connectivity changes. A retrospective identifies: a RESTCONF configuration write returns HTTP 403 for a read-only service identity. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that writes pass schema checks and operational data remains read-only; flag recurrence if a telemetry read using RESTCONF fails because an operational leaf is submitted as configuration.
  2. Check that schema validation and GET show a JSON boolean with the required state; flag recurrence if a RESTCONF interface update fails after the engineer sends string 'true' for a boolean leaf.
  3. Check that device responses distinguish intended configuration from real observed interface counters; flag recurrence if RESTCONF configuration appears correct but the client reads operational counters from the wrong datastore.
  4. Check that the scoped service identity can write the approved path and remains denied elsewhere; flag recurrence if a RESTCONF configuration write returns HTTP 403 for a read-only service identity.

Explanation

Correct Answer

D:

The check tests the restored condition, the scoped service identity can write the approved path and remains denied elsewhere, and explicitly flags a recurrence of a RESTCONF configuration write returns HTTP 403 for a read-only service identity.

Incorrect Answers

A:

This guard monitors a different regression trigger: a telemetry read using RESTCONF fails because an operational leaf is submitted as configuration. It does not directly validate the recovery condition, the scoped service identity can write the approved path and remains denied elsewhere.

B:

This guard monitors a different regression trigger: a RESTCONF interface update fails after the engineer sends string 'true' for a boolean leaf. It does not directly validate the recovery condition, the scoped service identity can write the approved path and remains denied elsewhere.

C:

This guard monitors a different regression trigger: RESTCONF configuration appears correct but the client reads operational counters from the wrong datastore. It does not directly validate the recovery condition, the scoped service identity can write the approved path and remains denied elsewhere.

Question 141

A containerized platform engineering team is working on GitLab-based infrastructure deployment pipeline. During deployment, a RESTCONF payload deletes unrelated interface fields after a PUT update. Which action most directly addresses this specific network automation problem?

  1. Resolve and target the exact YANG leaf and verify destructive scope before DELETE.
  2. Construct the RFC 8040 RESTCONF data URL from the device-supported YANG schema.
  3. Discover supported modules and revisions and update the schema-aware request mapping.
  4. Use a compatible PATCH for a partial change or provide a complete validated replacement.

Explanation

Correct Answer

D:

The observed failure is: a RESTCONF payload deletes unrelated interface fields after a PUT update. The underlying cause is: full-resource replacement semantics were applied to a partial desired object. Verify that unchanged interface leaves remain present after the intended update.

Incorrect Answers

A:

This would address a different condition: a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf. Here, the actual issue is: full-resource replacement semantics were applied to a partial desired object; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: a RESTCONF read returns HTTP 404 although the device is reachable over HTTPS. Here, the actual issue is: full-resource replacement semantics were applied to a partial desired object; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: the controller changes its schema revision and a RESTCONF automation starts receiving unknown-node errors. Here, the actual issue is: full-resource replacement semantics were applied to a partial desired object; it needs a scoped correction rather than this unrelated intervention.

Question 142

A containerized platform engineering team is working on GitLab-based infrastructure deployment pipeline. The team found that a RESTCONF payload deletes unrelated interface fields after a PUT update. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Only the intended description field changes and sibling interface settings remain intact.
  2. Requests match advertised module revisions and pass schema validation.
  3. Unchanged interface leaves remain present after the intended update.
  4. GET on the model-qualified path returns the expected structured resource.

Explanation

Correct Answer

C:

This evidence directly verifies the scoped correction, use a compatible PATCH for a partial change or provide a complete validated replacement, for the underlying issue: full-resource replacement semantics were applied to a partial desired object. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf, not necessarily from the reported incident. For the specified issue the relevant confirmation is: unchanged interface leaves remain present after the intended update.

B:

This would confirm recovery from the controller changes its schema revision and a RESTCONF automation starts receiving unknown-node errors, not necessarily from the reported incident. For the specified issue the relevant confirmation is: unchanged interface leaves remain present after the intended update.

D:

This would confirm recovery from a RESTCONF read returns HTTP 404 although the device is reachable over HTTPS, not necessarily from the reported incident. For the specified issue the relevant confirmation is: unchanged interface leaves remain present after the intended update.

Question 143

A containerized platform engineering team is working on GitLab-based infrastructure deployment pipeline. The team observes that a RESTCONF payload deletes unrelated interface fields after a PUT update. Which underlying mechanism best explains this failure?

  1. The client assumes an older YANG model path without capability discovery.
  2. Full-resource replacement semantics were applied to a partial desired object.
  3. The URI targets a parent container instead of the specific modeled leaf.
  4. The client requests an invented path rather than the module-qualified YANG data path.

Explanation

Correct Answer

B:

This mechanism explains the reported observation, a RESTCONF payload deletes unrelated interface fields after a PUT update. The targeted response is to use a compatible PATCH for a partial change or provide a complete validated replacement; the expected confirming result is that unchanged interface leaves remain present after the intended update.

Incorrect Answers

A:

That mechanism fits a different symptom: the controller changes its schema revision and a RESTCONF automation starts receiving unknown-node errors. The reported condition instead points to full-resource replacement semantics were applied to a partial desired object.

C:

That mechanism fits a different symptom: a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf. The reported condition instead points to full-resource replacement semantics were applied to a partial desired object.

D:

That mechanism fits a different symptom: a RESTCONF read returns HTTP 404 although the device is reachable over HTTPS. The reported condition instead points to full-resource replacement semantics were applied to a partial desired object.

Question 144

A containerized platform engineering team is working on GitLab-based infrastructure deployment pipeline. A retrospective identifies: a RESTCONF payload deletes unrelated interface fields after a PUT update. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that unchanged interface leaves remain present after the intended update; flag recurrence if a RESTCONF payload deletes unrelated interface fields after a PUT update.
  2. Check that GET on the model-qualified path returns the expected structured resource; flag recurrence if a RESTCONF read returns HTTP 404 although the device is reachable over HTTPS.
  3. Check that requests match advertised module revisions and pass schema validation; flag recurrence if the controller changes its schema revision and a RESTCONF automation starts receiving unknown-node errors.
  4. Check that only the intended description field changes and sibling interface settings remain intact; flag recurrence if a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf.

Explanation

Correct Answer

A:

The check tests the restored condition, unchanged interface leaves remain present after the intended update, and explicitly flags a recurrence of a RESTCONF payload deletes unrelated interface fields after a PUT update.

Incorrect Answers

B:

This guard monitors a different regression trigger: a RESTCONF read returns HTTP 404 although the device is reachable over HTTPS. It does not directly validate the recovery condition, unchanged interface leaves remain present after the intended update.

C:

This guard monitors a different regression trigger: the controller changes its schema revision and a RESTCONF automation starts receiving unknown-node errors. It does not directly validate the recovery condition, unchanged interface leaves remain present after the intended update.

D:

This guard monitors a different regression trigger: a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf. It does not directly validate the recovery condition, unchanged interface leaves remain present after the intended update.

Question 145

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. During deployment, an HTTPS RESTCONF script is run with certificate verification disabled across production sites. Which action most directly addresses this specific network automation problem?

  1. Acquire the authorized replacement credential and retry over verified TLS.
  2. Send the appropriate application/yang-data+json content type and valid JSON body.
  3. Construct a schema-valid resource body with the correct list-key semantics.
  4. Install a trusted CA chain and verify hostname and certificate before making changes.

Explanation

Correct Answer

D:

The observed failure is: an HTTPS RESTCONF script is run with certificate verification disabled across production sites. The underlying cause is: the client cannot validate the device's presented TLS identity. Verify that the handshake validates the expected device identity without insecure TLS overrides.

Incorrect Answers

A:

This would address a different condition: a client sees HTTP 401 after password rotation, despite valid network reachability. Here, the actual issue is: the client cannot validate the device's presented TLS identity; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: a RESTCONF PATCH returns HTTP 415 for a valid interface name. Here, the actual issue is: the client cannot validate the device's presented TLS identity; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. Here, the actual issue is: the client cannot validate the device's presented TLS identity; it needs a scoped correction rather than this unrelated intervention.

Question 146

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. The team found that an HTTPS RESTCONF script is run with certificate verification disabled across production sites. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. The authorized identity can access the intended RESTCONF resource without 401.
  2. Validation and a follow-up GET show the intended single list element.
  3. The handshake validates the expected device identity without insecure TLS overrides.
  4. The API accepts the modeled payload and subsequent GET reflects the intended value.

Explanation

Correct Answer

C:

This evidence directly verifies the scoped correction, install a trusted CA chain and verify hostname and certificate before making changes, for the underlying issue: the client cannot validate the device's presented TLS identity. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from a client sees HTTP 401 after password rotation, despite valid network reachability, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the handshake validates the expected device identity without insecure TLS overrides.

B:

This would confirm recovery from a RESTCONF PATCH is rejected when a list item includes an unrecognized key value, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the handshake validates the expected device identity without insecure TLS overrides.

D:

This would confirm recovery from a RESTCONF PATCH returns HTTP 415 for a valid interface name, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the handshake validates the expected device identity without insecure TLS overrides.

Question 147

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. The team observes that an HTTPS RESTCONF script is run with certificate verification disabled across production sites. Which underlying mechanism best explains this failure?

  1. The client cannot validate the device's presented TLS identity.
  2. The request uses an unsupported media type for YANG-modeled data.
  3. The client omits a required YANG list key or uses a mismatched key name.
  4. The authentication credentials are stale rather than the YANG payload.

Explanation

Correct Answer

A:

This mechanism explains the reported observation, an HTTPS RESTCONF script is run with certificate verification disabled across production sites. The targeted response is to install a trusted CA chain and verify hostname and certificate before making changes; the expected confirming result is that the handshake validates the expected device identity without insecure TLS overrides.

Incorrect Answers

B:

That mechanism fits a different symptom: a RESTCONF PATCH returns HTTP 415 for a valid interface name. The reported condition instead points to the client cannot validate the device's presented TLS identity.

C:

That mechanism fits a different symptom: a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. The reported condition instead points to the client cannot validate the device's presented TLS identity.

D:

That mechanism fits a different symptom: a client sees HTTP 401 after password rotation, despite valid network reachability. The reported condition instead points to the client cannot validate the device's presented TLS identity.

Question 148

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. A retrospective identifies: an HTTPS RESTCONF script is run with certificate verification disabled across production sites. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that the authorized identity can access the intended RESTCONF resource without 401; flag recurrence if a client sees HTTP 401 after password rotation, despite valid network reachability.
  2. Check that the handshake validates the expected device identity without insecure TLS overrides; flag recurrence if an HTTPS RESTCONF script is run with certificate verification disabled across production sites.
  3. Check that the API accepts the modeled payload and subsequent GET reflects the intended value; flag recurrence if a RESTCONF PATCH returns HTTP 415 for a valid interface name.
  4. Check that validation and a follow-up GET show the intended single list element; flag recurrence if a RESTCONF PATCH is rejected when a list item includes an unrecognized key value.

Explanation

Correct Answer

B:

The check tests the restored condition, the handshake validates the expected device identity without insecure TLS overrides, and explicitly flags a recurrence of an HTTPS RESTCONF script is run with certificate verification disabled across production sites.

Incorrect Answers

A:

This guard monitors a different regression trigger: a client sees HTTP 401 after password rotation, despite valid network reachability. It does not directly validate the recovery condition, the handshake validates the expected device identity without insecure TLS overrides.

C:

This guard monitors a different regression trigger: a RESTCONF PATCH returns HTTP 415 for a valid interface name. It does not directly validate the recovery condition, the handshake validates the expected device identity without insecure TLS overrides.

D:

This guard monitors a different regression trigger: a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. It does not directly validate the recovery condition, the handshake validates the expected device identity without insecure TLS overrides.

Question 149

An electric utility network group is working on substation telemetry and critical management routing. During deployment, a RESTCONF list lookup returns no matching entry when a composite list key is incomplete. Which action most directly addresses this specific network automation problem?

  1. Request the supported YANG JSON representation and validate the response schema.
  2. Assign approved role privileges through the platform access-control policy.
  3. Compare existing state and select appropriate update semantics instead of blind POST.
  4. Build the list identifier from all schema-required keys with correct encoding.

Explanation

Correct Answer

D:

The observed failure is: a RESTCONF list lookup returns no matching entry when a composite list key is incomplete. The underlying cause is: the request omits one YANG-defined list key segment. Verify that the exact keyed entry can be read and updated without selecting other records.

Incorrect Answers

A:

This would address a different condition: a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. Here, the actual issue is: the request omits one YANG-defined list key segment; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: a RESTCONF configuration write returns HTTP 403 for a read-only service identity. Here, the actual issue is: the request omits one YANG-defined list key segment; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a VLAN create request returns 409 while a read shows the VLAN already exists. Here, the actual issue is: the request omits one YANG-defined list key segment; it needs a scoped correction rather than this unrelated intervention.

Question 150

An electric utility network group is working on substation telemetry and critical management routing. The team found that a RESTCONF list lookup returns no matching entry when a composite list key is incomplete. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. The exact keyed entry can be read and updated without selecting other records.
  2. The scoped service identity can write the approved path and remains denied elsewhere.
  3. The request returns a parsed YANG data object without content-negotiation errors.
  4. The existing VLAN is updated without creating a duplicate list item.

Explanation

Correct Answer

A:

This evidence directly verifies the scoped correction, build the list identifier from all schema-required keys with correct encoding, for the underlying issue: the request omits one YANG-defined list key segment. It should be checked against actual device or pipeline output.

Incorrect Answers

B:

This would confirm recovery from a RESTCONF configuration write returns HTTP 403 for a read-only service identity, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the exact keyed entry can be read and updated without selecting other records.

C:

This would confirm recovery from a RESTCONF data request returns HTTP 406 after the client asks for generic text/html, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the exact keyed entry can be read and updated without selecting other records.

D:

This would confirm recovery from a VLAN create request returns 409 while a read shows the VLAN already exists, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the exact keyed entry can be read and updated without selecting other records.