Scaling Compute: Elastic Load Balancing and Auto Scaling Flashcards

1
Q

Design required for highly available and secure

website on EC2 with ALB, and DB on EC2

A

Launch ALB in public subnets, web servers in private subnets and DB layer in private subnets – all layers across AZs

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

HealthyHostCount metrics for an ALB have dropped from 6 to 2. Need to determine the cause

A

The health checks on target EC2 instances are failing

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

An instance attached to an ALB exceeded

the UnhealthyThresholdCount for consecutive health check failures. What will happen?

A

Health checks will continue and the ALB will take the instance out of service

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

Requirement to track the source IP of clients and the instance that processes the request

A

Check the ALB access logs for this information

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

Requirement to trigger an alarm when all instances are unhealthy

A

Use Amazon CloudWatch with the condition:

“AWS/ApplicationELB HealthyHostCount <= 0”

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

Need to check why users cannot connect to web server public IP and port (behind ALB)

A

Check the VPC Flow Logs

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

HTTPCode_ELB_5XX_Count Amazon CloudWatch metrics are noticed for an ALB

A

The target group may not contain any healthy

instances

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

CloudWatch shows 4XX errors for app with ALB but the Instances have already been terminated and need to analyze the root cause

A

Use ELB access logs to retrieve info from S3 bucket to find the originators of the requests

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

Need a load balancer where specific static public IP addresses can be whitelisted by clients

A

Use a Network Load Balancer (NLB)

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

Poor performance has been experienced for an application running on Amazon EC2

A

Use EC2 Auto Scaling to dynamically scale

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

503 and 504 errors experienced and instances have high CPU utilization

A

Use EC2 Auto Scaling to dynamically scale

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

ASG does not launch instances during busy periods despite max capacity not being reached

A

Could be due to service limits (check Trusted Advisor) or check for RunInstances requests in CloudTrail in case they are failing

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

Need to analyze instances before they are terminated

A

Use Auto Scaling lifecycle hooks to pause termination

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

Auto Scaling scales based on queue depth but at beginning of day app slows down

A

Create a scheduled scaling policy

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

Create highly available EC2 Auto Scaling group for a single instance app

A

Use at least 3 AZs, min size of 2, desired capacity of 2, and max of 2

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

Elastic Beanstalk worker node reads messages from SQS queue. Auto Scaling scales instances. App slows down when number of messages in queue increases

A

Update ASG to scale on queue depth

17
Q

ALB is expecting a large spike in traffic and the application is memory heavy

A

Use the RequestCountPerTarget metric to control scaling

18
Q

New instances in an Auto Scaling group are not showing up in the aggregated metrics. Step scaling is used

A

Likely due to the warm-up period having not yet expired