nerdexam
Google

PROFESSIONAL-CLOUD-ARCHITECT · Question #294

You are designing the storage architecture for a financial analytics platform. The platform ingests and stores terabytes of transactional data daily, which is used for both real-time fraud detection a

The correct answer is C. Configure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data. This question tests knowledge of cost-effective tiered storage using Cloud Storage Object Lifecycle Management to automatically move data between storage classes based on age.

Submitted by manish99· Mar 30, 2026Designing and planning a cloud solution architecture

Question

You are designing the storage architecture for a financial analytics platform. The platform ingests and stores terabytes of transactional data daily, which is used for both real-time fraud detection and long-term historical analysis. Transaction data from the last 30 days must be accessible with very low latency for the fraud detection engine. Data older than 30 days is accessed infrequently for quarterly reports, where retrieval times of a few seconds are acceptable. All data must be retained for five years to meet compliance regulations. You need to design a solution as cost- effective as possible. What should you do?

Options

  • AStore all transaction data in a Cloud Storage bucket using the Standard storage class for the
  • BIngest all data into BigQuery using time-partitioned tables, and rely on BigQuery's automatic long-
  • CConfigure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data
  • DConfigure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data

How the community answered

(30 responses)
  • A
    7% (2)
  • B
    27% (8)
  • C
    50% (15)
  • D
    17% (5)

Why each option

This question tests knowledge of cost-effective tiered storage using Cloud Storage Object Lifecycle Management to automatically move data between storage classes based on age.

AStore all transaction data in a Cloud Storage bucket using the Standard storage class for the

Storing all data in Standard storage class satisfies latency requirements but is prohibitively expensive for petabytes retained over five years when most data is rarely accessed.

BIngest all data into BigQuery using time-partitioned tables, and rely on BigQuery's automatic long-

BigQuery time-partitioned tables with automatic long-term pricing reduce cost for old data but BigQuery is an analytics warehouse optimized for SQL queries, not the sub-millisecond key lookups required by a real-time fraud detection engine.

CConfigure a Cloud Storage bucket with an Object Lifecycle Management policy to transition dataCorrect

Cloud Storage Object Lifecycle Management can automatically transition objects from Standard (low-latency, high-cost) to Nearline after 30 days for infrequently accessed data, then to Coldline or Archive for long-term compliance retention at minimal cost. This matches all requirements: sub-millisecond access for recent data, acceptable seconds-range retrieval for historical data, and five-year retention at the lowest possible price point.

DConfigure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data

This option uses lifecycle management but transitions data to an incorrect storage class or uses incorrect age thresholds that do not align with the 30-day hot window and multi-year retention requirements.

Concept tested: Cloud Storage Object Lifecycle Management tiered storage classes

Source: https://cloud.google.com/storage/docs/lifecycle

Topics

#Cloud Storage lifecycle#storage tiering#data retention#cost optimization

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-ARCHITECT Practice