Home › AWS Solutions Architect Associate › cloudcomputing › resilientarchitectures › Horizontal scaling on AWS is best characterised …
Horizontal scaling on AWS is best characterised as:
AMigrating the workload to S3 Glacier
BAdding more identical instances behind a load balancer to share traffic
CSwitching all servers to a single AZ for simplicity
DIncreasing the CPU and memory of a single existing EC2 instance
Answer & Solution
Correct answer: B. Adding more identical instances behind a load balancer to share traffic
Scale-out adds instances; vertical scale (scale-up) grows a single instance. Glacier is archival storage; consolidating into one AZ removes resilience.
Related questions
A stateless web tier sits behind an ALB across 3 AZs. The team wants to remove ANY single Step Functions on AWS is best characterised as:Which combination best implements a write-heavy event ingestion pipeline that needs to fanWhich AWS pattern lets an HTTP API handle 10× traffic spikes WITHOUT provisioning EC2 capaA workload requires recovery from a complete AWS Region failure with an RPO measured in miWhich database read-scaling primitive lets an Amazon RDS or Aurora cluster offload read-onWhen designing a multi-tier web app on AWS, which AWS Load Balancer type best fits an HTTPWhich AWS storage type is shared, mountable as a network file system (NFS), and ideal for