Exam AWS Certified Security - Specialty SCS-C02 topic 1 question 233 discussion

Exam question from Amazon's AWS Certified Security - Specialty SCS-C02

Question #: 233
Topic #: 1

[All AWS Certified Security - Specialty SCS-C02 Questions]

Amazon CloudWatch Logs agent is successfully delivering logs to the CloudWatch Logs service. However, logs stop being delivered after the associated log stream has been active for a specific number of hours.

What steps are necessary to identify the cause of this phenomenon? (Choose two.)

A. Ensure that file permissions for monitored files that allow the CloudWatch Logs agent to read the file have not been modified.
B. Verify that the OS Log rotation rules are compatible with the configuration requirements for agent streaming.
C. Configure an Amazon Kinesis producer to first put the logs into Amazon Kinesis Streams.
D. Create a CloudWatch Logs metric to isolate a value that changes at least once during the period before logging stops.
E. Use AWS CloudFormation to dynamically create and maintain the configuration file for the CloudWatch Logs agent.

Show Suggested Answer

Suggested Answer: AB 🗳️

by IPLogic at Dec. 5, 2024, 4:55 p.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

AWSLoverLoverLoverLoverLover

4 months ago

Selected Answer: AB

✅ A. File permissions issue – If the file permissions change (e.g., log rotation modifies ownership or access rights), the CloudWatch Logs agent may lose access to the logs and stop forwarding them. ✅ B. Log rotation issue – Many operating systems use log rotation mechanisms (e.g., logrotate in Linux). If a log file is rotated and the CloudWatch Logs agent is not configured to handle rotation correctly, it may lose track of the log stream and stop sending logs.

upvoted 3 times

...

Bachhu

5 months, 2 weeks ago

Selected Answer: AB

AB E is not the step to identify the cause but can potentially solve the issue.

upvoted 3 times

...

nznzwell

6 months ago

The question asks "What steps are necessary to identify the cause of this phenomenon? ". E is not a step to identify the cause, but an action to potentially solve the issue. So, should be A, B. For A, file permissions CAN change to prevent the Cloudwatch agent from reading it.

upvoted 1 times

...

IPLogic

6 months, 2 weeks ago

Selected Answer: BE

To identify the cause of logs stopping after a certain number of hours, you should: B. Verify that the OS Log rotation rules are compatible with the configuration requirements for agent streaming. E. Use AWS CloudFormation to dynamically create and maintain the configuration file for the CloudWatch Logs agent. These steps will help ensure that the log rotation process isn't interfering with the CloudWatch Logs agent and that the configuration is properly maintained

upvoted 1 times

IPLogic

6 months, 2 weeks ago

Option A. - Ensuring file permissions are correct can indeed impact the ability of the CloudWatch Logs agent to read files. However, the specific issue you're facing—where logs stop being delivered after a certain number of hours—suggests that the problem is more likely related to log rotation or configuration management, which is addressed by choices B and E. File permissions typically would cause an immediate issue, preventing any log delivery from the start. Since your logs are delivered successfully at first and then stop after some time, it's more indicative of a problem with how logs are being rotated or how the agent's configuration is maintained.

upvoted 1 times

panvik

5 months, 1 week ago

A. Ensure that file permissions for monitored files that allow the CloudWatch Logs agent to read the file have not been modified. The point says "have been modified" and that perfectly explains why they worked first and the stopped

upvoted 1 times

...