Old objects should move to cheaper classes automatically. What do you configure?
Why D is the answer
Lifecycle management
Lifecycle management moves old objects to cheaper classes automatically.
In detail
- Lifecycle management moves old objects to cheaper classes.
- Check access patterns first.
Use case
An illustrative scenario, not a real incident.
Logs move to colder classes after 90 days, by a lifecycle rule, with no code.
See it in different ways
mindmap
root((Stores))
BigQuery
Analytics
Bigtable
Key lookups at scale
Spanner
Global relational
AlloyDB
PostgreSQL
Firestore
Mobile documents
Memorystore
Microsecond cache
Cloud Storage
ObjectsstateDiagram-v2 state "Standard" as s0 state "Colder class" as s1 state "Deleted" as s2 [*] --> s0 s0 --> s1: after set days s1 --> s2: if a rule allows s2 --> [*]
Key point: Lifecycle rules move old objects.
Why the other options are wrong
- A. Object versioning
- Versioning keeps old copies.
- B. A DAG sensor
- A sensor waits for a condition.
- C. A materialized view
- A view is a BigQuery feature.