An enterprise SaaS platform generates automated database backup archives every night. Engineering teams require high-speed, immediate access to these backup files during the first 30 days to support rapid point-in-time recovery during software release cycles. After 30 days, access is rarely needed (less than once per year), but compliance regulations dictate that all backup files must be retained for 3 years and remain immediately accessible within milliseconds if requested during an audit. Which Cloud Storage configuration meets these requirements while minimizing total cost?
- Set the bucket's default storage class to Standard, and configure an Object Lifecycle Management rule to transition objects to Archive storage 30 days after creation.Cevap
- BSet the bucket's default storage class to Archive storage at bucket creation so all backup files are written directly to the lowest-cost tier.
- CSet the bucket's default storage class to Standard, and apply per-object Access Control Lists (ACLs) to change individual object storage classes to Archive 30 days after creation.
- DSet the bucket's default storage class to Standard, and configure an Object Lifecycle Management rule to transition objects to Nearline storage after 30 days and delete them after 90 days.
Cevap
Set the bucket's default storage class to Standard, and configure an Object Lifecycle Management rule to transition objects to Archive storage 30 days after creation.
The solution requiring Standard storage for the first 30 days followed by an Object Lifecycle Management transition to Archive storage optimally aligns with the workload profile. Standard storage avoids retrieval fees during frequent early recovery operations, while Archive storage provides the lowest cost tier for long-term retention beyond 30 days while ensuring millisecond latency when compliance audits occur.
Adım Adım Çözüm
Anahtar Kavram
Selecting Cloud Storage classes based on access patterns and configuring Object Lifecycle Management to automate cost-effective storage transitions.