This post is a part of the DP-700: Implementing Data Engineering Solutions Using Microsoft Fabric Exam Prep Hub.
This topic falls under these sections:
Ingest and transform data (30–35%)
   --> Ingest and transform streaming data
      --> Choose between native tables and OneLake shortcuts in Real-Time Intelligence

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

One of the key design decisions when building real-time analytics solutions in Microsoft Fabric is determining where data should reside and how it should be accessed. Within Real-Time Intelligence, data engineers frequently encounter scenarios where they must choose between:

• Native Tables in Eventhouse/KQL databases
• OneLake Shortcuts to data stored elsewhere

Understanding the differences between these approaches is important for the DP-700 exam because the choice impacts:

• Query performance
• Data latency
• Storage costs
• Data governance
• Data duplication
• Maintenance complexity

A successful data engineer must understand when to ingest data directly into Real-Time Intelligence and when to reference existing data through shortcuts.

Understanding Real-Time Intelligence

Real-Time Intelligence is Microsoft Fabric’s solution for ingesting, analyzing, and acting upon streaming and operational data.

Key components include:

• Eventstream
• Eventhouse
• KQL Databases
• Data Activator
• Real-Time Dashboards

Data stored within Eventhouse and KQL databases can come from multiple sources:

• Direct streaming ingestion
• Batch ingestion
• External storage systems
• OneLake data sources

This is where the choice between native tables and OneLake shortcuts becomes important.

What Are Native Tables?

Native tables are physical tables stored directly inside a KQL database or Eventhouse.

When data is ingested into Real-Time Intelligence, it is written into these tables and becomes part of the Eventhouse storage engine.

Characteristics of Native Tables

Native tables:

• Physically store data
• Support extremely fast query performance
• Are optimized for time-series analytics
• Support continuous streaming ingestion
• Provide low-latency access
• Support update policies and materialized views
• Enable advanced KQL analytics

Native Table Architecture

Event Source
      ↓
Eventstream
      ↓
Native Table
      ↓
KQL Queries
      ↓
Dashboards / Analytics

Data resides directly within the Eventhouse environment.

Advantages of Native Tables

Highest Query Performance

Because data is physically stored in the Eventhouse engine, query execution is highly optimized.

Benefits include:

• Faster aggregations
• Faster filtering
• Lower latency
• Better concurrency

Optimized for Streaming Workloads

Native tables are specifically designed for:

• High ingestion rates
• Continuous event streams
• Telemetry data
• Operational analytics

Support for Advanced Features

Native tables support:

• Materialized views
• Update policies
• Data retention policies
• Cached query execution
• Time-series functions

Lower Query Latency

Real-time dashboards often require results within seconds.

Native tables generally provide the lowest latency.

Disadvantages of Native Tables

Data Duplication

The same data may already exist elsewhere:

• Lakehouse
• Warehouse
• ADLS Gen2
• Other databases

Ingesting into native tables creates another copy.

Increased Storage Costs

More copies of data mean:

• More storage consumption
• Additional retention management

Additional Ingestion Processing

Data must be:

• Moved
• Loaded
• Managed

before it becomes available.

What Are OneLake Shortcuts?

A OneLake shortcut provides a virtual reference to data stored elsewhere.

Rather than copying data into Eventhouse, Real-Time Intelligence accesses the existing data through the shortcut.

Shortcut Concept

Instead of:

Source → Copy → Eventhouse

You get:

Source → OneLake Shortcut → Query

No physical duplication occurs.

Supported Sources

Shortcuts can reference:

• Fabric Lakehouses
• Fabric Warehouses
• Azure Data Lake Storage Gen2
• Amazon S3
• Other supported storage locations

Characteristics of OneLake Shortcuts

Shortcuts:

• Avoid copying data
• Provide a single source of truth
• Reduce storage costs
• Simplify governance
• Enable data reuse

Advantages of OneLake Shortcuts

Eliminate Data Duplication

One of the biggest advantages.

Instead of storing multiple copies:

One Source
    ↓
Multiple Consumers

All consumers access the same data.

Lower Storage Costs

Since data is not duplicated:

• Less storage consumption
• Lower management overhead

Faster Data Availability

No ingestion process is required.

Data becomes accessible immediately after the shortcut is created.

Improved Governance

Governance becomes easier because:

• Data remains in one location
• Policies remain centralized
• Data lineage remains clearer

Supports the One Copy Vision

OneLake is built around the principle of:

“One copy of data for the entire organization.”

Shortcuts are a key enabler of this strategy.

Disadvantages of OneLake Shortcuts

Potentially Higher Query Latency

Because data is not stored locally:

• Queries may require additional access steps
• Performance can be slower than native tables

Limited Optimization

Some advanced Eventhouse optimization capabilities are most effective with native data.

Examples include:

• Materialized views
• Update policies
• Streaming ingestion optimizations

Dependency on Source Availability

If the source becomes unavailable:

• Queries may fail
• Performance may degrade

Native tables do not have this dependency.

When to Choose Native Tables

Choose native tables when:

Real-Time Performance Is Critical

Examples:

• Monitoring dashboards
• Security analytics
• Fraud detection
• Manufacturing telemetry

Continuous Streaming Ingestion Exists

Examples:

• IoT sensors
• Application logs
• Device telemetry

High Query Volumes Are Expected

Examples:

• Enterprise dashboards
• Operational reporting

Advanced KQL Features Are Required

Examples:

• Materialized views
• Update policies
• Retention policies

When to Choose OneLake Shortcuts

Choose shortcuts when:

