Custom roles creation in GCP - Time & Space Complexity

Time Complexity: Custom roles creation

O(n)

Understanding Time Complexity

When creating custom roles in GCP, it is important to understand how the time to create roles grows as you add more permissions.

We want to know how the number of permissions affects the time and operations needed to create a custom role.

Scenario Under Consideration

Analyze the time complexity of creating a custom role with multiple permissions.

    gcloud iam roles create myCustomRole \
      --project=my-project \
      --title="My Custom Role" \
      --permissions=storage.buckets.get,storage.objects.list,compute.instances.start
    

This command creates a custom role with a list of permissions specified.

Identify Repeating Operations

Look at what happens when adding permissions to the role.

• Primary operation: API call to create or update the custom role with all permissions.
• How many times: One API call per role creation, but the size of the permissions list affects the payload size.

How Execution Grows With Input

As you add more permissions, the data sent in the API call grows linearly.

Input Size (n)	Approx. API Calls/Operations
10	1 API call with 10 permissions
100	1 API call with 100 permissions
1000	1 API call with 1000 permissions

Pattern observation: The number of API calls stays the same, but the payload size grows with the number of permissions.

Final Time Complexity

Time Complexity: O(n)

This means the time to create a custom role grows linearly with the number of permissions included.

Common Mistake

[X] Wrong: "Creating a custom role with many permissions requires multiple API calls, one per permission."

[OK] Correct: Actually, all permissions are sent in a single API call, so the number of calls does not increase with permissions.

Interview Connect

Understanding how API calls scale with input size helps you design efficient cloud operations and explain your reasoning clearly in interviews.

Self-Check

"What if we split permissions into multiple smaller roles instead of one big role? How would the time complexity change?"

Practice

1. What is the main purpose of creating a custom role in Google Cloud Platform?

easy

A. To create virtual machines quickly

B. To automatically assign all permissions to a user

C. To delete existing predefined roles

D. To tailor permissions specifically for your project needs

Solution

1. Step 1: Understand role customization

   Custom roles allow you to pick specific permissions instead of using broad predefined roles.

2. Step 2: Identify the purpose of custom roles

   They help tailor access to exactly what is needed, improving security and management.

3. Final Answer:

   To tailor permissions specifically for your project needs -> Option D

4. Quick Check:

   Custom roles = tailored permissions [OK]

Hint: Custom roles = pick permissions you want [OK]

Common Mistakes:

• Thinking custom roles give all permissions automatically
• Confusing custom roles with deleting roles
• Assuming custom roles create resources

2. Which of the following is the correct gcloud command syntax to create a custom role named myCustomRole in project my-project with the title "My Role" and permission storage.buckets.list?

easy

A. gcloud iam roles create myCustomRole --project=my-project --title="My Role" --permissions=storage.buckets.list --stage=GA

B. gcloud iam create role myCustomRole --project my-project --title My Role --permissions storage.buckets.list

C. gcloud roles create myCustomRole --project=my-project --title="My Role" --permissions=storage.buckets.list

D. gcloud iam roles add myCustomRole --project=my-project --title="My Role" --permissions=storage.buckets.list

Solution

1. Step 1: Identify correct gcloud command structure

   The correct command to create a custom role is gcloud iam roles create with flags for project, title, permissions, and stage.

2. Step 2: Match syntax with options

   gcloud iam roles create myCustomRole --project=my-project --title="My Role" --permissions=storage.buckets.list --stage=GA matches the correct syntax including --project, --title, --permissions, and --stage flags.

3. Final Answer:

   gcloud iam roles create myCustomRole --project=my-project --title="My Role" --permissions=storage.buckets.list --stage=GA -> Option A

4. Quick Check:

   Correct gcloud create syntax = gcloud iam roles create myCustomRole --project=my-project --title="My Role" --permissions=storage.buckets.list --stage=GA [OK]

Hint: Use 'gcloud iam roles create' with all flags [OK]

Common Mistakes:

• Using 'gcloud iam create role' instead of 'roles create'
• Missing the --stage flag
• Incorrect flag order or missing equal signs

3. Given this command:

gcloud iam roles create dataViewer --project=my-project --title="Data Viewer" --permissions=bigquery.datasets.get,bigquery.tables.list --stage=ALPHA

What will be the effect of this custom role?

medium

A. Allows users to get dataset metadata and list tables in BigQuery

B. Allows users to create and delete BigQuery datasets

C. Grants full admin access to BigQuery

D. Denies all BigQuery permissions

Solution

1. Step 1: Analyze permissions in the command

   The permissions bigquery.datasets.get and bigquery.tables.list allow reading dataset info and listing tables.

2. Step 2: Understand what these permissions enable

   These permissions let users view dataset metadata and see tables but not modify or delete them.

3. Final Answer:

   Allows users to get dataset metadata and list tables in BigQuery -> Option A

4. Quick Check:

   Permissions = read-only BigQuery access [OK]

Hint: Check permissions list for read or write actions [OK]

Common Mistakes:

• Assuming ALPHA stage means full access
• Confusing get/list with create/delete permissions
• Thinking it grants admin rights

4. You tried to create a custom role with this command:

gcloud iam roles create testRole --project=my-project --title="Test Role" --permissions=compute.instances.start,compute.instances.stop

But it failed. What is the most likely reason?

medium

A. Project ID is incorrect

B. Permissions are invalid for custom roles

C. Missing the --stage flag which is required

D. Role ID cannot contain uppercase letters

Solution

1. Step 1: Check required flags for role creation

   The --stage flag is mandatory when creating custom roles to specify the release stage.

2. Step 2: Identify missing flag in the command

   The command lacks the --stage flag, causing failure.

3. Final Answer:

   Missing the --stage flag which is required -> Option C

4. Quick Check:

   --stage flag required = Missing the --stage flag which is required [OK]

Hint: Always include --stage when creating custom roles [OK]

Common Mistakes:

• Ignoring the required --stage flag
• Assuming permissions are invalid
• Mistaking project ID or role ID format

5. You want to create a custom role that allows users to list storage buckets and read objects but not delete them. Which permissions should you include in your custom role?

hard

A. storage.buckets.list, storage.objects.delete

B. storage.buckets.list, storage.objects.get

C. storage.buckets.create, storage.objects.get

D. storage.buckets.delete, storage.objects.get

Solution

1. Step 1: Identify permissions for listing buckets and reading objects

   storage.buckets.list allows listing buckets, and storage.objects.get allows reading objects.

2. Step 2: Exclude delete permissions

   Do not include any delete permissions to prevent deletion.

3. Final Answer:

   storage.buckets.list, storage.objects.get -> Option B

4. Quick Check:

   List + read, no delete = storage.buckets.list, storage.objects.get [OK]

Hint: Include only list and get permissions, exclude delete [OK]

Common Mistakes:

• Including delete permissions by mistake
• Confusing create with list permissions
• Assuming read includes delete