A developer at a company needs to create a small application that makes the same API call once each day at a designated time. The company does not have infrastructure in the AWS Cloud yet, but the…

Question

Options

• AUse a Kubernetes cron job that runs on Amazon Elastic Kubernetes Service (Amazon EKS).
• BUse an Amazon Linux crontab scheduled job that runs on Amazon EC2.
• CUse an AWS Lambda function that is invoked by an Amazon EventBridge scheduled event.
• DUse an AWS Batch job that is submitted to an AWS Batch job queue.

• A
  13% (4)
• B
  3% (1)
• C
  80% (24)
• D
  3% (1)

Explanation

AWS Lambda + EventBridge is the correct choice because it requires zero infrastructure management - you write the function, set a cron-style schedule rule in EventBridge, and AWS handles everything else. There are no servers to provision, patch, or maintain, and you only pay for the seconds the function actually runs once per day.

Why the distractors fall short:

• A (EKS cron job): Kubernetes on EKS is massive overkill for a single daily API call - it requires provisioning and managing a cluster, nodes, and control plane overhead.
• B (EC2 crontab): Running a full EC2 instance 24/7 just to execute one task daily wastes compute and money, and you still own OS patching and instance management.
• D (AWS Batch): Batch is designed for large-scale, parallelizable compute jobs (think HPC or data processing pipelines) - submitting a simple API call to a job queue adds unnecessary complexity.

Memory tip: Think "no servers, no waste" - whenever an exam question involves a simple, infrequent, or time-triggered task with no existing infrastructure, Lambda + EventBridge is almost always the most operationally efficient answer. The phrase "operationally efficient" is a signal to eliminate anything that requires managing servers.

No community discussion yet for this question.