Your organization is planning a blue-green deployment strategy for a critical application hosted on Google Cloud. You must ensure zero downtime during traffic cutover and preserve the ability to execute an instant rollback if issues arise. Which TWO architectural practices are required to safely support this deployment strategy? (Select TWO answers.)
- Ensure that any database schema changes introduced in the release remain fully backward-compatible with the active blue application version.Answer
- BApply non-backward-compatible database schema updates during the green deployment and perform a point-in-time database restore if a rollback is triggered.
- Pre-provision and validate full compute resource capacity for the green environment before shifting production traffic.Answer
- DDeploy the green environment without checking regional quota limits, relying on autoscaling to automatically increase GCP project quotas during cutover.
Answer
The essential practices are maintaining backward-compatible database schemas so the existing active environment remains stable, and pre-provisioning green environment capacity to handle production traffic immediately.
Executing a zero-downtime blue-green deployment requires that both application versions remain fully operational against shared backends. Ensuring backward-compatible database schema changes guarantees that the running blue version is unaffected during testing and cutover. Additionally, fully pre-provisioning green capacity ensures the new target infrastructure is ready to ingest production traffic immediately without unexpected capacity bottlenecks.
Step-by-Step Solution
Key Concept
Blue-green deployments require backward-compatible datastore schema management and full infrastructure pre-provisioning to achieve zero-downtime cutovers and instant rollbacks.