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 76

Question 750

A remote-campus networking team is working on high-latency links and intermittent API access. The team found that a gNMI subscription is rejected while the same device supports NETCONF reads. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Collector receives timestamped interface samples at the configured subscription cadence.
  2. Samples from both branches align when measured against the same time baseline.
  3. Distinct router interfaces appear as separate continuous metric series.
  4. A subscription using the advertised transport and encoding succeeds.

Explanation

Correct Answer

D:

This evidence directly verifies the scoped correction, discover supported capabilities and configure the proper streaming protocol and encoding, for the underlying issue: the telemetry transport or encoding requested is not advertised by the platform. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from a streaming dashboard shows interface utilization only at the moment polling is manually started, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a subscription using the advertised transport and encoding succeeds.

B:

This would confirm recovery from telemetry packets arrive but historical trends are misaligned between branches, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a subscription using the advertised transport and encoding succeeds.

C:

This would confirm recovery from the central dashboard aggregates two identically named interfaces from different routers as one series, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a subscription using the advertised transport and encoding succeeds.

Question 751

A remote-campus networking team is working on high-latency links and intermittent API access. The team observes that a gNMI subscription is rejected while the same device supports NETCONF reads. Which underlying mechanism best explains this failure?

  1. The telemetry design uses ad hoc CLI polling instead of a configured continuous subscription.
  2. Device and collector clocks are not synchronized to an authoritative time source.
  3. The telemetry transport or encoding requested is not advertised by the platform.
  4. Metric identity omits stable device and site labels.

Explanation

Correct Answer

C:

This mechanism explains the reported observation, a gNMI subscription is rejected while the same device supports NETCONF reads. The targeted response is to discover supported capabilities and configure the proper streaming protocol and encoding; the expected confirming result is that a subscription using the advertised transport and encoding succeeds.

Incorrect Answers

A:

That mechanism fits a different symptom: a streaming dashboard shows interface utilization only at the moment polling is manually started. The reported condition instead points to the telemetry transport or encoding requested is not advertised by the platform.

B:

That mechanism fits a different symptom: telemetry packets arrive but historical trends are misaligned between branches. The reported condition instead points to the telemetry transport or encoding requested is not advertised by the platform.

D:

That mechanism fits a different symptom: the central dashboard aggregates two identically named interfaces from different routers as one series. The reported condition instead points to the telemetry transport or encoding requested is not advertised by the platform.

Question 752

A remote-campus networking team is working on high-latency links and intermittent API access. A retrospective identifies: a gNMI subscription is rejected while the same device supports NETCONF reads. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that distinct router interfaces appear as separate continuous metric series; flag recurrence if the central dashboard aggregates two identically named interfaces from different routers as one series.
  2. Check that a subscription using the advertised transport and encoding succeeds; flag recurrence if a gNMI subscription is rejected while the same device supports NETCONF reads.
  3. Check that samples from both branches align when measured against the same time baseline; flag recurrence if telemetry packets arrive but historical trends are misaligned between branches.
  4. Check that collector receives timestamped interface samples at the configured subscription cadence; flag recurrence if a streaming dashboard shows interface utilization only at the moment polling is manually started.

Explanation

Correct Answer

B:

The check tests the restored condition, a subscription using the advertised transport and encoding succeeds, and explicitly flags a recurrence of a gNMI subscription is rejected while the same device supports NETCONF reads.

Incorrect Answers

A:

This guard monitors a different regression trigger: the central dashboard aggregates two identically named interfaces from different routers as one series. It does not directly validate the recovery condition, a subscription using the advertised transport and encoding succeeds.

C:

This guard monitors a different regression trigger: telemetry packets arrive but historical trends are misaligned between branches. It does not directly validate the recovery condition, a subscription using the advertised transport and encoding succeeds.

D:

This guard monitors a different regression trigger: a streaming dashboard shows interface utilization only at the moment polling is manually started. It does not directly validate the recovery condition, a subscription using the advertised transport and encoding succeeds.

Question 753

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. During deployment, telemetry data exists but charts contain sporadic gaps after the collector process restarts. Which action most directly addresses this specific network automation problem?

  1. Enable supported queue persistence and resilient collector deployment.
  2. Authorize the exact destination and telemetry transport over the managed path.
  3. Size collectors and queues for burst traffic and implement bounded backpressure and alerting.
  4. Use an appropriately supported on-change subscription or event-triggered path for the state leaf.

Explanation

Correct Answer

A:

The observed failure is: telemetry data exists but charts contain sporadic gaps after the collector process restarts. The underlying cause is: the collector has no durable buffering or restart recovery strategy. Verify that restart testing retains or explicitly accounts for samples without unexplained gaps.

Incorrect Answers

B:

This would address a different condition: a telemetry dial-out stream fails after management ACL tightening. Here, the actual issue is: the collector has no durable buffering or restart recovery strategy; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a telemetry collector drops bursts of BGP updates while its CPU remains saturated. Here, the actual issue is: the collector has no durable buffering or restart recovery strategy; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: link-state alarms lag behind faults even though the collector is healthy. Here, the actual issue is: the collector has no durable buffering or restart recovery strategy; it needs a scoped correction rather than this unrelated intervention.

