DBS-C01 · Question #66
A Database Specialist has migrated an on-premises Oracle database to Amazon Aurora PostgreSQL. The schema and the data have been migrated successfully. The on-premises database server was also being…
The correct answer is C. Create AWS Lambda functions to run the maintenance jobs and schedule them with Amazon. Explanation Option C is correct because AWS Lambda functions can execute Python code (matching the existing scripts), integrate natively with Amazon EventBridge (formerly CloudWatch Events) for cron-style scheduling, require no server management, and are highly available by…
Question
A Database Specialist has migrated an on-premises Oracle database to Amazon Aurora PostgreSQL. The schema and the data have been migrated successfully. The on-premises database server was also being used to run database maintenance cron jobs written in Python to perform tasks including data purging and generating data exports. The logs for these jobs show that, most of the time, the jobs completed within 5 minutes, but a few jobs took up to 10 minutes to complete. These maintenance jobs need to be set up for Aurora PostgreSQL. How can the Database Specialist schedule these jobs so the setup requires minimal maintenance and provides high availability?
Options
- ACreate cron jobs on an Amazon EC2 instance to run the maintenance jobs following the required
- BConnect to the Aurora host and create cron jobs to run the maintenance jobs following the
- CCreate AWS Lambda functions to run the maintenance jobs and schedule them with Amazon
- DCreate the maintenance job using the Amazon CloudWatch job scheduling plugin.
How the community answered
(40 responses)- A5% (2)
- B20% (8)
- C70% (28)
- D5% (2)
Explanation
Explanation
Option C is correct because AWS Lambda functions can execute Python code (matching the existing scripts), integrate natively with Amazon EventBridge (formerly CloudWatch Events) for cron-style scheduling, require no server management, and are highly available by design - making them the lowest-maintenance, serverless solution for running tasks that complete within Lambda's 15-minute maximum execution timeout (well within the observed 5–10 minute window).
Why the distractors are wrong:
- Option A (EC2 cron jobs): Running cron jobs on EC2 introduces server management overhead (patching, monitoring, failover), defeating the goal of minimal maintenance and high availability.
- Option B (Aurora host cron jobs): You cannot directly SSH into an Aurora managed instance to create OS-level cron jobs - AWS manages the underlying host, and this approach is not supported.
- Option D (CloudWatch job scheduling plugin): There is no such thing as a "CloudWatch job scheduling plugin" - this is a fabricated distractor; CloudWatch Events/EventBridge is the scheduling service, used with Lambda (Option C).
Memory Tip
Think "Serverless = No Maintenance + High Availability." Whenever an exam question asks for minimal maintenance + high availability for scheduled scripts, pair Lambda + EventBridge - it's the go-to serverless scheduling combo on AWS.
Topics
Community Discussion
No community discussion yet for this question.