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 analytics team needs to allow a junior data analyst to view and read files within a specific Cloud Storage bucket named sales-reporting-data.
The solution must enforce the principle of least privilege by meeting the following constraints:
sales-reporting-data.Which Identity and Access Management (IAM) configuration should you implement?
The Storage Admin (roles/storage.admin) role is a predefined role that grants complete administrative control over Cloud Storage resources, including buckets and objects.
storage.objects.* and storage.buckets.*.This option would be correct if the scenario required a lead data architect to manage bucket metadata, set up retention policies, configure object lifecycle management, and control user access on the specific bucket.
The basic Viewer (roles/viewer) role is a legacy IAM role that grants read-only permissions across all Google Cloud services and resources within an entire project.
roles/viewer at the project level gives the analyst read access across BigQuery datasets, Compute Engine instances, Cloud SQL databases, and all other Cloud Storage buckets in the project.This option would be appropriate if the user were a project auditor who genuinely required read-only visibility into every resource, service configuration, and data asset across the entire Google Cloud project.
The Storage Object Viewer (roles/storage.objectViewer) role is a Google Cloud predefined role designed specifically for read-only access to objects within Cloud Storage. It bundles essential permissions such as storage.objects.get (to read object data and metadata) and storage.objects.list (to list objects within a bucket) without including any administrative or modification permissions.

roles/storage.objectViewer allows the analyst to list and download data files without providing create, edit, or delete capabilities.storage.objects.create, storage.objects.delete, or storage.buckets.update permissions, ensuring files and configurations cannot be altered.Applying a focused predefined role at the bucket level directly aligns with Google Cloud security best practices. Unlike basic roles or project-wide assignments, resource-level predefined roles restrict both the scope of permissions and the scope of resources, fulfilling all security constraints seamlessly.
In Google Cloud IAM, permissions (such as storage.objects.get) represent discrete, atomic authorization checks that allow a user or service account to perform specific API operations.
service.resource.verb).user:email) to roles (roles/roleName), never directly to permissions.This choice would only be conceptually valid if you were defining a Custom IAM Role by selecting specific individual permissions, which you would then assign to the user on the resource.
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