Cloud Digital Leader Practice Question: Drag and drop the steps to set up a Cloud Storage…

Answer analysis

Option-by-option breakdown

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

• ✓

  Access Cloud Storage, then create a bucket, then name the bucket, then select storage settings, then enable uniform bucket-level access.

  Why this is correct

  This order correctly reflects the Google Cloud Console workflow: you must first access Cloud Storage, then create a new bucket (which involves naming it), then configure settings like location and storage class, and finally enable uniform bucket-level access before finalizing.

• ✗

  Access Cloud Storage, then create a bucket, then select storage settings, then name the bucket, then enable uniform bucket-level access.

  Why it's wrong here

  This order fails because the bucket name is a required field in the 'Create a bucket' dialog before you can proceed to the 'Choose storage settings' step. In the Google Cloud Console, the naming input appears on the first page of the creation flow; if you attempt to select storage settings first, the console will block navigation because the name is mandatory. The correct sequence is to enter the name immediately after initiating bucket creation, and only then configure location, storage class, and other settings.

• ✗

  Access Cloud Storage, then enable uniform bucket-level access, then create a bucket, then name the bucket, then select storage settings.

  Why it's wrong here

  Uniform bucket-level access (UBLA) is a property of the bucket itself and can only be toggled after the bucket exists. You cannot enable it 'before creating a bucket' because there is no resource to attach the setting to. In the Console, the UBLA checkbox appears on the final 'Choose how to control access to objects' step of the creation wizard, so it must come after naming the bucket and selecting storage settings, not before the create action.

• ✗

  Create a bucket, then access Cloud Storage, then name the bucket, then select storage settings, then enable uniform bucket-level access.

  Why it's wrong here

  Accessing Cloud Storage is the mandatory entry point in the Google Cloud Console; you must first open the Cloud Storage service via the navigation menu or use `gcloud storage buckets create` before any bucket creation can occur. Starting with 'create a bucket' is impossible because the creation button and API calls are only available within the Cloud Storage interface. Additionally, the action of 'naming the bucket' is part of the creation dialog, so it cannot logically follow 'access Cloud Storage' if that access is meant to be a distinct step.

Go deeper

Related to this question