Members (users, groups, service accounts) in GCP - Time & Space Complexity

Time Complexity: Members (users, groups, service accounts)

O(n)

Understanding Time Complexity

When managing cloud permissions, we often add members like users, groups, or service accounts to roles.

We want to understand how the time to update permissions grows as we add more members.

Scenario Under Consideration

Analyze the time complexity of adding multiple members to a role binding in a policy.

policy = getIamPolicy(resource)
role_binding = {"role": role, "members": []}
for member in members_list:
    role_binding["members"].append(member)
policy["bindings"].append(role_binding)
setIamPolicy(resource, policy)
    

This sequence fetches the current policy, adds each member to a binding, then updates the policy.

Identify Repeating Operations

Look at what repeats as we add members.

• Primary operation: Adding each member to the role binding's members list.
• How many times: Once per member in the list.

How Execution Grows With Input

Each new member requires one append operation to the binding's members list.

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

Pattern observation: The number of operations grows directly with the number of members.

Final Time Complexity

Time Complexity: O(n)

This means the time to add members grows in a straight line as you add more members.

Common Mistake

[X] Wrong: "Adding multiple members is just one operation regardless of count."

[OK] Correct: Each member requires a separate addition, so time grows with the number of members.

Interview Connect

Understanding how permission updates scale helps you design efficient access controls and anticipate delays in large projects.

Self-Check

What if we batch all members into a single binding instead of adding them one by one? How would the time complexity change?

Practice

1. Which of the following is a correct way to specify a user as a member in GCP IAM?

easy

A. user:[e-mail]

B. serviceaccount:[e-mail]

C. group:[e-mail]

D. member:[e-mail]

Solution

1. Step 1: Understand member types in GCP IAM

   GCP IAM requires a prefix to identify the member type, such as user, group, or serviceaccount.

2. Step 2: Identify the correct prefix for a user

   The prefix for an individual user is user:. So the correct format is user:email.

3. Final Answer:

   user:[e-mail] -> Option A

4. Quick Check:

   User members start with 'user:' [OK]

Hint: User members always start with 'user:' prefix [OK]

Common Mistakes:

• Using 'member:' prefix which is invalid
• Confusing group and user prefixes
• Using serviceaccount prefix for users

2. Which of the following is the correct syntax to specify a service account member in GCP IAM?

easy

A. service-account:[e-mail]

B. serviceaccount:[e-mail]

C. group:[e-mail]

D. user:[e-mail]

Solution

1. Step 1: Recall the prefix for service accounts

   Service accounts use the prefix serviceaccount: followed by the full service account email.

2. Step 2: Check each option's prefix

   Only serviceaccount:[e-mail] uses the correct prefix serviceaccount: without hyphens or mistakes.

3. Final Answer:

   serviceaccount:[e-mail] -> Option B

4. Quick Check:

   Service accounts use 'serviceaccount:' prefix [OK]

Hint: Service accounts use 'serviceaccount:' prefix without hyphens [OK]

Common Mistakes:

• Using 'service-account:' with a hyphen
• Using 'user:' prefix for service accounts
• Using incomplete email addresses

3. Given the following IAM policy binding snippet, which member will have access?

{"role": "roles/viewer", "members": ["group:[e-mail]", "user:[e-mail]"]}

medium

A. Only users in the dev-team group and Bob

B. Only Bob

C. Only the dev-team group

D. All users in the project

Solution

1. Step 1: Analyze the members list in the policy

   The members list includes group:[e-mail] and user:[e-mail]. Both are granted the role.

2. Step 2: Understand access granted by group and user members

   All users in the dev-team group plus the individual user Bob have the role permissions.

3. Final Answer:

   Only users in the dev-team group and Bob -> Option A

4. Quick Check:

   Group and user members both get access [OK]

Hint: Group members grant access to all group users [OK]

Common Mistakes:

• Assuming only one member gets access
• Confusing group with user access scope
• Thinking all project users get access

4. You tried to add a member with user:alice to an IAM policy but got an error. What is the likely cause?

medium

A. IAM policy does not support user members

B. Using 'user:' prefix instead of 'group:'

C. Service account email used instead of user email

D. Missing full email address after 'user:' prefix

Solution

1. Step 1: Check the required format for user members

   User members must include the full email address after the user: prefix.

2. Step 2: Identify the error cause

   Using just user:alice is incomplete and causes a format error.

3. Final Answer:

   Missing full email address after 'user:' prefix -> Option D

4. Quick Check:

   User members need full email [OK]

Hint: Always include full email after 'user:' [OK]

Common Mistakes:

• Using only username without domain
• Confusing user and group prefixes
• Assuming IAM rejects user members

5. You want to grant a Cloud Function access to a Pub/Sub topic using a service account. Which member string should you add to the Pub/Sub IAM policy?

hard

A. group:[e-mail]

B. user:[e-mail]

C. serviceaccount:[e-mail]

D. service-account:[e-mail]

Solution

1. Step 1: Identify the correct member type for Cloud Function access

   Cloud Functions use service accounts to access other resources, so the member must be a service account.

2. Step 2: Use the correct prefix for service accounts

   The prefix is serviceaccount: followed by the full service account email.

3. Step 3: Verify the options

   Only serviceaccount:[e-mail] uses the correct prefix and format.

4. Final Answer:

   serviceaccount:[e-mail] -> Option C

5. Quick Check:

   Service accounts use 'serviceaccount:' prefix [OK]

Hint: Use 'serviceaccount:' prefix for Cloud Function identities [OK]

Common Mistakes:

• Using 'user:' prefix for service accounts
• Adding group instead of service account
• Using incorrect prefix with hyphen