Databricks-DE-Pro Data Ingestion and Acquisition Practice Question
Which THREE of the following are essential components of an effective ingestion monitoring strategy in Databricks?
⚠ Common exam trap
Candidates often select generic infrastructure metrics like CPU usage or memory, missing that ingestion monitoring specifically requires data-level metrics like record processing rates and quality expectations.
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
✓
Tracking the 'numInputRows' metric in the streaming query progress.
Monitoring ingestion requires visibility into both infrastructure health and data quality. By tracking metrics like micro-batch latency, file processing rates, and record-level validation through expectations, you gain a holistic view of the pipeline. These components allow engineers to identify bottlenecks, respond to data quality drops, and ensure SLAs are met consistently, which is critical for maintaining reliable downstream analytics in a data lakehouse architecture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monitoring the total number of files in the cloud storage bucket.
Why it's wrong here
While having too many files can cause listing latency, it is not a direct metric of the ingestion pipeline's performance. Monitoring the ingestion process, such as processing rate (rows/sec) and batch duration, is far more useful for identifying issues than simply counting the files in the bucket.
- ✓
Tracking the 'numInputRows' metric in the streaming query progress.
Why this is correct
This metric tells you how many records are being processed in each micro-batch. It is essential for detecting data spikes, identifying potential ingestion lags, and verifying that the volume of data flowing through the pipeline aligns with the expected source throughput, which helps in capacity planning and performance tuning.
- ✓
Setting up alerts on failed expectations in DLT.
Why this is correct
Expectations are the primary mechanism for detecting bad data. If a pipeline is running but data is being dropped or failing quality checks, you need immediate notification. Alerting on these failures ensures that data quality issues are addressed before they propagate to Silver or Gold tables, maintaining overall pipeline integrity.
- ✓
Using DLT event logs to analyze pipeline execution details.
Why this is correct
The DLT event log is a comprehensive source of truth for the health, progress, and performance of your pipelines. It contains metadata about every update, failure, and quality check result. Analyzing this data is the industry standard for troubleshooting and auditing production data pipelines in Databricks environments.
- ✗
Regularly restarting the cluster to clear cache.
Why it's wrong here
Regularly restarting clusters is not a monitoring strategy; it is a disruptive maintenance task that incurs cold-start latency. Performance issues should be solved through optimization and proper configuration, not by blindly restarting compute resources. This approach does nothing to provide visibility into the health of your ingestion streams.
About these practice questions
One of 267 original Databricks-DE-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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 Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks 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 Databricks-DE-Pro exam.