After restoring an Amazon RDS snapshot from 3 days ago, a company's Development team cannot connect to the restored RDS DB instance. What is the likely cause of this problem?

Question

Options

• AThe restored DB instance does not have Enhanced Monitoring enabled
• BThe production DB instance is using a custom parameter group
• CThe restored DB instance is using the default security group
• DThe production DB instance is using a custom option group

• A
  2% (1)
• B
  3% (2)
• C
  94% (61)
• D
  2% (1)

Explanation

RDS Snapshot Restore – Security Group Issue

When an RDS snapshot is restored, the new DB instance is automatically assigned the default VPC security group, not the security group from the original instance. The default security group typically lacks the inbound rules needed to allow database traffic (e.g., port 3306 for MySQL), so the Development team's connection attempts are blocked.

Why the distractors are wrong:

• A (Enhanced Monitoring): This is a performance observability feature and has absolutely no impact on network connectivity or the ability to connect to a DB instance.
• B (Custom parameter group): While a restored instance reverts to the default parameter group, parameter groups control database engine behavior (e.g., query settings), not network access - so this wouldn't block connections.
• D (Custom option group): Option groups add extra database features (e.g., Oracle TDE), but like parameter groups, they don't control who can connect to the instance.

Memory Tip: Think of a snapshot restore as moving into a new house with a default lock - you need to swap in the right key (security group) to let your team through the door. Always reassociate the correct security group immediately after restoring an RDS snapshot.

No community discussion yet for this question.