Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data analyst is conducting exploratory data analysis (EDA) on a new retail dataset in BigQuery. The analyst needs to understand the distribution of customer purchase amounts, calculate descriptive summary statistics (such as mean, min, max, and percentiles), and inspect potential outliers directly without leaving the Google Cloud console.
Which approach should the analyst use to accomplish this task?
This approach leverages BigQuery SQL aggregate functions and statistical functions—such as AVG(), MIN(), MAX(), and APPROX_QUANTILES()—combined with BigQuery console data visualization features (such as built-in Explore charts or Looker Studio integration) to conduct exploratory data analysis (EDA).
AVG, MIN, MAX, COUNT, STDDEV) provide essential measures of central tendency and spread across numeric columns.APPROX_QUANTILES(order_amount, 100) function divides numerical data into percentiles, allowing analysts to identify the median (50th percentile), interquartile ranges (25th and 75th percentiles), and extreme values.APPROX_QUANTILES() computes approximate percentiles efficiently over billions of rows with minimal compute overhead.Using built-in SQL statistical functions within BigQuery is the standard, native practice for exploratory data analysis in Google Cloud. It eliminates data egress costs, avoids unnecessary data transformations, and delivers fast, interactive insights on large-scale analytical datasets.
This option suggests running an open SELECT * query and attempting to analyze data distributions using Cloud Spanner Query Insights and system tables in SPANNER_SYS.
SELECT * on large analytical datasets scans full tables unnecessarily, incurring high query costs without calculating summary statistics.SPANNER_SYS.QUERY_STATS_* tables track query execution statistics, error counts, and database resource usage.The scenario asked how to troubleshoot slow execution times or investigate high CPU usage on a transactional Cloud Spanner database.
This option proposes using the EXPLAIN statement or viewing the Execution details / Query execution plan in BigQuery to evaluate numerical data values and summary distributions.
EXPLAIN plan and query execution graph show execution stages, compute worker allocation, input/output record counts, and slot time consumption, not the actual business data contents or column values.EXPLAIN does not compute descriptive metrics like averages, standard deviations, or quantiles for dataset attributes.The objective was to analyze the execution stages and performance bottlenecks of a slow-running BigQuery SQL query.
This option involves migrating BigQuery data into Cloud SQL for MySQL and using MySQL's Query Insights dashboard to perform exploratory data analysis.
The goal was to identify slow-running transactional queries or monitor active database connections in a MySQL database instance.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated