Most cost-effective AWS Glue execution class for daily non-urgent jobs?

Orchestrate data pipelines. Automate data processing by using AWS services.

Answer Correct answer: A — Choose the FLEX execution class so AWS Glue runs the daily jobs on spare capacity, reducing cost when start and finish times are flexible.

A data engineer needs to schedule a workflow that runs a set of AWS Glue jobs every day. The data engineer does not require the Glue jobs to run or finish at a specific time. Which solution will run the Glue jobs in the MOST cost-effective way?

Choose the FLEX execution class in the Glue job properties. Correct Answer
Use the Spot Instance type in Glue job properties.
Choose the STANDARD execution class in the Glue job properties.
Choose the latest version in the GlueVersion field in the Glue job properties.

Community Votes

100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Tests Glue execution class cost trade-offs and the trap that Spot Instances are not a Glue job property; FLEX is the discount class for non-time-sensitive workloads.

AWS Glue FLEX execution class runs non-urgent daily Glue jobs on spare capacity at a lower price than STANDARD, making it the most cost-effective option when start and finish times are flexible.

Learners often pick Spot Instances because they associate spare capacity with Spot pricing, but AWS Glue jobs expose STANDARD and FLEX execution classes rather than a Spot Instance type.

Community Discussion (6 comments)

pypelyncar 👍 7 Selected: A

The FLEX execution class leverages spare capacity within the AWS infrastructure to run Glue jobs at a discounted price compared to the standard execution class. Since the data engineer doesn't have specific time constraints, utilizing spare capacity is ideal for cost savings. Today's date its a checkbox in order to spare capacity and will mean we dont know when is going to finish, which is recommended to increase a timeout

TonyStark0122 👍 6

A. Choose the FLEX execution class in the Glue job properties. Explanation: The FLEX execution class in AWS Glue allows jobs to use idle resources within the Glue service, which can significantly reduce costs compared to the STANDARD execution class. With FLEX, Glue jobs run when resources are available, which is a cost-effective approach for jobs that don't need to be completed within a specific timeframe.

GabrielSGoncalves 👍 1 Selected: A

FLEX is how you lower Glue cost when you dont have urgency to run ETLs.

k350Secops 👍 3 Selected: A

As its said the FLEX job comes cheaper that hiring a spot instance

lucas_rfsb 👍 1 Selected: A

I'd go with A

lalitjhawar 👍 5

A Flex allows you to optimize your costs on your non-urgent or non-time sensitive data integration workloads such as testing, and one-time data loads. With Flex, AWS Glue jobs run on spare compute capacity instead of dedicated hardware. The start and runtimes of jobs using Flex can vary because spare compute resources aren’t readily available and can be reclaimed during the run of a job https://aws.amazon.com/blogs/big-data/introducing-aws-glue-flex-jobs-cost-savings-on-etl-workloads/

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

AWS Glue's FLEX execution class is designed for non-urgent workloads that can tolerate variable start and run times. When the engineer has no requirement for the daily Glue jobs to start or finish at a specific time, FLEX can use spare compute capacity and is billed at a lower rate than STANDARD. The question's key constraint—schedule daily but no specific start or finish—maps directly to FLEX's trade-off of variable timing for lower cost. Therefore A is the most cost-effective solution and still satisfies the daily scheduling requirement.

Why the Other Options Are Wrong

B is invalid because AWS Glue job properties do not include a Spot Instance type; FLEX is the supported spare-capacity option. C, STANDARD, runs on dedicated capacity at standard pricing, so it costs more when timing is flexible. D, latest GlueVersion, may provide newer engine features but does not by itself reduce cost or provide spare-capacity pricing.

Community Comment Notes

Learners strongly converged on FLEX: pypelyncar described it as using spare AWS capacity at a discounted price, which matches the cost objective. lalitjhawar noted that with Flex "Glue jobs run on spare compute capacity instead of dedicated hardware", and k350Secops summarized that FLEX is cheaper than hiring a Spot Instance. These comments reinforce the practical reading of the question without changing the independent verdict.

Official Reference

Exam Strategy

Look for the phrase 'does not require the jobs to run or finish at a specific time' as the signal for Glue FLEX, not for Spot Instances. FLEX trades timing flexibility for lower cost, while STANDARD is for time-sensitive production workloads.

Frequently Asked Questions

Why is the STANDARD execution class not the most cost-effective choice for these daily Glue jobs?

STANDARD uses dedicated Glue capacity at standard pricing. Because the jobs need not start or finish at a specific time, FLEX's spare-capacity discount is cheaper.

Does AWS Glue support a Spot Instance type in job properties?

No. Glue job properties expose worker types and execution classes such as STANDARD and FLEX; FLEX provides spare-capacity savings without a Spot Instance setting.

More DEA-C01 FAQ →

Related Analysis

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide