Reinforce DP-700 concepts with active-recall study cards covering all 3 blueprint domains. Each card shows the question on the front and the correct answer with a full explanation on the back.
Flashcards work through active recall — the process of retrieving information from memory rather than passively re-reading it. Research consistently shows that active recall produces stronger, longer-lasting memory than re-reading study guides. For DP-700 preparation, this means flashcards are one of the highest-return study tools available.
Attempt recall first
Read the DP-700 question on each card, pause, and attempt to formulate the answer in your own words before revealing. This retrieval attempt — even if wrong — dramatically strengthens memory compared to immediately reading the answer.
Review wrong cards again
When you get a card wrong, note it and add it back to your review pile. Spaced repetition — seeing difficult cards more frequently — is the mechanism that makes flashcard study far more efficient than linear reading.
Study by domain
Group your DP-700 flashcard sessions by domain for the first 3–4 weeks. Master one domain before moving to the next. In the final week, shuffle all cards together to test cross-domain recall — which is what the real DP-700 exam requires.
Short sessions beat marathon reviews
20–30 flashcard cards per session, done daily, produces better retention than a single 200-card marathon session. Five short daily sessions per week over 4 weeks gives you over 400 total card reviews — enough to reliably pass DP-700.
Sample cards from the DP-700 flashcard bank. Read the question, think of the answer, then read the explanation below.
You are monitoring a Microsoft Fabric Lakehouse. You notice that queries against a specific Delta table are performing slowly despite the table having a small data size. You need to identify the root cause of the performance degradation. What should you examine first?
The total number of files within the table directory.
In a Microsoft Fabric Lakehouse, Delta tables store data as Parquet files in a directory, and query performance is heavily influenced by file count rather than total data size. A small table fragmented into thousands of tiny files causes excessive metadata overhead, poor parallelism, and slow file listing during query planning. Examining the number of files in the table directory is the fastest way to confirm this 'small files problem.'
You are designing a Fabric pipeline to copy data from an on-premises SQL Server to a OneLake Lakehouse. Which integration runtime configuration ensures the highest throughput for large datasets?
Configure a Self-hosted Integration Runtime and enable the Staged Copy feature using an Azure Blob storage account.
Staged Copy with a Self-hosted Integration Runtime is the highest-throughput configuration for on-premises SQL Server to OneLake Lakehouse. The SHIR handles the on-premises source read, and Staged Copy uses an Azure Blob staging account to decouple the source read from the sink write, allowing the Copy Activity to use the Azure IR's full parallelism and DIU capacity for the write to OneLake. Without staging, the SHIR must both read from on-premises and write directly to OneLake, which bottlenecks on the SHIR's network and CPU.
Your organization uses Microsoft Fabric with three distinct workspaces for Development, Test, and Production. You need to automate the movement of a Lakehouse and its associated semantic model through these environments while ensuring that the Production environment uses a different data source connection string than the Development environment. Which feature should you implement?
Deployment Pipelines with Deployment Rules
Deployment Pipelines with Deployment Rules is the Fabric feature designed to automate promotion of items (Lakehouse, semantic model) across Development, Test, and Production workspaces while allowing environment-specific overrides such as a different data source connection string via data source rules. This directly satisfies the requirement for automated movement and per-stage connection strings.
Your team runs a Microsoft Fabric Data Pipeline that loads a Lakehouse Gold layer each night. The pipeline occasionally fails, and when it does, downstream reports show stale data for the whole day. You need the pipeline to automatically retry the failed activity a few times before alerting, and you need an audit trail of each retry attempt. Which configuration should you apply?
Set the activity's retry policy with an interval and count, and rely on the Monitoring hub run history for the attempts.
The activity-level retry policy is the native mechanism for bounded, interval-based reattempts, and every attempt it makes is captured in the run history surfaced by the Monitoring hub. Using it satisfies the automatic retry need and produces the per-attempt audit record. Loop-based or dependency-based workarounds add complexity and record attempts in forms that are harder to audit.
A Data Factory pipeline in Fabric fails during the execution of a Copy activity. You need to find the specific error message and the number of rows successfully written before the failure. Where should you look?
The pipeline run details in the Monitoring Hub
The pipeline run details in the Monitoring Hub provide a comprehensive view of each activity's execution, including error messages and metrics such as rows written. For a Copy activity failure, you can drill into the activity run to see the exact error and the number of rows successfully copied before the failure.
Refer to the exhibit. You are attempting to publish a Dataflow Gen2 that loads data into a Fabric Warehouse. Based on the error message, what action must you take to successfully publish the dataflow?
Enable the 'Staging' option for the dataflow queries.
Enabling the 'Staging' option for the dataflow queries is correct because Dataflow Gen2 requires staging when loading data into a Fabric Warehouse, as the error message indicates. Staging enables the dataflow to write intermediate data to a Lakehouse before loading into the Warehouse, which is necessary for certain transformations and destinations.
When a Spark notebook job finishes, what is the best practice for managing the underlying compute cluster resources?
Configure automatic termination for idle sessions
Configuring automatic termination for idle sessions ensures the Spark cluster shuts down when the notebook job finishes and no activity remains, preventing unnecessary compute charges. This is the standard cost-management best practice in Fabric for ephemeral notebook workloads.
A company is using Git integration in Microsoft Fabric to manage their Lakehouse and Report items. They notice that after a developer committed changes to a branch and synced them to the workspace, certain sensitive metadata files are being tracked in the repository. Which file should be modified in the local Git repository to prevent specific Fabric item metadata from being tracked in the future?
.gitignore
The .gitignore file in the local Git repository tells Git which files and patterns to exclude from tracking. Adding the specific Fabric item metadata files (or patterns) to .gitignore prevents them from being staged and committed going forward. This is the standard Git mechanism for excluding sensitive or unwanted files from version control.
An organization is using the 'Fabric Capacity Metrics' app to monitor their F64 capacity. They see a high 'Background rejection' rate. What does this indicator typically mean for the analytics solution?
Scheduled jobs and refreshes are being throttled due to capacity exhaustion.
A high 'Background rejection' rate in the Fabric Capacity Metrics app indicates that background jobs, such as scheduled refreshes and data pipelines, are being rejected or throttled because the capacity has exceeded its available resources. This means the analytics solution is experiencing performance issues due to capacity exhaustion, and users may see delays or failures in data refreshes.
You have a Fabric pipeline that runs a notebook. The notebook takes longer to start each time. What is the most likely cause?
The Spark session initialization is delayed.
In Microsoft Fabric, notebooks run on Spark sessions that must be initialized before execution. Each time a notebook runs, if the Spark session is not reused (e.g., due to session timeout or configuration), the initialization process—including cluster provisioning and library loading—adds startup latency. The most likely cause of increasing startup time is delayed Spark session initialization, which can be exacerbated by cold starts or resource contention.
You are designing a Microsoft Fabric solution that uses a Lakehouse to store Delta tables. A data engineer needs to update specific rows in a large Delta table based on a condition. The table is partitioned by date and contains billions of records. You need to minimize the amount of data rewritten during the update. What should you use?
Execute an UPDATE statement using Spark SQL with a WHERE clause on the partition column.
Delta Lake UPDATE statements with a WHERE clause on the partition column enable partition pruning, so only the relevant partitions are rewritten. This is the most efficient way to update specific rows in a large partitioned table. Other options either rewrite the entire table or do not guarantee partition-level filtering, leading to excessive data processing.
You manage a Microsoft Fabric workspace that contains a Data Pipeline which loads data into a Lakehouse every night. The pipeline occasionally fails with a timeout error during the Copy activity. You need to identify the root cause of the failure by reviewing the detailed execution logs and the duration of each activity. Which built-in Fabric feature should you use?
Monitor hub
The Monitor hub is the central place in Microsoft Fabric to view and troubleshoot pipeline runs. It shows each activity's status, duration, and error details, enabling you to pinpoint the timeout. Other tools focus on capacity, Spark, or external SQL Server, and do not offer the required pipeline-level diagnostics.
You are a data engineer in a Microsoft Fabric environment. You need to create a solution that allows business analysts to query data using T-SQL and also supports multi-table transactions. Which Fabric item should you use?
Warehouse
The Warehouse in Microsoft Fabric is the only item that natively supports T-SQL for both querying and data manipulation, including multi-table transactions. It is optimized for relational analytics and provides ACID compliance, which is essential for the business analysts' needs. Other items like Lakehouse and Notebook do not offer the same transactional T-SQL capabilities.
You are designing a data lakehouse architecture. Which file format is recommended for optimal performance in Fabric?
Delta Lake
Delta Lake is the recommended format in Microsoft Fabric because it provides ACID transactions, time travel, schema enforcement, and efficient upserts on top of Parquet files in OneLake. Fabric's Lakehouse, Warehouse, and Spark engines are all optimised for Delta, making it the native table format for the platform.
You are using a Fabric Data Factory pipeline to copy semi-structured JSON files from an Azure Data Lake Storage Gen2 account into a Fabric Lakehouse. The JSON files contain nested arrays, and the business needs each element of those arrays flattened into its own row in the destination table. The pipeline must run unattended and produce a Delta table. Which approach should you use?
Use a Dataflow Gen2 that reads the JSON, expands the nested array with the Expand structured column operation, and writes the result to the Lakehouse.
Flattening variable-length nested arrays into individual rows requires a transformation engine that can expand arrays, not a mapping that assigns array positions to columns. Dataflow Gen2's Expand operation on a structured column produces one row per element and can write directly to a Lakehouse Delta table, satisfying the unattended, relational output requirement.
You are monitoring a Spark notebook in Microsoft Fabric that is taking longer than expected to process a large dataset. You notice that a single executor is processing significantly more data than others. Which tool or feature should you use to identify the specific partition causing this data skew?
The Spark Advisor and Spark UI
The Spark Advisor and Spark UI provide detailed insights into Spark job execution, including stage and task-level metrics. The Spark UI shows task distribution and can highlight skew by revealing tasks that process significantly more data than others. Spark Advisor automatically detects skew and provides recommendations.
You have a Microsoft Fabric Data Warehouse that contains a large fact table. Users run many ad-hoc queries that filter on different columns. You notice that query performance is inconsistent and sometimes slow. You want to improve query performance by reducing the amount of data scanned. What should you do?
Partition the fact table by a commonly filtered column, such as date.
Partitioning the fact table on a commonly filtered column allows the Data Warehouse to skip partitions that do not match query predicates, significantly reducing the data scanned. This improves performance for ad-hoc queries that filter on that column. Other options like materialized views or caching are less effective for varied filters, and scaling up capacity does not address the underlying data scan inefficiency.
You are using a Fabric Spark notebook to ingest JSON files from a Lakehouse Files folder into a Delta table. The JSON is semi-structured, with nested arrays and occasional missing fields. Downstream queries need to access nested elements as columns, and the schema must be stable across runs even when new fields appear. What should you use?
Read the JSON with an explicit schema and use the explode function on nested arrays before writing the Delta table.
An explicit schema locks the structure so new fields do not shift the table shape, and explode flattens nested arrays into addressable columns for downstream queries. Inference can drift, string storage hides structure, and regex parsing is brittle and unstable, so none of those meet both the stability and column-access goals.
You need to access data from an external Azure Data Lake Storage (ADLS) Gen2 account in a Fabric Lakehouse without duplicating the physical data. Which feature should you use?
Shortcut
Shortcuts provide a way to reference data stored in external locations without the need for data movement or replication. This approach reduces storage costs and ensures that the Fabric environment always sees the most current version of the source data. It is a fundamental concept in OneLake for maintaining a single source of truth across different cloud providers.
You are a data engineer at a retail company using Microsoft Fabric. The company has a workspace with a Lakehouse that contains a large sales table. You need to ensure that when you run a notebook, it uses a specific Spark pool with autoscaling enabled to handle varying workloads. Which configuration should you apply to the notebook?
Create a custom Spark pool with autoscaling enabled and assign it to the notebook via the notebook's Spark pool setting.
To ensure a notebook uses a specific Spark pool with autoscaling, you must create a custom Spark pool with autoscaling enabled and then assign that pool to the notebook. This is done through the notebook's Spark pool setting, which overrides any workspace default. Other options either do not control the pool or do not guarantee the notebook uses the desired pool.
The DP-700 flashcard bank covers all 3 official blueprint domains published by Microsoft. Cards are distributed proportionally, so domains with higher exam weight have more cards.
Domain Coverage
Monitor and Optimize an Analytics Solution
Ingest and Transform Data
Implement and Manage an Analytics Solution
Both flashcards and practice questions are evidence-based study tools. The difference is in what they train:
Flashcards — concept retention
Best for memorising definitions, acronyms, protocol behaviours, command syntax, and conceptual distinctions. Use flashcards to build the foundational vocabulary that DP-700 questions assume you know.
Best in: weeks 1–3
Practice tests — application
Best for applying concepts to realistic scenarios, eliminating distractors, and building exam stamina.DP-700 questions test scenario reasoning — not just recall — so practice tests are essential.
Best in: weeks 3–6
The most effective DP-700 study plan combines both: use flashcards for the first 2–3 weeks to build conceptual foundations, then shift to practice tests and mock exams in the final 2–3 weeks to apply and benchmark that knowledge. Most candidates who pass on their first attempt use both tools.
Yes. Courseiva provides free DP-700 flashcards across all official exam domains. Every card includes the correct answer and a full explanation of why it is right and why the distractors are wrong. The platform also includes topic-based practice, mock exams, and readiness tracking — no account required.
Courseiva has 274+ original DP-700 flashcards across all 3 exam blueprint domains. New cards are added regularly as the question bank grows. All cards are checked against the official Microsoft exam objectives, with editorial oversight from an experienced network and security engineer.
Courseiva flashcards are purpose-built for IT certification exams. Unlike generic flashcard platforms where content quality varies, every Courseiva card is mapped to the official DP-700 exam blueprint, written by engineers who hold the certification, and includes a full explanation of the correct answer and why the distractors are wrong. This explanation quality is what separates genuine learning from rote memorisation.
Courseiva is a web platform — an internet connection is required. For offline study, we recommend creating free Courseiva account, using the platform in your browser, and using your device's offline capabilities if your browser supports offline web apps.
Save your results, see which domains need more work, and get spaced repetition recommendations — all free.
Sign Up FreeFree forever · Every certification included