An enterprise runs an operational and analytics data platform on Google Cloud with the following access profiles and requirements: IoT operational telemetry: High-throughput time-series data is written directly to Cloud Bigtable. Real-time dashboards require single-digit millisecond latency for the most recent 30 days of data. Records between 31 and 365 days are queried infrequently for troubleshooting. Analytical summary data: Historical reporting tables in BigQuery are queried for business analysis. Once written, partitions or tables older than 90 days are never updated or modified, but analysts require native query performance without latency degradation. Raw telemetry archives: Raw event payload objects in Cloud Storage are stored for disaster recovery and operational audits, with expected read access occurring roughly once every 45 to 60 days. Which multi-service tiered storage strategy optimizes storage and retrieval costs while maintaining the required query latency?

Configure Bigtable tiered storage with a 30-day rolling age threshold and apply timestamp range filters on real-time queries; rely on BigQuery automatic long-term storage pricing for unmodified tables older than 90 days; and transition Cloud Storage raw objects to Nearline storage via Object Lifecycle Management.: What the Multi-Service Tiered Architecture Is This architecture optimizes cost across disparate Google Cloud storage systems (Cloud Bigtable, BigQuery, and Cloud Storage) by mapping specific data lifecycle policies and storage classes to the distinct access frequency, query latency, and retention requirements of each workload. How It Meets Every Requirement Cloud Bigtable Cost and Performance: Enabling tiered storage with a 30-day rolling age threshold maintains the hot 30 days of telemetry in high-performance SSD storage while automatically migrating data older than 30 days to the lower-cost infrequent access tier. Applying a timestamp range filter to operational queries limits reads strictly to the SSD tier, preventing performance degradation caused by checking both storage tiers. BigQuery Long-Term Storage: BigQuery automatically reduces storage pricing by 50% for any table or partition that has not been modified for 90 consecutive days. This provides substantial cost savings without requiring export jobs, schema changes, or query latency trade-offs. Cloud Storage Nearline Class: The Nearline storage class is engineered for data accessed at most once a month, featuring a 30-day minimum storage duration. It provides lower monthly storage rates than Standard storage while keeping retrieval fees cost-effective for 45–60 day access cycles. Key Advantages Zero Latency Penalty: BigQuery long-term storage and Bigtable SSD-filtered reads maintain baseline query latencies. Automated Lifecycle Transitions: Storage tiering occurs seamlessly via native background compaction and automated pricing transitions without manual intervention. Cost Elimination: Avoids minimum storage duration penalties in Cloud Storage and reduces Bigtable SSD footprint. Why This Is Optimal This solution strikes the exact balance between storage-class rates, retrieval fees, and query latency across all three specialized GCP services.

Multi Service Tiered Storage Cost Optimization | Professional Cloud Data Engineer

AdvancedProfessional Cloud Data Engineer

A financial services organization ingests millions of analytical audit files daily into a Google Cloud Storage Standard bucket. Strict compliance regulations mandate that audit files must be retained immutably for exactly 7 years (2,555 days), preventing any user—including bucket and project administrators—from deleting or modifying them before the retention period expires. To optimize storage costs, the team identified the following operational requirements: Audit files larger than 10 MiB should automatically move from Standard to Coldline storage after 30 days of inactivity, avoiding transition costs on smaller files where operation fees exceed storage savings. Files should be permanently purged automatically as soon as the 7-year compliance period lapses. Which combination of Cloud Storage configurations satisfies all compliance and cost-optimization requirements?

Lifecycle management of data

AdvancedProfessional Cloud Data Engineer

A lead data engineer is designing a data lifecycle and cost-optimization architecture for an enterprise BigQuery data warehouse. The requirements are: All newly created partitioned event tables in the telemetry_events dataset must automatically delete individual daily partitions once they are older than 60 days, while retaining the base table structure for ongoing streaming ingestion. Any non-partitioned lookup tables created in the same dataset must be preserved indefinitely by default and automatically transition to BigQuery's lower-cost long-term storage tier after remaining unmutated for 90 days. High-priority analytics tables must be able to override the default partition retention to keep partitions for 180 days upon table creation. Which configuration should the data engineer implement?

Lifecycle management of data

AdvancedProfessional Cloud Data Engineer

An enterprise runs two primary BigQuery workloads under a capacity-based reservations model: Interactive BI Dashboards: Used concurrently by analysts and business users throughout the day, requiring consistent low-latency response times without queuing delays. Batch ETL Pipelines: Executed periodically throughout the day and night to process large staging tables; several queries contain complex Common Table Expressions (CTEs) referenced multiple times across downstream calculations. Recent monitoring shows that interactive dashboard queries experience sudden latency spikes when batch ETL tasks trigger rapid slot autoscaling. Furthermore, short-lived ETL queries that finish in a few seconds are driving unnecessary compute expenses by causing the autoscaler to provision large slot spikes, and multi-referenced CTEs are consuming excessive processing resources. Which strategy should you implement to optimize performance, eliminate workload contention, and control costs?

Interactive or batch query jobs

AdvancedProfessional Cloud Data Engineer

An enterprise data engineering team is designing a cost-optimized storage architecture on Cloud Storage for large-scale analytical training datasets and compliance logs. The data lifecycle and operational requirements are as follows: Ingestion & Active Processing (Days 1–30): Newly ingested datasets are actively read, transformed, and queried multiple times per day by data pipelines. Periodic Validation (Days 31–90): Datasets are accessed at most once per month for model validation and intermittent quarterly reporting. Long-term Compliance (Day 91 to 7 Years): Data must be retained for regulatory compliance for seven years, accessed less than once a year, but any ad-hoc audit queries require sub-second (millisecond) retrieval latency. Cost Governance: The strategy must minimize total storage costs while strictly avoiding early deletion fees and premature class transition penalties. Which Object Lifecycle Management policy should the team configure to meet these requirements?

Planning for storage costs and performance

AdvancedProfessional Cloud Data Engineer

An enterprise architecture team is designing a real-time streaming ingestion pipeline on Google Cloud using Cloud Pub/Sub to process events across multiple microservices. The Pub/Sub topic enforces an Apache Avro schema that evolves over time as upstream services add optional fields, creating multiple schema revisions. The downstream subscriber applications maintain their own reader schema and must reliably deserialize incoming binary-encoded messages that may have been published under different schema revisions. How should the subscriber application be architected to handle messages across evolving schema revisions?

Data acquisition and import

IntermediateProfessional Cloud Architect

Apigee Cloud Armor reCAPTCHA WAAP Architecture

API management best practices (e.g., Apigee)

Professional Cloud Data Engineer

Multi Service Tiered Storage Cost Optimization

Related questions

Apigee Cloud Armor reCAPTCHA WAAP Architecture

Professional Cloud Data Engineer

Multi Service Tiered Storage Cost Optimization

What the Multi-Service Tiered Architecture Is

How It Meets Every Requirement

Key Advantages

Why This Is Optimal

Related questions

Apigee Cloud Armor reCAPTCHA WAAP Architecture

What the Multi-Service Tiered Architecture Is

How It Meets Every Requirement

Key Advantages

Why This Is Optimal