Chapter 5: Elastic Load Balancin

2018-07-15  本文已影响25人  K1024

Chapter 5: Elastic Load Balancing, Amazon CloudWatch, and Auto Scaling

  1. A, D. An Auto Scaling group must have a minimum size and a launch configuration defined in order to be created. Health checks and a desired capacity are optional.
  1. B. The load balancer maintains two separate connections: one connection with the client and one connection with the Amazon EC2 instance.
  1. D. Amazon CloudWatch metric data is kept for 2 weeks.
  1. A. Only the launch configuration name, AMI, and instance type are needed to create an Auto Scaling launch configuration. Identifying a key pair, security group, and a block device mapping are optional elements for an Auto Scaling launch configuration.
  1. B. You can use the Amazon CloudWatch Logs Agent installer on existing Amazon EC2 instances to install and configure the CloudWatch Logs Agent.
  1. C. You configure your load balancer to accept incoming traffic by specifying one or more listeners.
  1. D. The default Amazon EC2 instance limit for all regions is 20.
  1. A. An SSL certificate must specify the name of the website in either the subject name or listed as a value in the SAN extension of the certificate in order for connecting clients to not receive a warning.
  1. C. When Amazon EC2 instances fail the requisite number of consecutive health checks, the load balancer stops sending traffic to the Amazon EC2 instance.
  1. D. Amazon CloudWatch metrics provide hypervisor visible metrics.
  1. C. Auto Scaling is designed to scale out based on an event like increased traffic while being cost effective when not needed.
  1. B. Auto Scaling will provide high availability across three Availability Zones with three Amazon EC2 instances in each and keep capacity above the required minimum capacity, even in the event of an entire Availability Zone becoming unavailable.
  1. B, E, F. Auto Scaling responds to changing conditions by adding or terminating instances, launches instances from an AMI specified in the launch configuration associated with the Auto Scaling group, and enforces a minimum number of instances in the min-size parameter of the Auto Scaling group.
  1. D. A, B, and C are all true statements about launch configurations being loosely coupled and referenced by the Auto Scaling group instead of being part of the Auto Scaling group.
  2. A, C. An Auto Scaling group may use On-Demand and Spot Instances. An Auto Scaling group may not use already stopped instances, instances running someplace other than AWS, and already running instances not started by the Auto Scaling group itself.
  1. A, F. Amazon CloudWatch has two plans: basic, which is free, and detailed, which has an additional cost. There is no ad hoc plan for Amazon CloudWatch.
  1. A, C, D. An Elastic Load Balancing health check may be a ping, a connection attempt, or a page that is checked.
  1. B, C. When connection draining is enabled, the load balancer will stop sending requests to a deregistered or unhealthy instance and attempt to complete in-flight requests until a connection draining timeout period is reached, which is 300 seconds by default.
  1. B, E, F. Elastic Load Balancing supports Internet-facing, internal, and HTTPS load balancers.
  1. B, D, E. Auto Scaling supports maintaining the current size of an Auto Scaling group using four plans: maintain current levels, manual scaling, scheduled scaling, and dynamic scaling.

知识点总结

上一篇下一篇

猜你喜欢

热点阅读