AWS - General Flashcards

1
Q

What is the difference between IaaS and PaaS?

A

[1] Infrastructure as a Service (IaaS) allows organizations to utilize AWS instead of owning and operating their own datacenter. You can simply rent VMs or physical servers from AWS.
Amazon Web Services manages the Infrastructure for you.

[2] The Platform as a Service (PaaS) on the other hand removes the need for your organization to manage the underlying platforms like a database, streaming services, etc. This allows you to focus on the deployment and management of your core applications and not worry about the IaaS and PaaS layers.

PaaS in turn, gets organizations to be more efficient and focused as you don’t need to worry about resource procurement, capacity planning, software maintenance, patching, or any of the other undifferentiated heavy lifting involved in running your application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the 4 primary areas of AWS?

A

[1] Compute (EC2, LightSail, ECS, Lambda, Batch)

[2] Storage (EBS, EFS, S3, Glacier, Storage Gateway, Storage Migration Services)

[3] Database (RDS, Redshift)

[4] Network (CloudFront, VPC, Direct Connect, Load Balancing, Route 53)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is AWS Region? How many regions AWS has? What is an Availability Zone?

A

AWS has 16 Regions and 44 Availability Zones.

A Region is a geographically distinct area—for example, the west coast of the USA.

Availability Zones are datacenters within a region. The availability zones are fault-tolerant between each other. Each Availability Zone (AZ) has its own power and is independent of other AZ within that region.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Why we should design application to be deployed on many AZ?

A

Ideally, you design your application to be across more than one AZ that way if one AZ goes down you have another.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Why we should design application to be deployed on many AZ?

A

Ideally, you design your application to be across more than one AZ that way if one AZ goes down you have another.

When designing an application you try to have redundancy between the three AZs. That way if AZ1 goes down due to a power failure, AZ2 will be alive and will not be affected and in turn, your applications and their underlying data are not affected.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly