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 data streaming platform designed for ingesting large volumes of telemetry events from devices, applications, and services, but it is primarily a one-way ingestion pipeline. It does not include a device registry, device twins, or cloud-to-device messaging, so you cannot send commands or manage devices through Event Hubs alone. For a scenario needing full bidirectional IoT communication and device management, Event Hubs is insufficient without an additional orchestration layer.

• ✓

  Azure IoT Hub

  Why this is correct

  Azure IoT Hub is a fully managed service that enables reliable and secure bidirectional communication between IoT applications and millions of devices. It supports both device-to-cloud telemetry and cloud-to-device commands, along with device twins, direct methods, and automatic device registration with per-device security keys or certificates. Its built-in integration with Azure Event Hubs for telemetry and its SDKs for MQTT, AMQP, and HTTPS make it the correct choice for this scenario, providing comprehensive device management and control.

• ✗

  Azure Service Bus

  Why it's wrong here

  Azure Service Bus is a general-purpose enterprise message broker that provides queues, topics, and relays for decoupling applications, with support for AMQP and other protocols. While it can carry messages between systems, it does not offer IoT-specific features such as per-device authentication, device twin synchronization, or MQTT support, which are essential for securing and managing a fleet of IoT devices. Service Bus would require custom implementation for device identity and control, making it a poor fit for a native IoT communication hub.

• ✗

  Azure Notification Hubs

  Why it's wrong here

  Azure Notification Hubs is a push notification engine that broadcasts notifications to any platform (iOS, Android, Windows) via device registration and tag-based targeting. It is purely a one-way notification sender to mobile devices, lacking the device-to-cloud telemetry ingestion, device twin, and direct method capabilities that IoT Hub offers. For this scenario, which requires persistent bidirectional communication with IoT devices, Notification Hubs cannot manage device lifecycle or receive telemetry from the device.

Go deeper

Related to this question