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 data analytics team stores reporting archives in a Cloud Storage bucket using the Standard storage class. The team identifies that reports are accessed frequently during the first 90 days after creation, but access drops significantly after this period.
To optimize storage costs, the team needs to automatically move reports older than 90 days to the Nearline storage class. Additionally, to avoid Class A transition operation charges outweighing storage savings on small files, only objects larger than 5 MiB (5,242,880 bytes) should be transitioned.
Which Object Lifecycle Management configuration should you implement on the bucket?
Delete action, and specify the conditions daysSinceNoncurrentTime = 90, isLive = false, and sizeAboveBytes = 5242880.The Delete action permanently removes objects or object versions from Cloud Storage. The daysSinceNoncurrentTime condition applies exclusively to buckets with Object Versioning enabled and measures the number of days that have passed since an object version was superseded and became noncurrent.
daysSinceNoncurrentTime evaluates replaced or deleted object versions rather than active live objects that are 90 days old from their initial creation date.SetStorageClass or define a destination class like Nearline.daysSinceNoncurrentTime has no effect on buckets without Object Versioning enabled.The scenario stated: "The team has Object Versioning enabled and wants to permanently delete historical, noncurrent versions of reports that have been replaced for more than 90 days to free up space."
SetStorageClass action set to NEARLINE, and specify the conditions age = 90, matchesStorageClass = STANDARD, and sizeBelowBytes = 5242880.The sizeBelowBytes condition in Object Lifecycle Management matches objects whose data payload is strictly smaller than the specified threshold. It is typically used to set an upper size limit for actions, such as cleaning up small temporary metadata files or deleting empty objects.
sizeBelowBytes targets only files smaller than 5 MiB for transition to Nearline storage.sizeBelowBytes evaluates only object data payload size in bytes and excludes object metadata overhead.sizeBelowBytes is 5 TiB.The requirement stated: "The team wants to move only lightweight thumbnail or summary files smaller than 5 MiB to Nearline storage while keeping all large reporting datasets in Standard storage."
SetStorageClass action set to NEARLINE, and specify the conditions age = 90, matchesStorageClass = STANDARD, and sizeAboveBytes = 5242880.Object Lifecycle Management (OLM) in Cloud Storage allows users to define automated rules that manage objects throughout their lifecycle. By using the SetStorageClass action, Cloud Storage automatically transitions matching objects to colder, lower-cost storage tiers (such as Nearline, Coldline, or Archive) without requiring manual scripts or data rewrites.
age condition to 90 ensures that Cloud Storage evaluates the object's creation date and triggers the action once the object reaches 90 days of age.matchesStorageClass to STANDARD ensures the rule only applies to objects currently residing in Standard storage, avoiding unnecessary re-evaluations or redundant operations.SetStorageClass action specifies NEARLINE as the target tier, which matches data accessed less than once a month.sizeAboveBytes to 5242880 (5 MiB) establishes a minimum size filter. Small objects beneath this threshold are excluded, preventing the Class A transition operation fee from exceeding the ongoing storage cost savings.SetStorageClass do not rewrite data, avoiding inter-region replication fees and data retrieval charges during transition.age, matchesStorageClass, sizeAboveBytes, matchesPrefix, and matchesSuffix to target exact object subsets.This configuration directly targets the specific access pattern by shifting data to the appropriate storage class while safeguarding the organization against uneconomical Class A API transition costs on small files.
NEARLINE.Object holds (such as event-based holds and temporary holds) and Bucket Retention Policies are data governance tools used to enforce data immutability and compliance (WORM — Write Once, Read Many). They prevent objects from being deleted or overwritten until a retention duration has elapsed or a hold is explicitly released.
sizeAboveBytes.The scenario stated: "Regulatory compliance requires that financial reports must remain immutable and protected against accidental deletion or modification for at least 90 days after creation."
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