PDE Maintaining and Automating Data Workloads Practice Question
You are setting up Dataplex data quality rules for a BigQuery table. You want to define rules that check for non-null values in key columns and also validate that a column's values fall within a certain range. Which TWO rule types must you use? (Choose 2)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Row rule (e.g., not null)
Dataplex data quality rules include row rules (for null checks) and column rules (for range or value checks). Table rules apply to the entire table; custom SQL can be used but row and column rules are the standard.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Table rule (e.g., row count)
Why it's wrong here
Table rules such as row count operate on whole-table metrics, not per-column null or range conditions. It is tempting because table-level checks are genuinely useful, and a table rule would be the correct choice when asserting that a dataset contains an expected number of rows or freshness.
- ✓
Row rule (e.g., not null)
Why this is correct
A row rule evaluates each record independently, so a not-null condition on key columns is expressed as a row-level rule. Range validation on a column's values is also row-scoped, checking every value against the defined bounds. Both satisfy the non-null and range checks required.
- ✗
Partition rule
Why it's wrong here
Partition rules govern how data is physically split across storage, not value validation. The stem needs a non-null rule and a range rule, which are distinct rule types. Partition rules would be chosen when defining how a table's data is segmented for query performance or cost, not for checking column contents.
- ✓
Column rule (e.g., value range)
Why this is correct
A column rule evaluates each value within a single column against a condition, so a range check on numeric values is defined here. It satisfies the range-validation requirement, since the constraint applies per-cell rather than across an entire row.
- ✗
Custom SQL rule
Why it's wrong here
Custom SQL rules express arbitrary queries, but non-null and range checks are covered by built-in rule types, so they are not the required pair. It is tempting because SQL offers full flexibility, and it would be the correct choice for validating cross-column logic that built-in rules cannot express.
About these practice questions
Courseiva writes every PDE question from scratch — 747 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PDE exam.