Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An enterprise e-commerce platform processes terabytes of raw clickstream events daily. The architecture ingests data into Cloud Storage and loads it into BigQuery for analytical processing. The FinOps team identifies escalating storage and compute expenses and establishes the following requirements:
Which combination of actions should the DevOps engineer implement to meet these architectural and financial goals?
This solution implements an integrated FinOps data optimization strategy that automates storage lifecycle transitions in Cloud Storage, reduces query data scanning via BigQuery partitioning and clustering, and enforces predictable compute spending using BigQuery capacity-based slot reservations.
DATE(event_timestamp) enables partition pruning, eliminating scans on dates outside query filter clauses. Clustering on user_id and event_type co-locates related data within partitions, further reducing the byte blocks read during analytical queries.This architecture directly aligns infrastructure utilization with data access patterns. It avoids manual batch operations or complex sharding anti-patterns while maximizing cost efficiency across the complete data lifecycle.
This approach orchestrates data backups using Cloud Composer transfer operators, applies integer range partitioning on user IDs in BigQuery, and moves query computation to a dedicated Dataproc cluster.
user_id integer ranges fails to prune data across temporal boundaries, increasing scanned byte volumes.The workload was a fixed-capacity Apache Spark batch processing job that required continuous integer-keyed transformations against external relational databases.
This option relies on Storage Batch Operations scheduled via custom manifests for object transitions, table sharding by date naming conventions (events_YYYYMMDD), and query-level LIMIT syntax under on-demand billing.
LIMIT clause to an on-demand query does not reduce the number of bytes scanned or billed across scanned columns.A team needed a one-time migration to modify custom metadata or apply compliance legal holds across millions of specific objects identified by an external audit manifest.
This option configures lifecycle deletion rules on Cloud Storage after 30 days, shifts BigQuery datasets to physical storage billing, and places daily byte query quotas on on-demand projects.
The workload dealt exclusively with transient staging data where data older than 30 days had zero retention value, and hard budget caps were preferred over query continuity.
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 Validated