Question 168 of 500
Automation and Quality of ServicemediumMultiple SelectObjective-mapped

Quick Answer

The correct answer is that model-driven telemetry uses a push model while SNMP primarily uses a pull model. This distinction is rooted in how each technology handles data collection: SNMP relies on a manager polling devices at intervals, which introduces CPU and network overhead that makes sub-second polling impractical, whereas model-driven telemetry (MDT) streams structured, YANG-modeled data directly from the device to a collector, enabling sub-second intervals for real-time monitoring. On the Cisco SPCOR / CCNP Service Provider Core 350-501 exam, this question tests your understanding of modern network monitoring paradigms, often appearing as a two-answer multiple-choice item where a common trap is confusing SNMP traps (a push exception) with SNMP’s primary pull behavior. Remember the memory tip: “SNMP pulls, MDT pushes—sub-second streams are the telemetry’s rush.”

350-501 Automation and Quality of Service Practice Question

This 350-501 practice question tests your understanding of automation and quality of service. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which TWO statements about model-driven telemetry compared to SNMP are correct? (Choose two.)

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Model-driven telemetry can stream data at sub-second intervals.

Model-driven telemetry (MDT) uses a push model where the network device streams structured data (e.g., YANG-modeled) to a collector, enabling sub-second intervals for real-time monitoring. This contrasts with SNMP's pull model, where the manager polls the device at intervals limited by CPU and network overhead, making sub-second polling impractical.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Model-driven telemetry uses UDP for transport by default.

    Why it's wrong here

    Typically uses TCP; gRPC or SSL.

  • Model-driven telemetry can stream data at sub-second intervals.

    Why this is correct

    Correct: Telemetry supports high-frequency streaming.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Model-driven telemetry uses a push model while SNMP primarily uses a pull model.

    Why this is correct

    Correct: Telemetry pushes data; SNMP is poll-based.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Model-driven telemetry only sends data on change (event-driven).

    Why it's wrong here

    It supports both periodic and on-change; not only on-change.

  • Model-driven telemetry uses MIBs to define data structures.

    Why it's wrong here

    MIBs are SNMP; telemetry uses YANG.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Cisco often tests the misconception that model-driven telemetry is purely event-driven, but it supports periodic streaming as a primary mode, and candidates confuse the transport protocol (UDP vs. TCP) because SNMP uses UDP by default.

Detailed technical explanation

How to think about this question

Model-driven telemetry leverages YANG models (e.g., from RFC 8344 for interfaces) and encoding like GPB or JSON over gRPC, allowing sub-second cadences (e.g., 100 ms) without the polling overhead of SNMP. Under the hood, the device pushes telemetry data via a persistent TCP connection, reducing CPU spikes and enabling near-real-time analytics for dynamic environments like SD-WAN or QoS monitoring.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the 350-501 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related 350-501 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free 350-501 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this 350-501 question test?

Automation and Quality of Service — This question tests Automation and Quality of Service — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Model-driven telemetry can stream data at sub-second intervals. — Model-driven telemetry (MDT) uses a push model where the network device streams structured data (e.g., YANG-modeled) to a collector, enabling sub-second intervals for real-time monitoring. This contrasts with SNMP's pull model, where the manager polls the device at intervals limited by CPU and network overhead, making sub-second polling impractical.

What should I do if I get this 350-501 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This 350-501 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-501 exam.