Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

Answer analysis

Option-by-option breakdown

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

• ✓

  Create and prepare the bucket, then set up a load balancer, then enable Cloud CDN, then test.

  Why this is correct

  You must first create and prepare a Cloud Storage bucket to serve as the origin, because it holds the content that Cloud CDN will cache. Next, configure an external HTTPS load balancer with a backend service that references that bucket, since the load balancer provides the front-end IP and routing rules. Only after the backend service exists can you enable Cloud CDN on it, attaching edge caching to the backend. Finally, test by sending requests to the load balancer and checking cache-hit headers like Age and Cache-Control.

• ✗

  Create and prepare the bucket, then enable Cloud CDN, then set up a load balancer, then test.

  Why it's wrong here

  This fails because Cloud CDN is not an independent service; it is a toggle or configuration setting applied to an existing backend service of a load balancer. If you attempt to enable Cloud CDN before the load balancer exists, there is no backend service to attach it to, and the operation will error. The bucket alone cannot have Cloud CDN enabled because the bucket must be referenced by a backend service as the origin for the CDN to route and cache traffic. Therefore, creating the bucket first is not sufficient—the load balancer and its backend must be created before CDN can be enabled.

• ✗

  Set up a load balancer, then create and prepare the bucket, then enable Cloud CDN, then test.

  Why it's wrong here

  This order is invalid because the load balancer's backend service must point to an existing origin. When you configure a backend service for a Cloud Storage bucket, the bucket must already be created and accessible (via public access or IAM binding) so that the backend can verify the bucket's existence and serve content from it. You cannot set up the load balancer first because its backend configuration will reject a non-existent bucket reference, causing a dependency error. Thus, the bucket must be prepared before the load balancer is set up.

• ✗

  Create and prepare the bucket, then set up a load balancer, then test, then enable Cloud CDN.

  Why it's wrong here

  Testing before enabling Cloud CDN would not validate the CDN feature at all; it would only confirm that the load balancer and bucket can serve responses. Without Cloud CDN enabled, responses will not include cache-related headers such as Age or Cache-Control: hit/miss, so the test would give false confidence that the configuration works. Only after enabling Cloud CDN can you verify that repeated requests for the same object are served from the edge cache, reducing latency and load on the origin. Therefore, the test step must occur after Cloud CDN is enabled.

Go deeper

Related to this question