Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your financial services company is building a compliance archiving system on Google Cloud to store trade confirmation files in an existing Cloud Storage bucket. Both existing files already in the bucket and all future uploaded files must meet strict regulatory Write Once, Read Many (WORM) requirements:
Which approach should you implement?
A Cloud Storage bucket retention policy defines a minimum retention period during which no object in the bucket can be deleted or replaced. Locking that policy with Bucket Lock makes the configuration permanent and irreversible, establishing true Write Once, Read Many (WORM) immutability for regulatory compliance.
403 - retentionPolicyNotMet error.resourcemanager.projects.delete so the project cannot be deleted prematurely.Delete rule will only remove an object after it has fulfilled the 7-year retention period.Unlike unlocked policies, holds, or versioning alone, combining a locked bucket retention policy with Object Lifecycle Management delivers irreversible, bucket-wide WORM enforcement for both existing and future objects while automating cost-effective cleanup after the compliance window closes.
Object Versioning preserves older versions of objects as noncurrent versions whenever a live object is overwritten or deleted. The default event-based hold bucket property automatically attaches an event-based hold flag to newly uploaded objects, blocking deletion or replacement until the hold is released.
You needed to retain documents indefinitely until an unpredictable business event occurred (such as closing an account or paying off a loan) and then begin a locked retention countdown once that event happened.
Object Retention Lock allows setting individual retain-until times on specific objects rather than uniformly across a bucket, with Unlocked (GOVERNANCE) mode permitting authorized modifications. Soft delete preserves recently deleted objects for a configured recovery window so they can be restored.
Unlocked mode, users with the storage.objects.overrideUnlockedRetention permission can shorten or remove an object's retention configuration at any time, violating the requirement to block project owners and administrators from early deletion.Unlocked (modifiable by authorized users) and Locked (COMPLIANCE, irreversible).Different files in the same bucket required distinct, object-specific retention dates, the mode were set to Locked, existing objects were updated via a batch job, and an automated lifecycle rule were added for post-retention deletion.
An unlocked bucket retention policy enforces a minimum age before objects can be deleted or overwritten, while Identity and Access Management (IAM) permissions restrict which principals can invoke storage.buckets.update to alter bucket settings.
storage.buckets.update—such as a member of the dedicated security group or a project owner—can reduce the retention period or remove the policy completely.resourcemanager.projects.delete, leaving the entire project vulnerable to premature deletion.You were only protecting against accidental application-level deletions during a testing phase and needed the flexibility to shorten or remove the retention policy later.
Best practice is to configure and verify an unlocked retention policy first, and then permanently lock it with Bucket Lock once the retention duration is confirmed.
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