AWS DevOps Engineer Professional Practice Test 2026 - Free DevOps Practice Questions and Certification Study Guide

The correct choice pertains to using the Worker tier with a cron.yml file in an Elastic Beanstalk environment, which is specifically designed to handle periodic tasks effectively.

When deploying applications on Elastic Beanstalk, you have the option to create a Worker environment, which is tailored for background processing and asynchronous tasks. The cron.yml file is a configuration file that allows you to define scheduled tasks that the worker environment will execute at specified intervals. This setup is optimal for tasks that are either time-sensitive or need to be executed regularly, such as sending emails, processing data, or other background jobs.

Utilizing the Worker tier with cron.yml provides built-in support for handling these tasks seamlessly within the Elastic Beanstalk framework, ensuring that the application scales and manages resources effectively, thereby enhancing overall performance.

In contrast, other options do provide capabilities for executing tasks but are not as finely suited for the specific context of periodic execution within an Elastic Beanstalk environment. For instance, AWS Batch is more aligned with batch processing jobs rather than periodic tasks linked to web applications, while EC2 Scheduled Tasks operate on individual EC2 instances rather than being tied specifically to Elastic Beanstalk's scaling capabilities. CloudWatch Events can trigger events on a schedule, but without the direct