A company is planning to close for several days. A Database Specialist needs to stop all applications along with the DB instances to ensure employees do not have access to the systems during this time

Question

Options

• AStop the source instances before stopping their read replicas
• BDelete each read replica before stopping its corresponding source instance
• CStop the read replicas before stopping their source instances
• DUse the AWS CLI to stop each read replica and source instance at the same

• A
  8% (3)
• B
  84% (31)
• C
  3% (1)
• D
  5% (2)

Explanation

Explanation

Amazon RDS does not allow you to stop a DB instance that has active read replicas - the stop operation will simply fail, which is exactly what the Database Specialist observed in the logs. Option B is correct because deleting the read replicas first removes this dependency, allowing the source instance to then be stopped successfully; since the company is closing temporarily, the read replicas can be recreated when operations resume.

Option A is wrong because attempting to stop the source instance before its read replicas violates the RDS dependency rule - RDS will block the stop action as long as read replicas exist. Option C is wrong because while stopping replicas first sounds logical, RDS read replicas cannot be independently stopped - they can only be deleted or left running. Option D is wrong for the same reason; no AWS CLI command can stop a read replica as a standalone action, and running stop commands simultaneously does not bypass the dependency constraint.

Memory Tip: Think of read replicas as "children" that must leave the house (be deleted) before the parent (source instance) can lock the doors and stop. You can't stop a parent RDS instance while its read replica children are still around!

No community discussion yet for this question.