How to Update RDS Instance Type Without Downtime Using Blue/Green Deployment in CloudFormation

A developer is using AWS CloudFormation to deploy a stack that includes an Amazon RDS DB instance. The developer wants to update the DB instance to a larger instance type without causing downtime. The current template has DeletionPolicy set to 'Delete'. What should the developer do?

Quick Answer

The correct answer is to use a blue/green deployment by creating a new stack with the larger instance type and updating the application to point to the new database. This approach is necessary because CloudFormation in-place updates to an RDS instance type require a database reboot, which causes downtime; a blue/green deployment avoids this by provisioning the upgraded instance in a separate, parallel environment (green) while the original (blue) continues serving traffic, then performing a seamless cutover. On the AWS Certified Developer Associate DVA-C02 exam, this question tests your understanding of zero-downtime deployment strategies versus the default CloudFormation behavior, where changing the DBInstanceClass triggers a replacement or modification that interrupts service. A common trap is assuming that removing the DeletionPolicy or using a simple update will suffice, but any change to the instance class inherently requires a reboot. Memory tip: think "Blue stays live while Green gets the upgrade" — you never modify the running database directly.

⚠ Common exam trap

Many exam-takers assume CloudFormation stack updates can resize RDS instances without downtime, but in reality, modifying the DBInstanceClass requires a reboot, making blue/green deployments the only zero-downtime option among the choices.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use a blue/green deployment by creating a new stack with the larger instance type and updating the application to point to the new database.

A blue/green deployment allows you to create a new stack with the larger DB instance type in a separate environment (green), then switch the application traffic to the new database with minimal downtime. This approach avoids the downtime associated with in-place modifications, as CloudFormation updates to RDS instance types typically require a reboot, which causes an outage. By using a blue/green deployment, the developer can validate the new instance and cut over seamlessly.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Take a snapshot of the DB instance and restore it to a larger instance type.
Why it's wrong here
Restoring from snapshot causes downtime.
✓
Use a blue/green deployment by creating a new stack with the larger instance type and updating the application to point to the new database.
Why this is correct
Blue/green deployment minimizes downtime by switching to a new stack.
✗
Change the DeletionPolicy to 'Retain' and update the stack.
Why it's wrong here
DeletionPolicy only affects deletion, not updates.
✗
Create a read replica with the larger instance type and promote it.
Why it's wrong here
Promoting a read replica can cause downtime and data loss.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on DVA-C02

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A developer is using AWS CloudFormation to deploy a stack that includes an Amazon RDS DB instance. The developer wants to update the stack to change the DB instance class. The update fails because CloudFormation cannot modify the DB instance class without replacement. The developer needs to complete the update with minimal downtime. What should the developer do?

hard

A.Delete the stack and create a new stack with the new DB instance class.
B.Use a custom resource with an AWS Lambda function to perform the modification, ensuring data is backed up and downtime is minimized.
C.Update the stack and disable rollback on failure.
D.Update the stack using a change set, then execute it.

Why : Changing the DB instance class of an Amazon RDS DB instance causes some interruption. For a Single-AZ instance, the database is completely unavailable while the instance type is being modified. By converting the instance to a Multi-AZ deployment first, AWS RDS creates a redundant standby instance. When the DB instance class is subsequently updated, RDS updates the standby instance first, performs a rolling failover (which typically takes under a minute), and then updates the original primary instance. This strategy minimizes downtime to a brief failover window.

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.