Requester pays configuration in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Requester Pays buckets in GCP

What is the main purpose of enabling the Requester Pays feature on a Google Cloud Storage bucket?

A To automatically encrypt all data in the bucket using requester-provided keys.

B To prevent any charges for data access by making the bucket free for all users.

C To make the bucket owner pay for all data access costs regardless of who accesses the data.

D To require users accessing the bucket to pay for the data access costs instead of the bucket owner.

💡 Hint

Think about who is billed for data access when Requester Pays is enabled.

Requester Pays buckets shift the cost of data access from the bucket owner to the user who requests the data. This means users pay for their own data access charges.

❓ Configuration

intermediate

Enabling Requester Pays on a GCP bucket

Which of the following gcloud commands correctly enables Requester Pays on a bucket named my-data-bucket?

A gcloud storage buckets update my-data-bucket --requester-pays

B gcloud storage buckets update my-data-bucket --billing requesterPays=true

C gcloud storage buckets update my-data-bucket --enable-requester-pays

D gcloud storage buckets update my-data-bucket --billing requester-pays

💡 Hint

Check the exact flag name used to enable Requester Pays in gcloud commands.

The correct flag to enable Requester Pays on a bucket is --requester-pays used with gcloud storage buckets update.

❓ service_behavior

advanced

Accessing a Requester Pays bucket without billing project

What happens if a user tries to list objects in a Requester Pays bucket without specifying a billing project?

A The request succeeds and the bucket owner is billed for the access.

B The request fails with a 400 Bad Request error indicating billing project is required.

C The request succeeds but the user is billed for the access automatically.

D The request is queued until a billing project is specified.

💡 Hint

Requester Pays requires a billing project to be specified by the requester.

When accessing a Requester Pays bucket, the user must specify a billing project to pay for the access. Without it, the request fails with an error.

❓ security

advanced

Security implications of Requester Pays buckets

Which security consideration is most important when enabling Requester Pays on a bucket?

A Users must have permission to specify a billing project, which can expose billing information if misconfigured.

B Enabling Requester Pays restricts access only to users with billing accounts.

C Requester Pays buckets automatically encrypt data with customer-managed keys.

D Requester Pays disables all public access to the bucket.

💡 Hint

Think about what permissions users need to access Requester Pays buckets.

Users must have permission to specify a billing project when accessing Requester Pays buckets. If permissions are too broad, billing info could be exposed or misused.

❓ Architecture

expert

Designing a multi-tenant data sharing architecture with Requester Pays

You manage a GCP bucket shared by multiple external teams. You want each team to pay only for their own data access costs. Which architecture best achieves this using Requester Pays?

A Enable Requester Pays and share a single billing project with all teams to simplify billing.

B Disable Requester Pays and have the bucket owner pay all access costs, then invoice teams manually.

C Enable Requester Pays on the bucket and require each team to use their own billing project when accessing data.

D Use separate buckets for each team without Requester Pays to isolate billing.

💡 Hint

Requester Pays is designed to shift billing to the requester. How can you leverage this for multiple teams?

Enabling Requester Pays and requiring each team to use their own billing project ensures each team pays only for their own data access costs, aligning with the goal.