A medical company is running a REST API on a set of Amazon EC2 instances. The EC2 instances run in an Auto Scaling group behind an Application Load Balancer (ALB). The ALB runs in three public…

Question

Options

• AStore a random string in AWS Secrets Manager. Create an AWS Lambda function for automatic
• BCreate an AWS WAF web ACL rule with an IP match condition of the CloudFront service IP
• CStore a random string in AWS Systems Manager Parameter Store. Configure Parameter Store
• DConfigure AWS Shield Advanced. Create a security group policy to allow connections from

• A
  22% (9)
• B
  7% (3)
• C
  10% (4)
• D
  61% (25)

Explanation

https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html It shows For Amazon EC2 Auto Scaling, there are two primary process types: Launch and Terminate. The Launch process adds a new Amazon EC2 instance to an Auto Scaling group, increasing its capacity. The Terminate process removes an Amazon EC2 instance from the group, decreasing its capacity. HealthCheck process for EC2 autoscaling is not a primary process! It is a process along with the following AddToLoadBalancer AlarmNotification AZRebalance HealthCheck InstanceRefresh ReplaceUnhealthy ScheduledActions From the requirements, Some EC2 instances are now being marked as unhealthy and are being terminated. Application is running at reduced capacity not because instances are marked unhealthy but because they are being terminated. https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume- processes.html#choosing-suspend-resume

No community discussion yet for this question.