Creating buckets and uploading objects in GCP - Practice Exercises

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you upload an object to a non-existent bucket?

You try to upload a file to a Google Cloud Storage bucket that does not exist. What is the expected outcome?

A The upload succeeds and the bucket is created automatically.

B The upload succeeds but the object is stored in a default bucket.

C The upload is queued until the bucket is created manually.

D The upload fails with a 'Not Found' error indicating the bucket does not exist.

💡 Hint

Think about how cloud storage services handle resources that must exist before use.

Google Cloud Storage requires the bucket to exist before uploading objects. Uploading to a non-existent bucket results in a 'Not Found' error.

❓ Configuration

intermediate

Which command creates a bucket with uniform access control?

You want to create a Google Cloud Storage bucket with uniform bucket-level access enabled. Which gsutil command achieves this?

A gsutil mb -l us-central1 gs://my-bucket/ && gsutil uniformbucketlevelaccess set on gs://my-bucket/

B gsutil mb -l us-central1 -b off gs://my-bucket/

C gsutil mb -l us-central1 -b on gs://my-bucket/

D gsutil mb -l us-central1 -b on --uniform gs://my-bucket/

💡 Hint

Uniform bucket-level access must be set after bucket creation using a separate gsutil command.

gsutil mb creates the bucket without a direct flag for uniform access; use 'gsutil uniformbucketlevelaccess set on gs://my-bucket/' afterward.

❓ Architecture

advanced

Which bucket location type minimizes latency for users in multiple continents?

You are designing a storage solution for a global app with users in North America, Europe, and Asia. Which bucket location type should you choose to minimize latency?

A Multi-region bucket

B Region bucket located in us-central1

C Dual-region bucket in us-central1 and us-east1

D Region bucket located in europe-west1

💡 Hint

Think about how data location affects access speed globally.

Multi-region buckets store data across multiple regions within a continent, reducing latency for geographically distributed users compared to single-region buckets.

❓ security

advanced

What is the effect of enabling 'Requester Pays' on a bucket?

You enable 'Requester Pays' on a Google Cloud Storage bucket. What changes in billing behavior occur?

A The bucket owner pays for all data access and egress costs.

B The requester pays for data access and egress costs when accessing objects.

C All costs are waived for both requester and owner.

D The bucket owner pays only for storage costs, not access costs.

💡 Hint

Consider who is charged when data is accessed from a bucket with this feature.

With 'Requester Pays' enabled, the user requesting data access is billed for data retrieval and network egress, not the bucket owner.

✅ Best Practice

expert

What is the recommended approach to securely upload objects from a client app without exposing service account keys?

You want users of your mobile app to upload files directly to a Google Cloud Storage bucket securely, without embedding service account keys in the app. What is the best practice?

A Embed service account keys in the app and use them to upload directly.

B Make the bucket public so anyone can upload files without authentication.

C Use signed URLs generated by a backend service to allow temporary upload access.

D Require users to authenticate with OAuth and upload using their own credentials.

💡 Hint

Think about how to grant limited, temporary access without sharing sensitive keys.

Signed URLs allow clients to upload objects with temporary permissions without exposing service account keys.