Answer-first summary for fast verification
Answer: Since logs are excluded only after being received by the Logging API, the exclusion filters do not decrease the number of entries.write API calls.
The correct answer highlights that the core issue lies with the entries.write API calls, which push logs to Cloud Logging before any exclusion filters are applied. Reducing the volume of logs collected is the solution. The other options are incorrect because exclusion filters operate post-logging API call, meaning logs are already in Cloud Logging when filters are applied, and no additional permissions are required for the Managed Instance Group to access Cloud Logging. For more details, refer to the documentation on routing overview and logging quotas.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Imagine you're a DevOps engineer at a rapidly growing social media company, responsible for monitoring their flagship web application. The application, deployed on Managed Instance Groups behind an HTTP(S) load balancer, is generating logs at such a volume that the project is exceeding the logging API quota. Despite implementing exclusion filters in Cloud Logging, the issue continues. What could be the underlying problem?
A
Additional log types must be included in the exclusion filters to address the quota issue.
B
The exclusion filter's configuration might be incorrect, preventing it from functioning as intended.
C
The Managed Instance Group's service account lacks the necessary permissions to utilize the exclusion filters effectively.
D
Since logs are excluded only after being received by the Logging API, the exclusion filters do not decrease the number of entries.write API calls.