Question 890
At the Birchhaven online ticketing service, following an organizational restructuring, responders manually download millions of application logs to isolate a five-minute authentication outage. What is the most significant cause of this behavior?
Explanation
Correct Answer
The situation indicates that unbounded manual log exports slow investigation and obscure meaningful event patterns. The recommended response is to query relevant Log Analytics data with scoped KQL filters on time, service and failure context, with a follow-up check that a targeted KQL query identifies failing requests and their associated operation IDs. This directly addresses the reported issue at the Birchhaven online ticketing service.
Incorrect Answers
Aggregate CPU and HTTP counts cannot reveal the slow step in a distributed request path. This can occur in other projects, but it is not the primary explanation at the Birchhaven online ticketing service.
This explanation belongs to application insights telemetry. The immediate weakness in the question is that unbounded manual log exports slow investigation and obscure meaningful event patterns. For the Birchhaven online ticketing service, the priority is to query relevant Log Analytics data with scoped KQL filters on time, service and failure context.
Although node-wide averages can hide individual container resource exhaustion, the situation does not describe that specific cause; it instead indicates that unbounded manual log exports slow investigation and obscure meaningful event patterns. For the Birchhaven online ticketing service, the priority is to query relevant Log Analytics data with scoped KQL filters on time, service and failure context.