How to investigate BigQuery query performance and slot usage?
You are a BigQuery admin supporting a team of data consumers who run ad hoc queries and downstream reporting in tools such as Looker. All data and users are combined under a single organizational project. You recently noticed some slowness in query results and want to troubleshoot where the slowdowns are occurring. You think that there might be some job queuing or slot contention occurring as users run jobs, which slows down access to results. You need to investigate the query job information and determine where performance is being affected. What should you do?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests the ability to distinguish between implementing a solution (like reservations) and performing a diagnostic investigation
To diagnose BigQuery slowness and identify slot contention, administrators should utilize administrative resource charts alongside INFORMATION_SCHEMA queries. The community consensus confirms that this combination provides the necessary visibility into job execution and resource allocation.
Selecting Option A is a common error because it suggests a remediation strategy (slot reservations) rather than fulfilling the specific requirement to investigate the root cause of the performance issue.
Community Discussion (5 comments)
- BigQuery provides administrative resource charts that show slot utilization and job performance, which can help identify patterns of heavy usage or contention. - Additionally, querying the INFORMATION_SCHEMA with the JOBS or JOBS_BY_PROJECT view can provide detailed information about specific queries, including execution time, slot usage, and whether they were queued.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C is the correct choice because the question explicitly asks to "investigate" and "determine where performance is being affected." Administrative resource charts provide a high-level view of slot utilization and job performance over time, while querying theINFORMATION_SCHEMA (specifically JOBS or JOBS_BY_PROJECT) allows for a deep dive into specific query metrics, such as execution time, slot milliseconds consumed, and whether a job was queued. This two-pronged approach directly addresses the need to pinpoint bottlenecks.Why the Other Options Are Wrong
Option A is incorrect because it proposes a configuration change (creating reservations) to solve the problem, rather than investigating the cause first. Option B involves Cloud Monitoring, which is useful for alerts but lacks the specific, detailed historical job analysis provided by the administrative charts andINFORMATION_SCHEMA for troubleshooting current slowness. Option D is irrelevant because it focuses on auditing access control changes via Cloud Logging, which has no bearing on query execution speed or slot contention.Community Comment Notes
Community members strongly validated Option C, emphasizing that BigQuery's administrative charts are the primary tool for visualizing slot usage patterns. Additionally, comments highlighted the utility ofINFORMATION_SCHEMA for retrieving detailed statistics on individual queries, which is essential for confirming if queuing is the source of the delay. Official Reference
Exam Strategy
Carefully distinguish between action verbs like 'investigate' or 'troubleshoot' versus 'implement' or 'configure'. For questions requiring investigation, prioritize diagnostic tools like system views and monitoring charts over configuration changes.