Monitoring Options with CloudWatch
Question
HikeHills.com (HH) is an online specialty retailer that sells clothing and outdoor refreshment gear for trekking, go camping, boulevard biking, mountain biking, rock hiking, ice mountaineering, skiing, avalanche protection, snowboarding, fly fishing, kayaking, rafting, road and trace running, and many more. HH runs their entire online infrastructure on multiple java based web applications and other web framework applications running on AWS.
The HH is capturing click stream data and use custom-build recommendation engine to recommend products which eventually improve sales, understand customer preferences and already using AWS Kinesis Streams (KDS) to collect events and transaction logs and process the stream.
Multiple departments from HH use different streams to address real-time integration and induce analytics into their applications and uses Kinesis as the backbone of real-time data integration across the enterprise. HH understand that Monitoring plays a major role in monitoring and managing the streaming platform.
HH using producer library to process events and consumer library to collect and disseminate.
What kind of monitoring can be enabled using CloudWatch? Select 4 options.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E. F. G.Answer: A, C, E, H.
Option A is correct -Metrics configured for streams are automatically collected and pushed to CloudWatch every minute.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption B is incorrect -Metrics configured for streams are automatically collected and pushed to CloudWatch every minute.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption C is correct -Metrics are archived for two weeks; after that period, the data is discarded.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption D is incorrect -Metrics are archived for two weeks; after that period, the data is discarded.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption E is correct -Basic stream level data is captured every minute at no additional charge.
This includes basic information about stream.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption F is incorrect -Basic stream level data is captured every minute at no additional charge.
This includes basic information about stream.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption G is incorrect -Enhanced Shard-level Metrics are being sent to CloudWatch every minute.
These metrics are not enabled by default.
There is a charge for enhanced metrics emitted from Kinesis.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption H is correct -Enhanced Shard-level Metrics are being sent to CloudWatch every minute.
These metrics are not enabled by default.
There is a charge for enhanced metrics emitted from Kinesis.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlCloudWatch is an AWS service that provides monitoring and management of AWS resources and applications. It collects and processes metrics, logs, and events from various sources, including Amazon Kinesis Streams (KDS). HH can enable various monitoring options using CloudWatch to monitor and manage their streaming platform.
The following are the four monitoring options that can be enabled using CloudWatch:
Metrics configured for streams are automatically collected and pushed to CloudWatch every minute: CloudWatch provides various preconfigured metrics for Kinesis streams, such as incoming bytes, incoming records, and outgoing bytes. These metrics are collected every minute by default and can be viewed in the CloudWatch console or through APIs. HH can use these metrics to monitor the health of their Kinesis streams and identify any issues.
Metrics are archived for two weeks; after that period, the data is discarded: CloudWatch archives Kinesis stream metrics for up to two weeks. This means that HH can view historical data for up to two weeks. After that period, the data is discarded and cannot be retrieved. HH can use this feature to monitor and analyze trends in their Kinesis stream metrics over time.
Basic stream level data is captured every minute at no additional charge: CloudWatch provides basic stream level data, such as incoming bytes, incoming records, and outgoing bytes, at no additional charge. This data is captured every minute and can be used by HH to monitor their Kinesis stream's health and performance.
Shard-level data is sent every second at no additional charge: CloudWatch also provides shard-level data, such as incoming records, outgoing records, and iterator age, at no additional charge. This data is sent every second and can be used by HH to monitor their Kinesis stream's shard-level performance.
Option A and D are incorrect because metrics are collected every minute and archived for two weeks, not every second or for one week. Option E and F are incorrect because basic stream level data is captured every minute, not every second. Option G is incorrect because shard-level data is sent every second at no additional charge, not for an additional cost (Option H).
In summary, HH can use CloudWatch to monitor and manage their streaming platform by enabling various monitoring options, such as collecting and processing Kinesis stream metrics, archiving historical data, and monitoring stream and shard-level performance.
