Correct Answer: Define an IoT Edge route in the deployment manifest from the module to $upstream with a condition filter
IoT Edge message routing in the deployment manifest allows you to define routes between modules and to $upstream (IoT Hub). You can add a condition (WHERE clause) so only messages ...
Correct Answer
Define an IoT Edge route in the deployment manifest from the module to $upstream with a condition filter
Why This Answer Is Correct
IoT Edge message routing in the deployment manifest allows you to define routes between modules and to $upstream (IoT Hub). You can add a condition (WHERE clause) so only messages matching the anomaly criteria are routed upstream. This ensures filtering happens on the device before any cloud bandwidth is consumed.
This question evaluates your knowledge of Azure IoT Edge — a core concept tested in Microsoft Certified: Azure IoT Developer Specialty (AZ-220). Understanding Azure IoT Edge is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
An IoT Edge device in a remote oil field has intermittent internet connectivity. You need the device to continue collecting and processing sensor data during outages and sync to the cloud when connectivity is restored. Which IoT Edge capability enables this?
You need to deploy a third-party machine learning model to IoT Edge devices for local inferencing. The model is packaged as a Docker container. Which component of IoT Edge is responsible for managing the lifecycle of this container on the device?
You need legacy devices without native IoT SDK support to connect to IoT Hub through an IoT Edge device. Each legacy device should appear as a separate device identity in IoT Hub. Which IoT Edge gateway pattern should you implement?
You are deploying an IoT Edge solution to 500 devices in a factory. You need to update the deployment manifest for all devices simultaneously whenever a new module version is released. Which approach scales for 500 devices without manual per-device updates?
You need to deploy an IoT Edge custom module that requires access to a hardware device (e.g., /dev/ttyUSB0 for serial communication) on the host gateway. How should you configure this module in the deployment manifest?