CV0-002 · Question #215
A cloud engineer is using a hosted service for aggregating the logs for all the servers in a public cloud environment. Each server is configured via syslog to send its logs to a central location. A ne
The correct answer is C. The data limit has been exceeded at the SaaS provider.. The most likely reason the SaaS log aggregation service stops processing logs at noon daily, given a 50% daily increase in log size, is that the SaaS provider's data limit for logging has been exceeded.
Question
A cloud engineer is using a hosted service for aggregating the logs for all the servers in a public cloud environment. Each server is configured via syslog to send its logs to a central location. A new version of the application was recently deployed, and the SaaS server now stops processing logs at noon each day. In reviewing the system logs, the engineer notices the size of the logs has increased by 50% each day. Which of the following is the MOST likely reason the logs are not being published after noon?
Options
- AThe logging directory does not have sufficient storage space.
- BThe syslog service is not running on the servers.
- CThe data limit has been exceeded at the SaaS provider.
- DThere is a cloud service provider outage.
How the community answered
(25 responses)- A12% (3)
- B8% (2)
- C60% (15)
- D20% (5)
Why each option
The most likely reason the SaaS log aggregation service stops processing logs at noon daily, given a 50% daily increase in log size, is that the SaaS provider's data limit for logging has been exceeded.
If the logging directory on the source servers did not have sufficient storage, logs would not be sent, or the application might crash, but it wouldn't cause the SaaS service to stop processing logs specifically at noon.
If the syslog service were not running on the servers, no logs would be sent at all, rather than logs stopping specifically at noon each day.
SaaS logging services often have daily or monthly data intake limits, and a consistent stoppage at noon each day, combined with a 50% daily increase in log size, strongly indicates that the service is hitting its predefined data volume cap around that time, causing it to stop processing further logs.
A general cloud service provider outage would likely affect more than just log processing at a specific time each day and would be a more widespread issue.
Concept tested: SaaS log management limitations, log volume management
Topics
Community Discussion
No community discussion yet for this question.