Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A financial analytics company stores transaction export files in a Cloud Storage bucket with the Standard storage class. To optimize storage costs and adhere to company retention guidelines, the data engineering team must implement an Object Lifecycle Management policy that meets the following requirements:
Which lifecycle management configuration correctly satisfies these requirements?
This configuration applies three separate Delete actions at different age thresholds (30, 90, and 365 days) rather than transitioning objects between storage classes.
30 days of age, all objects will be permanently deleted after 30 days. The subsequent rules for 90 days and 365 days will never take effect.Delete rules on a bucket results in the shortest age condition always taking precedence.The business requirement required all objects to have a strict 30-day lifespan with immediate deletion and no archiving requirements.
Object Lifecycle Management is a built-in feature of Google Cloud Storage that automates the transition of objects to colder storage classes or deletes them when predefined conditions are met. Rules are assigned at the bucket level and evaluated asynchronously by Google Cloud Storage.
SetStorageClass action set to NEARLINE, paired with the age condition of 30 days and matchesStorageClass set to STANDARD. When a Standard object reaches 30 days of age, Cloud Storage transitions it to Nearline storage without rewriting the data.SetStorageClass action set to COLDLINE, paired with the age condition of 90 days and matchesStorageClass set to NEARLINE. This ensures that objects already in Nearline transition to Coldline once their overall age reaches 90 days.Delete action with an age condition of 365 days, removing objects that have reached the end of their 1-year retention lifecycle regardless of their current storage class.SetStorageClass does not rewrite the object data or incur retrieval fees or early deletion penalties during transition.This configuration cleanly separates the transition and deletion criteria into discrete, standard lifecycle rules using the native SetStorageClass and Delete actions. It avoids common misconfigurations by explicitly specifying both the target age and the current matchesStorageClass condition for each tier.

This option sets up incorrect target storage classes and completely replaces the Delete action with a SetStorageClass action at day 365.
STANDARD at 30 days (which the objects already possess). Rule 2 sets objects to NEARLINE at 90 days instead of 30 days, and Rule 3 transitions objects to COLDLINE at 365 days rather than deleting them.COLDLINE retains the data indefinitely in cold storage, violating data retention and deletion policies.SetStorageClass on objects already in Standard storage incurs Class A operation fees without providing any business or cost benefit.The policy required retaining objects forever, keeping them in Standard storage for 90 days, Nearline for up to 365 days, and then archiving them in Coldline storage permanently.
This configuration attempts to bypass intermediate storage tiers by moving objects directly from Standard storage to Coldline storage at 90 days, completely skipping the Nearline storage tier. It then configures a deletion rule that only targets objects in Coldline storage.
Delete action strictly to matchesStorageClass: COLDLINE, any object that failed to transition or was uploaded directly to a different class would never be deleted at 365 days.The business requirements specified that objects should remain in Standard storage for 90 days and transition directly to Coldline storage, with no Nearline intermediate tier required.
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