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 17

Question 160

An industrial robotics supplier is working on deterministic configuration and monitoring automation. A retrospective identifies: a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf. Which ongoing regression check best detects recurrence of this precise failure?

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

Explanation

Correct Answer

A:

The check tests the restored condition, only the intended description field changes and sibling interface settings remain intact, and explicitly flags a recurrence of a RESTCONF DELETE removes an entire interface subtree when the intent was to reset one description leaf.

Incorrect Answers

B:

This guard monitors a different regression trigger: an HTTPS RESTCONF script is run with certificate verification disabled across production sites. It does not directly validate the recovery condition, only the intended description field changes and sibling interface settings remain intact.

C:

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, only the intended description field changes and sibling interface settings remain intact.

D:

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, only the intended description field changes and sibling interface settings remain intact.

Question 161

A shipping-port operator is working on container-terminal wired and wireless infrastructure. During deployment, a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. Which action most directly addresses this specific network automation problem?

  1. Send the appropriate application/yang-data+json content type and valid JSON body.
  2. Construct a schema-valid resource body with the correct list-key semantics.
  3. Acquire the authorized replacement credential and retry over verified TLS.
  4. Build the list identifier from all schema-required keys with correct encoding.

Explanation

Correct Answer

B:

The observed failure is: a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. The underlying cause is: the client omits a required YANG list key or uses a mismatched key name. Verify that validation and a follow-up GET show the intended single list element.

Incorrect Answers

A:

This would address a different condition: a RESTCONF PATCH returns HTTP 415 for a valid interface name. Here, the actual issue is: the client omits a required YANG list key or uses a mismatched key name; it needs a scoped correction rather than this unrelated intervention.

C:

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 omits a required YANG list key or uses a mismatched key name; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: a RESTCONF list lookup returns no matching entry when a composite list key is incomplete. Here, the actual issue is: the client omits a required YANG list key or uses a mismatched key name; it needs a scoped correction rather than this unrelated intervention.

Question 162

A shipping-port operator is working on container-terminal wired and wireless infrastructure. The team found that a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Validation and a follow-up GET show the intended single list element.
  2. The exact keyed entry can be read and updated without selecting other records.
  3. The API accepts the modeled payload and subsequent GET reflects the intended value.
  4. The authorized identity can access the intended RESTCONF resource without 401.

Explanation

Correct Answer

A:

This evidence directly verifies the scoped correction, construct a schema-valid resource body with the correct list-key semantics, for the underlying issue: the client omits a required YANG list key or uses a mismatched key name. It should be checked against actual device or pipeline output.

Incorrect Answers

B:

This would confirm recovery from a RESTCONF list lookup returns no matching entry when a composite list key is incomplete, not necessarily from the reported incident. For the specified issue the relevant confirmation is: validation and a follow-up GET show the intended single list element.

C:

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: validation and a follow-up GET show the intended single list element.

D:

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: validation and a follow-up GET show the intended single list element.

Question 163

A shipping-port operator is working on container-terminal wired and wireless infrastructure. The team observes that a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. Which underlying mechanism best explains this failure?

  1. The request uses an unsupported media type for YANG-modeled data.
  2. The request omits one YANG-defined list key segment.
  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

C:

This mechanism explains the reported observation, a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. The targeted response is to construct a schema-valid resource body with the correct list-key semantics; the expected confirming result is that validation and a follow-up GET show the intended single list element.

Incorrect Answers

A:

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 omits a required YANG list key or uses a mismatched key name.

B:

That mechanism fits a different symptom: a RESTCONF list lookup returns no matching entry when a composite list key is incomplete. The reported condition instead points to the client omits a required YANG list key or uses a mismatched key name.

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 omits a required YANG list key or uses a mismatched key name.

Question 164

A shipping-port operator is working on container-terminal wired and wireless infrastructure. A retrospective identifies: a RESTCONF PATCH is rejected when a list item includes an unrecognized key value. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that the exact keyed entry can be read and updated without selecting other records; flag recurrence if a RESTCONF list lookup returns no matching entry when a composite list key is incomplete.
  2. 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.
  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

D:

The check tests the restored condition, validation and a follow-up GET show the intended single list element, and explicitly flags a recurrence of a RESTCONF PATCH is rejected when a list item includes an unrecognized key value.

Incorrect Answers

A:

This guard monitors a different regression trigger: a RESTCONF list lookup returns no matching entry when a composite list key is incomplete. It does not directly validate the recovery condition, validation and a follow-up GET show the intended single list element.

B:

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, validation and a follow-up GET show the intended single list element.

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, validation and a follow-up GET show the intended single list element.

Question 165

A large retail franchise is working on repeatable branch network configuration releases. During deployment, a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. Which action most directly addresses this specific network automation problem?

  1. Request the supported YANG JSON representation and validate the response schema.
  2. Filter writes to schema-writable leaves and read operational state separately.
  3. Assign approved role privileges through the platform access-control policy.
  4. Compare existing state and select appropriate update semantics instead of blind POST.

Explanation

Correct Answer

A:

The observed failure is: a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. The underlying cause is: the client's Accept header does not request a supported YANG data representation. Verify that the request returns a parsed YANG data object without content-negotiation errors.

Incorrect Answers

B:

This would address a different condition: a telemetry read using RESTCONF fails because an operational leaf is submitted as configuration. Here, the actual issue is: the client's Accept header does not request a supported YANG data representation; it needs a scoped correction rather than this unrelated intervention.

C:

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 client's Accept header does not request a supported YANG data representation; it needs a scoped correction rather than this unrelated intervention.

D:

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 client's Accept header does not request a supported YANG data representation; it needs a scoped correction rather than this unrelated intervention.

Question 166

