Prepare and test your skills

Prepare and test your skills

Assess Access Frequency and Performance Characteristics means matching each object to the storage class that fits how often it will be read and how long it must be kept. Cloud Storage (opens in a new tab) is a scalable, managed object store that keeps data as objects inside buckets. Buckets are associated with projects, and projects are grouped under organizations. Each bucket and object has a storage class and a location, which together set the durability, availability, and cost for that data.
How storage class follows access frequency is the rule that frequently read data stays warm while rarely read data moves colder. Standard is the default class for active data that needs to be readily available. Nearline and Coldline are for rarely accessed data and can lower billing costs compared with Standard when reads are infrequent. Archive is the cheapest and most durable class and is used for data kept for legal reasons or long-term retention.
The table below summarizes the access role of each class and its cost note.
| Storage class | Access pattern | Cost and durability note |
|---|---|---|
| Standard | Default for frequent access | Default class with no special discount |
| Nearline | Rarely accessed data | Lower billing than Standard when rarely accessed |
| Coldline | Rarely accessed data | Lower billing than Standard when rarely accessed |
| Archive | Legal hold and long-term retention | Cheapest and most durable class |
Placement follows retrieval needs, so data that stops being read every day can move from Standard to Nearline or Coldline, while data that must be kept for years for legal reasons can move to Archive.
Performance tradeoffs between storage and retrieval mean each class has its own pricing structure for keeping data versus reading it back. Storage and retrieval are priced separately, so the cost of reading data or metadata is part of the decision. In general, lower-cost classes are intended for data that is not accessed often, while Standard is intended for data that must be readily available. Specific latency values are not defined for each class, so the choice depends on access frequency and retention duration rather than a promised speed number.
Tools for analyzing access patterns help teams decide when to move data colder based on real use instead of guesses. Storage Intelligence provides centralized visibility and control over Cloud Storage data at scale:
These tools show which buckets are idle, which objects are rarely read, and where an unoptimized class is raising the bill.
Changing a stored object's class lets the bucket follow the data as access drops over time. Storage batch operations can transform storage classes across large collections of objects at once. Bucket relocation moves buckets between geographic locations while preserving bucket names, object metadata, and storage classes. For DICOM objects in the Cloud Healthcare API, the class can be changed at the study, series, or instance level, which requires the healthcare.dicomStores.dicomWebWrite permission or the Healthcare DICOM Store Administrator (roles/healthcare.dicomStoreAdmin) Identity and Access Management (IAM) role.
Exam tip: Standard is the default class. Move rarely accessed data to Nearline or Coldline to save on billing, and use Archive for data kept for legal reasons because it is the cheapest and most durable class.
Compare Cost Models Across Storage Classes means looking at how Cloud Storage (opens in a new tab) charges for keeping data versus accessing it. The four classes — Standard, Nearline, Coldline, and Archive — have different cost and performance characteristics based on access frequency and retention length. Standard is the default for active data, while Nearline, Coldline, and Archive reduce storage cost compared with Standard but add retrieval costs. Choosing the right class lowers billing costs while still meeting needs for backup, disaster recovery, and long-term retention.
Storage cost compared with retrieval cost is the central tradeoff that storage cost falls as data gets colder while retrieval cost rises. Each class has its own pricing structure, so changing an object's class changes both what is paid to store it and what is paid to read data or metadata back. Archive is economical only when reads are rare, because any retrieval costs more than it would in a warmer class. Nearline is designed for backup scenarios where access is at most about once a month, which supports regular disaster recovery tests without giving up periodic access.
Standard to Archive compared left to right showing storage cost falling from highest to cheapest while retrieval cost rises from lowest to highest, with access frequency and use case for each class.
| Storage class | Relative storage cost | Relative retrieval cost | Typical access frequency |
|---|---|---|---|
| Standard | Highest | Lowest | High-frequency access to active objects |
| Nearline | Lower than Standard | Higher than Standard | Low-frequency access, at most about once a month |
| Coldline | Lower than Nearline | Higher than Nearline | Lower-frequency access than Nearline |
| Archive | Cheapest and most durable | Highest | Lowest-frequency access for long-term preservation |
Because the two costs move in opposite directions, moving data colder saves money only when the drop in storage cost is larger than the rise in retrieval cost.
Minimum durations and extra operational costs are billing rules that apply to Nearline, Coldline, and Archive. When data is stored in one of these classes, the account is charged for the minimum duration for that class even if the object is deleted or moved to another class earlier. There are also additional costs for retrieving data or metadata stored in these classes earlier than the minimum duration allows. Operational work such as testing restores, reading metadata, or moving objects between classes can therefore add retrieval charges.
This duration rule means short-lived data can cost more in a cold class than in Standard, even though the advertised storage rate is lower. Effective cost planning considers how long objects will remain in the class, not just the monthly storage rate.
Choosing classes for short-term and long-term retention uses class changes to match cost to how often data is actually needed. Rarely accessed images or backups can move from Standard to Nearline or Coldline to save on billing costs once daily access ends. Patient data or other records that must be kept for legal reasons can move to Archive, which provides the lowest storage cost for data that is kept for years but almost never read. The decision balances storage savings against retrieval charges and the minimum billing period.
Exam tip: Standard is the default for frequent access, while Archive has the lowest storage cost but the highest retrieval cost — move data colder only when access drops and retention is long enough to satisfy the minimum duration.
Determine Appropriate Use Cases for Each Storage Class means choosing Standard, Nearline, Coldline, or Archive based on business needs for access, cost, and durability. Cloud Storage (opens in a new tab) is a managed object store where each bucket has a storage class and a location that set durability and availability. Storage class selection balances how often data is accessed against storage cost, retrieval cost, and minimum storage duration rules. Standard fits high-frequency access, Nearline and Coldline fit low-frequency access, and Archive fits lowest-frequency access.
Matching each class to its access pattern connects the frequency of reads to the right cost profile and business scenario. Nearline, Coldline, and Archive reduce storage cost compared with Standard, but they add retrieval costs and minimum storage duration charges. They save money only when data is truly infrequently accessed. The choice should therefore follow the access pattern, with frequent access staying in Standard and infrequent access moving colder.
| Storage class | Access frequency | Cost profile | Typical use cases |
|---|---|---|---|
| Standard | High-frequency access | Higher storage cost than colder classes | Active content delivery, web serving, and frequently accessed data |
| Nearline | Low-frequency access, at most once a month in backup scenarios | Lower storage cost than Standard, plus retrieval and duration charges | Backup, disaster recovery (DR), and regular DR stress tests |
| Coldline | Low-frequency access | Lower storage cost than Standard, plus retrieval and duration charges | Rarely accessed data |
| Archive | Lowest-frequency access | Cheapest and most durable, plus retrieval and duration charges | Archival storage and data kept for legal retention |
Backup, disaster recovery, and archival scenarios are the most common reasons to use colder classes. Cloud Storage as an object store is ideal for storing backup files. Nearline is designed for backup scenarios where access is at most once a month, which supports regular DR stress tests while keeping storage costs low. Archive aligns with archival storage and data kept for legal reasons because it is the cheapest and most durable class.
Protection and import services support these plans. Soft Delete preserves deleted and overwritten objects for a specified period to guard against accidental or malicious deletion, while Object holds prevent deletion or updates to objects. Storage Transfer Service can import data into Cloud Storage from:
This import capability helps move existing backups into Cloud Storage before or during a recovery plan.
Using lifecycle planning to control cost means moving data colder as access frequency drops while watching retrieval rules. Standard fits active content delivery and frequently accessed data because it is designed for high-frequency access. As access drops, lifecycle planning can move data to Nearline or Coldline to lower storage cost, but retrieval charges and minimum storage durations must be considered. For the lowest-frequency access, Archive provides the lowest storage cost and highest durability, making it appropriate for long-term retention.
A lifecycle diagram showing an object cooling from Standard through Nearline and Coldline to Archive as access frequency drops, with storage cost falling and retrieval cost rising, and a re-warm path back to Standard.
Exam tip: Nearline is designed for backup data accessed at most once a month, while Archive is the cheapest and most durable class for long-term retention.
Standard is the default class for high-frequency access to active data and has the highest storage cost but the lowest retrieval cost. Nearline and Coldline are for rarely accessed data with lower storage cost than Standard but higher retrieval cost, with Coldline having lower storage cost and higher retrieval cost than Nearline. Archive is the cheapest and most durable class for lowest-frequency long-term preservation but has the highest retrieval cost.
Use Archive for data kept for legal reasons or long-term retention that is almost never read. It provides the lowest storage cost and highest durability but adds retrieval costs and minimum storage duration charges, so it saves money only when access is at its lowest frequency and retention is long.
Use Nearline for backup and disaster recovery (DR) data that is accessed at most about once a month. It has lower storage cost than Standard while still supporting periodic access such as regular DR stress tests, but it adds retrieval costs and minimum storage duration charges.
Nearline, Coldline, and Archive charge for a minimum storage duration even if an object is deleted or moved to another class earlier, plus additional costs for retrieving data or metadata. Short-lived data can therefore cost more in a cold class than in Standard when the minimum duration and retrieval charges outweigh the lower storage rate.
A retail organization is updating its business continuity strategy and needs to store critical system images in Cloud Storage for disaster recovery. The organization has established the following storage requirements:
Which Cloud Storage class best aligns with these business requirements?
Last updated