Which combination of steps would allow the Database Specialist to accomplish this?
(Choose two.)
Review the stack drift before modifying the template
Create and review a change set before applying it
Export the database resources as stack outputs
Define the database resources in a nested stack
Set a stack policy for the database resources
Explanations:
Reviewing stack drift before modifying the template helps identify changes to existing resources, but it does not prevent modifications to RDS resources by the Application team. It only reports existing differences without enforcing any restrictions.
Creating and reviewing a change set allows the Database Specialist to preview changes that will be applied to the stack, ensuring that the RDS resources remain unaffected before deployment. This helps confirm if any unintended changes to the database are included.
Exporting the database resources as stack outputs does not protect or prevent changes to the database resources. Stack outputs are used for cross-stack references and sharing values but do not control modification permissions or behavior.
Defining database resources in a nested stack can help organize resources but does not protect the RDS resources from changes in the main stack. Nested stacks can still be modified if changes are applied to the main stack.
Setting a stack policy for the database resources provides a mechanism to protect specific resources, such as the RDS instances, from updates. This prevents accidental modifications by restricting update actions on protected resources.