Answer-first summary for fast verification
Answer: Logs are processed by the Logging API before exclusion filters are applied, meaning the number of entries.write API calls isn't reduced by excluding logs.
Options A and B are incorrect because exclusion filters operate after the logging API has been called and the logs are already in Cloud Logging. Option C is correct as the core issue lies with the entries.write API calls that push logs to Cloud Logging before exclusion filters can act. Reducing the volume of logs collected is the solution. Option D is incorrect since no additional permissions are required; the Managed Instance Group already has access to Cloud Logging. For more details, refer to [Cloud Logging Exclusions](https://cloud.google.com/logging/docs/exclusions) and [Logging Quotas](https://cloud.google.com/logging/quotas#log-limits).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
As a DevOps engineer for a rapidly growing social media company, you're part of the monitoring team for their flagship web application. The application, deployed on Managed Instance Groups behind an HTTP(S) load balancer, is generating logs at a rate that exceeds the project's logging API quota. Despite implementing exclusion filters in Cloud Logging, the issue continues. What could be the underlying problem?
A
The exclusion filter configuration is incorrect.
B
Additional log types need to be included in the exclusion filters.
C
Logs are processed by the Logging API before exclusion filters are applied, meaning the number of entries.write API calls isn't reduced by excluding logs.
D
The Managed Instance Group's service account lacks the necessary permissions to utilize exclusion filters effectively.