AZ-900 Describe Azure architecture and services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure Event Hubs

  Why it's wrong here

  Azure Event Hubs is a high-throughput telemetry ingestion service capable of accepting millions of events per second, but it is fundamentally unidirectional. It does not provide device identity management, device twins, or a feedback channel for cloud-to-device messages, making it impossible to control or manage devices through Event Hubs alone. Event Hubs is often deployed downstream of IoT Hub to stream telemetry into analytics pipelines, not to handle device connectivity. Thus, it fails to meet the full requirements of an IoT platform.

• ✓

  Azure IoT Hub

  Why this is correct

  Azure IoT Hub is the complete IoT connectivity platform, offering secure, bidirectional communication between devices and the cloud over MQTT, AMQP, and HTTPS. It provides a device identity registry, per-device authentication, device twins for desired and reported state, direct methods for remote commands, and automatic device provisioning. IoT Hub also handles telemetry ingestion and cloud-to-device messaging, along with file upload and device management at scale. This makes it the central, correct service for connecting and managing IoT devices.

• ✗

  Azure Stream Analytics

  Why it's wrong here

  Azure Stream Analytics is a real-time stream processing engine that runs SQL-like queries over data streaming from sources such as IoT Hub, Event Hubs, or Blob Storage. It has no device connectivity, identity registry, or command capabilities; it merely consumes and analyzes data after that data has already been ingested from devices. While Stream Analytics could be used to process IoT telemetry, it cannot register, authenticate, or control devices in any way. Consequently, it is not an IoT platform but a downstream analytics service.

• ✗

  Azure Service Bus

  Why it's wrong here

  Azure Service Bus is an enterprise message broker designed for reliable, ordered messaging between cloud and on-premises applications, not for IoT device connectivity. It lacks an IoT device identity registry, device twins, direct methods, and built-in MQTT support for fleets of devices. Without these capabilities, Service Bus cannot authenticate or manage devices, nor can it execute cloud-initiated commands on individual devices. Therefore, it is not the correct service for IoT connectivity and management.

Go deeper

Related to this question