Examkin

Soru

Zorluk: Çok zorPlanning Cloud Storage Buckets and Storage Classes

A fintech enterprise is designing a storage architecture on Google Cloud for financial audit logs. The access pattern and compliance requirements are defined as follows:

• Log objects are continuously uploaded and accessed heavily by real-time fraud detection systems during their first 30 days.
• After 30 days, access drops to near-zero, but data must be retained for 7 years (2,5552,555 days) to comply with legal regulations.
• In the rare event of a regulatory audit, objects must remain retrievable in milliseconds without multi-hour vault restoration delays.
• The architecture must guarantee immutability against deletion or modification during the compliance window while minimizing total cost of ownership (storage, retrieval fees, and early transition penalties).

Which TWO configuration decisions should the cloud engineer implement to satisfy these requirements?

  1. Set the bucket default storage class to Standard, and apply an Object Lifecycle Management rule to transition objects to Archive storage when their age reaches 30 days.Cevap
  2. Configure a Retention Policy with a duration of 7 years (2,555 days) on the bucket and lock it using Bucket Lock.Cevap
  3. C
    Set the bucket default storage class to Archive storage at creation time to minimize per-gigabyte storage costs starting from day one.
  4. D
    Apply a lifecycle policy that transitions objects to Nearline storage at day 7, Coldline storage at day 14, and Archive storage at day 30.

Cevap

The optimal strategy requires ingesting data into Standard storage and transitioning to Archive storage after 30 days via Object Lifecycle Management, paired with a locked Bucket Lock retention policy set to 7 years.
Ingesting data into Standard storage avoids high retrieval fees during the active 30-day querying phase. Transitioning directly to Archive storage at day 30 minimizes monthly storage fees for the remaining 7 years without early transition penalties. GCP Archive storage retains millisecond retrieval latency when regulatory audits occur. Furthermore, locking a 7-year Retention Policy using Bucket Lock ensures irreversible compliance with regulatory immutability requirements.

Adım Adım Çözüm

1
Analyze access frequency and retrieval costs during the active period (Days 1–30).
Real-time query workloads generate frequent read requests. Using Standard storage incurs zero retrieval fees per gigabyte processed.
Coldline and Archive classes charge substantial retrieval fees per GB, making them cost-prohibitive during active processing.
2
Evaluate long-term retention and minimum duration constraints.
Transitioning directly from Standard to Archive at day 30 incurs no minimum duration penalty because Standard storage has no minimum retention requirement. Archive storage provides the lowest rate for the remaining 7 years while offering millisecond latency upon retrieval.
Staging through Nearline (30-day minimum) or Coldline (90-day minimum) within short windows creates prorated early transition penalty charges.
3
Select compliance and immutability controls.
Configuring a bucket Retention Policy locked via Bucket Lock enforces regulatory WORM (Write Once, Read Many) compliance.
Standard IAM permissions or lifecycle rules alone do not prevent accidental deletion by privileged administrative accounts.

Anahtar Kavram

Cloud Storage Class Selection, Lifecycle Minimum Duration Penalties, and Bucket Lock Planning
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Planning Cloud Storage Buckets and Storage Classes

Bu konudan daha fazla soru