Question 754

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. The team found that telemetry data exists but charts contain sporadic gaps after the collector process restarts. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Replay tests show expected sample counts without silent drop during bounded bursts.
  2. A simulated link transition reaches the collector within the agreed detection objective.
  3. Restart testing retains or explicitly accounts for samples without unexplained gaps.
  4. The established secure device-to-collector session resumes without opening unrelated endpoints.

Explanation

Correct Answer

C:

This evidence directly verifies the scoped correction, enable supported queue persistence and resilient collector deployment, for the underlying issue: the collector has no durable buffering or restart recovery strategy. It should be checked against actual device or pipeline output.

Incorrect Answers

A:

This would confirm recovery from a telemetry collector drops bursts of BGP updates while its CPU remains saturated, not necessarily from the reported incident. For the specified issue the relevant confirmation is: restart testing retains or explicitly accounts for samples without unexplained gaps.

B:

This would confirm recovery from link-state alarms lag behind faults even though the collector is healthy, not necessarily from the reported incident. For the specified issue the relevant confirmation is: restart testing retains or explicitly accounts for samples without unexplained gaps.

D:

This would confirm recovery from a telemetry dial-out stream fails after management ACL tightening, not necessarily from the reported incident. For the specified issue the relevant confirmation is: restart testing retains or explicitly accounts for samples without unexplained gaps.

Question 755

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. The team observes that telemetry data exists but charts contain sporadic gaps after the collector process restarts. Which underlying mechanism best explains this failure?

  1. A high-period sampled telemetry subscription is used for a change event that needs prompt detection.
  2. The pipeline has insufficient ingestion buffers or backpressure handling for the event rate.
  3. The device's outbound collector destination is no longer permitted.
  4. The collector has no durable buffering or restart recovery strategy.

Explanation

Correct Answer

D:

This mechanism explains the reported observation, telemetry data exists but charts contain sporadic gaps after the collector process restarts. The targeted response is to enable supported queue persistence and resilient collector deployment; the expected confirming result is that restart testing retains or explicitly accounts for samples without unexplained gaps.

Incorrect Answers

A:

That mechanism fits a different symptom: link-state alarms lag behind faults even though the collector is healthy. The reported condition instead points to the collector has no durable buffering or restart recovery strategy.

B:

That mechanism fits a different symptom: a telemetry collector drops bursts of BGP updates while its CPU remains saturated. The reported condition instead points to the collector has no durable buffering or restart recovery strategy.

C:

That mechanism fits a different symptom: a telemetry dial-out stream fails after management ACL tightening. The reported condition instead points to the collector has no durable buffering or restart recovery strategy.

Question 756

A retail banking SOC is working on read-only network diagnostics and constrained agent tools. A retrospective identifies: telemetry data exists but charts contain sporadic gaps after the collector process restarts. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that replay tests show expected sample counts without silent drop during bounded bursts; flag recurrence if a telemetry collector drops bursts of BGP updates while its CPU remains saturated.
  2. Check that restart testing retains or explicitly accounts for samples without unexplained gaps; flag recurrence if telemetry data exists but charts contain sporadic gaps after the collector process restarts.
  3. Check that a simulated link transition reaches the collector within the agreed detection objective; flag recurrence if link-state alarms lag behind faults even though the collector is healthy.
  4. Check that the established secure device-to-collector session resumes without opening unrelated endpoints; flag recurrence if a telemetry dial-out stream fails after management ACL tightening.

Explanation

Correct Answer

B:

The check tests the restored condition, restart testing retains or explicitly accounts for samples without unexplained gaps, and explicitly flags a recurrence of telemetry data exists but charts contain sporadic gaps after the collector process restarts.

Incorrect Answers

A:

This guard monitors a different regression trigger: a telemetry collector drops bursts of BGP updates while its CPU remains saturated. It does not directly validate the recovery condition, restart testing retains or explicitly accounts for samples without unexplained gaps.

C:

This guard monitors a different regression trigger: link-state alarms lag behind faults even though the collector is healthy. It does not directly validate the recovery condition, restart testing retains or explicitly accounts for samples without unexplained gaps.

D:

This guard monitors a different regression trigger: a telemetry dial-out stream fails after management ACL tightening. It does not directly validate the recovery condition, restart testing retains or explicitly accounts for samples without unexplained gaps.

Question 757

A government service-delivery team is working on segmented infrastructure spanning two departments. During deployment, high-cardinality per-flow labels exhaust the monitoring system's index. Which action most directly addresses this specific network automation problem?

  1. Discover the platform's supported telemetry paths and select compatible model namespaces.
  2. Restrict metric labels and sampling scope to approved operational dimensions.
  3. Discover supported capabilities and configure the proper streaming protocol and encoding.
  4. Add stable device identity and site dimensions to series labels while avoiding excess cardinality.

Explanation

