Correct Answer: Identity translation gateway — Edge proxies messages but each legacy device has its own IoT Hub identity
The identity translation gateway pattern allows IoT Edge to act as a proxy for downstream devices that cannot speak the IoT Hub protocol. IoT Edge maintains separate device identit...
Correct Answer
Identity translation gateway — Edge proxies messages but each legacy device has its own IoT Hub identity
Why This Answer Is Correct
The identity translation gateway pattern allows IoT Edge to act as a proxy for downstream devices that cannot speak the IoT Hub protocol. IoT Edge maintains separate device identities in IoT Hub for each downstream device and translates their messages accordingly. This gives each legacy device its own twin and telemetry stream in IoT Hub.
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.
You have an Azure IoT Edge device deployed at a factory. A custom module processes sensor data and should forward only anomaly alerts to IoT Hub to minimize bandwidth. Normal readings should be discarded at the edge. How do you configure this routing?
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 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?