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 89

Question 880

A containerized platform engineering team is working on GitLab-based infrastructure deployment pipeline. A retrospective identifies: a pyATS validation run uses an unrestricted admin account for simple show commands. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that the diff identifies only intended OSPF adjacency changes; flag recurrence if a pyATS post-change check cannot determine whether the OSPF neighbor state regressed.
  2. Check that required checks pass with limited permissions and no elevated credential exposure; flag recurrence if a pyATS validation run uses an unrestricted admin account for simple show commands.
  3. Check that replayed normal traffic variation does not produce false configuration-regression alarms; flag recurrence if pyATS can parse route summaries but compares changing counters as if they were stable config.
  4. Check that expected adjacency reaches the accepted state before the deadline; flag recurrence if a post-deploy pyATS job runs before routing protocols finish converging.

Explanation

Correct Answer

B:

The check tests the restored condition, required checks pass with limited permissions and no elevated credential exposure, and explicitly flags a recurrence of a pyATS validation run uses an unrestricted admin account for simple show commands.

Incorrect Answers

A:

This guard monitors a different regression trigger: a pyATS post-change check cannot determine whether the OSPF neighbor state regressed. It does not directly validate the recovery condition, required checks pass with limited permissions and no elevated credential exposure.

C:

This guard monitors a different regression trigger: pyATS can parse route summaries but compares changing counters as if they were stable config. It does not directly validate the recovery condition, required checks pass with limited permissions and no elevated credential exposure.

D:

This guard monitors a different regression trigger: a post-deploy pyATS job runs before routing protocols finish converging. It does not directly validate the recovery condition, required checks pass with limited permissions and no elevated credential exposure.

Question 881

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. During deployment, a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. Which action most directly addresses this specific network automation problem?

  1. Generate a new CSR with correct subject alternative names and obtain CA signature.
  2. Revoke compromised credentials and store new keys only in restricted protected storage.
  3. Match the certificate to the original private key and protect the key in an approved store.
  4. Restore verify-on TLS behavior with a controlled CA bundle and hostname check.

Explanation

Correct Answer

A:

The observed failure is: a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. The underlying cause is: the certificate SAN does not include the DNS name clients actually use. Verify that TLS hostname verification succeeds for every approved client name.

Incorrect Answers

B:

This would address a different condition: a team uploads a private TLS key to an unrestricted repository along with the public certificate. Here, the actual issue is: the certificate SAN does not include the DNS name clients actually use; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: the CSR generated for a device contains the intended DNS name but signature validation fails. Here, the actual issue is: the certificate SAN does not include the DNS name clients actually use; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: a client bypasses TLS errors by disabling certificate validation in a Python requests session. Here, the actual issue is: the certificate SAN does not include the DNS name clients actually use; it needs a scoped correction rather than this unrelated intervention.

Question 882

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. The team found that a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. The service handshake proves possession of the matching private key.
  2. Invalid server identities are rejected and valid CA-signed endpoints work.
  3. Repository scan is clean and TLS service uses the rotated protected key.
  4. TLS hostname verification succeeds for every approved client name.

Explanation

Correct Answer

D:

This evidence directly verifies the scoped correction, generate a new CSR with correct subject alternative names and obtain CA signature, for the underlying issue: the certificate SAN does not include the DNS name clients actually use. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from the CSR generated for a device contains the intended DNS name but signature validation fails, not necessarily from the reported incident. For the specified issue the relevant confirmation is: TLS hostname verification succeeds for every approved client name.

B:

This would confirm recovery from a client bypasses TLS errors by disabling certificate validation in a Python requests session, not necessarily from the reported incident. For the specified issue the relevant confirmation is: TLS hostname verification succeeds for every approved client name.

C:

This would confirm recovery from a team uploads a private TLS key to an unrestricted repository along with the public certificate, not necessarily from the reported incident. For the specified issue the relevant confirmation is: TLS hostname verification succeeds for every approved client name.

Question 883

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. The team observes that a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. Which underlying mechanism best explains this failure?

  1. The deployment combines the signed certificate with a different private key.
  2. The certificate SAN does not include the DNS name clients actually use.
  3. Private-key handling lacks access controls and separation from distributable certificate material.
  4. Encryption without server authentication leaves the client vulnerable to impersonation.

Explanation

Correct Answer

B:

This mechanism explains the reported observation, a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. The targeted response is to generate a new CSR with correct subject alternative names and obtain CA signature; the expected confirming result is that TLS hostname verification succeeds for every approved client name.

Incorrect Answers

A:

That mechanism fits a different symptom: the CSR generated for a device contains the intended DNS name but signature validation fails. The reported condition instead points to the certificate SAN does not include the DNS name clients actually use.

