Question-31: Object Versioning is the GCP's way of automatic archival. Once object versioning is enabled for a bucket, every version of the object (resulting from multiple writes) will be given an identification tag, which will be called generation number and all of the versions will be archived automatically. If you have object versioning enabled on a multi-regional bucket, what will the following lifecycle config file do? {lifecycle: { rule: [ { action: {type: Delete}, condition: { age: 30, isLive: true } }, { action: { type: SetStorageClass, storageClass: COLDLINE}, condition: { age: 365, matchesStorageClass: [MULTI_REGIONAL] } } ] } }
A. Archive items older than thirty days (the second rule has no effect).
B. Remove things older than thirty days (the second rule has no effect).
C. Archive objects older than thirty days and transfer things to Coldline Storage after one year.
D. Remove things older than 30 days and place them in Coldline Storage after 365 days.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 3 Explanation: Option-1. Deletions always take precedence over SetStorage (so if any objects meet both rules when this is created - it will delete). Option-2. The bucket has object versioning enabled. A deletion of a versioned object with isLive:true, simply removes the live object and creates a noncurrent version -which is essentially an archived version of the object. Option-3. These noncurrent versions (considered archived) - are now moved to ColdLine Storage after 365 days So reading Option-3 “Archive objects older than 30 days and move objects to Coldline Storage after 365 days� - makes most sense. The bucket has versioning enabled so the delete action on Live items (isLive:true) makes them non-current, does not delete them. Second rule moves to coldline. Option-3 is right.