Question : You have an Auto Scaling group associated with an Elastic Load Balancer (ELB). You have noticed that instances launched via the Auto Scaling group are being marked unhealthy due to an ELB health check, but these unhealthy instances are not being terminated What do you need to do to ensure trial instances marked unhealthy by the ELB will be terminated and replaced? 1. Change the thresholds set on the Auto Scaling group health check 2. Add an Elastic Load Balancing health check to your Auto Scaling group 3. Access Mostly Uused Products by 50000+ Subscribers 4. Change the health check set on the Elastic Load Balancer to use TCP rather than HTTP checks
Correct Answer : Get Lastest Questions and Answer : Explanation: If you set the autoscaling group's health check type to ELB then it will automatically retire any instances that fail the ELB health checks (ie doesn't respond in a timely manner to the URL configured) As long as the configured health check properly reports than an instance is bad (which sounds like it is the case since you say ELB is marking the instance as unhealthy) this should work
Auto Scaling periodically performs health checks on the instances in your group and replaces instances that fail these checks. By default, these health checks use the results of EC2 instance status checks to determine the health of an instance. If you use a load balancer with your Auto Scaling group, you can optionally choose to include the results of Elastic Load Balancing health checks. Auto Scaling marks an instance as unhealthy if the instance status is any state other than running, the system status is impaired, or Elastic Load Balancing reports the instance state as OutOfService. You can customize the health check conducted by your Auto Scaling group by specifying additional checks or by having your own health check system and then sending the instance's health information directly from your system to Auto Scaling After an instance is marked unhealthy because of an Amazon EC2 or Elastic Load Balancing health check, it is scheduled for replacement.
Replacing Unhealthy Instances : After an instance has been marked unhealthy as a result of an Amazon EC2 or Elastic Load Balancing health check, it is almost immediately scheduled for replacement. It never automatically recovers its health. You can intervene manually by calling the SetInstanceHealth action (or the as-set-instance-health command) to set the instance's health status back to healthy, but you will get an error if the instance is already terminating. Because the interval between marking an instance unhealthy and its actual termination is so small, attempting to set an instance's health status back to healthy with the SetInstanceHealth action (or, as-set-instance-health command) is probably useful only for a suspended group. For more information, see Suspend and Resume Auto Scaling Processes. Auto Scaling creates a new scaling activity for terminating the unhealthy instance and then terminates it. Subsequently, another scaling activity launches a new instance to replace the terminated instance. When your instance is terminated, any associated Elastic IP addresses are disassociated and are not automatically associated with the new instance. You must associate these Elastic IP addresses with the new instance manually. Similarly, when your instance is terminated, its attached EBS volumes are detached. You must attach these EBS volumes to the new instance manually.
Add an Elastic Load Balancing Health Check to your Auto Scaling Group By default, an Auto Scaling group periodically reviews the results of EC2 instance status to determine the health state of each instance. However, if you have associated your Auto Scaling group with an Elastic Load Balancing load balancer, you can choose to use the Elastic Load Balancing health check. In this case, Auto Scaling determines the health status of your instances by checking the results of both the EC2 instance status check and the Elastic Load Balancing instance health check.
Question : Which two AWS services provide out-of-the-box user configurable automatic backup-as-a-service and backup rotation options?
Choose 2 answers A. Amazon S3 B. Amazon RDS C. Amazon EBS D. Amazon Red shift
Explanation: By default and at no additional charge, Amazon RDS enables automated backups of your DB Instance with a 1 day retention period. Free backup storage is limited to the size of your provisioned database and only applies to active DB Instances. For example, if you have 10GB-months of provisioned database storage, we will provide at most 10GB-months of backup storage at no additional charge. If you would like to extend your backup retention period beyond one day, you can do so using the CreateDBInstance API (when creating a new DB Instance) or ModifyDBInstance API (for an existing DB Instance). You can use these APIs to change the RetentionPeriod parameter from 1 to the desired number of days. By default, Amazon Redshift enables automated backups of your data warehouse cluster with a 1-day retention period. Free backup storage is limited to the total size of storage on the nodes in the data warehouse cluster and only applies to active data warehouse clusters. For example, if you have total data warehouse storage of 8TB, we will provide at most 8TB of backup storage at no additional charge. If you would like to extend your backup retention period beyond one day, you can do so using the AWS Management Console or the Amazon Redshift APIS. For more information on automated snapshots, please refer to the Amazon Redshift Management Guide. Amazon Redshift only backs up data that has changed so most snapshots only use up a small amount of your free backup storage.
Question :
How would you move an EBS volume to another availability zone?
1. Right click on the volume and select . 2. Create a snapshot of the volume and then create a volume based off the snapshot in the new availability zone. 3. Access Mostly Uused Products by 50000+ Subscribers 4. None of the above
Explanation: You can use a copy of an Amazon EBS snapshot in the following ways:
Geographic Expansion: You can launch your applications in a new region.
Migration: You can migrate an application to a new region, to enable better availability and minimize cost.
Disaster Recovery: You can back up your data and logs across different geographical locations at regular intervals. In case of disaster, you can restore your applications using point-in-time backups stored in the secondary region. This minimizes data loss and recovery time.
Question : For which of the following use cases are Simple Workflow Service (SWF) and Amazon EC an appropriate solution? Choose answers A. Using as an endpoint to collect thousands of data points per hour from a distributed fleet of sensors B. Managing a multi-step and multi-decision checkout process of an e-commerce website C. Orchestrating the execution of distributed and auditable business processes D. Using as an SNS (Simple Notification Service) endpoint to trigger execution of video transcoding jobs E. Using as a distributed session store for your web application 1. A,B 2. B,C 3. Access Mostly Uused Products by 50000+ Subscribers 4. D,E
Ans : 1 Exp : Q: Can I reassign my RI from one instance family (e.g., c1.xlarge) to another (e.g., m1.large)? No. An RI is associated with a specific instance family for the duration of the RI term; however, you can change from one instance type (e.g., c3.large) to another (e.g., c3.xlarge) in the same family, if it is a Linux/UNIX RI. Hence Option D is out. The only difference between a Reserved instance and a regular instance is the billing, All other features such as AutoScaling and AMIs remain the same. It is important that you factor the billing aspect of Reserved Instance's in to your deployment design as you do not want to have paid Reserved Instances not in use as you have already paid for them upfront. Hence option B is out, and C is correct.
Question : In AWS, which security aspects are the customer's responsibility? Choose answers A. Security Group and ACL (Access Control List) settings B. Decommissioning storage devices C. Patch management on the EC2 instance's operating system D. Life-cycle management of IAM credentials E. Controlling physical access to compute resources F. Encryption of EBS (Elastic Block Storage) volumes
1. Use a DynamoDB table with an attribute defining the priority level. Transformation instances will scan the table for tasks, sorting the results by priority level. 2. Use Route 53 latency based-routing to send high priority tasks to the closest transformation instances. 3. Access Mostly Uused Products by 50000+ Subscribers Transformation instances first poll the high priority queue; if there is no message, they poll the default priority queue. 4. Use a single SQS queue. Each message contains the priority level. Transformation instances poll high-priority messages first.