MENU
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?
Suggested Answer: D
Get Premium Associate Data Practitioner Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
EV
Evan
11 months ago
C is useful if you need more detailed insights.
CA
Catarina
11 months ago
Wait, you can query audit logs in BigQuery? That's new to me!
JA
Jacquelyne
11 months ago
B sounds a bit complicated for a quick fix.
LO
Louvenia
11 months ago
I think D is just as effective, though!
TI
Tiera
12 months ago
Option A is the quickest way to find the error details.
TA
Tamar
12 months ago
I vaguely recall something about exporting logs with gcloud, but it seems more complex than just checking the logs directly.
LA
Lavonda
1 year ago
I practiced a similar question where we had to analyze scheduled query failures. I feel like navigating to the Scheduled queries page could be the quickest option.
DE
Denise
1 year ago
I'm not entirely sure, but I think querying the information_schema might take longer since I would need admin access first.
KR
Kris
1 year ago
I remember we discussed using the Logs Explorer for troubleshooting in class. It seems like a straightforward way to find error details.
JO
Johnna
1 year ago
This is a tricky one. I'm tempted to go straight to the Scheduled queries page, but I'm not sure if that will give me all the information I need. Maybe I should try a few different approaches and see which one provides the most useful troubleshooting details.
TH
Thersa
1 year ago
Okay, I think the key here is to quickly identify the root cause of the failure. Querying the information_schema.jobs view with the failed job ID seems like the most direct way to get the error details I need.
MI
Micaela
1 year ago
Hmm, I'm not sure which option is the best approach here. I might try setting up a log sink to export the BigQuery audit logs, then querying those to identify the error. But I'm not totally confident that's the right solution.
AL
Alpha
1 year ago
This looks like a straightforward troubleshooting question. I'd start by navigating to the Logs Explorer page and using filters to find the failed job and analyze the error details.
CH
Chauncey
2 years ago
This exam question is like trying to find a needle in a haystack, but at least they're giving us some sharp tools to work with.
CE
Celeste
2 years ago
D) Navigate to the Scheduled queries page in the Google Cloud console. Select the failed job, and analyze the error details.
PH
Phung
2 years ago
C) Request access from your admin to the BigQuery information_schema. Query the jobs view with the failed job ID, and analyze error details.
MO
Mozelle
2 years ago
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.
ME
Melita
2 years ago
A) Navigate to the Logs Explorer page in Cloud Logging. Use filters to find the failed job, and analyze the error details.
RO
Rossana
2 years ago
B) Exporting the logs to BigQuery is a great idea! You can really dive deep into the issue that way.
MA
Marion
2 years ago
B) Exporting the logs to BigQuery is a great idea! You can really dive deep into the issue that way.
JO
Jody
2 years ago
A) Navigate to the Logs Explorer page in Cloud Logging. Use filters to find the failed job, and analyze the error details.
DO
Domingo
2 years ago
I prefer setting up a log sink using the gcloud CLI to export BigQuery audit logs. It might provide more detailed information about the error.
CY
Cyril
2 years ago
I agree with Jonell. Analyzing the error details there would help us troubleshoot the issue quickly.
JE
Jennifer
2 years ago
D) The Scheduled queries page in the console seems like the most intuitive option. I'd go with that for a quick fix.
MO
Mozell
2 years ago
I agree, option D) on the Scheduled queries page in the console seems like the quickest solution.
AN
An
2 years ago
I'm going to request access to the BigQuery information_schema and analyze the error details with option C).
GE
Gerry
2 years ago
I prefer option B) to export BigQuery audit logs and identify the error associated with the failed job ID.
CA
Caren
2 years ago
I think I'll go with option A) and check the Logs Explorer page for error details.
JO
Jonell
2 years ago
I think we should navigate to the Logs Explorer page in Cloud Logging to find the failed job.
PE
Pete
2 years ago
A) Seems like the fastest way to troubleshoot. I like how it lets you directly analyze the error details.
TE
Terrilyn
2 years ago
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.
LO
Lonna
2 years ago
A) Navigate to the Logs Explorer page in Cloud Logging. Use filters to find the failed job, and analyze the error details.
GA
Gayla
2 years ago
C) Accessing the information_schema seems like a more comprehensive approach. Though it might require admin approval, it could provide more detailed insights.