Correct Answer: Set parent_hostname in the config.toml file of the child device to point to the parent Edge device
In nested IoT Edge setups, child Edge devices must establish connection with their parent Edge device. This is defined in the child device's config.toml using the parent_hostname p...
Correct Answer
Set parent_hostname in the config.toml file of the child device to point to the parent Edge device
Why This Answer Is Correct
In nested IoT Edge setups, child Edge devices must establish connection with their parent Edge device. This is defined in the child device's config.toml using the parent_hostname parameter pointing to the parent's hostname or IP address.
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 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?