Which Storage Class After 30 Days for Financial Data

PCA Last updated

Configuring individual storage systems. Designing network, storage, and compute resources.

Short answer

D Use an Object Lifecycle Management policy to move data from Standard to Coldline after 30 days, meeting low-latency fraud access and quarterly-report needs.

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?

  1. Store all transaction data in a Cloud Storage bucket using the Standard storage class for the entire five-year retention period.
  2. Ingest all data into BigQuery using time-partitioned tables, and rely on BigQuery’s automatic long-term storage pricing for data older than 90 days.
  3. Configure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data from the Standard class to the Archive class after 30 days.
  4. Configure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data from the Standard class to the Coldline class after 30 days. Correct Answer

Key Takeaways

The question tests whether you can match storage class retrieval latency to stated access patterns, and the trap is choosing Archive for its cheaper per-GB rate while ignoring its minutes-to-hours restore time and higher retrieval fees.

This PCA storage-design question tests Cloud Storage storage classes and Object Lifecycle Management for a five-year financial transaction dataset with a 30-day low-latency fraud window. The correct approach keeps recent data in Standard and automatically transitions older data to Coldline, which supports second-level retrieval for quarterly reports at a fraction of Standard's cost.

Common mistake: Option C (Archive) is the most tempting wrong choice because Archive has the lowest at-rest price, but Archive restores take minutes to hours and its retrieval fee is roughly 2.5 times Coldline's, so it violates the stated few-seconds requirement for quarterly reports.

Expert Analysis

Why the Answer Is Correct

Option D satisfies every stated requirement with the lowest total cost: Standard storage keeps the last 30 days of transactions available at millisecond latency for the real-time fraud detection engine, and an Object Lifecycle Management policy moves everything older to Coldline automatically. Google documents Coldline as the class for data read or modified at most once a quarter, which maps exactly onto the quarterly report workload with retrieval times of a few seconds. Coldline's standard online retrieval completes in seconds (with millisecond expedited retrieval available), so the stated retrieval target is met while at-rest cost drops to roughly a fifth of Standard. Because the data is retained for the full five years, Coldline's 90-day minimum storage duration is never violated by the 30-day transition point.

Why the Other Options Are Wrong

Option A keeps everything in Standard for five years, which meets latency but is by far the most expensive choice for data that is only touched quarterly, directly failing the cost-effectiveness requirement. Option C uses Archive, whose restores require a restore operation taking minutes to hours and whose retrieval fee is significantly higher than Coldline's, so quarterly reports would not complete within the acceptable few-second window; the 365-day minimum duration also adds risk. Option B relies on BigQuery long-term storage pricing that only kicks in after roughly 90 days of inactivity, leaving the critical 30-to-90-day tier at full price with no tiering control, and it does not provide the explicit low-latency versus cheap-archive separation the scenario describes. As respawn summarized, the very-low-latency rule for the 30-day window is what eliminates the Archive option.

Community Comment Notes

The comments split between C and D, with D holding the clearer majority: cachopo argued that Coldline "is explicitly designed for data accessed at most once a quarter," while ahmed75.zahran00 bluntly noted that "Archive retrieval is hours, not seconds." jeussin and Bunny3388 backed C by quoting the Coldline documentation and by claiming "Coldline storage is for 90 days," but that confuses the 90-day minimum storage duration with an eligibility threshold—the data remains stored far beyond 90 days. 41168b9 weighed the numbers directly, showing that Archive's higher retrieval fee can outweigh its storage savings for terabyte-scale quarterly reads, and hitmax87's cost breakdown supports the same conclusion.

Official Reference

Exam Strategy

On storage-tier questions, extract an access-frequency and latency matrix first (here: 0-30 days millisecond latency, quarterly reads with seconds allowed, five-year retention), then eliminate any class whose restore time exceeds the stated window. Always check minimum storage duration and early-delete rules before finalizing a lifecycle transition age.

Frequently Asked Questions

Why is Archive (option C) wrong if it is cheaper per GB than Coldline?

Archive restores take minutes to hours and its retrieval fee is far higher than Coldline's, so quarterly reports would miss the acceptable few-second retrieval window. The storage saving is offset by retrieval cost at terabyte scale.

Does transitioning to Coldline at 30 days break its 90-day minimum storage duration?

No. The minimum duration only penalizes objects deleted or reclassified before 90 days, and this data is retained for five years, so the charge never applies.

More PCA FAQ →

Discussion 10 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded.

From public community threads 10

  1. jeussin 👍 3 Answered C
    answer C https://docs.cloud.google.com/storage/docs/storage-classes?hl=en Coldline storage is ideal for data you plan to read or modify at most once a quarter.
  2. 41168b9 👍 2 Answered D
    Why not C: Archive (Option C) has a 365-day minimum storage duration and much higher retrieval fees. While Archive is cheaper at rest, its retrieval fees ($0.05/GB) are significantly higher than Coldline ($0.02/GB). For quarterly reports involving terabytes of data, the high retrieval cost of Archive would likely outweigh the storage savings.
  3. CyberPeter 👍 2 Answered D
    Archive retrival does not meet the quick retrival requriment, so D is the right answer
  4. connorgee9 👍 2 Answered D
    D is correct.
  5. cachopo 👍 1 Answered D
    D. Configuring an Object Lifecycle Management policy to transition data to Coldline after 30 days perfectly aligns with the access patterns and cost-optimization goals. Standard storage provides the millisecond latency required for the 30-day real-time fraud detection window. Coldline storage is explicitly designed for data accessed at most once a quarter, making it the ideal, most cost-effective tier for your quarterly historical reporting. All Cloud Storage classes offer low-latency retrieval (time to first byte in milliseconds), so it easily meets the "few seconds" requirement.
Show 5 more comments
  1. hitmax87 👍 1 Answered C
    This is tricky question, even retrieval is cheaper for Cold storage, storage itself is cheaper on Archive: Option D: Moving to Coldline Storage At-Rest Storage Cost: 1,000 GB × $0.004/GB × 59 months = $236.00 Data Retrieval Cost: 1,000 GB × $0.02/GB × 20 quarters = $400.00💰 Total Coldline Cost: $636.00 Option C: Moving to Archive StorageAt-Rest Storage Cost: 1,000 GB × $0.0012/GB × 59 months = $70.80 Data Retrieval Cost: 1,000 GB × $0.05/GB × 20 quarters = $1,000.00💰 Total Archive Cost: $1,070.80
  2. respawn 👍 1 Answered D
    Correct answer is D. "Transaction data from the last 30 days must be accessible with very low latency for the fraud detection engine" This rules out C archive class because archive retrieval can take minutes to hours. A is wrong because standard class meets latency, but far too expensive for infrequently accessed historical data. B is wrong because long-term storage pricing only kicks in after 90 days, not 30 days. BQ is not ideal as the primary low-latency store for real-time fraud engines.
  3. cachopo 👍 1
    So 90 days is a quarter. Just what you need for quarterly reports.
  4. ahmed75.zahran00 👍 1 Answered D
    Archive retrieval is hours, not seconds
  5. Bunny3388 👍 1 Answered C
    Coldline storage is for 90 days

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Optimizing Data Transfer for ETL with Cellular Connections

S-Grade

Streamlining Cloud IAM Audit Analysis with BigQuery

S-Grade

Auditing BigQuery User Query Counts

S-Grade

Practice All PCA Questions

Access 81 questions with complete answers and detailed explanations.

View Full PCA Practice Test →

← Back to PCA Study Guide