Data Already Exists in OneLake

Avoid creating unnecessary copies.

Storage Costs Must Be Minimized

Shortcuts reduce storage requirements.

Data Sharing Is Important

Multiple teams can access the same dataset.

Data Is Primarily Historical

Examples:

• Historical archives
• Reference datasets
• Slowly changing datasets

Governance Is a Priority

Maintaining a single source of truth simplifies compliance and governance efforts.

Comparing Native Tables and OneLake Shortcuts

Common DP-700 Exam Scenarios

Scenario 1

A manufacturing company ingests millions of telemetry events every minute and requires dashboards that refresh within seconds.

Best Choice: Native Tables

Reason:

• Maximum ingestion performance
• Lowest query latency

Scenario 2

An organization already stores enterprise sales data in a Fabric Lakehouse and wants Eventhouse users to analyze it without creating another copy.

Best Choice: OneLake Shortcut

Reason:

• Eliminates duplication
• Supports centralized governance

Scenario 3

A security operations center performs continuous threat monitoring using KQL.

Best Choice: Native Tables

Reason:

• Optimized for streaming analytics
• Fast query response times

Scenario 4

A data engineering team needs occasional access to historical archive data stored in ADLS Gen2.

Best Choice: OneLake Shortcut

Reason:

• No need to ingest large historical datasets
• Lower storage costs

Decision Framework

Ask the following questions:

Is the data arriving continuously?

If yes → Native Tables.

Is ultra-low latency required?

If yes → Native Tables.

Does the data already exist in OneLake?

If yes → Consider OneLake Shortcuts.

Is avoiding duplication important?

If yes → OneLake Shortcuts.

Are advanced KQL optimization features required?

If yes → Native Tables.

DP-700 Exam Tips

Remember these key distinctions:

• Native tables physically store data inside Eventhouse.
• Native tables provide the highest performance.
• Native tables are ideal for streaming ingestion.
• OneLake shortcuts reference data without copying it.
• Shortcuts support the One Copy vision of OneLake.
• Shortcuts reduce storage costs.
• Native tables are preferred when low-latency analytics is critical.
• Shortcuts are preferred when data already exists elsewhere and duplication should be avoided.
• Exam questions often focus on balancing performance versus storage and governance.

Practice Exam Questions

Question 1

A company requires sub-second analytics on continuously arriving IoT telemetry data in Eventhouse.

Which storage approach should be selected?

A. OneLake shortcut to a Lakehouse
B. OneLake shortcut to ADLS Gen2
C. Native table
D. Dataflow Gen2

Answer: C

Explanation:
Native tables provide the lowest latency and are optimized for continuous streaming ingestion and real-time analytics.

Question 2

An organization already stores customer history in a Fabric Lakehouse and wants Eventhouse users to analyze the data without creating additional copies.

Which option should be used?

A. Native table
B. OneLake shortcut
C. Eventstream ingestion
D. Data Activator

Answer: B

Explanation:
OneLake shortcuts allow access to existing data without physically copying it into Eventhouse.

Question 3

What is the primary advantage of using OneLake shortcuts?

A. Faster ingestion speeds
B. Automatic materialized views
C. Lower query latency
D. Elimination of data duplication

Answer: D

Explanation:
Shortcuts provide virtual access to data and eliminate the need to create additional copies.

Question 4

Which feature is most strongly associated with native tables?

A. Single source of truth
B. External data access
C. Physical storage within Eventhouse
D. Reduced storage costs

Answer: C

Explanation:
Native tables physically store data within Eventhouse and are optimized for real-time analytics.

Question 5

A team wants to minimize storage costs while analyzing historical datasets already stored in OneLake.

Which option is best?

A. Native tables
B. OneLake shortcuts
C. Spark cache tables
D. Temporary KQL tables

Answer: B

Explanation:
Shortcuts allow direct access to existing data without storing another copy.

Question 6

Which scenario most strongly favors native tables?

A. Historical archive access
B. Shared enterprise data reuse
C. High-volume streaming telemetry analytics
D. Storage cost reduction

Answer: C

Explanation:
Native tables are designed for continuous ingestion and high-performance real-time analytics.

Question 7

A data engineer wants to support the OneLake principle of maintaining a single copy of organizational data.

Which option best aligns with this goal?

A. Native tables
B. Materialized views
C. Streaming ingestion
D. OneLake shortcuts

Answer: D

Explanation:
Shortcuts are specifically designed to support OneLake’s single-copy architecture.

Question 8

Which statement about native tables is true?

A. They never store data physically.
B. They generally provide better query performance than shortcuts.
C. They require external storage systems.
D. They cannot be queried with KQL.

Answer: B

Explanation:
Because the data is stored directly inside Eventhouse, native tables typically deliver the highest performance.

Question 9

A company wants to use advanced KQL features such as update policies and materialized views on streaming data.

Which approach should be selected?

A. OneLake shortcut
B. Warehouse shortcut
C. Native table
D. Dataflow Gen2

Answer: C

Explanation:
Advanced Eventhouse optimization features are most commonly associated with native tables.

Question 10

Which factor most commonly drives the decision to use a OneLake shortcut instead of a native table?

A. Requirement for lowest latency analytics
B. Requirement for continuous event ingestion
C. Requirement for materialized views
D. Requirement to avoid storing duplicate copies of data

Answer: D

Explanation:
The primary benefit of OneLake shortcuts is enabling data access without physically duplicating data, reducing storage costs and simplifying governance.

Go to the DP-700 Exam Prep Hub main page.