300-635 · Question #24
During the process of starting a Python network telemetry collector, which command starts the Cisco bigmuddy-network-telemetry-collector from GitHub?
The correct answer is B. telemetry-receiver.py --ip-address <addr> --port <port>. Option B is correct because telemetry-receiver.py is the actual Python script included in the Cisco bigmuddy-network-telemetry-collector repository, and it accepts --ip-address and --port flags to specify where the collector listens for incoming telemetry streams - these are…
Question
Options
- Amodel driven telemetry
- Btelemetry-receiver.py --ip-address <addr> --port <port>
- Ctelemetry-receiver.py --destination <port> --url <url>
- Dstreaming telemetry
How the community answered
(24 responses)- B92% (22)
- C4% (1)
- D4% (1)
Explanation
Option B is correct because telemetry-receiver.py is the actual Python script included in the Cisco bigmuddy-network-telemetry-collector repository, and it accepts --ip-address and --port flags to specify where the collector listens for incoming telemetry streams - these are the standard parameters needed to bind a receiver to a network socket.
Why the distractors are wrong:
- A ("model driven telemetry") and D ("streaming telemetry") are technology concepts or Cisco IOS configuration keywords, not executable commands - you'd type these in a router's CLI to configure the sending side, not to start a collector.
- C uses
--destinationand--url, which are not the correct flags for this script; these sound more like parameters for an HTTP-based forwarder or a different tool entirely.
Memory tip: Think "receiver needs an address and a port to listen on" - just like any server socket. The --ip-address / --port pairing maps directly to how you'd bind any Python socket server, making option B the only choice that makes technical sense for starting a listener.
Topics
Community Discussion
No community discussion yet for this question.