Dev and production must stay separate. What is a sound design?
Why C is the answer
Separate projects for each environment
Separate projects give each environment a clear boundary for access and billing.
In detail
- Separate projects isolate environments.
- Projects are boundaries for IAM and billing.
Use case
An illustrative scenario, not a real incident.
A developer's test query cannot touch production, because dev and prod live in separate projects.
See it in different ways
mindmap
root((Governance))
Location
Regional storage
Organization policies
Protection
Cloud DLP
Data masking
Separation
Project per environment
Ownership
Federated governancemindmap
root(("Environments"))
n1["Dev project"]
n2["Test data"]
n3["Production project"]
n4["Real data"]Key point: Projects isolate environments.
Why the other options are wrong
- A. One service account for everything
- One account removes separation.
- B. One shared project with name prefixes
- Prefixes do not isolate anything.
- D. One shared table with a column for the environment
- One table mixes environments.