2. Your company has multiple applications running on AWS. Your company wants to develop a tool that notifies on-call teams Immediately via email when an alarm Is triggered in your environment. You have multiple on- call teams that work different shifts, and the tool should handle notifying the correct teams at the correct times. How should you implement this solution?

A) Create an Amazon SNS topic and configure your on-call team email addresses as subscribers. Create a secondary Amazon SNS topic for alarms and configure your Cloud Watch alarms to notify this topic when triggered. Create an HTTP subscriber to this topic that notifies your application via HTTP POST when an alarm is triggered. Use the AWS(Amazon Web Service) SDK tools to integrate your application with Amazon SNS and send messages to the first topic so that onc all engineers receive alerts.
B) Create an Amazon SNS topic and an Amazon SOS queue. Configure the Amazon SQS queue as a subscriber to the Amazon SNS topic. Configure Cloud Watch alarms to notify this topic when an alarm is triggered. Create an Amazon EC2 Auto Scaling group with both minimum and desired Instances configured to 0. Worker nodes in this group spawn when messages are added to the queue. Workers then use Amazon Simple Email Service to send messages to your on call teams.
C) Create an Amazon SNS topic for each on-call group, and configure each of these with the team member emails as subscribers. Create another Amazon SNS topic and configure your Cloud Watch alarms to notify this topic when triggered. Create an HTTP subscriber to this topic that notifies your application via HTTP POST when an alarm is triggered. Use the AWS(Amazon Web Service) SDK tools to integrate your application with Amazon SNS and send messages to the correct team topic when on shift.
D) Create an Amazon SNS topic and configure your on-call team email addresses as subscribers. Use the AWS(Amazon Web Service) SDK tools to integrate your application with Amazon SNS and send messages to this new topic. Notifications will be sent to on-call users when a Cloud Watch alarm is triggered.



3. ou use Amazon Cloud Watch as your primary monitoring system for your web application. After a recent software deployment, your users are getting Intermittent 500 Internal Server Errors when using the web application. You want to create a Cloud Watch alarm, and notify an on-call engineer when these occur. How can you accomplish this using AWS(Amazon Web Service) services? Choose three answers from the options given below Please select:(Select 2answers)

A) Deploy your web application as an AWS(Amazon Web Service) Elastic Beanstalk application. Use the default Elastic Beanstalk Cloud watch metrics to capture 500 Internal Server Errors. Set a Cloud Watch alarm on that metric.
B) Use Amazon Simple Email Service to notify an on-call engineer when a Cloud Watch alarm is triggered.
C) Use Amazon Simple Notification Service to notify an on-call engineer when a Cloud Watch alarm is triggered.
D) Install a Cloud Watch Logs Agent on your servers to stream web application logs to Cloud Watch.
E) Create a Cloud Watch Logs group and define metric filters that capture 500 Internal Server Errors. Set a Cloud Watch alarm on that metric.


4. You have an Auto Scaling group with an Elastic Load Balancer. You decide to suspend the Auto Scaling Add To Load Balancer for a short period of time. What will happen to the instances launched during the suspension period?

A) The instances will be registered with ELS once the process has resumed
B) The instances will not be registered with ELB. You must manually register when the process is resumed .
C) Auto Scaling will not launch the instances during this period because of the suspension
D) It is not possible to suspend the Add To Load Balancer process



5. You currently have the following setup in AWS(Amazon Web Service) 1)An Elastic Load Balancer 2) Auto scaling Group which launches EC Instances3) AMIs with your code pre-installed You want to deploy the updates to your app to only a certain number of users. You want to have a cost-effective solution. You should also be able to revert back quickly. Which of the below solutions is the most feasible one?

A) Create a full second stack of instances, cut the DNS over to the new stack of instances, and change the ONS back if a rollback is needed.
B) Redeploy with AWS(Amazon Web Service) Elastic Beanstalk and Elastic Beanstalk versions. Use Route 53 Weighted Round Robin records to adjust the proportion of traffic hitting the two ELB5
C) Create a second ELB. Auto Scaling. Create the AMI with the new app. Use a new launch configuration. Use Route 53 Weighted Round Robin records to adjust the proportion of traffic hitting the two ELBs.
D) Create new AMIs with the new app. Then use the new EC2 instances in half proportion to the older instances.