Roles (basic, predefined, custom) in GCP - Time & Space Complexity

Time Complexity: Roles (basic, predefined, custom)

O(n)

Understanding Time Complexity

When assigning roles in Google Cloud, it's important to understand how the number of operations grows as you assign roles to more users or resources.

We want to know how the time to assign roles changes when the number of assignments increases.

Scenario Under Consideration

Analyze the time complexity of assigning roles to multiple users.

# Assign roles to users
for user in user_list:
  gcloud projects add-iam-policy-binding my-project \
    --member="user:" + user.email \
    --role="roles/viewer"
    

This sequence assigns the predefined "viewer" role to each user in a list.

Identify Repeating Operations

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

• Primary operation: IAM policy binding API call to assign a role to a user.
• How many times: Once per user in the list.

How Execution Grows With Input

Each user requires a separate API call to assign the role, so the total calls grow directly with the number of users.

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

Pattern observation: The number of API calls increases one-to-one with the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to assign roles grows linearly as you add more users.

Common Mistake

[X] Wrong: "Assigning roles to many users happens instantly regardless of number."

[OK] Correct: Each assignment requires a separate API call, so more users mean more time.

Interview Connect

Understanding how role assignments scale helps you design efficient access control in cloud projects, a useful skill for real-world cloud management.

Self-Check

What if we batch multiple role assignments into a single API call? How would the time complexity change?