Free AWS SAA-C03 Actual Exam Questions – Solutions Architect Questions - Question 5 Discussion

Question No. 5
A company deployed a three-tier web application in a single Availability Zone in the us-east-1 Region
on a single Amazon EC2 instance. Usage of the application is growing.
A solutions architect needs to ensure that the application can handle the growing amount of traffic.
The solutions architect also needs to ensure the application is resilient.
Which solution will meet these requirements MOST cost-effectively?
Select one option, then reveal solution.
US
AV
Amit V.
2026-02-21

C imo since scheduled scaling keeps costs predictable without cross-AZ data charges.

0
RL
Ryan L.
2026-02-19

It’s C because keeping instances in the same AZ can reduce data transfer costs and complexity, plus scheduled scaling helps control expenses without over-provisioning across multiple AZs.

0
IX
Irfan X.
2026-02-18

Makes sense to avoid A since vertical scaling can get pricey and risky if a single instance fails. D is smarter with spreading instances across AZs and using horizontal scaling for growth. D

0
IX
Irfan X.
2026-02-16

Option D looks best since spreading instances across AZs boosts resilience and horizontal scaling handles traffic growth efficiently without extra manual steps like scheduled scaling in C.

0
SN
Sami N.
2026-02-12

B seems overkill with nine instances, which can get expensive fast. D hits the balance by spreading three instances across AZs and scaling horizontally, which is more cost-effective and resilient.

0
MD
Michael D.
2026-01-21

The key here is resilience and cost-effectiveness, so spreading instances across multiple AZs like in D is better. Vertical scaling in A can get pricey and less reliable under heavy load. D.

0
IE
Irfan E.
2026-01-19

A/D? A doesn’t do horizontal scaling properly and depends on vertical scaling, which isn’t great for cost or resilience. D spreads instances across AZs and uses horizontal scaling, which is more resilient and handles traffic spikes better. It also keeps costs down by scaling based on demand rather than over-provisioning upfront like B. C is close but misses the multi-AZ part, which is critical for resilience. So D looks like the solid, cost-effective choice here.

0
PH
Peter H.
2026-01-15

D/C? D covers multi-AZ for resilience and scales horizontally, which seems best cost-wise and for uptime. C misses multi-AZ, so less resilient.

0