Streetlight controllers report status every minute with no operator in the loop. What source class is that telemetry?
Select an answer to reveal the explanation.
Short Explanation
Lights phoning home on a timer is machines chatting with machines. Nobody is on the call. That is textbook machine-to-machine telemetry for Big Data pipelines.
Full Explanation
Machine-to-machine (M2M) sources are automated device-to-system or device-to-device exchanges without a human composing each message. Streetlight controllers reporting status every minute with no operator in the loop illustrate high-Velocity M2M telemetry. Municipal IoT programs rely heavily on this class for civic infrastructure health.
Calling the telemetry person-to-person hotline transcripts fails by concept: no human conversation is composing each status. Calling it person-to-machine only when a resident flips a light switch online fails by concept: autonomous controller heartbeats are M2M, not resident form clicks. Calling it manual survey responses entered by field crews fails by concept: surveys are human-entered, not automated minute heartbeats.
Exam caveat: Automated device status without per-message human authorship is M2M—distinguish it from P2P transcripts and P2M clicks.
Operational check: Inventory streetlight heartbeats as M2M, size streaming ingest for minute-level Velocity, and keep crew surveys in a separate human-entered source class. Document residual risk for civic operators and revisit after the next production change window. Confirm owners, SLAs, and rollback criteria in the runbook before go-live.