Blue-Green Deployment — Concept Check
Questions on Blue-Green Deployment. Run two identical production environments; switch the load-balancer to the new (green) release instantly, with the old (blue) kept on standby for instant rollback.
Questions in this quiz
8 questions on Blue-Green Deployment — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.You have deployed a new version of your application to the green environment. After switching traffic to green, users report errors. What should you do next?
- ADeploy a hotfix to green
- BRollback to the blue environment immediately
- CRestart the green environment
- DWait for more data before deciding
2.In Kubernetes, how is traffic switched from the blue to the green deployment?
- AScaling down the blue deployment
- BRestarting the Kubernetes cluster
- CUpdating the Service selector label
- DDeleting the blue deployment
3.A developer argues that blue-green deployment is cost-effective. What is a valid counterpoint?
- AIt complicates database migrations
- BIt leads to mixed version issues
- CIt requires double infrastructure, increasing costs
- DIt eliminates rollback capabilities
4.After deploying green, you notice the database schema differs between blue and green. What should you ensure?
- ABoth versions are compatible with the current schema
- BGreen uses a different database
- CBlue is taken offline immediately
- DSchema changes are rolled back
5.During a blue-green deployment, the green environment is idle until cutover. What is a potential issue with this?
- AService unavailability
- BSchema incompatibility
- CIncreased traffic load
- DCold start problem
6.Why might someone mistakenly believe blue-green deployment avoids database schema issues?
- AThey assume schema changes are unnecessary
- BThey believe the deployment process handles all schema changes
- CThey think both environments use separate databases
- DThey assume schema changes are part of the deployment
7.What is a primary advantage of blue-green deployment over canary releases?
- ASimplicity and instant rollback
- BGradual traffic shift
- CAutomatic database migration
- DLower infrastructure costs
8.In the expand-contract pattern, what should never be done during a deployment?
- AAdd a NOT NULL column without default
- BAdd a nullable column
- CDeploy green before blue
- DRun smoke tests after deployment