A redpoll-fen IoT farm emits thousands of temperature readings per second for analytics, and a teammate creates an Event Grid topic. Which service should carry that telemetry stream instead?
Select an answer to reveal the explanation.
Short Explanation
Discrete reactions versus firehose telemetry—don’t confuse them. Stream the temperatures through Event Hubs and save Event Grid for “something happened” events.
Full Explanation
Thousands of temperature readings per second for analytics is a high-volume telemetry stream. Event Hubs is built for that append-only firehose with multiple independent readers. Event Grid should remain for discrete reactions (“something happened”), so the redpoll-fen farm should carry sensor streams on Event Hubs rather than publishing each reading as an Event Grid reaction forever.
Keeping Event Grid and publishing each reading as a discrete reaction topic forever fails scale and cost characteristics: Event Grid is optimized for discrete event routing, not continuous multi-thousand-per-second sensor firehoses.
Queue Storage alone as the analytics firehose of record fails throughput and fan-out patterns that Event Hubs provides for streaming analytics consumers.
Microsoft Graph change notifications for sensor millivolts fails because Graph notifications track Graph resources, not IoT telemetry streams.
Exam caveat: you can still raise discrete alerts (threshold crossed) on Event Grid while the raw stream lives on Event Hubs—do not treat the services as mutually exclusive for every signal type. Operational check: send a high-rate test stream to Event Hubs, attach an analytics consumer group, and confirm Event Grid is reserved for sparse municipal reaction events.