PDE Designing Data Processing Systems Practice Question
A company wants to use Dataproc Metastore to manage metadata for their Spark jobs. Which TWO benefits does Dataproc Metastore provide?
⚠ Common exam trap
PDE often tests the distinction between Dataproc (compute) features like autoscaling and Dataproc Metastore (metadata) features like HA and managed Hive metastore, causing candidates to pick compute-related options.
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
✓
High availability with automatic failover
Option B is correct because Dataproc Metastore is a highly available, fully managed service that provides automatic failover across zones, ensuring metadata remains accessible even if a zone fails. Option C is correct because Dataproc Metastore is essentially a fully managed, serverless implementation of the Hive Metastore (HMS), which Spark and other engines use to store and retrieve metadata such as table schemas and partitions. Option A is incorrect because automatic scaling of compute resources is a feature of Dataproc clusters or autoscaling policies, not of the metadata service itself. Option D is incorrect because Dataproc Metastore does not provide native BigQuery integration; it serves Hive/Spark-style metadata via the Hive Metastore Thrift protocol. Option E is incorrect because data lineage tracking is provided by tools like Data Catalog or Dataplex, not by Dataproc Metastore.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Automatic scaling of compute resources
Why it's wrong here
Dataproc Metastore stores and serves metadata; scaling of Spark cluster compute is handled by Dataproc itself, not by the metastore service. It tempts because both are managed Dataproc-family offerings, and it would be correct if the requirement were elastic worker capacity for fluctuating job workloads.
- ✓
High availability with automatic failover
Why this is correct
Dataproc Metastore is a fully managed, highly available service that replicates metadata across zones and performs automatic failover without administrative intervention. This satisfies the stem's requirement for a managed metadata service for Spark jobs, eliminating the single point of failure inherent in a self-managed Hive Metastore deployment.
- ✓
Fully managed Hive metastore service
Why this is correct
Dataproc Metastore delivers a fully managed Hive metastore, removing the need to run and patch your own metastore on Compute Engine. This satisfies the stem's requirement for managed metadata serving Spark jobs, since Spark reads and writes Hive-compatible table definitions through the Thrift metastore endpoint without infrastructure upkeep.
- ✗
Integration with BigQuery
Why it's wrong here
Dataproc Metastore exposes a Hive Metastore Thrift endpoint for engines such as Spark and Hive; BigQuery uses its own Dataplex Universal Catalog metadata, so no direct integration exists. It tempts because both sit in the Google Cloud data estate, and it would be correct if the requirement were querying BigQuery tables.
- ✗
Built-in data lineage tracking
Why it's wrong here
Dataproc Metastore is a managed Hive Metastore service holding table and partition definitions; lineage is captured separately by Dataplex or Data Catalog. It tempts because metadata management sounds like lineage, and it would be correct if the requirement were tracing column-level data movement across pipelines.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
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.