Azure IoT Developer (AZ-220) study materials
Azure IoT Developer (AZ-220) study resources

Azure IoT Developer (AZ-220) case studies

Azure IoT Developer (AZ-220) · Put your knowledge to work in context.

AZ-220, Microsoft Azure IoT Developer, was a specialty-level Microsoft certification exam for developers who build both the cloud and device sides of an IoT solution. According to Microsoft's exam page, candidates were expected to configure and maintain devices through cloud services, set up physical devices, and troubleshoot device configuration across the lifecycle. The measured skills were setting up Azure IoT Hub solution infrastructure, provisioning and managing devices, implementing IoT Edge, implementing business integration, processing and managing data, monitoring, troubleshooting, and optimizing solutions, and implementing security. Microsoft published these as ranges, from 5–10% for business integration up to 20–25% for IoT Edge. The Azure IoT Developer (AZ-220) case studies are 5 cases and about 3,364 words.

1

Right-Sizing Throughput for a Bursty Telemetry Fleet

Contoso operates 8,000 leaf devices that report every 10 seconds during business hours (08:00–18:00 local) and every 5 minutes otherwise. Each message is 1.5 KB and devices use MQTT over TLS.

752 words, about 4 min
2

Device Provisioning at Scale with Intermittent Connectivity

Fabrikam manufactures 25,000 environmental sensors per quarter. Devices are assembled in three factories, each with unreliable Wi-Fi during initial commissioning.

674 words, about 3 min
3

IoT Edge Module Routing Under Intermittent Uplink

A manufacturing line runs an IoT Edge device on a gateway that aggregates 40 Modbus sensors. The site has a satellite uplink that drops for 20–90 minutes several times per day.

627 words, about 3 min
4

Routing Telemetry to Multiple Business Systems with Different SLAs

A utility company ingests smart-meter readings through IoT Hub. Three downstream systems need the data: (1) a billing pipeline that must receive every reading exactly once and tolerates 15-minute latency; (2) a real-time outage dashboard that needs sub-5-second latency and can tolerate occasional loss; (3) a cold archive that stores raw messages for seven years.

654 words, about 3 min
5

Diagnosing Silent Device Disconnects and Security Posture

A healthcare customer runs 5,000 bedside monitors connected over hospital Wi-Fi. Over two weeks, roughly 300 devices stop sending telemetry but remain powered on; nurses report stale readings.

657 words, about 3 min