Cloud identity and access management in Cybersecurity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the entity that represents a user or service in cloud IAM.

Cybersecurity

entity = "[1]"

Drag options to blanks, or click blank then click option'

Apolicy

Bbucket

Cfirewall

Dprincipal

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'policy' with the entity that accesses resources.

Using 'bucket' which is a storage container, not an identity.

In cloud IAM, a principal is the entity (user, service, or system) that can be granted permissions.

2fill in blank

medium

Complete the code to define a set of permissions assigned to a user in cloud IAM.

Cybersecurity

role = "[1]"

Drag options to blanks, or click blank then click option'

Afirewall

Brole

Cregion

Dnetwork

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'firewall' which controls network traffic, not permissions.

Confusing 'region' with access control.

A role in cloud IAM is a collection of permissions assigned to a user or service.

3fill in blank

hard

Fix the error in the statement that grants permissions to a user by filling the blank.

Cybersecurity

grant_access(principal, [1])

Drag options to blanks, or click blank then click option'

Arole

Bbucket

Cfirewall

Dregion

Attempts:

3 left

💡 Hint

Common Mistakes

Passing 'bucket' which is a storage resource, not a permission set.

Using 'firewall' or 'region' which are unrelated to access permissions.

The function grant_access requires a role to specify what permissions are granted to the principal.

4fill in blank

hard

Fill both blanks to create a policy that assigns a role to a principal.

Cybersecurity

policy = {
  'bindings': [
    {
      'role': '[1]',
      'members': ['[2]']
    }
  ]
}

Drag options to blanks, or click blank then click option'

Aroles/viewer

Broles/editor

Cuser:[e-mail]

DserviceAccount:[e-mail]

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up roles and members in the policy structure.

Using service account instead of a user email for this example.

This policy binds the roles/viewer role to the user [e-mail].

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps users to their assigned roles if the role includes 'admin'.

Cybersecurity

admin_users = { [1]: [2] for [3], [2] in user_roles.items() if 'admin' in [2] }

Drag options to blanks, or click blank then click option'

Auser

Brole

Duser_roles

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing keys and values in the dictionary comprehension.

Using the wrong variable names for iteration.

This comprehension creates a dictionary of users and their roles where the role contains 'admin'. The keys are users, and the values are roles.

Practice

1. What is the main purpose of Cloud Identity and Access Management (IAM)?

easy

A. To control who can access cloud resources and what actions they can perform

B. To store data securely in the cloud

C. To monitor network traffic in cloud environments

D. To manage cloud billing and payments

Solution

1. Step 1: Understand the role of IAM

   IAM is designed to manage access permissions for users and services in the cloud.

2. Step 2: Compare options with IAM purpose

   Only To control who can access cloud resources and what actions they can perform describes controlling access and actions, which is the core of IAM.

3. Final Answer:

   To control who can access cloud resources and what actions they can perform -> Option A

4. Quick Check:

   IAM controls access and permissions [OK]

Hint: IAM manages access and permissions, not data or billing [OK]

Common Mistakes:

• Confusing IAM with data storage services
• Thinking IAM handles billing or payments
• Mixing IAM with network monitoring tools

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

easy

A. Delete the user and recreate with the role

B. Assign the role directly to the user in the IAM policy

C. Create a new user without any roles

D. Assign the role to the cloud storage bucket

Solution

1. Step 1: Understand role assignment in IAM

   Roles are assigned to users or groups to grant permissions.

2. Step 2: Evaluate options for correct syntax

   Assigning the role directly to the user is the correct method; other options are incorrect or unrelated.

3. Final Answer:

   Assign the role directly to the user in the IAM policy -> Option B

4. Quick Check:

   Roles assigned directly to users [OK]

Hint: Roles go to users or groups, not resources like buckets [OK]

Common Mistakes:

• Assigning roles to resources instead of users
• Creating users without roles expecting access
• Deleting users unnecessarily to assign roles

3. Consider this IAM policy snippet:

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

What permission does Alice have?

medium

A. Write access to modify resources

B. Full admin access to all resources

C. No access to any resources

D. Read-only access to view resources

Solution

1. Step 1: Identify the role in the policy

   The role assigned is "roles/viewer", which is a predefined role for read-only access.

2. Step 2: Understand what "roles/viewer" means

   This role allows viewing resources but not modifying or administering them.

3. Final Answer:

   Read-only access to view resources -> Option D

4. Quick Check:

   roles/viewer = read-only access [OK]

Hint: "viewer" role means read-only access [OK]

Common Mistakes:

• Confusing viewer with admin or editor roles
• Assuming viewer can modify resources
• Ignoring the role name and guessing permissions

4. A cloud IAM policy is not working as expected. The user cannot access resources despite being assigned a role. What is a common mistake to check?

medium

A. The cloud region is incorrect

B. The cloud storage bucket is empty

C. The user email is misspelled in the policy

D. The user has too many roles assigned

Solution

1. Step 1: Identify common IAM policy errors

   One frequent error is a typo in the user identifier, such as a misspelled email.

2. Step 2: Understand impact of misspelled user

   If the user email is wrong, the policy does not apply to the intended user, causing access failure.

3. Final Answer:

   The user email is misspelled in the policy -> Option C

4. Quick Check:

   Misspelled user email blocks access [OK]

Hint: Check user email spelling first when access fails [OK]

Common Mistakes:

• Ignoring typos in user or group names
• Blaming resource content instead of permissions
• Assuming too many roles cause denial

5. You want to give temporary access to a contractor for only one cloud project without exposing other projects. Which IAM feature should you use?

hard

A. Assign a role with project-level scope and set an expiration time

B. Add the contractor to the organization-wide admin group

C. Create a new user with full access to all projects

D. Share your personal login credentials with the contractor

Solution

1. Step 1: Identify requirement for limited, temporary access

   The contractor needs access only to one project and only temporarily.

2. Step 2: Choose IAM feature matching scope and duration

   Assigning a role scoped to the project with an expiration time fits the need perfectly.

3. Step 3: Evaluate other options

   Other options give too broad access or are insecure practices.

4. Final Answer:

   Assign a role with project-level scope and set an expiration time -> Option A

5. Quick Check:

   Project-scoped role + expiration = temporary limited access [OK]

Hint: Use scoped roles with expiration for temporary access [OK]

Common Mistakes:

• Giving organization-wide admin rights unnecessarily
• Sharing personal credentials (security risk)
• Creating users with full access instead of limited