Correct Answer

B:

The observed failure is: high-cardinality per-flow labels exhaust the monitoring system's index. The underlying cause is: the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics. Verify that cardinality and resource use remain within monitoring budgets under load.

Incorrect Answers

A:

This would address a different condition: collectors see telemetry for uplinks but not for the newly installed device family. Here, the actual issue is: the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics; it needs a scoped correction rather than this unrelated intervention.

C:

This would address a different condition: a gNMI subscription is rejected while the same device supports NETCONF reads. Here, the actual issue is: the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics; it needs a scoped correction rather than this unrelated intervention.

D:

This would address a different condition: the central dashboard aggregates two identically named interfaces from different routers as one series. Here, the actual issue is: the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics; it needs a scoped correction rather than this unrelated intervention.

Question 758

A government service-delivery team is working on segmented infrastructure spanning two departments. The team found that high-cardinality per-flow labels exhaust the monitoring system's index. After remediation, which observation is the strongest evidence that this particular fault is resolved?

  1. Cardinality and resource use remain within monitoring budgets under load.
  2. Distinct router interfaces appear as separate continuous metric series.
  3. A subscription using the advertised transport and encoding succeeds.
  4. The collector parses the new platform's interface data under the validated schema.

Explanation

Correct Answer

A:

This evidence directly verifies the scoped correction, restrict metric labels and sampling scope to approved operational dimensions, for the underlying issue: the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics. It should be checked against actual device or pipeline output.

Incorrect Answers

B:

This would confirm recovery from the central dashboard aggregates two identically named interfaces from different routers as one series, not necessarily from the reported incident. For the specified issue the relevant confirmation is: cardinality and resource use remain within monitoring budgets under load.

C:

This would confirm recovery from a gNMI subscription is rejected while the same device supports NETCONF reads, not necessarily from the reported incident. For the specified issue the relevant confirmation is: cardinality and resource use remain within monitoring budgets under load.

D:

This would confirm recovery from collectors see telemetry for uplinks but not for the newly installed device family, not necessarily from the reported incident. For the specified issue the relevant confirmation is: cardinality and resource use remain within monitoring budgets under load.

Question 759

A government service-delivery team is working on segmented infrastructure spanning two departments. The team observes that high-cardinality per-flow labels exhaust the monitoring system's index. Which underlying mechanism best explains this failure?

  1. The configured sensor path references a schema absent from the new platform's advertised YANG modules.
  2. The telemetry transport or encoding requested is not advertised by the platform.
  3. The sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics.
  4. Metric identity omits stable device and site labels.

Explanation

Correct Answer

C:

This mechanism explains the reported observation, high-cardinality per-flow labels exhaust the monitoring system's index. The targeted response is to restrict metric labels and sampling scope to approved operational dimensions; the expected confirming result is that cardinality and resource use remain within monitoring budgets under load.

Incorrect Answers

A:

That mechanism fits a different symptom: collectors see telemetry for uplinks but not for the newly installed device family. The reported condition instead points to the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics.

B:

That mechanism fits a different symptom: a gNMI subscription is rejected while the same device supports NETCONF reads. The reported condition instead points to the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics.

D:

That mechanism fits a different symptom: the central dashboard aggregates two identically named interfaces from different routers as one series. The reported condition instead points to the sensor policy exports unnecessary per-connection dimensions instead of bounded operational metrics.

Question 760

A government service-delivery team is working on segmented infrastructure spanning two departments. A retrospective identifies: high-cardinality per-flow labels exhaust the monitoring system's index. Which ongoing regression check best detects recurrence of this precise failure?

  1. Check that the collector parses the new platform's interface data under the validated schema; flag recurrence if collectors see telemetry for uplinks but not for the newly installed device family.
  2. Check that distinct router interfaces appear as separate continuous metric series; flag recurrence if the central dashboard aggregates two identically named interfaces from different routers as one series.
  3. Check that a subscription using the advertised transport and encoding succeeds; flag recurrence if a gNMI subscription is rejected while the same device supports NETCONF reads.
  4. Check that cardinality and resource use remain within monitoring budgets under load; flag recurrence if high-cardinality per-flow labels exhaust the monitoring system's index.

Explanation

Correct Answer

D:

The check tests the restored condition, cardinality and resource use remain within monitoring budgets under load, and explicitly flags a recurrence of high-cardinality per-flow labels exhaust the monitoring system's index.

Incorrect Answers

A:

This guard monitors a different regression trigger: collectors see telemetry for uplinks but not for the newly installed device family. It does not directly validate the recovery condition, cardinality and resource use remain within monitoring budgets under load.

B:

This guard monitors a different regression trigger: the central dashboard aggregates two identically named interfaces from different routers as one series. It does not directly validate the recovery condition, cardinality and resource use remain within monitoring budgets under load.

C:

This guard monitors a different regression trigger: a gNMI subscription is rejected while the same device supports NETCONF reads. It does not directly validate the recovery condition, cardinality and resource use remain within monitoring budgets under load.