Cloud Digital Leader Fundamental Cloud Concepts 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 Storage with Cloud CDN for static content, and Compute Engine instances behind Cloud Load Balancing for dynamic content

  Why this is correct

  Cloud Storage buckets serve immutable static assets (HTML, CSS, images) with native HTTP(S) support, and Cloud CDN caches those objects at Google's edge points of presence, minimizing latency and origin load for global users. Dynamic or personalized content—shopping carts, product recommendations, checkout logic—is handled by managed Compute Engine instance groups deployed across regions, fronted by HTTP(S) Load Balancing, which provides a global anycast IP, health checking, and autoscaling. This separation lets each layer scale independently: static delivery is cheap and cacheable, while dynamic backends only process uncached requests.

• ✗

  Compute Engine with Cloud Armor

  Why it's wrong here

  Cloud Armor is a security service that protects applications against distributed denial-of-service (DDoS) attacks and web exploits via WAF rules, but it does nothing to reduce latency or cache static content. Deploying Compute Engine instances with Cloud Armor would only secure the origin; users would still traverse the public internet to a single region, missing the edge caching and anycast routing that Cloud CDN and Cloud Load Balancing provide. This addresses security objectives, not the e-commerce site's global low-latency serving requirement.

• ✗

  Cloud Functions for all content

  Why it's wrong here

  Cloud Functions is a serverless, event-driven compute product intended for lightweight APIs and background tasks; it executes a function per HTTP request, but every invocation incurs compute overhead and possible cold start latency. Serving a full website—especially static assets like JavaScript, CSS, and images—would be inefficient and costly because static files consume function invocations instead of being cached at the edge. Additionally, Cloud Functions has timeout and concurrency constraints that make it unsuitable for long-lived connections, file streaming, or high-throughput static asset delivery required by a global e-commerce brand.

• ✗

  Cloud Storage only

  Why it's wrong here

  Cloud Storage is an object store designed for durable, highly available binary or file objects; it can serve static content through an HTTP endpoint and integrate with Cloud CDN, but it cannot execute server-side code, query databases, or process transactional logic. Dynamic website features such as user authentication, inventory management, cart operations, and personalized page rendering require a compute tier, so an e-commerce site limited to Cloud Storage would be unable to deliver any behavior beyond simple file retrieval. Therefore, Cloud Storage alone cannot satisfy the full website serving requirement.

Go deeper

Related to this question