Cloud Digital Leader Trust and security with Google Cloud Practice Question

A company wants to enforce that all Cloud Storage buckets in a project have uniform bucket-level access enabled. Which Google Cloud tool should they use?

⚠ Common exam trap

Google Cloud often tests the distinction between monitoring/logging tools (like Audit Logs) and enforcement tools (like Organization Policies), leading candidates to choose a reactive solution instead of a proactive, policy-based one.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Define an Organization Policy with a constraint on uniform bucket-level access.

Organization Policies in Google Cloud allow administrators to enforce constraints across the entire resource hierarchy. The constraint `constraints/storage.uniformBucketLevelAccess` can be applied at the project, folder, or organization level to require uniform bucket-level access on all Cloud Storage buckets, preventing any bucket from being created or updated without it.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Use Cloud Audit Logs to monitor and alert on non-compliant buckets.
Why it's wrong here
Cloud Audit Logs record actions and provide an audit trail, but they cannot prevent a bucket from being created without uniform access. They are a reactive monitoring tool; even with alerts triggered by logs, the non-compliant bucket already exists and must be remediated manually. Enforcement requires a preventative mechanism that rejects non-compliant configurations at the time of the API call, which audit logs do not do.
✓
Define an Organization Policy with a constraint on uniform bucket-level access.
Why this is correct
An Organization Policy with the constraint *storage.uniformBucketLevelAccess* enforces that every bucket in a given hierarchy must have uniform bucket-level access enabled. When set to True, this list constraint blocks any request to create or update a bucket that does not have uniform access, effectively acting as an immutable compliance guardrail. This is the correct because it is a prerequisite enforcement method provided by Google Cloud's organization policy service.
✗
Set an IAM policy to deny access to buckets without uniform access.
Why it's wrong here
IAM deny policies restrict who can perform certain actions on resources, but they do not modify or enforce bucket configuration settings like uniform access. A deny rule could attempt to block access to buckets lacking uniform access, but IAM conditions would require a custom attribute that isn't inherently exposed. Moreover, IAM is designed for identity-based access control, not for validating resource properties or enforcing configuration standards.
✗
Use Cloud Key Management Service to rotate keys.
Why it's wrong here
Cloud Key Management Service rotates cryptographic keys used for encryption, which protects data at rest but is completely separate from access control settings. Uniform bucket-level access governs how object-level permissions are evaluated, whereas KMS handles key lifecycle and encryption. Rotating keys would not cause a bucket to adhere to uniform access requirements and therefore does not address the stated enforcement need.

Go deeper

Cloud Digital Leader Trust and security with Google Cloud Practice Question

Why each option matters

Option-by-option breakdown

Related to this question