Databricks-DE-Assoc Governance and Security Practice Question
An organization requires that all data access logs across multiple Databricks workspaces be captured and sent to a centralized security information and event management (SIEM) system. Which Databricks feature should be configured to capture these audit events?
⚠ Common exam trap
Candidates often confuse cluster logs or driver logs with audit logs, forgetting that compliance and security event tracking for SIEM ingestion require diagnostic log delivery configurations.
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
✓
Configure diagnostic log delivery to stream account and workspace audit logs to cloud storage or event hubs.
Databricks audit logs capture workspace-level and account-level user activities, including data access, administrative actions, and permission changes. Organizations configure audit log delivery to route these JSON event logs directly to cloud storage buckets, where SIEM tools like Splunk or Datadog can ingest and analyze them for compliance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable Spark event logs in the cluster configuration UI for every running compute cluster.
Why it's wrong here
Spark event logs record job, stage and task execution telemetry to storage; they capture no audit events such as workspace logins, cluster changes or permission edits, so nothing reaches the SIEM. They are tempting because they are per-cluster and easy to enable, and they would be correct for debugging Spark performance.
- ✓
Configure diagnostic log delivery to stream account and workspace audit logs to cloud storage or event hubs.
Why this is correct
Diagnostic log delivery streams account and workspace audit logs to cloud storage or event hubs, giving the centralised feed the SIEM requires. This directly satisfies the requirement to capture audit events across multiple workspaces into one security information and event management system.
- ✗
Run a nightly notebook that queries the system.information schema for active user sessions.
Why it's wrong here
The system.information schema exposes current session and query metadata only at query time; a nightly notebook misses everything between runs and captures no workspace-level audit events, so the SIEM feed is incomplete. It is tempting because it uses SQL already available, and it would suit ad hoc usage reporting, not continuous audit capture.
- ✗
Install a Python logging package on every cluster driver node to intercept SQL queries.
Why it's wrong here
A driver-side Python package intercepts only queries passing through that driver, missing API, login and workspace events, and it must be installed and maintained on every cluster. It is tempting because it is customisable, and it would be correct for application-level query logging, not centralised audit delivery.
About these practice questions
Courseiva writes every Databricks-DE-Assoc question from scratch — 276 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 Databricks exam blueprint
This Databricks-DE-Assoc 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-Assoc exam.