CheckPoints -CIS

You have created an application load balancer and selected two EC2 instances as targets. However, when you are trying to make a request to load balancer from the internet, the requests are getting failed. What could be the reason?

• 
  The subnets specified for load balancer does not have internet gateway attached to their route tables.

• Target EC2 instances are in private instances without any internet gateway attached.

• There is no elastic IP address attached to the load balancer.

• Cross-zone load balancer is not enabled

For compliance purposes, you would like to expose a fixed static IP address to your end-users so that they can write firewall rules that will be stable and approved by regulators. What type of Elastic Load Balancer would you choose?

• Network Load Balancer

• Application Load Balancer

• Classic Load Balancer

Answer explanation

Network Load Balancers (NLB) expose a public static IP, whereas an Application or Classic Load Balancer exposes a static DNS (URL)

Which of these important Cloud concepts will an ELB improve? (Choose two answers)

• Fault Tolerance

• High Availability

• Scalability

• Elasticity

A user is planning to scale up an application by 8 AM and scale down by 7 PM daily using Auto Scaling. What should the user do in this case?

• User should setup a batch process which launches the EC2 instance at a specific time

• Setup the scaling policy to scale up and down based on the CloudWatch alarms

• Setup scheduled actions to scale up or down at a specific time

• User should increase the desired capacity at 8 AM and decrease it by 7 PM manually

An organization has configured Auto Scaling for hosting their application. The system admin wants to understand the Auto Scaling health check process. If the instance is unhealthy, Auto Scaling launches an instance and terminates the unhealthy instance. What is the order execution?

• Auto Scaling launches a new instance first and then terminates the unhealthy instance

• Auto Scaling launches and terminates the instances simultaneously

• Auto Scaling performs the launch and terminate processes in a random order

• Auto Scaling terminates the instance first and then launches a new instance

An organization has configured Auto Scaling with ELB. There is a memory issue in the application which is causing CPU utilization to go above 90%. The higher CPU usage triggers an event for Auto Scaling as per the scaling policy. If the user wants to find the root cause inside the application without triggering a scaling activity, how can he achieve this?

• Stop the scaling process until research is completed

• It is not possible to find the root cause from that instance without triggering scaling

• Delete Auto Scaling until research is completed

• Suspend the scaling process until research is completed

A user has configured ELB with Auto Scaling. The user suspended the Auto Scaling Alarm Notification (which notifies Auto Scaling for CloudWatch alarms) process for a while. What will Auto Scaling do during this period?

• AWS will not receive the alarms from CloudWatch

• Auto Scaling will execute the policy but it will not launch the instances until the process is resumed

• AWS will receive the alarms but will not execute the Auto Scaling policy

• It is not possible to suspend the AlarmNotification process

A sys admin is trying to understand the Auto Scaling activities. Which of the below mentioned processes is not performed by Auto Scaling?

• Reboot Instance

• Schedule Actions

• Replace Unhealthy

• Availability Zone Re-Balancing

Which of the following is not true? (Choose two.)

• 
  A subnet can have the same CIDR block as the VPC within which it exists.

• A subnet can have a smaller CIDR block than the VPC within which it exists.

• 
  A subnet can have a larger CIDR block than the VPC within which it exists

• A subnet does not have to have a CIDR block specified.

What kind of relationship is a VPC peering connection?

• 
  One-to-one between subnets

• 
  One-to-many between subnets

• One-to-one between VPCs

• One-to-many between VPCs