Matching a storage class to how often the data gets read
Cloud Storage offers four storage classes (Standard, Nearline, Coldline, and Archive) that let you optimize cost based on how frequently data is accessed and how long it must be retained. All classes provide the same low latency (milliseconds) and high durability (99.999999999%), differing only in storage price, access/retrieval cost, and minimum storage duration. Choosing the right class balances access frequency against storage and retrieval costs to minimize total cost of ownership.
Must-know
- Standard storage is best for frequently accessed ('hot') data or data stored for brief periods, with no minimum storage duration and no retrieval fees.
- Nearline storage is ideal for data accessed less than once a month (e.g., backups), has a 30-day minimum storage duration, and incurs retrieval costs.
- Coldline storage suits data accessed less than once a quarter (e.g., disaster recovery), has a 90-day minimum storage duration, and higher retrieval costs than Nearline.
- Archive storage is the lowest-cost, coldest tier for data accessed less than once a year (e.g., long-term archival/compliance), with a 365-day minimum storage duration and the highest retrieval costs and latency for retrieval requests (though data access itself is still immediate).
- Object Lifecycle Management rules can automatically transition objects between storage classes (or delete them) based on age, allowing cost optimization without manual intervention.
- Deleting or moving objects out of Nearline, Coldline, or Archive before their minimum storage duration incurs early deletion charges equivalent to the remaining minimum duration cost.
A retail analytics team stores daily point-of-sale summary files that business users query at least once a week for trend dashboards. The files must remain immediately available with no retrieval delay or extra access fees. Which Cloud Storage class should the team select for this data?
What you have tried across GCP ADP's objectives, not a readiness score.
Data Preparation and Ingestion
- When to load first and when to transform first, and what sits between the two
- Picking a way to move existing data into Google Cloud
- Judging whether a dataset is trustworthy enough to build on
- Fixing messy records before they reach a report
- Telling CSV, JSON, Parquet, Avro, and relational tables apart, and where each fits
- Picking how to pull data out of a source system
- Matching a workload to the right storage or database service
- Getting files and tables loaded with a CLI, a transfer service, or a client library
Data Analysis and Presentation
- Writing BigQuery SQL that answers a reporting question
- Exploring and charting data inside a hosted notebook
- Turning a question from the business into an analysis that settles it
- Building a dashboard and getting it in front of the right people
- Deciding whether a job calls for Looker or for Looker Studio
- Editing LookML to change what a model exposes
- Spotting a problem worth solving with BigQuery ML or AutoML
- Calling a hosted Google language model straight from BigQuery
- Sequencing a machine learning project from raw data to served predictions
- Building, fitting, and scoring a model with SQL alone
- Running predictions against a model you already trained
- Keeping trained models catalogued in one place
Data Pipeline Orchestration
- Matching a transformation job to Dataproc, Dataflow, Dataform, or a managed alternative
- Weighing whether the transform belongs before or after the load
- Assembling the services a simple transformation pipeline needs
- Putting a query on a schedule and keeping it running
- Watching a Dataflow job and spotting where it stalls
- Reading logs and metrics to work out what a pipeline actually did
- Choosing what should drive a multi-step workflow
- Streaming messages into BigQuery as they arrive rather than in batches
- Wiring a trigger so one event starts the next step
Data Management
- Granting only the access a person or service actually needs
- Controlling who can read a bucket, and what uniform access changes
- Sharing a dataset with another team or company without copying it
- Matching a storage class to how often the data gets read
- Expiring old data automatically so it stops costing money
- Picking somewhere to park data that must be kept but is rarely read
- Comparing the managed backup and restore options across services
- Working out when a second copy is worth what it costs
- Regions, dual-regions, multi-regions, and zones as redundancy choices
- Deciding who should hold the encryption keys
- What a key management service does for creating, rotating, and revoking keys
- Protecting data on the wire versus data sitting on a disk
Coverage checked against the published exam guide on Aug 12, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.