When designing a lakehouse to accommodate both real-time and batch processing workloads, which strategy ensures data is efficiently accessible across both without redundant storage or processing?

Real Exam

Adopt an event sourcing pattern, recording all changes as immutable events in the lakehouse, and creating materialized views for various workload needs.

22.4%

Use separate storage solutions for real-time and batch data, with periodic synchronization between them.

8.2%

Employ a single Delta Lake table that accommodates both streaming writes and batch reads/updates, organizing data by ingestion time.

61.2%

Store streaming data temporarily and batch load it into the lakehouse at predetermined intervals.

8.2%

Databricks Certified Data Engineer - Professional

Get started today

Comments

When designing a lakehouse to accommodate both real-time and batch processing workloads, which strategy ensures data is efficiently accessible across both without redundant storage or processing?