A large retail franchise is working on repeatable branch network configuration releases. The team found that a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. The scoped service identity can write the approved path and remains denied elsewhere.
  2. Writes pass schema checks and operational data remains read-only.
  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

C:

This evidence directly verifies the scoped correction, request the supported YANG JSON representation and validate the response schema, for the underlying issue: the client's Accept header does not request a supported YANG data representation. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

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 request returns a parsed YANG data object without content-negotiation errors.

B:

This would confirm recovery from a telemetry read using RESTCONF fails because an operational leaf is submitted as configuration, not necessarily from the reported incident. For the specified issue the relevant confirmation is: the request returns a parsed YANG data object without content-negotiation errors.

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 request returns a parsed YANG data object without content-negotiation errors.

Question 167

A large retail franchise is working on repeatable branch network configuration releases. The team observes that a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. Which underlying mechanism best explains this failure?

  1. The caller lacks write authorization even though authentication succeeded.
  2. The client assumes create semantics for an existing list entry.
  3. The client confuses read-only operational state with writable config=true nodes.
  4. The client's Accept header does not request a supported YANG data representation.

Explanation

Correct Answer

D:

This mechanism explains the reported observation, a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. The targeted response is to request the supported YANG JSON representation and validate the response schema; the expected confirming result is that the request returns a parsed YANG data object without content-negotiation errors.

Incorrect Answers

A:

That mechanism fits a different symptom: a RESTCONF configuration write returns HTTP 403 for a read-only service identity. The reported condition instead points to the client's Accept header does not request a supported YANG data representation.

B:

That mechanism fits a different symptom: a VLAN create request returns 409 while a read shows the VLAN already exists. The reported condition instead points to the client's Accept header does not request a supported YANG data representation.

C:

That mechanism fits a different symptom: a telemetry read using RESTCONF fails because an operational leaf is submitted as configuration. The reported condition instead points to the client's Accept header does not request a supported YANG data representation.

Question 168

A large retail franchise is working on repeatable branch network configuration releases. A retrospective identifies: a RESTCONF data request returns HTTP 406 after the client asks for generic text/html. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that the existing VLAN is updated without creating a duplicate list item; flag recurrence if a VLAN create request returns 409 while a read shows the VLAN already exists.
  2. Check that the request returns a parsed YANG data object without content-negotiation errors; flag recurrence if a RESTCONF data request returns HTTP 406 after the client asks for generic text/html.
  3. 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.
  4. 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.

Explanation

Correct Answer

B:

The check tests the restored condition, the request returns a parsed YANG data object without content-negotiation errors, and explicitly flags a recurrence of a RESTCONF data request returns HTTP 406 after the client asks for generic text/html.

Incorrect Answers

A:

This guard monitors a different regression trigger: a VLAN create request returns 409 while a read shows the VLAN already exists. It does not directly validate the recovery condition, the request returns a parsed YANG data object without content-negotiation errors.

C:

This guard monitors a different regression trigger: a RESTCONF configuration write returns HTTP 403 for a read-only service identity. It does not directly validate the recovery condition, the request returns a parsed YANG data object without content-negotiation errors.

D:

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 request returns a parsed YANG data object without content-negotiation errors.

Question 169

A medical imaging provider is working on latency-sensitive site networking safeguards. During deployment, RESTCONF configuration appears correct but the client reads operational counters from the wrong datastore. Which action most directly addresses this specific network automation problem?

  1. Use a compatible PATCH for a partial change or provide a complete validated replacement.
  2. Serialize the value using its YANG-defined boolean data type.
  3. Query the model-defined operational state fields and distinguish them from configuration leaves.
  4. Resolve and target the exact YANG leaf and verify destructive scope before DELETE.

Explanation

Correct Answer

C:

The observed failure is: RESTCONF configuration appears correct but the client reads operational counters from the wrong datastore. The underlying cause is: configuration and state data are conflated in the modeled query. Verify that device responses distinguish intended configuration from real observed interface counters.

Incorrect Answers

A:

This would address a different condition: a RESTCONF payload deletes unrelated interface fields after a PUT update. Here, the actual issue is: configuration and state data are conflated in the modeled query; it needs a scoped correction rather than this unrelated intervention.

B:

This would address a different condition: a RESTCONF interface update fails after the engineer sends string 'true' for a boolean leaf. Here, the actual issue is: configuration and state data are conflated in the modeled query; it needs a scoped correction rather than this unrelated intervention.

D:

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: configuration and state data are conflated in the modeled query; it needs a scoped correction rather than this unrelated intervention.

Question 170

A medical imaging provider is working on latency-sensitive site networking safeguards. The team found that RESTCONF configuration appears correct but the client reads operational counters from the wrong datastore. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Device responses distinguish intended configuration from real observed interface counters.
  2. Schema validation and GET show a JSON boolean with the required state.
  3. Only the intended description field changes and sibling interface settings remain intact.
  4. Unchanged interface leaves remain present after the intended update.

Explanation

Correct Answer

A:

This evidence directly verifies the scoped correction, query the model-defined operational state fields and distinguish them from configuration leaves, for the underlying issue: configuration and state data are conflated in the modeled query. It should be checked against actual device or pipeline output.

Incorrect Answers

B:

This would confirm recovery from a RESTCONF interface update fails after the engineer sends string 'true' for a boolean leaf, not necessarily from the reported incident. For the specified issue the relevant confirmation is: device responses distinguish intended configuration from real observed interface counters.

C:

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: device responses distinguish intended configuration from real observed interface counters.

D:

This would confirm recovery from a RESTCONF payload deletes unrelated interface fields after a PUT update, not necessarily from the reported incident. For the specified issue the relevant confirmation is: device responses distinguish intended configuration from real observed interface counters.