How to normalize BigQuery data with a no-code recurring job?
You have data located in BigQuery that is used to generate reports for your company. You have noticed some weekly executive report fields do not correspond to format according to company standards. For example, report errors include different telephone formats and different country code identifiers. This is a frequent issue, so you need to create a recurring job to normalize the data. You want a quick solution that requires no coding. What should you do?
Community Votes
81% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests your ability to match a 'no coding' requirement with a fully visual, code-free data transformation tool, while the common trap is choosing BigQuery scheduled queries because the data already resides in BigQuery.
For the Google Professional Data Engineer (PDE) exam, the correct answer is A: Use Cloud Data Fusion and Wrangler to normalize the data and schedule a recurring job. Community voting strongly favors A (81%), with many commenters citing Wrangler's no-code visual interface and scheduling capabilities.
The most common wrong answer is D: Use BigQuery and GoogleSQL to normalize the data and schedule recurring queries. This is tempting because the data is already in BigQuery and scheduled queries are simple, but SQL queries are still code, so it does not satisfy the explicit 'requires no coding' constraint.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Cloud Data Fusion Wrangler provides a no-code, visual interface for building data transformation pipelines. You can connect directly to BigQuery, use built-in transformations to normalize fields such as telephone numbers and country codes, and schedule the pipeline to run recurringly. Comment [1] reinforces this by stating "definitely A, cloud data fusion and wrangler to setup the clean up pipeline with no coding required," and comment [3] explains that Wrangler's no-code interface and Data Fusion's scheduling meet both requirements.Why the Other Options Are Wrong
B (Dataflow SQL) requires writing or configuring SQL and then manually scheduling the pipeline after the first run, which is more complex and not a no-code solution. C (Dataproc Serverless with Spark) requires Spark code, clearly violating the no-coding requirement. D (BigQuery with GoogleSQL) is a strong distractor because the data is already in BigQuery, but GoogleSQL transformations such as REGEXP_REPLACE are code, not no-code. Comment [2] argues for D, but comment [4] incorrectly calls SQL "no-code," which misses the exam's intended distinction.Community Comment Notes
The community overwhelmingly supports A, with 81% of votes and comments like [1], [3], [5], and [7]. Comment [5] provides the official Cloud Data Fusion documentation link, which is a reliable reference. A small minority (19%) chose D, often citing convenience since the data is already in BigQuery. However, the phrase "requires no coding" is the deciding factor, and Cloud Data Fusion Wrangler is the only option that is fully code-free and supports built-in recurring schedules.Official Reference
Exam Strategy
When the question emphasizes 'no coding,' immediately eliminate any option that requires SQL, Spark, or other programming languages. Cloud Data Fusion Wrangler is the only fully visual, no-code tool with native scheduling, so identify it even when the data is already in BigQuery.