Section 6 - 8 Flashcards
T/F - Elastic Network Interface (ENI) can be attached to EC2 instances in another AZ.
False. ENIs are bound to a specific AZ and cannot be attached to EC2 instances outside of that AZ
The io1/io2 family of EBS volumes can use EBS multi-attach. How many instances can be attached to a single EBS volume at a time?
16 instances
T/F - EFS is only compatible with Windows based AMIs
False. EFS is only compatible with Linux based AMIs
You are running a high-performance database that requires an IOPS of 310,000 for its underlying storage. What do you recommend?
EC2 Instance Store
You are running a website on 10 EC2 instances fronted by an Elastic Load Balancer. Your users are complaining about the fact that the website always asks them to re-authenticate when they are moving between website pages. You are puzzled because it’s working just fine on your machine and in the Dev environment with 1 EC2 instance. What could be the reason?
You need to enable Sticky Sessions to ensure that the clients traffic is always redirecting to the same target (in this case the EC2 instance).
Essentially the client is getting sent to other EC2 instances by the load balancer while they’re navigating the website.
Your website is using an ALB to distribute traffic to your EC2 instances. You website only sees the traffic coming from your own ALBs private IPv4 addresses. If you modify your websites backend, where can you request the clients IP address from?
The X-Forwarded-For header
T/F - ALB does not support the TCP protocol
True, ALB supports HTTP/HTTPS, and WebSocket
T/F - ALBs can route traffic to different Target Groups based on URL Path, Hostname, HTTP Headers, and Query Strings.
True
T/F - ALBs can route traffic to different Target Groups based on the clients geographical location
False, do not confuse an ALB with Route 53
T/F - An ALB can have an NLB as its target group
False, an ALB cannot route traffic to a lower level in the OSI model (it would be going backwards)
T/F - An NLB can have an ALB as its target group
True, since an NLB operates at a lower layer, it can use an ALB as a target group
You need a fixed static IP address for your end-users. What type of Elastic Load Balancer would you use?
Network Load Balancer, ALBs do not have a static IP
T/F - Both NLBs and ALBs have a static DNS name
True
T/F - Network Load Balancer has 1 static IP address per AZ
True
Which ELB can you attach a Elastic IP address to?
An NLB, ALBs cannot have Elastic Ip addresses
You have an ALB that is configured to redirect traffic to 3 Target Groups with these hostnames: users.example.com, api.external.example.com, and checkout.example.com.
You would like to configure HTTPS for each of these hostnames. How do you configure the ALB to make this work?
Use Server Name Indication (SNI)
How does SNI work?
It loads multiple SSL certificates on to 1 web server, to serve multiple pages
In your ASG you set both “desired” and “maximum” capacity to 3. You set up CloudWatch to scale out your ASG when CPU utilization reaches 60%. What happens to the desired/max capacity when CPU utilization reaches 60%?
Absolutely nothing. Maximum obviously stays the same, and Desired cannot go higher than maximum.
You have an Auto Scaling Group fronted by an Application Load Balancer. You have configured the ASG to use ALB Health Checks, then one EC2 instance has just been reported unhealthy. What will happen to the EC2 instance?
The ASG will terminate the instance
Which protocols are supported in NLB Health Checks?
TCP, HTTP, and HTTPS
