Weighing an accelerated shortcut against a standard one for query speed
In Real-Time Intelligence, OneLake shortcuts let a KQL database reference Delta tables in OneLake without copying data, but querying that data directly can be slow because it isn't stored in the KQL engine's native indexed format. Query acceleration for OneLake shortcuts builds and maintains a cached, indexed copy of the shortcut data behind the scenes, giving near-native KQL query performance at the cost of extra storage and a caching delay. Choosing between them is a trade-off between query speed/complexity versus storage cost and data freshness requirements.
Must-know
- Standard OneLake shortcuts read source Delta/Parquet files on demand, so queries run without extra storage cost but with lower performance for complex, high-cardinality, or frequent analytical queries.
- Query acceleration adds a background caching/indexing process that transforms shortcut data into the KQL engine's optimized storage format, improving query speed similar to native ingested tables.
- Because acceleration runs asynchronously, there is a lag between new data landing in the source and it becoming available in the accelerated cache, so very fresh data may briefly be served from the unaccelerated path.
- Enabling query acceleration incurs additional storage consumption in the Fabric capacity since it maintains a cached copy alongside the original OneLake data.
- Choose standard shortcuts when data volume/query frequency is low, near-real-time freshness is critical, or minimizing storage cost matters; choose query acceleration for large datasets with frequent, complex, or performance-sensitive analytical queries.
- Query acceleration is configured per shortcut (not automatically applied to all shortcuts), so it must be explicitly enabled where performance gains are needed.
After enabling query acceleration on a OneLake shortcut in an Eventhouse, an engineer notices that queries return slightly outdated results compared to the latest rows just written to the source Lakehouse table. Which explanation correctly accounts for this behavior?
What you have tried across DP-700's objectives, not a readiness score.
Implement and manage an analytics solution
- Tuning a workspace's Spark compute defaults and pool sizing
- Grouping and governing workspaces with a Fabric domain
- Setting per-workspace defaults for OneLake storage
- Standing up an Airflow job runtime inside a workspace
- Connecting a workspace to a Git repository
- Managing schema changes with a database project
- Promoting Fabric items across environments with a deployment pipeline
- Granting and restricting access at the workspace level
- Locking down who can open a single Fabric item
- Layering row, column, object, and file-level security rules
- Hiding sensitive column values behind a dynamic mask
- Classifying Fabric items with a sensitivity label
- Marking a trusted item as promoted or certified
- Reading a Fabric audit log to see who did what
- Securing data at the OneLake storage layer
- Picking the right build tool among a dataflow, a pipeline, and a notebook
- Kicking off a job on a schedule or in response to an event
- Chaining notebooks and pipelines together with parameters and dynamic expressions
Ingest and transform data
- Deciding between a full reload and an incremental load
- Shaping source data ahead of a dimensional-model load
- Landing a continuous stream of data into storage
- Matching a workload to the right Fabric data store
- Picking a transformation tool from dataflows, notebooks, KQL, or T-SQL
- Linking to external data without copying it via a OneLake shortcut
- Keeping a source database continuously replicated into Fabric
- Moving data into Fabric with a data pipeline
- Writing transform logic in PySpark, SQL, or KQL
- Flattening related tables into one wide, denormalized shape
- Rolling records up with group-by aggregations
- Dealing with duplicate rows, gaps, and data that arrives late
- Selecting the right engine for a real-time workload
- Weighing storage-in-place against a linked shortcut for a Real-Time Intelligence table
- Weighing an accelerated shortcut against a standard one for query speed
- Routing and reshaping live events with an Eventstream
- Handling a continuous flow of records with Spark's structured streaming
- Querying and reshaping event data with KQL
- Aggregating a stream over sliding or tumbling time windows
Monitor and optimize an analytics solution
- Watching an ingestion job's health and progress
- Watching a transformation job's health and progress
- Tracking whether a semantic model's refresh actually succeeded
- Setting up an alert to catch a failure early
- Tracking down why a pipeline run failed and fixing it
- Diagnosing why a dataflow run failed
- Debugging a notebook run that failed
- Troubleshooting a misbehaving Eventhouse
- Troubleshooting a misbehaving Eventstream
- Debugging a T-SQL statement that failed
- Fixing a broken or unreachable shortcut
- Speeding up a Lakehouse table with maintenance operations
- Making a slow pipeline run faster
- Tuning a Fabric warehouse for faster queries
- Improving throughput on real-time streaming components
- Tuning a Spark job to run faster and cheaper
- Making a slow query run faster
Coverage checked against the published exam guide on Aug 11, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.