The answer is to verify that the sensor paths are correct and that the data is being generated. When troubleshooting model-driven telemetry with no data received, a connected destination with a stale “last data sent” timestamp indicates the telemetry pipeline is established but no telemetry data is flowing, which points to a sensor path or data-generation issue rather than a network or connectivity problem. On the Cisco DCCOR 350-601 exam, this scenario tests your understanding that gRPC telemetry relies on correctly defined sensor paths to push data; a common trap is assuming a successful ICMP reachability or a “connected” collector status guarantees data delivery. Remember the memory tip: “Connected does not mean collecting”—always validate the sensor path hierarchy and confirm the monitored interfaces are actively producing statistics before adjusting network or collector settings.
350-601 Automation Practice Question
This 350-601 practice question tests your understanding of automation. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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.
An organization is migrating from traditional SNMP monitoring to model-driven telemetry on their Nexus 9000 switches. They have configured a telemetry destination using gRPC and have defined sensor paths for interface statistics. After several hours, the collector (a Linux server running Telegraf) reports no data received. The engineer verifies that the switch can reach the collector via ICMP. On the switch, 'show telemetry data collector details' indicates the destination is 'connected', but the 'last data sent' timestamp is several hours old. Which action should the engineer take next?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Verify that the sensor paths are correct and that the data is being generated
The 'show telemetry data collector details' output shows the destination is 'connected' and the switch can reach the collector, ruling out network or connectivity issues. The stale 'last data sent' timestamp indicates the telemetry process is running but no data is being published, which typically means the configured sensor paths are not producing data—either because the paths are incorrect, the MIB objects are not supported, or the interfaces are not generating the expected statistics. Option C is correct because verifying the sensor paths and ensuring data generation addresses the root cause without unnecessary changes or reboots.
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.
✗
Change the transport protocol from gRPC to HTTP
Why it's wrong here
Would not fix missing data; might break other functionality.
✗
Reboot the switch to reset the telemetry process
Why it's wrong here
Unnecessary; the process is running.
✓
Verify that the sensor paths are correct and that the data is being generated
Why this is correct
Most likely cause: sensor path not matching actual data.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the telemetry sampling interval to reduce load
Why it's wrong here
Does not address why data is not sent at all.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that a 'connected' telemetry destination implies data is flowing, when in fact the connection state only reflects the gRPC session, not the subscription health—candidates may waste time on transport or connectivity fixes instead of verifying the sensor paths.
Detailed technical explanation
How to think about this question
Model-driven telemetry on Nexus 9000 uses YANG-modeled sensor paths (e.g., 'Cisco-NX-OS-device:system/interface-stats') to subscribe to data; if the path is misspelled, unsupported, or the interface is administratively down, no updates are published. The gRPC dial-out collector remains in 'connected' state because the TCP/gRPC session is established, but the subscription itself may be empty—checking 'show telemetry data collector details' and 'show telemetry sensor-group' can reveal if the sensor group has any active subscriptions. In real-world scenarios, engineers often forget that sensor paths must match the exact YANG module and that some statistics (e.g., per-interface counters) require the interface to be up and passing traffic.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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.
Automation — This question tests Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Verify that the sensor paths are correct and that the data is being generated — The 'show telemetry data collector details' output shows the destination is 'connected' and the switch can reach the collector, ruling out network or connectivity issues. The stale 'last data sent' timestamp indicates the telemetry process is running but no data is being published, which typically means the configured sensor paths are not producing data—either because the paths are incorrect, the MIB objects are not supported, or the interfaces are not generating the expected statistics. Option C is correct because verifying the sensor paths and ensuring data generation addresses the root cause without unnecessary changes or reboots.
What should I do if I get this 350-601 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 →
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.
This 350-601 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-601 exam.
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.
Sign in to join the discussion.