Q46 — AWS SAA-C03 Ch.3
Question 46 of 65 | ← Chapter 3
Q176. A company is building a solution that will report Amazon EC2 Auto Scaling events across all the applications in an AWS account. The company needs to use a serverless solution to store the EC2 Auto Scaling status data in Amazon S3. The company then will use the data in Amazon S3 to provide near-real-time updates in a dashboard. The solution must not affect the speed of EC2 instance launches. How should the company move the data to Amazon S3 to meet these requirements?
- A. Use an Amazon CloudWatch metric stream to send the EC2 Auto Scaling status data to Amazon Kinesis Data Firehose. Store the data in Amazon S3 ✓
- B. Launch an Amazon EMR cluster to collect the EC2 Auto Scaling status data and send the data to Amazon Kinesis Data Firehose. Store the data in Amazon S3.
- C. Create an Amazon EventBridge (Amazon CloudWatch Events) rule to invoke an AWS Lambda function on a schedule. Configure the Lambda function to send the EC2Auto Scaling status data directly to Amazon S3
- D. Use a bootstrap script during the launch of an EC2 instance to install Amazon Kinesis Agent. Configure Kinesis Agent to collect the EC2Auto Scaling status data and send the data to Amazon Kinesis Data Firehose. Store the data in Amazon S3.
Correct Answer: A. Use an Amazon CloudWatch metric stream to send the EC2 Auto Scaling status data to Amazon Kinesis Data Firehose. Store the data in Amazon S3
Explanation
To report Amazon EC2 Auto Scaling events across all the applications in an AWS account, and store the EC2 Auto Scaling status data in Amazon S3 using a serverless solution that does not affect the speed of EC2 instance launches, a solutions architect should use an Amazon CloudWatch metric stream to send the EC2 Auto Scaling status data to Amazon Kinesis Data Firehose. The data can then be stored in Amazon S3. Therefore, option A is the correct answer.Option C suggests creating an Amazon EventBridge (Amazon CloudWatch Events) rule to invoke an AWS Lambda function on a schedule to send the EC2 Auto Scaling status data directly to Amazon S3. While this approach could work, it may add unnecessary complexity compared to using Amazon CloudWatch metric streams and Amazon Kinesis Data Firehose.Option B suggests launching an Amazon EMR cluster to collect the EC2 Auto Scaling status data and send the data to Amazon Kinesis Data Firehose for storage in Amazon S3. This approach may be more complex than necessary and may not provide the desired near-real-time updates required by the dashboard.Option D suggests using a bootstrap script during the launch of an EC2 instance to install Amazon Kinesis Agent. Configure Kinesis Agent to collect the EC2 Auto Scaling status data and send the data to Amazon Kinesis Data Firehose to store the data in Amazon S3. This approach requires modifying the EC2 instance launch configuration, which may not meet the requirement of not affecting the speed of EC2 instance launches.Using an Amazon CloudWatch metric stream to send the EC2 Auto Scaling status data to Amazon Kinesis Data Firehose provides a simple, scalable, and cost-effective solution for reporting Amazon EC2 Auto Scaling events across all the applications in an AWS account and storing the data in Amazon S3. Once the data is stored in Amazon S3, it can be used to provide near-real-time updates in a dashboard. This approach meets the requirements and does not affect the speed of EC2 instance launches.