Cloud Digital Leader Practice Question: Reduce latency for IoT devices located in remote…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Deploy Cloud CDN to cache responses.

  Why it's wrong here

  Cloud CDN caches static web content (e.g., images, CSS, JS) at edge POPs, but IoT device telemetry is dynamic, time-sensitive streaming data. Responses cannot be meaningfully cached because each reading is unique and must reflect real-time state; a cached response would serve stale sensor values, which is unacceptable for monitoring or control. Therefore, CDN addresses repeated requests for static assets, not the bidirectional low-latency data path required for IoT devices.

• ✓

  Use edge computing devices that run Cloud IoT Edge and preprocess data.

  Why this is correct

  Cloud IoT Edge runs on local gateway devices (e.g., industrial gateways, Raspberry Pi) and performs data preprocessing, filtering, aggregation, and even local ML inference before sending only essential data to the cloud. This reduces the volume and frequency of data transmitted over possibly poor or high-latency connectivity, which directly lowers end-to-end latency for decisions made at the edge. It also enables real-time responses even if the cloud is temporarily unreachable, making it the correct approach for latency-sensitive IoT deployments.

• ✗

  Use Cloud IoT Core with MQTT and process data on the server side.

  Why it's wrong here

  Cloud IoT Core with MQTT establishes a persistent, lightweight connection, but all raw device data is still transmitted to the cloud and processed server-side. The latency includes network transit from the device to the cloud region and back, which can be significant over unreliable or congested networks. Server-side processing does not reduce that transit latency; it merely performs computation after the data arrives, so it cannot satisfy a strict latency reduction goal for devices in remote or distributed locations.

• ✗

  Use a VPN to connect devices directly to the cloud.

  Why it's wrong here

  A VPN creates an encrypted tunnel to the cloud, but it adds network encapsulation overhead and still requires all data to travel the full round trip from device to cloud and back. It does not place any computation or data handling near the device, does not preprocess or filter data locally, and can even increase latency due to encryption processing and additional protocol headers. VPNs solve security and private connectivity concerns, not geographic or proximity-based latency problems.

Go deeper

Related to this question