Courseiva
Planning and Configuring a Cloud SolutionhardMultiple ChoiceObjective-mapped

Google ACE Planning and Configuring a Cloud Solution Practice Question

A company has a Cloud Storage bucket that stores sensitive files. They want to ensure that objects are automatically deleted after 30 days to comply with data retention policies. Additionally, they need to keep a copy of all object deletions for audit purposes. Which combination of bucket settings should they use?

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

Enable object versioning and add a lifecycle rule with condition 'Age: 30 days' and action 'Delete' for the current version

Cloud Storage lifecycle management can automatically delete objects after 30 days using a SetStorageClass or Delete action with an Age condition. Object versioning enables keeping deleted or overwritten versions (noncurrent versions). By combining lifecycle rules to delete noncurrent versions after a period (e.g., 0 days) or simply keeping them, you can audit deletions. However, the question says 'keep a copy of all object deletions for audit purposes' – versioning retains noncurrent versions when objects are deleted or overwritten. Lifecycle rules can be set to expire the noncurrent versions after a longer period, but for audit purposes, you would keep them indefinitely or for a long period. The simplest is to enable versioning and set a lifecycle rule to delete objects after 30 days; deleted objects become noncurrent versions and are retained until a lifecycle rule removes them. To keep a copy, you might not delete noncurrent versions. The correct answer: enable versioning and add a lifecycle rule with condition Age:30 and action Delete for current objects. Noncurrent versions will remain unless a separate rule deletes them. For audit, you may also set a rule to delete noncurrent versions after a longer period, but the question asks for 'which combination' – the combination that achieves both requirements is versioning + lifecycle rule to delete current objects after 30 days. The deleted objects become noncurrent versions, which are retained (so audit copy is kept). If they need to keep the deletion records forever, they should not delete noncurrent versions. Among options, the one that includes versioning and a lifecycle rule that deletes objects after 30 days is correct. Option D includes versioning and lifecycle rule: 'Delete object after 30 days' – that's it. Option A is 'Object versioning' only – no deletion. Option B is 'Bucket lock' – not for automatic deletion. Option C is 'Lifecycle rule to delete objects after 30 days' without versioning – then when deleted, there is no version history. So D is best.

Answer analysis

Option-by-option breakdown

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

  • Enable bucket lock and use object holds

    Why it's wrong here

    Bucket Lock enforces a Write-Once-Read-Many (WORM) policy that prevents objects from being deleted or overwritten, and object holds indefinitely block deletion until explicitly released. Neither mechanism schedules automatic deletion after 30 days; instead they preserve data for an indefinite or externally controlled period. This fails the core requirement for automated lifecycle-based deletion, and holds would require manual release before any deletion could occur.

  • Enable object versioning and set a retention policy with a retention period of 30 days

    Why it's wrong here

    Enabling object versioning alone does not trigger deletion, and a retention policy imposes a minimum retention period during which objects cannot be deleted, overwritten, or have their retention time shortened. After 30 days the retention policy simply expires and allows deletion; it does not autonomously delete objects at day 30. The requirement is automatic deletion after 30 days, so this configuration actually protects objects from lifecycle deletion during that window and leaves them untouched afterward.

  • Enable a lifecycle rule with condition 'Age: 30 days' and action 'Delete'

    Why it's wrong here

    A lifecycle rule with Age:30 and Delete will remove the current object version after 30 days, satisfying the deletion timing, but without versioning the delete action permanently erases the object's data and metadata, leaving no audit copy. The company needs to retain an immutable or recoverable record of the deletion; versioning preserves the deleted object as a noncurrent version, which a bare lifecycle rule cannot do. Therefore this option meets only half the requirement and offers no forensic trail.

  • Enable object versioning and add a lifecycle rule with condition 'Age: 30 days' and action 'Delete' for the current version

    Why this is correct

    Versioning retains noncurrent versions when objects are deleted, providing an audit trail. The lifecycle rule deletes current versions after 30 days, and the noncurrent versions remain (or can be deleted later with a separate rule). This combination meets both requirements.

About these practice questions

This ACE question is part of Courseiva's 769-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.