Question : Slect the all the correct features of Amazon CloudWatch Alarms
1. You can create up to 500 alarms per AWS account.To create or update an alarm, you use the PutMetricAlarm API function 2. You can list any or all of the currently configured alarms, and list any alarms in a particular state using the DescribeAlarms API 3. Access Mostly Uused Products by 50000+ Subscribers 4. You can test an alarm by setting it to any state using the SetAlarmState API 5. Finally, you can view an alarm's history using the DescribeAlarmHistory API
You can create up to 5000 alarms per AWS account. To create or update an alarm, you use the PutMetricAlarm API function (mon-put-metric-alarm command).
You can list any or all of the currently configured alarms, and list any alarms in a particular state using the DescribeAlarms API (mon-describe-alarms command). You can further filter the list by time range.
You can disable and enable alarms by using the DisableAlarmActions and EnableAlarmActions APIs (mon-disable-alarm-actions and mon-enable-alarm-actions commands).
You can test an alarm by setting it to any state using the SetAlarmState API (mon-set-alarm-state command). This temporary state change lasts only until the next alarm comparison occurs.
Finally, you can view an alarm's history using the DescribeAlarmHistory API (mon-describe-alarm-history command). CloudWatch preserves alarm history for two weeks. Each state transition is marked with a unique time stamp. In rare cases, your history might show more than one notification for a state change. The time stamp enables you to confirm unique state changes.
Note Some AWS resources do not send metric data to CloudWatch under certain conditions.
For example, Amazon EBS may not send metric data for an available volume that is not attached to an Amazon EC2 instance, because there is no metric activity to be monitored for that volume. If you have an alarm set for such a metric, you may notice its state change to Insufficient Data. This may simply be an indication that your resource is inactive, and may not necessarily mean that there is a problem.
Question : You have two Elastic Compute Cloud (EC) instances inside a Virtual Private Cloud (VPC) in the same Availability Zone (AZ) but in different subnets.One instance is running a database and the other instance an application that will interface with the database. You want to confirm that they can talk to each other for your application to work properly. Which two things do we need to confirm in the VPC settings so that these EC2 instances can communicate inside the VPC?
Choose 2 answers A. A network ACL that allows communication between the two subnets. B. Both instances are the same instance class and using the same Key-pair. C. That the default route is set to a NAT instance or internet Gateway (IGW) for them to communicate. D. Security groups are set to allow the application host to talk to the database on the right port/protocol.
Explanation: Complete scenerio described at http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html
Question : How different is creating an Amazon RDS Reserved Instance from creating an Amazon RDS On-Demand Instance? 1. Both has to be configured differently 2. There is no difference 3. Access Mostly Uused Products by 50000+ Subscribers 4. On_demand has DB Parameter Groups but reserved instance has optional DB Parameter Groups
Explanation: Reserved DB instances let you make a one time up front payment for a DB instance and reserve the DB instance for a one or three y ear term at significantly lower rates. There is no difference in creating an Amazon RDS Reserved Instance from creating an Amazon RDS On-Demand Instance. Reserved Instances are available in three varieties Heavy Utilization, Medium Utilization, and Light Utilization that enable you to optimize your Amazon RDS costs based on your expected utilization