Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 134 discussion

C is correct. only eventbridge can run scheduled task

If there wasn't a schedule element I would choose AWS Batch because it pretty much loads a container and does the job, especially since it's like a 20-minute job. However the step functions part doesn't help with the scheduling part, hence I go for C

AWS Fargate is ideal for running containerized workloads without managing underlying EC2 instances. Even though the application is a binary and its source code cannot be modified, it can be easily packaged into a Docker container without changing the binary itself. Since the application runs periodically (every 4 hours) and for a short duration (up to 20 minutes), Fargate provides a cost-effective, serverless execution environment. Amazon EventBridge (CloudWatch Events) can be scheduled to invoke Fargate tasks precisely at defined intervals.

Option C clearly includes EventBridge for scheduling, aligning with the requirement to run tasks every 4 hours. While AWS Batch is technically better for CPU-intensive workloads, the lack of explicit EventBridge integration in Option B makes C the correct answer under AWS’s service design principles.

B. Use AWS Batch to run the application. Use an AWS Step Functions state machine to invoke the AWS Batch job every 4 hours.

B: Usa uma máquina de estado do AWS Step Functions para invocar o trabalho do AWS Batch a cada 4 horas. Por que não é a letra C : Embora possa executar containers, é mais adequado para aplicações de longa duração

Option C : https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/run-event-driven-and-scheduled-workloads-at-scale-with-aws-fargate.html

A = CW Log cannot invoke lambda every 4 hours B = Step Function cannot invoke batch job every 4 hour (unless you use an EventBridhe scheduled event) C = correct (but I do not like when Fargate is mentioned as a standalone service, as it is a serverless compute option for some some services) D = CodeDeploy cannot run an application every 4 hours

none. "highly CPU intensive" means no Fargate. scheduling means eventbridge.

https://aws.amazon.com/about-aws/whats-new/2018/10/aws-lambda-supports-functions-that-can-run-up-to-15-minutes/ Lambda's max running time is 15 mins, cannot support up to 20mins application.

https://aws.amazon.com/tutorials/scheduling-a-serverless-workflow-step-functions-amazon-eventbridge-scheduler/ Step Function cannot schedule a job. Step Function needs EventBridge as the scheduler.

B is not possible as Step Function can not be used to run scheduled a job every 4 hour

containers are well-suited for applications that are built in microservices architecture, where each service is a self-contained unit that performs a specific task. These types of applications are typically designed to be scalable and easy to deploy, making them a good fit for containerization. I feel D is the best option

I think Both B 、C is missing some key point Option B does not explain how to AWS Step Functions to trigger an AWS Batch job regually, in this case 4 hours per run. Option C does not explain how to use EventBridge to call the Fargate task, which is not native support, it might involved lambda to achive.

C. schedule -> eventbridge

The application is a Linux binary which can be packaged into a container, then run on AWS Fargate and scheduled using Event Bridge. # Use a base image that matches your application's runtime environment FROM ubuntu:latest # Copy the Linux binary into the container COPY myapp /usr/local/bin/myapp # Set the entry point to execute the binary ENTRYPOINT ["/usr/local/bin/myapp"]

C - Fargate is the best choice here