mediummultiple choiceObjective-mapped

A data engineering team runs a nightly ETL job on EC2. The job can be checkpointed every 5 minutes and can be retried from the last checkpoint if the instance terminates. The job runtime varies from 2 to 4 hours, and the team has no need for a specific instance type, as long as it completes before 7:00 AM local time. They currently run the job on On-Demand EC2, leading to high monthly compute cost.

Which change best reduces cost while maintaining the business deadline?

Question 1mediummultiple choice
Full question →

A data engineering team runs a nightly ETL job on EC2. The job can be checkpointed every 5 minutes and can be retried from the last checkpoint if the instance terminates. The job runtime varies from 2 to 4 hours, and the team has no need for a specific instance type, as long as it completes before 7:00 AM local time. They currently run the job on On-Demand EC2, leading to high monthly compute cost.

Which change best reduces cost while maintaining the business deadline?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Use Spot Instances for the ETL workload, and configure the job to checkpoint frequently and restart on interruption.

Spot can significantly reduce costs, and checkpointing plus retries mitigate interruption risk.

B

Distractor review

Use Reserved Instances with a 1-year term to lower costs, since reservations provide discounts for any usage.

Reserved Instances discount On-Demand-like capacity but do not exploit the largest discount available for interruptible work.

C

Distractor review

Switch to On-Demand but enable Auto Scaling so the job finishes faster during peak hours.

Auto Scaling can improve speed, but it does not address the primary cost driver of always-on On-Demand usage.

D

Distractor review

Use Spot Instances but disable checkpointing to simplify the application.

Without checkpointing, interruptions can cause substantial recomputation and may miss the 7:00 AM deadline.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Use Spot Instances for the ETL workload, and configure the job to checkpoint frequently and restart on interruption. — The best approach is to use Spot Instances for the ETL job because the workload is explicitly interruption-tolerant when paired with checkpointing and retry. Spot provides the most aggressive pricing among EC2 purchasing options, and checkpointing every 5 minutes limits wasted work if an interruption occurs. Deadline risk is managed by the application’s ability to restart from the last checkpoint. Reserved Instances mainly reduce cost for steady, predictable usage but do not target interruption-based economics like Spot. Keeping On-Demand or removing checkpointing ignores the cost and reliability requirements. Why others are wrong: Reserved Instances can reduce cost versus On-Demand, but they generally cost more than Spot and do not align with interruption-driven optimization. Using Auto Scaling on On-Demand can help performance, not cost, when instances remain On-Demand priced. Disabling checkpointing increases recomputation and makes it difficult to reliably meet the 7:00 AM completion requirement after Spot interruptions.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.