C:

That mechanism fits a different symptom: a team uploads a private TLS key to an unrestricted repository along with the public certificate. The reported condition instead points to the certificate SAN does not include the DNS name clients actually use.

D:

That mechanism fits a different symptom: a client bypasses TLS errors by disabling certificate validation in a Python requests session. The reported condition instead points to the certificate SAN does not include the DNS name clients actually use.

Question 884

A cloud-connected stadium operator is working on high-volume API telemetry and configuration pushes. A retrospective identifies: a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that repository scan is clean and TLS service uses the rotated protected key; flag recurrence if a team uploads a private TLS key to an unrestricted repository along with the public certificate.
  2. Check that invalid server identities are rejected and valid CA-signed endpoints work; flag recurrence if a client bypasses TLS errors by disabling certificate validation in a Python requests session.
  3. Check that TLS hostname verification succeeds for every approved client name; flag recurrence if a controller's HTTPS endpoint is rejected by browsers because its certificate names another host.
  4. Check that the service handshake proves possession of the matching private key; flag recurrence if the CSR generated for a device contains the intended DNS name but signature validation fails.

Explanation

Correct Answer

C:

The check tests the restored condition, TLS hostname verification succeeds for every approved client name, and explicitly flags a recurrence of a controller's HTTPS endpoint is rejected by browsers because its certificate names another host.

Incorrect Answers

A:

This guard monitors a different regression trigger: a team uploads a private TLS key to an unrestricted repository along with the public certificate. It does not directly validate the recovery condition, TLS hostname verification succeeds for every approved client name.

B:

This guard monitors a different regression trigger: a client bypasses TLS errors by disabling certificate validation in a Python requests session. It does not directly validate the recovery condition, TLS hostname verification succeeds for every approved client name.

D:

This guard monitors a different regression trigger: the CSR generated for a device contains the intended DNS name but signature validation fails. It does not directly validate the recovery condition, TLS hostname verification succeeds for every approved client name.

Question 885

An electric utility network group is working on substation telemetry and critical management routing. During deployment, an internal collector rejects a valid leaf certificate as untrusted. Which action most directly addresses this specific network automation problem?

  1. Put the actual service IP in the IP-type SAN or use the approved DNS hostname.
  2. Deploy the proper CA-issued leaf and intermediate chain without replacing root trust indiscriminately.
  3. Issue and deploy node-appropriate trusted certificates across all active endpoints.
  4. Monitor expiry and rotate CA-issued certificates before the defined renewal threshold.

Explanation

Correct Answer

B:

The observed failure is: an internal collector rejects a valid leaf certificate as untrusted. The underlying cause is: the server omits a required intermediate certificate from its presented chain. Verify that a clean trusted client validates the full certificate chain.

Incorrect Answers

A:

This would address a different condition: a certificate request contains an IP address in CN but clients connect by IP and fail validation. Here, the actual issue is: the server omits a required intermediate certificate from its presented chain; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a high-availability controller cluster accepts TLS on one node but rejects it on another. Here, the actual issue is: the server omits a required intermediate certificate from its presented chain; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: an automation API goes offline when its only TLS certificate expires during a holiday. Here, the actual issue is: the server omits a required intermediate certificate from its presented chain; it needs a scoped correction rather than this unrelated intervention.

Question 886

An electric utility network group is working on substation telemetry and critical management routing. The team found that an internal collector rejects a valid leaf certificate as untrusted. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. A scheduled rotation preserves secure API access without expired-certificate errors.
  2. A TLS client validates the chosen address against the SAN successfully.
  3. Failover testing preserves trusted TLS to every active cluster endpoint.
  4. A clean trusted client validates the full certificate chain.

Explanation

Correct Answer

D:

This evidence directly verifies the scoped correction, deploy the proper CA-issued leaf and intermediate chain without replacing root trust indiscriminately, for the underlying issue: the server omits a required intermediate certificate from its presented chain. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from an automation API goes offline when its only TLS certificate expires during a holiday, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a clean trusted client validates the full certificate chain.

B:

This would confirm recovery from a certificate request contains an IP address in CN but clients connect by IP and fail validation, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a clean trusted client validates the full certificate chain.

C:

This would confirm recovery from a high-availability controller cluster accepts TLS on one node but rejects it on another, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a clean trusted client validates the full certificate chain.

Question 887

An electric utility network group is working on substation telemetry and critical management routing. The team observes that an internal collector rejects a valid leaf certificate as untrusted. Which underlying mechanism best explains this failure?

  1. Cluster members have inconsistent certificate chain or host identity configuration.
  2. No renewal monitoring or staged certificate rotation exists.
  3. The server omits a required intermediate certificate from its presented chain.
  4. IP-based identities are not encoded as IP-address SAN entries.

Explanation

Correct Answer

C:

This mechanism explains the reported observation, an internal collector rejects a valid leaf certificate as untrusted. The targeted response is to deploy the proper CA-issued leaf and intermediate chain without replacing root trust indiscriminately; the expected confirming result is that a clean trusted client validates the full certificate chain.

Incorrect Answers

A:

That mechanism fits a different symptom: a high-availability controller cluster accepts TLS on one node but rejects it on another. The reported condition instead points to the server omits a required intermediate certificate from its presented chain.

B:

That mechanism fits a different symptom: an automation API goes offline when its only TLS certificate expires during a holiday. The reported condition instead points to the server omits a required intermediate certificate from its presented chain.

D:

That mechanism fits a different symptom: a certificate request contains an IP address in CN but clients connect by IP and fail validation. The reported condition instead points to the server omits a required intermediate certificate from its presented chain.

Question 888

An electric utility network group is working on substation telemetry and critical management routing. A retrospective identifies: an internal collector rejects a valid leaf certificate as untrusted. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that a clean trusted client validates the full certificate chain; flag recurrence if an internal collector rejects a valid leaf certificate as untrusted.
  2. 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.
  3. Check that a scheduled rotation preserves secure API access without expired-certificate errors; flag recurrence if an automation API goes offline when its only TLS certificate expires during a holiday.
  4. 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.

Explanation

Correct Answer

A:

The check tests the restored condition, a clean trusted client validates the full certificate chain, and explicitly flags a recurrence of an internal collector rejects a valid leaf certificate as untrusted.

Incorrect Answers

B:

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, a clean trusted client validates the full certificate chain.

C:

This guard monitors a different regression trigger: an automation API goes offline when its only TLS certificate expires during a holiday. It does not directly validate the recovery condition, a clean trusted client validates the full certificate chain.

D:

This guard monitors a different regression trigger: a high-availability controller cluster accepts TLS on one node but rejects it on another. It does not directly validate the recovery condition, a clean trusted client validates the full certificate chain.

Question 889

A municipal water operator is working on audited configuration changes for utility links. During deployment, a new automation server presents a self-signed certificate in production. Which action most directly addresses this specific network automation problem?

  1. Generate a new CSR with correct subject alternative names and obtain CA signature.
  2. Generate a private key and CSR, complete required CA validation, then deploy the signed chain.
  3. Install the approved CA trust chain after verifying organizational trust policy.
  4. Revoke compromised credentials and store new keys only in restricted protected storage.

Explanation

Correct Answer

B:

The observed failure is: a new automation server presents a self-signed certificate in production. The underlying cause is: the deployment skipped the organization CA issuance process. Verify that an authorized client establishes authenticated TLS using the approved trust anchors.

Incorrect Answers

A:

This would address a different condition: a controller's HTTPS endpoint is rejected by browsers because its certificate names another host. Here, the actual issue is: the deployment skipped the organization CA issuance process; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a controller certificate is signed by a CA unknown to the enterprise trust policy. Here, the actual issue is: the deployment skipped the organization CA issuance process; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: a team uploads a private TLS key to an unrestricted repository along with the public certificate. Here, the actual issue is: the deployment skipped the organization CA issuance process; it needs a scoped correction rather than this unrelated intervention.

Question 890

A municipal water operator is working on audited configuration changes for utility links. The team found that a new automation server presents a self-signed certificate in production. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. An authorized client establishes authenticated TLS using the approved trust anchors.
  2. Only certificates anchored to trusted CA roots are accepted.
  3. TLS hostname verification succeeds for every approved client name.
  4. Repository scan is clean and TLS service uses the rotated protected key.

Explanation

Correct Answer

A:

This evidence directly verifies the scoped correction, generate a private key and CSR, complete required CA validation, then deploy the signed chain, for the underlying issue: the deployment skipped the organization CA issuance process. It should be checked against actual device or pipeline output.

Incorrect Answers

B:

This would confirm recovery from a controller certificate is signed by a CA unknown to the enterprise trust policy, not necessarily from the reported incident. For the specified issue the relevant confirmation is: an authorized client establishes authenticated TLS using the approved trust anchors.

C:

This would confirm recovery from a controller's HTTPS endpoint is rejected by browsers because its certificate names another host, not necessarily from the reported incident. For the specified issue the relevant confirmation is: an authorized client establishes authenticated TLS using the approved trust anchors.

D:

This would confirm recovery from a team uploads a private TLS key to an unrestricted repository along with the public certificate, not necessarily from the reported incident. For the specified issue the relevant confirmation is: an authorized client establishes authenticated TLS using the approved trust anchors.