Question : Sysadmin is trying to connect to a running EC instance using SSH. However, the user gets a Host key not found error. Which of the below mentioned options is a possible reason for rejection? 1. The user has provided the wrong user name for the OS login 2. The instance CPU is heavily loaded 3. The security group is not configured properly 4. The access key to connect to the instance is wrong
Correct Answer : 1
Explanation: If the user is trying to connect to a Linux EC2 instance and receives the Host Key not found error the probable reasons are: The private key pair is not right The user name to login is wrong
Question : : A user has hosted an application on EC instances. The EC instances are configured with ELB and Auto Scaling. The application server session time out is 2 hours. The user wants to configure connection draining to ensure that all in-flight requests are supported by ELB even though the instance is being deregistered. What time out period should the user specify for connection draining? 1. 5 minutes 2. 1 hour 3. 30 minutes 4. 2 hours
Correct Answer :2
Explanation: When you enable Connection Draining on a load balancer, any back-end instances that you deregister will complete requests that are in progress before deregistration. Likewise, if a back-end instance fails health checks, the load balancer will not send any new requests to the unhealthy instance but will allow existing requests to complete.
This means that you can perform maintenance such as deploying software upgrades or replacing back-end instances without impacting your customers experience.
Connection Draining is also integrated with Auto Scaling, making it even easier to manage the capacity behind your load balancer. When Connection Draining is enabled, Auto Scaling will wait for outstanding requests to complete before terminating instances.
You can enable Connection Draining via the AWS Management Console, API, or Command Line Interface (CLI), as well as AWS CloudFormation. When you enable connection draining, you can specify a maximum time for the load balancer to keep the connections alive before reporting the instance as deregistered. If you do not specify the maximum timeout period, by default, the load balancer will close connections to the deregistering instance after 300 seconds.
The maximum timeout value can be set between 1 and 3600 seconds.
Question : A user is using the AWS EC. The user wants to have setup as such that when there is an issue in the EC server, such as instance status failed, it should start a new instance in the user's private cloud. Which AWS service helps to achieve this automation? 1. AWS CloudWatch + Cloudformation 2. AWS CloudWatch + AWS AutoScaling + AWS ELB 3. AWS CloudWatch + AWS VPC 4. AWS CloudWatch + AWS SNS
Correct Answer : 4
Explanation: Amazon SNS can deliver notifications by SMS text message or email to the Amazon Simple Queue Service (SQS. queues or to any HTTP endpoint. The user can configure a web service (HTTP End point. in his data centre which receives data and launches an instance in the private cloud. The user should configure the CloudWatch alarm to send a notification to SNS when the "StatusCheckFailed" metric is true for the EC2 instance. The SNS topic can be configured to send a notification to the user's HTTP end point which launches an instance in the private cloud. You can create an CloudWatch alarm that sends an Amazon Simple Notification Service message when the alarm changes state. An alarm watches a single metric over a time period you specify, and performs one or more actions based on the value of the metric relative to a given threshold over a number of time periods. The action is a notification sent to an Amazon Simple Notification Service topic or Auto Scaling policy. Alarms invoke actions for sustained state changes only. CloudWatch alarms will not invoke actions simply because they are in a particular state, the state must have changed and been maintained for a specified number of periods. After an alarm invokes an action due to a change in state, its subsequent behavior depends on the type of action that you have associated with the alarm. For Auto Scaling policy notifications, the alarm continues to invoke the action for every period that the alarm remains in the new state. For Amazon Simple Notification Service notifications, no additional actions are invoked. An alarm has three possible states: " OK-The metric is within the defined threshold " ALARM-The metric is outside of the defined threshold " INSUFFICIENT_DATA-The alarm has just started, the metric is not available, or not enough data is available for the metric to determine the alarm state