Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are managing permissions for a data analyst who needs access to resources in your Google Cloud project.
The analyst has the following requirements:
reports-bucket.Following the principle of least privilege, how should you configure IAM roles for this user?
roles/storage.objectCreator) role at the project level, and grant the Storage Object Viewer (roles/storage.objectViewer) role at the bucket level for reports-bucket.This option inverts the resource levels for the roles, granting the Storage Object Creator role across the entire project and restricting the Storage Object Viewer role to a single bucket.
roles/storage.objectCreator at the project level enables the user to upload and create objects in every bucket within the project, violating the requirement to restrict uploads exclusively to reports-bucket.roles/storage.objectViewer to the bucket level means the user cannot view or read objects stored in any of the other buckets across the project.The analyst needed to upload files into every bucket across the entire project but was only permitted to view and inspect uploaded objects within reports-bucket.
roles/storage.objectViewer) role at the project level, and grant the Storage Object Creator (roles/storage.objectCreator) role at the bucket level for reports-bucket.This configuration applies Identity and Access Management (IAM) roles at distinct levels of the Google Cloud resource hierarchy to enforce the principle of least privilege. It pairs project-level inheritance for project-wide read permissions with a targeted bucket-level binding for object creation.
roles/storage.objectViewer) role at the project level grants read access to all objects stored in all buckets under that project because IAM permissions are inherited additively down the resource hierarchy.roles/storage.objectCreator) role directly on reports-bucket ensures that object creation and write privileges are restricted specifically to that bucket alone.
This approach cleanly fulfills both operational requirements without over-granting permissions. The user receives only read access across the project and write access where needed, avoiding unnecessary administrative overhead or security exposure.
roles/storage.legacyBucketReader) role at the project level, and grant the Storage Legacy Object Owner (roles/storage.legacyObjectOwner) role at the bucket level for reports-bucket.This option relies on Legacy Bucket and Legacy Object IAM roles that were designed for backward compatibility with the legacy ACL system.
roles/storage.legacyBucketReader) role only grants permissions to list the contents of a bucket and inspect bucket metadata; it does not grant permissions to read the actual object data contents across all buckets in the project.reports-bucket grants full control over objects (including deleting objects and modifying object ACLs) rather than merely allowing object creation and uploading.storage.objects.get).roles/storage.objectViewer and roles/storage.objectCreator.The requirement specifically mandated managing legacy XML API permissions in tandem with bucket ACLs where the user only needed to list bucket contents and administer object ownership in reports-bucket.
roles/storage.admin) role at the project level, and configure a bucket Access Control List (ACL) to restrict write access to reports-bucket.This option grants the Storage Admin (roles/storage.admin) role at the project level, which gives full administrative control over all storage buckets and objects, and attempts to restrict write access using legacy Access Control Lists (ACLs).
storage.buckets.delete, storage.buckets.setIamPolicy, and storage.objects.delete.The user were a storage infrastructure administrator responsible for managing bucket lifecycles, permissions policies, and storage configurations across the entire Google Cloud project.
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