DOP-C02 · Question #465
A company streams logs to CloudWatch Logs. Logs must be searchable for 30 days, low-latency accessible for 90 days, and occasionally retrieved after 180 days. Which solution is MOST cost- effective?
The correct answer is D. Configure retention of 30 days and stream via Kinesis Data Firehose to S3. Transition to S3. Exporting logs using CloudWatch subscription filters + Firehose -> S3 enables long-term archival. S3 lifecycle transitions optimize cost with Standard-IA (low-latency) and Deep Archive (long-term retention). This matches AWS best practice for cost-effective log retention.
Question
A company streams logs to CloudWatch Logs. Logs must be searchable for 30 days, low-latency accessible for 90 days, and occasionally retrieved after 180 days. Which solution is MOST cost- effective?
Options
- AConfigure log retention of 30 days and export to S3 via Kinesis Data Streams. Use S3 Lifecycle
- BConfigure retention of 30 days and stream to S3 via Kinesis Data Firehose. Transition to S3 One
- CConfigure retention of 30 days and stream via Kinesis Data Streams, then store in S3 Standard-
- DConfigure retention of 30 days and stream via Kinesis Data Firehose to S3. Transition to S3
How the community answered
(45 responses)- A9% (4)
- B4% (2)
- C16% (7)
- D71% (32)
Explanation
Exporting logs using CloudWatch subscription filters + Firehose -> S3 enables long-term archival. S3 lifecycle transitions optimize cost with Standard-IA (low-latency) and Deep Archive (long-term retention). This matches AWS best practice for cost-effective log retention.
Topics
Community Discussion
No community discussion yet for this question.