CV0-003 · 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 A. The logging directory does not have sufficient storage space.. Log growth of 50% per day caused the logging directory to run out of storage space, stopping log ingestion at the point the disk fills each day.
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
(38 responses)- A76% (29)
- B3% (1)
- C8% (3)
- D13% (5)
Why each option
Log growth of 50% per day caused the logging directory to run out of storage space, stopping log ingestion at the point the disk fills each day.
The new application version increased log verbosity by 50% daily, so the local logging directory accumulates data until it reaches capacity. Once the directory is full - which now consistently occurs around noon - the syslog receiver can no longer write new entries, halting log publishing for the rest of the day.
If the syslog service were not running, logs would never be received at any time of day, not just after a specific cutoff point.
A SaaS-side data limit might throttle or reject logs, but the question specifically references the logging directory and local storage behavior, pointing to a local capacity constraint.
A cloud provider outage would cause an unpredictable, intermittent failure pattern affecting all hours, not a consistent daily cutoff at noon.
Concept tested: Log storage capacity and syslog ingestion limits
Source: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-workspace-overview
Topics
Community Discussion
No community discussion yet for this question.