Why IAM is foundational in GCP - Quick Recap

Recall & Review

beginner

What does IAM stand for in Google Cloud Platform?

IAM stands for Identity and Access Management. It controls who can do what in GCP.

beginner

Why is IAM considered foundational in GCP?

Because it manages permissions and access to all resources, keeping your cloud secure and organized.

intermediate

What are the three main components of IAM in GCP?

Users (who), Roles (what), and Resources (where). Together they define access rules.

beginner

How does IAM help in real-life cloud security?

It’s like giving keys only to people who need them, so no one can access things they shouldn’t.

beginner

What is a role in GCP IAM?

A role is a set of permissions that you assign to users to let them perform specific actions.

What is the main purpose of IAM in GCP?

A To monitor network traffic

B To store data securely

C To control who can access cloud resources

D To create virtual machines

IAM controls access permissions to cloud resources, ensuring security.

Which of these is NOT a component of IAM?

A Users

B Roles

C Resources

D Databases

Databases are resources but not a component of IAM itself.

What does a role in IAM define?

A What actions are allowed

B Who can access resources

C Where resources are located

D When access expires

Roles define the permissions or actions a user can perform.

Why is it important to assign the least privilege in IAM?

A To limit access to only what is needed

B To reduce costs

C To speed up network traffic

D To increase storage space

Least privilege means giving only necessary access to improve security.

IAM in GCP is most similar to which real-life concept?

A A library card

B A house key

C A shopping list

D A calendar

IAM is like a house key that controls who can enter and what they can do inside.

Explain why IAM is foundational in GCP and how it helps secure cloud resources.

Think about who can do what and where in your cloud.

Describe the main components of IAM in GCP and their roles.

Who, what, and where define access.

Practice

1. What is the main purpose of IAM in Google Cloud Platform?

easy

A. To monitor network traffic

B. To store data securely in the cloud

C. To create virtual machines automatically

D. To control who can access and manage cloud resources

Solution

1. Step 1: Understand IAM's role in GCP

   IAM stands for Identity and Access Management, which controls user permissions.

2. Step 2: Identify the main function

   IAM manages who can access and change cloud resources, ensuring security and organization.

3. Final Answer:

   To control who can access and manage cloud resources -> Option D

4. Quick Check:

   IAM controls access = C [OK]

Hint: IAM is about access control, not storage or monitoring [OK]

Common Mistakes:

• Confusing IAM with data storage services
• Thinking IAM manages network traffic
• Assuming IAM creates resources automatically

2. Which of the following is the correct way to assign a role to a user in GCP IAM?

easy

A. Grant the user a role using the IAM policy binding

B. Add the user to a Compute Engine instance

C. Create a new virtual machine for the user

D. Enable billing for the user account

Solution

1. Step 1: Review how roles are assigned in IAM

   Roles are assigned by adding users to IAM policy bindings on resources.

2. Step 2: Identify the correct method

   Granting a role via IAM policy binding is the proper way to assign permissions.

3. Final Answer:

   Grant the user a role using the IAM policy binding -> Option A

4. Quick Check:

   Role assignment = IAM policy binding [OK]

Hint: Roles are assigned via IAM policies, not VM or billing settings [OK]

Common Mistakes:

• Confusing user role assignment with VM creation
• Thinking billing enables permissions
• Adding users directly to instances instead of IAM

3. Consider this IAM policy snippet:

{
  "bindings": [
    {
      "role": "roles/storage.objectViewer",
      "members": ["user:[e-mail]"]
    }
  ]
}

What permission does Alice have?

medium

A. She can delete storage objects

B. She can create new storage buckets

C. She can view objects in Cloud Storage buckets

D. She can manage billing for storage

Solution

1. Step 1: Identify the role in the policy

   The role is "roles/storage.objectViewer", which grants read-only access to storage objects.

2. Step 2: Understand the permissions of the role

   This role allows viewing objects but not creating or deleting them.

3. Final Answer:

   She can view objects in Cloud Storage buckets -> Option C

4. Quick Check:

   objectViewer means read-only access [OK]

Hint: Viewer roles allow read-only access, not changes [OK]

Common Mistakes:

• Assuming viewer role allows object creation or deletion
• Confusing billing management with storage permissions
• Thinking role applies to bucket creation

4. You wrote this IAM policy but users report they cannot access the resource:

{
  "bindings": [
    {
      "role": "roles/editor",
      "members": ["user:[e-mail]"]
    }
  ]
}

What is the likely problem?

medium

A. The role "roles/editor" does not exist

B. The policy is missing the resource it applies to

C. The member email is incorrectly formatted

D. IAM policies cannot assign roles to users

Solution

1. Step 1: Check the policy structure

   The policy snippet shows bindings but does not specify the resource it applies to.

2. Step 2: Understand IAM policy application

   IAM policies must be attached to a specific resource (project, folder, or organization) to take effect.

3. Final Answer:

   The policy is missing the resource it applies to -> Option B

4. Quick Check:

   IAM policy needs resource context [OK]

Hint: IAM policies must be attached to resources to work [OK]

Common Mistakes:

• Assuming roles can be assigned without resource context
• Thinking role names are invalid
• Believing member emails are wrongly formatted

5. You want to give a team member permission to manage Compute Engine instances but not billing or project settings. Which IAM role should you assign?

hard

A. roles/compute.instanceAdmin

B. roles/owner

C. roles/billing.admin

D. roles/viewer

Solution

1. Step 1: Identify required permissions

   The team member needs to manage Compute Engine instances only, without billing or project-wide control.

2. Step 2: Match role to permissions

   roles/compute.instanceAdmin allows managing instances but not billing or project settings, unlike roles/owner or billing.admin.

3. Final Answer:

   roles/compute.instanceAdmin -> Option A

4. Quick Check:

   Instance admin role limits permissions correctly [OK]

Hint: Use specific roles, not owner or billing, for limited access [OK]

Common Mistakes:

• Assigning owner role gives too many permissions
• Using billing.admin grants billing rights unnecessarily
• Choosing viewer role does not allow managing instances