Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data engineering team wants to allow a new team member to upload raw data files to a Google Cloud Storage bucket. Following the principle of least privilege, the team wants to ensure the user receives only the specific capability to write objects (such as storage.objects.create), without gaining unnecessary administrative control or wide access across the entire project.
Which statement accurately describes how Google Cloud IAM structures permissions and roles to fulfill this access requirement?
Predefined roles are fine-grained, Google-managed roles tailored to specific services and job duties (e.g., Storage Object Creator, Storage Admin). IAM deny policies are rules that prevent principals from using specific permissions, overriding any granted allow roles.
Every predefined role had universal administrative privileges and IAM followed a pure blacklist/subtractive permission model rather than a role-based allow model.
Basic roles (previously known as primitive roles: Owner, Editor, and Viewer) are broad, legacy roles that existed prior to IAM. They grant blanket access across almost all Google Cloud services within an entire project.
Editor gives extensive modification and deletion rights to virtually all services in the project, which directly contradicts least-privilege security requirements.roles/storage.objectCreator) or custom roles.A scenario required broad, unrestricted development privileges across all computing, storage, and networking resources in a disposable sandbox environment.
This option incorrectly asserts that Google Cloud IAM allows direct attachment of standalone individual permissions (like storage.objects.create) directly to a user's identity in an IAM policy.
Google Cloud IAM operated on an Access Control List (ACL) model that permitted assigning raw API actions directly to user entities without utilizing roles as an intermediary abstraction.
In Google Cloud Identity and Access Management (IAM), permissions are the fundamental, granular units of access that define discrete actions allowed on a resource (for example, storage.objects.create or storage.buckets.list). Roles are organized collections or bundles of one or more permissions designed to represent specific operational responsibilities.
roles/storage.objectCreator) or build a custom role containing only the necessary permissions and bind it at the bucket level.
Understanding that permissions exist as the underlying mechanism packaged within roles is foundational in Google Cloud. It ensures administrators use tailored predefined or custom roles at the correct resource hierarchy level rather than defaulting to overly broad basic roles.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated