mediummulti selectObjective-mapped

An ecommerce company runs a 24/7 frontend tier on EC2 and a nightly image-rendering job that can be interrupted and resumed from checkpoints. They want to minimize monthly compute cost without changing the application architecture. Which two actions should they take? Select two.

Question 1mediummulti select
Full question →

An ecommerce company runs a 24/7 frontend tier on EC2 and a nightly image-rendering job that can be interrupted and resumed from checkpoints. They want to minimize monthly compute cost without changing the application architecture. Which two actions should they take? 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

Purchase a Compute Savings Plan for the always-on frontend tier.

A Compute Savings Plan reduces cost for steady compute usage while keeping flexibility across supported compute services. It is a strong fit for the always-on frontend tier because the workload runs continuously and is not interruption tolerant.

B

Best answer

Use Spot Instances for the rendering job fleet.

Spot Instances are ideal for interruptible workloads that can checkpoint and restart. The nightly rendering job can resume after interruptions, so Spot can substantially lower compute spend compared with On-Demand capacity.

C

Distractor review

Move both workloads to Dedicated Hosts.

Dedicated Hosts are meant for license or compliance isolation needs, not routine cost reduction. They usually increase cost and add management overhead for workloads that do not require host-level tenancy.

D

Distractor review

Keep the rendering fleet entirely on On-Demand Instances.

On-Demand is the simplest option, but it is usually the most expensive for interruptible batch processing. The scenario explicitly allows interruptions, so this does not minimize monthly cost.

E

Distractor review

Use dedicated GPUs for the frontend tier even though it is CPU-light.

GPU instances are specialized and expensive, and they do not reduce cost for a CPU-light frontend tier. This would add unnecessary spend without improving the described workload.

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: Purchase a Compute Savings Plan for the always-on frontend tier. — The best cost pattern is to combine a steady-state commitment for predictable usage with Spot for interruptible work. A Compute Savings Plan lowers the cost of the always-on frontend tier while preserving flexibility. Spot Instances are the most cost-effective choice for the rendering fleet because the job can checkpoint and recover after interruption. Together, these two choices reduce spend without changing the application design. Dedicated Hosts, all On-Demand capacity, and unnecessary GPU instances all increase cost or add complexity. They do not match the scenario’s core requirement: keep the frontend running continuously at a lower price and exploit interruption tolerance in the rendering workload.

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.