AWS Architecture

Question 1

Highly available

Answer 1

When a system can withstand failure to components

Question 2

Redundancy

Answer 2

Standby: Functionality is recovered on a secondary resource using failover. The resource is not available during this time
Active: Requests are distributed on multiple instances, so if one fails, the others just absorb the extra workload

Question 3

Elasticity

Answer 3

Can support growth in users, traffic, or data size

Question 4

Vertical scaling

Answer 4

Make the instance/resource better using memory etc.

Question 5

Horizontal scaling

Answer 5

Increase number of resources

Question 6

Stateless application

Answer 6

The compute needs no knowledge of previous interactions and stores no session information. Horizontal scaling because any request can be serviced by any available compute

Question 7

Loose coupling

Answer 7

As complexity increases. The architecture needs to be broken down into smaller components so failures don’t cascade down to other components

Question 8

Storage services

Answer 8

Backup: S3
Archiving: AWS S3 Glacier
Disaster recovery: RDS backups and snapshots
Block storage: AWS EBS
File Storage: Amazon EFS
Object: S3