DBS-C01 · Question #50
A company has an on-premises system that tracks various database operations that occur over the lifetime of a database, including database shutdown, deletion, creation, and backup. The company…
The correct answer is C. Create RDS event subscriptions. Have the tracking systems subscribe to specific RDS event. Explanation Option C is correct because RDS Event Subscriptions are a native, purpose-built AWS feature designed specifically to track database lifecycle events such as creation, deletion, shutdown, and backup - exactly matching the on-premises requirements. Event subscriptions…
Question
A company has an on-premises system that tracks various database operations that occur over the lifetime of a database, including database shutdown, deletion, creation, and backup. The company recently moved two databases to Amazon RDS and is looking at a solution that would satisfy these requirements. The data could be used by other systems within the company. Which solution will meet these requirements with minimal effort?
Options
- ACreate an Amazon Cloudwatch Events rule with the operations that need to be tracked on
- BCreate an AWS Lambda function to trigger on AWS CloudTrail API calls. Filter on specific RDS
- CCreate RDS event subscriptions. Have the tracking systems subscribe to specific RDS event
- DWrite RDS logs to Amazon Kinesis Data Firehose. Create an AWS Lambda function to act on
How the community answered
(37 responses)- A3% (1)
- B8% (3)
- C73% (27)
- D16% (6)
Explanation
Explanation
Option C is correct because RDS Event Subscriptions are a native, purpose-built AWS feature designed specifically to track database lifecycle events such as creation, deletion, shutdown, and backup - exactly matching the on-premises requirements. Event subscriptions use Amazon SNS to publish notifications, allowing multiple downstream systems to easily subscribe and consume the data with minimal configuration effort.
Option A is incorrect because while CloudWatch Events (now EventBridge) can capture some RDS events, it requires more configuration and is not the most direct or minimal-effort solution for tracking RDS-specific operational events compared to native RDS event subscriptions.
Option B is incorrect because CloudTrail captures API calls (control plane actions) but does not comprehensively track all database operational events like backups or internal database lifecycle changes, and building a Lambda filtering solution adds unnecessary complexity.
Option D is incorrect because routing RDS logs to Kinesis Data Firehose with a Lambda function is an overly complex, high-effort architecture for what is essentially a notification/tracking requirement that RDS Event Subscriptions handle natively.
Memory Tip: Think of RDS Event Subscriptions as the "database diary" - it's the AWS-native way to subscribe to exactly the database lifecycle events you care about, similar to subscribing to a newsletter. If the question mentions tracking RDS operational events with minimal effort, always think Event Subscriptions + SNS.
Topics
Community Discussion
No community discussion yet for this question.