Frequently Asked Questions
Do I need ACE before PDE?
There are no formal prerequisites. However, PDE assumes you understand GCP IAM, networking, and core services at an operational level. ACE builds that foundation. If you already have 1+ year of hands-on GCP experience, you can skip ACE and go straight to PDE.
How many practice questions should I aim for?
Aim for at least 600 unique questions across all domains, ensuring you prioritize quality over quantity. ExamOS provides over 2,000 high quality practice questions covering all domains and designed to explain the rationale behind both correct and incorrect answers.
When should I book the exam?
Once you are consistently hitting 80% or above on Legend mode across two or more sessions, and you feel comfortable explaining data engineering decisions for realistic GCP scenarios, you are ready. Trust your preparation.
How long is the exam?
120 minutes (2 hours) for 50-60 questions. That averages to roughly 2 minutes per question. Scenario-heavy questions may take longer, so keep an eye on the clock.
What languages is the exam available in?
English and Japanese only. This is more limited than most Microsoft and AWS exams. Google does not offer additional time accommodations for non-native speakers.
Can I use reference materials during the exam?
No. The PDE exam is closed-book. You cannot access documentation, websites, or any external resources during the test. All questions are designed to be answerable from your knowledge of GCP data services, architecture patterns, and best practices.
What is the most important domain to study?
Designing Data Processing Systems (~30%) is the heaviest domain. Combined with Building and Operationalizing (~25%), over half the exam is about designing and implementing data pipelines and storage systems. The biggest trap is over-studying ML and under-studying pipeline architecture and storage design.
What is the difference between Dataflow and Dataproc?
Dataflow is a fully managed streaming and batch processing service based on Apache Beam. It handles autoscaling, windowing, and exactly-once processing automatically. Dataproc is a managed Spark and Hadoop service for batch processing, ETL, and legacy workloads. The exam tests whether you know when each is the right choice: Dataflow for streaming and unified batch/streaming, Dataproc for Spark-native workloads and migration from on-premises Hadoop.
What are the most common ways people fail?
- Not knowing BigQuery table design. Partitioning, clustering, and the difference between partitioned and clustered tables are tested constantly. Knowing when to use each and how they affect query cost and performance is essential.
- Confusing Dataflow windowing strategies. Fixed, sliding, session, and global windows each serve different use cases. The exam tests whether you can match a business requirement (e.g., "aggregate per user session") to the right windowing strategy.
- Underestimating Dataplex. It is a newer service but it covers data quality, governance, lineage, and metadata discovery. Questions on data quality scans and Dataplex zones appear regularly.
- Confusing BigQuery loading methods. Batch load, legacy streaming inserts, and Storage Write API have different characteristics around latency, cost, and exactly-once semantics. Know when to use each.
- Ignoring security at the column and row level. Column-level security, row access policies, and authorized views are all tested. Candidates who only know dataset-level IAM miss these questions.
- Not understanding BQML vs Vertex AI. BQML is for simple models trained directly in BigQuery. Vertex AI is for custom training, deployment, and serving at scale. Know the boundary between them.
What are the three biggest preparation mistakes?
- Studying services without studying architecture patterns. PDE tests how services work together, not in isolation. Knowing BigQuery and Dataflow individually is not enough. You need to understand how Pub/Sub, Dataflow, BigQuery, and Cloud Monitoring connect into a production pipeline.
- Not writing BigQuery SQL or Beam code. The exam tests whether you understand how these services actually work. Reading about MERGE statements is different from writing one that handles NULLs and duplicates correctly. Code practice builds the understanding that the exam tests.
- Skipping the selection framework. Many questions give you four plausible services and ask you to pick the best one. If you do not have a decision framework (latency, cost, data volume, consistency requirements), you will second-guess yourself on every question.
Is there a renewal option?
Yes. PDE is valid for 2 years. To renew, retake the current version of the exam. Check the Google Cloud certification portal for the most current renewal options.
Quick-Reference: What Is on the Exam
For the full, always-current list, visit the official PDE exam guide.
| Domain |
Key Skills |
| Designing Data Processing Systems (~30%) |
Storage service selection (BigQuery, Bigtable, Cloud Storage, Cloud Spanner, AlloyDB), BigQuery table design (partitioning, clustering, external tables, BigLake), pipeline architecture (batch, streaming, hybrid, lambda vs kappa), Pub/Sub design (ordering keys, retention, dead-letter topics), event-driven architecture (Eventarc, Cloud Functions), pipeline orchestration (Cloud Composer, Cloud Scheduler, Eventarc), data migration (Database Migration Service, Storage Transfer Service, Datastream CDC) |
| Building and Operationalizing Data Processing Systems (~25%) |
Apache Beam programming model (PCollections, DoFn, GroupByKey), Dataflow windowing (fixed, sliding, session, global) and triggers and watermarks, Dataflow templates (flex templates, classic templates) and autoscaling, Dataproc (standard clusters, ephemeral, serverless, Spark jobs), BigQuery loading (batch load, Storage Write API, streaming inserts), BigQuery DML (MERGE, CTAS, stored procedures), Cloud Composer DAG design and GCP operators |
| Operationalizing Machine Learning Models (~20%) |
BigQuery ML (CREATE MODEL, ML.EVALUATE, ML.PREDICT), Vertex AI (model training, deployment, endpoints), Vertex AI Feature Store (online vs offline serving), Vertex AI Pipelines vs Cloud Composer, model monitoring (prediction drift, feature skew), ML integration patterns in data pipelines |
| Ensuring Solution Quality (~15%) |
Dataplex (lakes, zones, assets, metadata discovery), Dataplex data quality rules (completeness, uniqueness, validity, referential integrity), data lineage and data catalog, data validation in pipelines (schema validation, quarantine patterns), pipeline testing (unit testing with DirectRunner, integration testing), performance optimization (BigQuery EXPLAIN, materialized views, BI Engine), BigQuery reservations and slot management |
| Managing Data Security and Compliance (~10%) |
BigQuery access control (dataset IAM, table IAM, column-level security, row access policies, authorized views), Cloud DLP (inspection jobs, de-identification: masking, tokenization, FPE, pseudonymization), CMEK for BigQuery and Cloud Storage (key rotation), VPC Service Controls (service perimeters, dry-run mode, access levels), audit logging (BigQuery Data Access logs), compliance patterns (HIPAA, PCI-DSS, GDPR data residency) |