AWS Cloud Development Kit - From Beginner to Professional - CloudWatch Alarms: EC2, Lambda

What is the primary purpose of using CloudWatch alarms and metrics?

• To create new EC2 instances

• To delete unused resources

• To increase server storage capacity

• To monitor resource performance and user experience

What is the role of an SNS topic in the context of CloudWatch alarms?

• To create new Lambda functions

• To notify the OPS team when an alarm is triggered

• To store data logs

• To manage EC2 instance security

What metric is primarily monitored for EC2 instances to trigger alarms?

• Network bandwidth

• Disk space

• Memory usage

• CPU utilization

What happens when an EC2 instance's CPU utilization falls below the set threshold?

• The instance is automatically shut down

• An alarm is triggered

• The instance is restarted

• No action is taken

What is the significance of setting a low threshold for CPU utilization in a demo environment?

• To ensure alarms are triggered quickly for demonstration

• To optimize resource usage

• To increase server performance

• To prevent any alarms from being triggered

What is the first step in creating a CloudWatch alarm for a Lambda function?

• Setting up a test event

• Creating a metric for errors

• Configuring the SNS topic

• Deploying the Lambda function

How can you verify that a CloudWatch alarm has been triggered?

• By checking the EC2 instance logs

• By checking the Lambda function code

• By receiving an email notification

• By observing increased CPU usage

What action is taken when a Lambda function alarm is triggered due to errors?

• The function is deleted

• The function is restarted

• An email notification is sent

• The function is paused

What is the purpose of introducing errors in the Lambda function during testing?

• To improve function performance

• To trigger alarms and test notifications

• To reduce server load

• To optimize code execution

What should you do if you encounter issues while setting up CloudWatch alarms?

• Post questions in the comments for community help

• Consult the AWS documentation

• Restart the entire setup process

• Ignore the issues