Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A financial services organization stores transaction audit files in a Cloud Storage bucket with Object Versioning enabled. The files are written under the prefix audit-logs/ and follow specific access patterns:
audit-logs/ prefix should be permanently removed 14 days after becoming noncurrent.Which Object Lifecycle Management (OLM) configuration meets these requirements with the least operational overhead?
audit-logs/ to transition storage to Nearline at age 30, transition to Coldline at age 90, delete live objects at age 365, and delete noncurrent versions using daysSinceNoncurrentTime: 14.Cloud Storage Object Lifecycle Management (OLM) allows administrators to define declarative rules consisting of actions (such as SetStorageClass and Delete) coupled with specific conditions (such as Age, MatchesPrefix, IsLive, and DaysSinceNoncurrentTime). Cloud Storage automatically inspects objects within the bucket and executes the configured actions asynchronously without requiring external compute infrastructure.
SetStorageClass with target Nearline at Age: 30 aligns with monthly access patterns.SetStorageClass with target Coldline at Age: 90 matches quarterly access requirements.MatchesPrefix: audit-logs/ condition ensures that only audit log objects are affected by these policies.Delete action with Age: 365 purges live logs after one year.DaysSinceNoncurrentTime: 14 (or IsLive: false with noncurrent age) ensures that superseded or deleted log versions are permanently removed 14 days after becoming noncurrent, preventing unbounded storage accumulation in version-enabled buckets.
Native lifecycle policies execute directly within the storage control plane, providing predictable lifecycle transitions and deletions while strictly honoring prefix constraints and version states.
Autoclass automatically transitions objects between Standard, Nearline, Coldline, and Archive based on individual object access patterns. A Bucket Lock (Retention Policy) places a compliance lock on objects to prevent them from being deleted until the retention period elapses.
audit-logs/) or automated time-bound object deletions.Access patterns were entirely unpredictable across the entire bucket and regulatory mandates required a legal, immutable compliance lock preventing data deletion.
This architecture relies on event-driven computing via Cloud Storage Pub/Sub notifications and Cloud Functions to handle storage tiering and deletion programmatically via custom code and storage API mutations.
Custom business logic required external validation against an on-premises database or third-party approval system before authorizing storage tier shifts or deletions.
This configuration moves objects directly to Archive storage after 30 days and uses Identity and Access Management (IAM) Deny policies to block identity access to noncurrent object versions.
Data was strictly intended for long-term disaster recovery accessed less than once a year, and access needed to be administratively blocked without modifying bucket contents.
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