Cloud Digital Leader Why Cloud Technology Can Transform Business Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Cloud Interconnect

  Why it's wrong here

  Cloud Interconnect creates a dedicated, high-speed connection between your on-premises network and Google Cloud, reducing latency for hybrid cloud traffic by avoiding the public internet. However, it does not cache media content or deliver it from edge locations; it only extends your network path to GCP. For a media streaming company serving global end users, the latency bottleneck is the last-mile delivery from the origin to the user, which Cloud Interconnect cannot address, making it an incorrect choice for this requirement.

• ✗

  Cloud Storage

  Why it's wrong here

  Cloud Storage is a highly durable object storage service where you can store media files and serve them directly over HTTP. While it can handle large volumes of content, it does not provide any built-in caching at Google's edge locations; each request for a media segment travels over the public internet to the bucket's region, which can introduce significant latency for distant users. It is often used as an origin backend for Cloud CDN, but on its own it fails to reduce user-perceived latency for media streaming.

• ✗

  Cloud Load Balancing

  Why it's wrong here

  Cloud Load Balancing distributes incoming traffic across multiple backend instances (e.g., VM groups or managed instance groups) based on factors like health, capacity, and proximity, improving scalability and availability. However, it operates only at the forwarding and routing level—it does not cache media content or store it at edge points-of-presence; it simply sends each request to a backend, which remains the single origin. For media streaming, the origin's geographic distance still dictates latency, so load balancing alone does not solve the problem of reducing latency for global users.

• ✓

  Cloud CDN

  Why this is correct

  Cloud CDN is the correct choice because it leverages Google's globally distributed edge infrastructure to cache media content (such as video segments, images, and other static assets) at points of presence closer to end users. When a user requests a media file, the CDN serves it from the nearest edge cache, dramatically reducing round-trip time and network hops compared to fetching from the origin. It also offloads traffic from origin servers, reducing bandwidth costs and origin load, and it supports flexible cache modes and TTLs for both static and dynamic content—making it the ideal solution for low-latency media streaming.

Go deeper

Related to this question