hardmulti selectObjective-mapped

A company processes product-image uploads in bursts. Each transform takes up to ten minutes, and every job can be retried safely from the beginning. The current EC2 worker fleet is idle most of the day. Which two changes most reduce cost and idle capacity? Select two.

Question 1hardmulti select
Full question →

A company processes product-image uploads in bursts. Each transform takes up to ten minutes, and every job can be retried safely from the beginning. The current EC2 worker fleet is idle most of the day. Which two changes most reduce cost and idle capacity? Select two.

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

Buffer jobs in Amazon SQS and let workers scale from queue depth.

Correct. SQS decouples uploads from processing and smooths bursty demand. Queue depth is a practical scaling signal, so the company avoids paying for idle workers while still absorbing traffic spikes.

B

Best answer

Run the workers on AWS Fargate Spot, since interruptions are acceptable.

Correct. Fargate Spot lowers container compute cost when the workload can tolerate interruption and retry. For retry-safe image processing, the cost savings are significant compared with always-on EC2 workers.

C

Distractor review

Keep a fixed fleet of m6i.large instances in an Auto Scaling group with a higher minimum.

Incorrect. A higher minimum keeps capacity running even when the queue is empty, so idle cost remains high. It also does not provide the burst efficiency that queued, event-driven processing gives you.

D

Distractor review

Use Reserved Instances for the workers even though demand is highly bursty.

Incorrect. Reserved Instances work best for stable, predictable utilization. Bursty workers would leave committed capacity unused much of the time, which wastes money.

E

Distractor review

Process uploads only during a nightly window so the fleet looks busier.

Incorrect. Batch scheduling may reduce perceived complexity, but it increases latency and does not inherently reduce compute cost if the same amount of work must still be done.

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: Buffer jobs in Amazon SQS and let workers scale from queue depth. — The cheapest design for bursty, retry-safe work is to decouple requests from compute and use discounted container capacity. SQS prevents the worker fleet from sitting idle while waiting for uploads, and scaling from queue depth matches supply to demand. Fargate Spot then lowers the unit price for the workers because interruptions are acceptable and every job can be retried from the beginning. This combination reduces both idle time and orchestration overhead. Why others are wrong: Keeping a fixed minimum fleet or buying Reserved Instances makes sense only when utilization is consistently high. Neither choice fits bursty upload processing. A nightly batch window may appear simpler, but it increases end-user delay and does not solve the underlying idle-capacity problem. The workload is already retry-safe, so forcing a time-based schedule adds friction without meaningful savings.

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.