Explanation:
Option D is correct. Creating an AWS Lambda function to start and stop the EC2 and RDS instances, and configuring Amazon EventBridge to invoke the Lambda function on a schedule, minimizes both cost and infrastructure maintenance. Lambda functions are serverless solutions provided by AWS that ensure you only pay for the compute time you consume, and EventBridge allows for event-driven architecture which can be scheduled easily. This approach eliminates the need to maintain additional EC2 instances as required by option C, as well as avoids dependency on third-party solutions as suggested in option B. Option A is invalid because it incorrectly suggests functionalities ('elastic resize' and 'scale to zero') that are not applicable to EC2 and RDS instances in the provided context.
Ultimate access to all questions.
No comments yet.
A company is migrating to AWS Cloud, utilizing EC2 and RDSDB instances. They require an automated solution to manage the start and stop of these instances during off-hours to minimize costs and maintenance.
A
Utilize elastic resize for EC2 and scale RDS to zero outside business hours.
B
Find a partner solution in AWS Marketplace for scheduled start/stop of instances.
C
Deploy an additional EC2 instance with a crontab to script the start/stop of existing instances.
D
Develop a Lambda function for instance management, triggered by EventBridge on a schedule.