ELB + ASG Flashcards

1
Q

Scaling by increasing the size of the instance

A

Vertically scalability

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

scaling that is very common for non-distributed systems, such as a database

A

Vertically scalability

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

Scaling by increasing the number of instances/systems for your application

A

Horizontal Scalability

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

Scaling that is common for web applications/modern applications

A

Horizontal Scalability

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

Ensure and agreed level of operational performance (uptime) for a higher-than-normal period

A

High availability

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

Having redundant copies of an object or resource to make sure that another can take its place when something happens to it

A

High availability

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

Horizontal Scaling for EC2 involves using _________________ to scale out/in the number of instances

A

Auto Scaling Group or a Load Balancer

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

High Availability for EC2 involves using ___________________ to run instances for the same application across multi-AZ

A

Auto Scaling Group multi-AZ, Load Balancer multi-AZ

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

Servers that forward traffic to multiple servers (e.g., EC2 instances) downstream that expose a single point of access (DNS) to your application

A

Load Balancers

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

Enables the load balancer to know if instances it forwards traffic to are available to reply to requests

A

Health Checks

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

Type of Load Balancer that uses HTTP, HTTPS, WebSocket. Is a great fit for micro services & container-based applications

A

Application Load Balancer

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

Type of Load Balancer that handles millions of request per second and uses TCP, TLS (secure TCP), UDP. There is only one static IP per AZ.

A

Network Load Balancer

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

Type of load balancer that operates at layer 3 (Network layer) – IP Protocol. Used to deploy, scale, and manage a fleet of 3rd party network virtual appliances in AWS

A

Gateway Load Balancer

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

Do NLBs support assigning Elastic IPs?

A

Yes

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

Target group of a load balancer:

  • EC2 instances (can be managed by an Auto Scaling Group) – HTTP
  • ECS tasks (managed by ECS itself) – HTTP
  • Lambda functions – HTTP request is translated into a JSON event
  • IP Addresses – must be private IPs
A

Application Load Balancer

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

Target group of a load balancer:

  • EC2 instances
  • IP Addresses – must be private IPs
  • Application Load Balancer
A

Network Load Balancer

17
Q

Term that means the same client is always redirected to the same instance behind a load balancer

A

Sticky Sessions (Session Affinity)

18
Q

Term for each load balancer instance distributes evenly across all registered instances in all AZ

A

Cross-Zone Load Balancing

19
Q

Allows traffic between your clients and your load balancer to be encrypted in transit (in-flight encryption)

A

SSL Certificate

20
Q

Used with privatelink to provide services to other VPCs

A

Network Load Balancer

21
Q

Can you get detailed health checking with a network load balancer?

A

No

22
Q

ALB must have SSL certifications installed if HTTPS is used

A

True

23
Q

Specifies instance configuration information that can be used to easily provision instances in the same configuration

A

LaunchTemplates

24
Q

Keeps running instances at the desired capacity by provisioning or termination instances

A

Auto Scaling Groups

25
Q

Updates the capacity based on certain criteria/metrics

A

Scaling Policies

26
Q

Manually adjust desired capacity

A

Manual Scaling

27
Q

Time based scaling used for known periods of usage

A

Scheduled Scaling

28
Q

Scale out or in based on a metric reaching an alarm state (ex. cpu usage, i/o)

A

Simple Scaling

29
Q

Scaling similar to Simple scaling but the adjustments vary based on the size of the alarm breach, add more control of scaling

A

Stepped Scaling

30
Q

Used to ensure that your bootstrap scripts have completed successfully and the applications on the instances are ready to accept traffic

A

ASG Lifecycle Hooks

31
Q

How long to wait on a scaling action before performing another (default 300 seconds)

A

Cooldown period

32
Q

Allows you to load multiple SSL certificates on one listener

A

Server Name Indication (SNI)

33
Q

Allows you to expose multiple HTTPS applications each with its own SSL certificate on the same listener

A

Server Name Indication (SNI)