Data for Google Clouds
Data on Google Cloud means choosing where information lives. Cloud Storage holds objects such as images and backups, Cloud SQL provides managed MySQL, PostgreSQL and SQL Server, and other services such as Firestore and BigQuery cover document data and analytics. The skill is matching the data shape and access pattern to the right service.
Stage: Data and Networking · Part of the Google Cloud roadmap · Last reviewed 19 November 2026
What to learn in Data
- Create a Cloud Storage bucket and choose a storage class
- Upload and share objects using signed URLs or IAM
- Create a Cloud SQL instance and connect to it from an application
- Compare Firestore, Cloud SQL and BigQuery for a given use case
- Configure backups and a retention rule for stored data
Data interview questions
What are the Cloud Storage classes and how do you choose one?
Standard, Nearline, Coldline and Archive differ mainly in price for storage versus retrieval and in minimum storage duration. Use Standard for frequently accessed data, and colder classes for backups or records you rarely read, since retrieval costs rise as storage costs fall.
When is BigQuery a better fit than Cloud SQL?
BigQuery is built for analytical queries that scan large datasets, using columnar storage and serverless execution. Cloud SQL is a transactional relational database suited to application reads and writes of individual rows. Use BigQuery for reporting and analysis, Cloud SQL for the app backend.
Where Data fits in the Google Cloud roadmap
Data belongs to the Data and Networking stage (intermediate level). Store and connect.
Other units in this stage
Back to the full Google Cloud roadmap