Which Azure Service Processes IoT Edge MQTT Data at Lowest Cost?
You have a production line that is monitored by using IoT devices. The devices use Message Queuing Telemetry Transport (MQTT) to transport monitoring data. You plan to deploy Azure IoT Edge runtimes in containers to process the messages. You need to recommend a cloud service solution that can process and analyze the data in Azure. The solution must minimize costs. What should you include in the recommendation?
Community Insight
The key test is that Azure IoT Edge is a standard-tier IoT Hub capability; the trap is selecting Event Hubs because it is a familiar low-cost telemetry ingestion service.
This AZ-305 question tests which Azure service ingests and processes MQTT telemetry from IoT Edge containers at minimum cost. The answer is Azure IoT Hub standard tier, the lowest IoT Hub tier that supports IoT Edge modules and routing.
The common wrong choice is Azure Event Hubs standard tier, since it is a low-cost streaming service, but it does not provide the IoT Edge device lifecycle and module management that the scenario requires.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure IoT Edge runtimes and modules are deployed and managed through IoT Hub, and Microsoft documents IoT Edge support only in the standard tier. Standard tier also supports MQTT ingestion and message routing, so the edge containers can process monitoring data and forward results into Azure without adding a separate ingestion service. Because basic tier cannot host the edge deployment at all, standard tier is the lowest-cost IoT Hub option that satisfies the mandatory requirement. The community note from gpais reinforces this by pointing to the IoT Hub scaling table where edge support differentiates the tiers.Why the Other Options Are Wrong
Azure Event Hubs standard tier is a capable telemetry stream service, but it is not the control plane for IoT Edge runtimes or module deployment, so it does not meet the edge requirement and would add unnecessary cost. Azure IoT Hub basic tier is cheaper but explicitly excludes IoT Edge, making it a trap when cost is emphasized. Azure Event Hubs premium tier costs more than standard and still lacks IoT Edge management, so it is both over-provisioned and functionally incomplete.Community Comment Notes
The single relevant comment, from gpais, states that "Only standard tier supports IOT eDGE" and links to Microsoft's IoT Hub tier comparison. That matches the product limitation: basic tier is intended for basic device-to-cloud messaging, while standard tier adds IoT Edge and module capabilities. No commenter argues for Event Hubs, and the vote record marks standard tier as the consensus answer.Official Reference
Exam Strategy
When an AZ-305 question mentions IoT Edge, immediately check the IoT Hub tier; Basic is a trap because edge support is a standard-tier feature. Then compare Event Hubs only if the requirement is raw event ingestion without device management, and favor the lowest tier that meets mandatory features.
Frequently Asked Questions
Why is Azure Event Hubs standard tier not the best fit for IoT Edge MQTT data?
Event Hubs can ingest telemetry but does not deploy or manage IoT Edge runtimes; the scenario requires IoT Hub standard tier for edge modules and routing.
Does Azure IoT Hub basic tier support IoT Edge?
No. IoT Edge requires the standard tier; basic tier is limited to basic device-to-cloud and cloud-to-device messaging.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →