Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A financial analytics company ingests terabytes of transaction logs daily into Google Cloud. Analysts frequently query recent log data within a 30-day window, but analytical queries occasionally analyze records up to 90 days old. Logs older than 90 days are no longer queried in the data warehouse and must automatically expire to control operational expenditure. Additionally, raw audit files stored in Cloud Storage must be preserved for three years for compliance, transitioning automatically to lower-cost storage tiers as access frequency declines.
Which storage and lifecycle design should the cloud architect implement to balance query performance, data availability, and cost?
DELETE statements, and enable Cloud Storage soft delete with a 3-year retention duration.This approach uses a standard, nonpartitioned table where records are periodically purged using scheduled SQL DELETE queries, alongside Cloud Storage soft delete configured for long-term retention.
DELETE statements over nonpartitioned multi-terabyte tables requires full-table scans to locate expired rows, incurring massive recurring compute and slot costs compared to zero-cost partition drops.The goal was strictly to protect against accidental object deletion within a short recovery window without any requirement for tiered storage classes or analytics query optimization.
This approach suggests using BigLake managed tables backed by Apache Iceberg in Cloud Storage with BigQuery partition expiration and Cloud Storage hierarchical namespaces for data lifecycle tiering.
partition_expiration_days).You needed an open-table format (Apache Iceberg) to enable multi-engine compute interoperability across Spark and BigQuery on raw Parquet files without requiring native BigQuery partition expiration features.
This pattern relies solely on table clustering to organize BigQuery data while using custom code deployed on Cloud Run functions to manually copy and rewrite objects into distinct Cloud Storage buckets configured with different storage classes.
DELETE queries or custom partition logic.partition_expiration_days only applies to partitioned tables, not unpartitioned clustered tables.Google Cloud lacked declarative lifecycle policies and required custom serverless functions to orchestrate cross-bucket migrations based on proprietary application metadata tags.
This architecture combines BigQuery partition-level expiration with Cloud Storage Object Lifecycle Management (OLM) to automate data retention and tiered storage across analytics and object storage systems.
partition_expiration_days = 90 ensures that individual partition slices automatically expire and are deleted once they reach 90 days, eliminating unnecessary data warehouse storage costs without requiring scheduled deletion scripts.Native BigQuery partition expiration combined with Cloud Storage Object Lifecycle Management provides a fully managed, serverless lifecycle tiering framework that requires zero custom operational compute infrastructure.

Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated