Examkin

Soru

Zorluk: ZorManaging Storage and Database Solutions

A cloud operations engineer manages a Google Cloud Storage bucket storing high-volume security telemetry logs. The operational requirements dictate that logs must be accessed frequently during the first 30 days for real-time security analysis, accessed rarely over the subsequent 60 days for periodic auditing, and archived long-term for 3 years before deletion. The engineer must automate this workflow to minimize storage and access costs without incurring early retrieval fees during the analysis window. Which Object Lifecycle Management policy configuration should the engineer apply to the bucket?

  1. Keep newly uploaded log objects in Standard storage, add a lifecycle rule to transition objects to Nearline storage after 30 days, add a rule to transition to Coldline storage after 90 days, and add a rule to delete objects after 1095 days.Cevap
  2. B
    Transition newly uploaded log objects directly to Coldline storage upon bucket upload, and set a lifecycle rule to delete all objects after 1095 days.
  3. C
    Migrate the log storage workflow to a Cloud Bigtable table configured with TTL age-based retention policies to automatically delete row data after 3 years.
  4. D
    Upload all log files as Standard storage objects, and configure per-object ACLs to change the object storage class to Archive after 30 days while Uniform Bucket-Level Access is enabled.

Cevap

Keep newly uploaded log objects in Standard storage, add a lifecycle rule to transition objects to Nearline storage after 30 days, add a rule to transition to Coldline storage after 90 days, and add a rule to delete objects after 1095 days.
The correct option keeps log files in Standard storage during the initial 30-day security analysis window to prevent high retrieval fees. It configures Object Lifecycle Management rules to transition objects to Nearline storage after 30 days, to Coldline storage after 90 days (covering the 60-day audit window), and deletes them after 1095 days.

Adım Adım Çözüm

1
Analyze access frequency and data lifecycle requirements.
Days 1–30 require frequent access (Standard storage prevents retrieval costs). Days 31–90 require occasional auditing (Nearline storage). Days 91–1095 require long-term retention (Coldline storage). Day 1095 requires deletion.
Matching Cloud Storage classes to access patterns minimizes total operational cost while preventing early retrieval fee penalties.
2
Formulate Google Cloud Storage Object Lifecycle Management rules.
Rule 1: Set Storage Class to Nearline at age 30. Rule 2: Set Storage Class to Coldline at age 90 (30 + 60 days). Rule 3: Delete Object at age 1095 (3 years).
Object Lifecycle Management automates transitions seamlessly without modifying application code.

Anahtar Kavram

Cloud Storage Object Lifecycle Management and Storage Class Cost Optimization
Bu soruyu puanla

Konular

Managing Storage and Database Solutions