Service accounts for applications in GCP - Time & Space Complexity

Time Complexity: Service accounts for applications

O(n)

Understanding Time Complexity

When applications use service accounts, they often request tokens to access cloud resources. Understanding how the number of token requests grows helps us see how the system performs as usage increases.

We want to know: how does the number of token requests change as more applications or services use the service account?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// For each application instance
for (int i = 0; i < n; i++) {
  // Request an access token from the service account
  token = requestAccessToken(serviceAccount);
  // Use the token to call a cloud API
  callCloudAPI(token);
}

This sequence shows multiple application instances each requesting a token from the same service account and then calling a cloud API.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Requesting an access token from the service account.
• How many times: Once per application instance (n times).

How Execution Grows With Input

Each new application instance makes its own token request, so the total number of token requests grows directly with the number of instances.

Input Size (n)	Approx. Api Calls/Operations
10	10 token requests
100	100 token requests
1000	1000 token requests

Pattern observation: The number of token requests increases one-to-one with the number of application instances.

Final Time Complexity

Time Complexity: O(n)

This means that as you add more application instances, the total token requests grow in direct proportion.

Common Mistake

[X] Wrong: "Requesting one token can serve all application instances, so the number of requests stays the same no matter how many instances run."

[OK] Correct: Each instance usually needs its own token to authenticate separately, so requests increase with instances.

Interview Connect

Understanding how token requests scale helps you design applications that handle authentication efficiently and avoid bottlenecks as usage grows.

Self-Check

"What if multiple application instances shared a cached token instead of requesting new ones each time? How would the time complexity change?"

Practice

1. What is the main purpose of a service account in Google Cloud Platform (GCP)?

easy

A. To allow applications to authenticate and access GCP resources securely

B. To create user accounts for people to log in to GCP Console

C. To store data in Google Cloud Storage buckets

D. To monitor network traffic between virtual machines

Solution

1. Step 1: Understand service account role

   A service account is a special account used by applications or virtual machines to authenticate and access Google Cloud resources securely without user intervention.

2. Step 2: Differentiate from user accounts

   User accounts are for people to log in, while service accounts are for applications or services to act on behalf of users or themselves.

3. Final Answer:

   To allow applications to authenticate and access GCP resources securely -> Option A

4. Quick Check:

   Service account = app authentication [OK]

Hint: Service accounts are for apps, not people [OK]

Common Mistakes:

• Confusing service accounts with user accounts
• Thinking service accounts store data
• Assuming service accounts monitor network

2. Which of the following is the correct way to assign a service account to a Compute Engine VM instance during creation?

easy

A. Use the --service-account flag with gcloud compute instances create

B. Add the service account email to the VM's firewall rules

C. Specify the service account in the VM's startup script

D. Create a user account with the same name as the service account

Solution

1. Step 1: Identify how to assign service accounts to VMs

   The gcloud compute instances create command supports a --service-account flag to specify which service account the VM should use.

2. Step 2: Eliminate incorrect options

   Firewall rules do not assign service accounts, startup scripts do not assign service accounts, and user accounts are unrelated to service account assignment.

3. Final Answer:

   Use the --service-account flag with gcloud compute instances create -> Option A

4. Quick Check:

   Assign service account with --service-account flag [OK]

Hint: Use --service-account flag when creating VM [OK]

Common Mistakes:

• Trying to assign service account via firewall
• Using startup scripts to assign service accounts
• Confusing user accounts with service accounts

3. Consider this Python code snippet using Google Cloud client libraries:

from google.cloud import storage

client = storage.Client()
buckets = list(client.list_buckets())
print(len(buckets))

What must be true for this code to successfully list buckets?

medium

A. The user must be logged in to GCP Console in a browser

B. The environment must have a service account with Storage Viewer role configured

C. The code must run on a VM with no service account assigned

D. No authentication is needed to list buckets

Solution

1. Step 1: Understand authentication requirement

   Google Cloud client libraries require authentication, usually via a service account or user credentials, to access resources like buckets.

2. Step 2: Identify required permissions

   To list buckets, the service account or user must have at least the Storage Viewer role to read bucket metadata.

3. Final Answer:

   The environment must have a service account with Storage Viewer role configured -> Option B

4. Quick Check:

   Service account with Storage Viewer role needed [OK]

Hint: List buckets needs Storage Viewer role on service account [OK]

Common Mistakes:

• Assuming user login in browser is enough
• Running code without any service account
• Thinking no auth is needed for bucket listing

4. You deployed an application on a GCP VM with a service account, but it fails to access Cloud Storage buckets. What is the most likely cause?

medium

A. The service account email is not the same as the VM name

B. The VM does not have an external IP address

C. The application code is missing the Cloud Storage client library import

D. The service account lacks the necessary IAM permissions for Cloud Storage

Solution

1. Step 1: Check service account permissions

   If the application cannot access Cloud Storage, the most common reason is missing IAM permissions on the service account assigned to the VM.

2. Step 2: Rule out other causes

   Lack of external IP does not block access if using private Google access; missing import causes code errors but not permission failures; service account email unrelated to VM name.

3. Final Answer:

   The service account lacks the necessary IAM permissions for Cloud Storage -> Option D

4. Quick Check:

   Missing IAM permissions cause access failure [OK]

Hint: Check IAM roles on service account first [OK]

Common Mistakes:

• Assuming external IP is required for access
• Blaming code imports without error evidence
• Confusing service account email with VM name

5. You want to deploy a serverless application on Cloud Run that accesses a Cloud SQL database securely. Which approach correctly uses a service account to grant least privilege access?

hard

A. Assign the Cloud Run service account the Storage Admin role to access Cloud SQL

B. Use the default Compute Engine service account with Owner role for Cloud Run

C. Create a service account with only Cloud SQL Client role and assign it to the Cloud Run service

D. Create a user account with Cloud SQL Admin role and embed its credentials in the app

Solution

1. Step 1: Identify least privilege principle

   Grant only the permissions needed. For Cloud SQL access, the Cloud SQL Client role is sufficient.

2. Step 2: Assign correct service account to Cloud Run

   Create a dedicated service account with Cloud SQL Client role and assign it to the Cloud Run service to avoid over-permission.

3. Step 3: Eliminate insecure or excessive options

   Using default service account with Owner role is too broad; Storage Admin role is unrelated; embedding user credentials is insecure.

4. Final Answer:

   Create a service account with only Cloud SQL Client role and assign it to the Cloud Run service -> Option C

5. Quick Check:

   Least privilege: Cloud SQL Client role on service account [OK]

Hint: Use least privilege role on dedicated service account [OK]

Common Mistakes:

• Using overly broad Owner role
• Assigning unrelated roles like Storage Admin
• Embedding user credentials in app code