Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise security engineer is auditing legacy Google Cloud Storage buckets that contain sensitive data. Currently, access to files within the buckets is governed by a combination of legacy Object Access Control Lists (ACLs) and Cloud IAM role bindings. The security team mandates that object-level ACLs must be eliminated in favor of centralized IAM policy enforcement to prevent permission drift and simplify compliance auditing.
Which strategy should the security engineer implement to transition the buckets to Uniform Bucket-Level Access (UBLA) without disrupting access for authorized users?
Uniform Bucket-Level Access (UBLA) is a Cloud Storage security feature that unifies and simplifies access management by enforcing permissions exclusively through Identity and Access Management (IAM). When UBLA is enabled on a bucket, Cloud Storage ignores all existing object-level and bucket-level Access Control Lists (ACLs), ensuring that access is granted solely through IAM policies defined at the bucket, folder, project, or organization level.
roles/storage.objectViewer) or Storage Object Admin (roles/storage.objectAdmin)—at the bucket level ensures legitimate users retain required read/write permissions.This approach follows Google Cloud best practices for IAM migration. It proactively maps out legacy access patterns, grants appropriate least-privilege IAM roles at the bucket resource level, and cleanly deactivates object-level ACL parsing by enabling UBLA.
This option advocates using legacy ACL manipulation commands to set bucket ACLs to private, granting broad Storage Admin (roles/storage.admin) roles at the project level, and rewriting or re-uploading all stored objects.
The organization needed to wipe all existing data and provision completely new storage infrastructure from scratch under full project-level administration.
Bucket Lock is a compliance and governance feature in Cloud Storage that permanently locks a bucket's retention policy, ensuring objects cannot be deleted or overwritten until a specified retention period has elapsed (supporting WORM compliance).
The security requirement called for preventing any user or administrator from deleting financial audit records for a mandatory 7-year regulatory period.
This option suggests modifying object-level metadata to assign IAM roles like Storage Legacy Object Owner (roles/storage.legacyObjectOwner) directly to individual objects before applying an Organization Policy.
roles/storage.legacyObjectOwner role is an IAM role granted at the bucket or project level to mimic legacy ACL behaviors, not an attribute that can be written to object metadata.getIamPolicy/setIamPolicy).The requirement were to grant legacy-compatible object management permissions at the bucket level to support legacy tools that still expect ACL-like role mappings.
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 Validated