When an Auto Scaling group is running in Amazon Elastic Compute Cloud (EC2), your application rapidly scales up and down in response to load within a 10-minute window; however, after the load peaks, you begin to see problems in your configuration management system where previously terminated Amazon EC2 resources are still showing as active.
What would be a reliable and efficient way to handle the cleanup of Amazon EC2 resources within your configuration management system?
Choose 2 answers

• A.Configure an Amazon Simple Queue Service (SQS) queue for Auto Scaling actions that has a script that listens for new messages and removes terminated instances from the configuration management system.
• B.Use Amazon Simple Workflow Service (SWF) to maintain an Amazon DynamoDB database that contains a whitelist of instances that have been previously launched, and allow the Amazon SWF worker to remove information from the configuration management system.
• C.Write a small script that is run during Amazon EC2 instance shutdown to de-register the resource from the configuration management system.
• D.Write a script that is run by a daily cron job on an Amazon EC2 instance and that executes API Describe calls of the EC2 Auto Scaling group and removes terminated instances from the configuration management system.
• E.Use your existing configuration management system to control the launching and bootstrapping of instances to reduce the number of moving parts in the automation.

Comment: *

Name: *

Email: *

Verification: *

When thinking of DynamoDB, what are true of Local Secondary Key properties?

• A.Either the partition key or the sort key can be different from the table, but not both.
• B.Only the sort key can be different from the table.
• C.The partition key and sort key can be different from the table.
• D.Only the partition key can be different from the table.

Comment: *

Name: *

Email: *

Verification: *

You have an Auto Sealing group of Instances that processes messages from an Amazon Simple Queue Service (SQS) queue.
The group scales on the size of the queue. Processing Involves calling a third-party web service.
The web service is complaining about the number of failed and repeated calls it is receiving from you.
You have noticed that when the group scales in, instances are being terminated while they are processing.
What cost-effective solution can you use to reduce the number of incomplete process attempts?

• A.Create a new Auto Scaling group with minimum and maximum of 2 and instances running web proxy software.
  Configure the VPC route table to route HTTP traffic to these web proxies.
• B.Increase the minimum and maximum size for the Auto Scaling group, and change the scaling policies so they scale less dynamically.
• C.Modify the application running on the instances to put itself into an Auto Scaling Standby state while it processes a task and return itself to InService when the processing is complete.
• D.Modify the application running on the instances to enable termination protection while it processes a task and disable it when the processing is complete.

Comment: *

Name: *

Email: *

Verification: *

You currently have an Autoscalinggroup that has the following settings
Min capacity-2
Desired capacity - 2
Maximum capacity - 2
Your launch configuration has AMI'S which are based on the t2.micro instance type. The application running on these instances are now experiencing issues and you have identified that the solution is to change the instance type of the instances running in the Autoscaling Group.
Which of the below solutions will meet this demand.

• A.Change the Instance type in the current launch configuration. Change the Desired value of the Autoscaling Group to 4. Ensure the new instances are launched.
• B.Delete the current Launch configuration. Create a new launch configuration with the new instance type and add it to the Autoscaling Group. This will then launch the new instances.
• C.Make a copy the Launch configuration. Change the instance type in the new launch configuration.
  Attach that to the Autoscaling Group.
  Change the maximum and Desired size of the Autoscaling Group to 4. Once the new instances are launched, change the Desired and maximum size back to 2.
• D.Change the desired and maximum size of the Autoscaling Group to 4. Make a copy the Launch configuration. Change the instance type in the new launch configuration. Attach that to the Autoscaling Group. Change the maximum and Desired size of the Autoscaling Group to 2

Comment: *

Name: *

Email: *

Verification: *

A web-startup runs its very successful social news application on Amazon EC2 with an Elastic Load Balancer, an Auto-Scaling group of Java/Tomcat application-servers, and DynamoDB as data store. The main web application best runs on m2 x large instances since it is highly memory- bound. Each new deployment requires semi-automated creation and testing of a new AMI for the application servers which takes quite a while and is therefore only done once per week. Recently, a new chat feature has been implemented in nodejs and waits to be integrated in the architecture. First tests show that the new component is CPU bound because the company has some experience with using Chef, they decided to streamline the deployment process and use AWS Ops Works as an application life cycle tool to simplify management of the application and reduce the deployment cycles. What configuration in AWS Ops Works is necessary to integrate the new chat module in the most cost-efficient and flexible way?

• A.Createone AWS Ops Works stack, create one AWS Ops Works layer, create one customrecipe
• B.Createone AWS Ops Works stack create two AWS Ops Works layers create one customrecipe
• C.Createtwo AWS Ops Works stacks create two AWS Ops Works layers create one customrecipe
• D.Createtwo AWS Ops Works stacks create two AWS Ops Works layers create two customrecipe

Comment: *

Name: *

Email: *

Verification: *