Your organization uses scheduled queries to perform transformations on data stored in BigQuery. You discover that one of your scheduled queries has failed. You need to troubleshoot the issue as quickly as possible. What should you do?
A.
Navigate to the Logs Explorer page in Cloud Logging. Use filters to find the failed job, and analyze the error details.
B.
Set up a log sink using the gcloud CLI to export BigQuery audit logs to BigQuery. Query those logs to identify the error associated with the failed job ID.
C.
Request access from your admin to the BigQuery information_schema. Query the jobs view with the failed job ID, and analyze error details.
D.
Navigate to the Scheduled queries page in the Google Cloud console. Select the failed job, and analyze the error details.
The best option is D. Scheduled queries page. Option D is best because it's the direct console page for scheduled query errors. Option A (Logs Explorer) is incorrect because it's less direct than the dedicated page. Option B (Log sink) is incorrect because it's for future logs, not immediate troubleshooting, and too complex. Option C (INFORMATION_SCHEMA) is incorrect because console page is faster and easier than SQL queries for most users. Therefore, Option D, Scheduled queries page, is the quickest troubleshooting method.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
n2183712847
1 month, 4 weeks ago