Fixing a broken or unreachable shortcut
OneLake shortcuts are virtual references that point to data stored in another location, either within OneLake or in external sources like ADLS Gen2, S3, or Dataverse. When a shortcut breaks or misbehaves, it's usually due to permission changes, deleted source data, expired credentials, or network/firewall configuration issues, and troubleshooting starts with the shortcut's status and target path validation.
Must-know
- A shortcut error often surfaces as a failure to browse, query, or list files under the shortcut node in the Lakehouse explorer, so first confirm the target path still exists at the source.
- For shortcuts to external sources (ADLS Gen2, S3-compatible storage, on-premises via gateway), the connection credentials or SAS token/key stored in the shortcut's connection must remain valid; expired or rotated credentials are a common cause of failures.
- Internal OneLake-to-OneLake shortcuts fail if the caller lacks read permissions on the source item (Lakehouse/Warehouse) or if the source item, workspace, or capacity has been deleted or moved.
- Shortcuts to external storage require correct network access; if the source storage account enforces firewall rules or private endpoints, OneLake's outbound IPs or the required trusted service/managed private endpoint must be allowed.
- Deleting a shortcut only removes the reference in OneLake and never deletes the underlying source data, so a broken shortcut can typically be safely removed and recreated once the underlying access issue is fixed.
- Renaming, moving, or deleting the source folder/table after a shortcut is created will break the shortcut, since shortcuts bind to a specific path and do not automatically follow renames.
A data engineer creates a shortcut in a Fabric lakehouse that points to a folder in an Azure Data Lake Storage Gen2 account. The connection was configured to authenticate using the organizational account of whoever queries the shortcut. A colleague with Viewer access to the workspace opens the shortcut and receives an access-denied error, even though the engineer can query the same shortcut without issue. What is the most likely cause?
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 12, 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.