You add a binding in an IAM policy that assigns the role roles/storage.objectViewer to a user. What is the immediate effect on that user's permissions?
Think about what the roles/storage.objectViewer role allows.
The roles/storage.objectViewer role grants read access to objects in Cloud Storage buckets. It does not allow creating buckets, deleting objects, or modifying IAM policies.
Consider the following statements about IAM policy bindings. Which one is correct?
Think about the structure of an IAM policy binding.
Each binding assigns exactly one role to one or more members. Multiple roles require multiple bindings. Bindings can assign roles to users, groups, service accounts, and can be applied at various resource levels.
You bind the role roles/owner to a user on a project. What is the main security risk of this action?
Consider the permissions included in the roles/owner role.
The roles/owner role grants full control over all resources in the project, including deleting the project and all resources, which is a significant security risk if misused.
Identify the correct JSON snippet that binds the role roles/editor to the group dev-team@example.com on a project.
Check the member type prefix and email spelling.
The correct member prefix for a group is group:. The email must be spelled correctly. Option A uses the correct prefix and email.
Given a role binding at the organization level, which statement best describes how it affects projects and resources below it?
Think about how IAM policies propagate in GCP's resource hierarchy.
IAM policies set at higher levels like organization or folder automatically apply to all child resources unless explicitly denied or overridden.