Your company decided to improve on the current batch processing model and start using the AWS Batch instead of the currently running SQS and EC2 with Auto Scaling configurations. Your processing jobs are using Docker containers. You also expect the jobs to grow in future. These jobs pull messages from the AWS SQS queue and write the data into DynamoDB tables once the processing is completed. You have created a small Proof-of-concept application to try out the AWS Batch before you actually migrate your job containers.

Answer options:

A.Make sure a CloudWatch Log group is set up for the Batch job.
B.Make sure Internet Access is available to your container.
C.Make sure suitable CPU and RAM are allocated for the Batch job.
D.Make sure your AWS account has not reached to the EC2 limit.
E.Make sure the VPC Endpoint is set to access the SQS queue from the containers inside the VPC.

Correct Answers: B, C, and D
Option Ais INCORRECT because the CloudWatch Log group does not impact the Batch job`s running status.
Please refer to the following link:
https://aws.amazon.com/premiumsupport/knowledge-center/batch-job-stuck-runnable-status/
Option B is CORRECT because no internet access for the compute resources may result in this issue.
Refer to the link: https://docs.aws.amazon.com/batch/latest/userguide/troubleshooting.html
Option C is CORRECT because if the job has asked for more resources than the attached compute environment has, the Batch will not schedule the job to execute, and the job will stay in the RUNNABLE state forever.
Option D is CORRECT because the job may require starting new instances to run the additional containers. If the AWS account has reached its limit, the service will not start new containers, and the job will remain in the RUNNABLE state.
Option E is INCORRECT because the question has not mentioned connecting to the SQS privately from the VPC. VPC Endpoint is not required for AWS Batch to work.