Question

A DevOps team maintains a production CDK application that provisions a critical DynamoDB table and an S3 bucket. To improve readability, a developer refactors the code by wrapping several resources inside a new nested Construct and renames the construct scope. During the next pipeline run, `cdk diff` shows the DynamoDB table and S3 bucket will be destroyed and recreated. Both resources contain production data that must not be lost. Which approach allows the refactor to proceed WITHOUT data loss and with minimal manual intervention?

Accepted Answer

Apply the `overrideLogicalId` method (or explicitly set the logical IDs) so the refactored resources keep their original CloudFormation logical IDs, preventing replacement.

Answer

Add a `DeletionPolicy: Retain` to the resources, deploy the refactor, then manually re-import the orphaned resources into the stack.

Answer

Enable termination protection on the stack so CloudFormation refuses to delete the DynamoDB table and S3 bucket during the update.

Answer

Run `cdk deploy` with the `--force` flag to skip the diff confirmation, since CDK automatically preserves stateful resources during refactors.