Implementing Data Engineering Solutions Using Microsoft Fabric (DP-700) — Free Practice Questions
10 free sample questions from a bank of 127, with the correct answers and explanations. No signup required — start practising right now.
1Case Study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions.
Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Overview. Company Overview -
Contoso, Ltd. is an online retail company that wants to modernize its analytics platform by moving to Fabric. The company plans to begin using Fabric for marketing analytics.
Overview. IT Structure -
The company’s IT department has a team of data analysts and a team of data engineers that use analytics systems.
The data engineers perform the ingestion, transformation, and loading of data. They prefer to use Python or SQL to transform the data.
The data analysts query data and create semantic models and reports. They are qualified to write queries in Power Query and T-SQL.
Existing Environment. Fabric -
Contoso has an F64 capacity named Cap1. All Fabric users are allowed to create items.
Contoso has two workspaces named WorkspaceA and WorkspaceB that currently use Pro license mode.
Existing Environment. Source Systems
Contoso has a point of sale (POS) system named POS1 that uses an instance of SQL Server on Azure Virtual Machines in the same Microsoft Entra tenant as Fabric. The host virtual machine is on a private virtual network that has public access blocked. POS1 contains all the sales transactions that were processed on the company’s website.
The company has a software as a service (SaaS) online marketing app named MAR1. MAR1 has seven entities. The entities contain data that relates to email open rates and interaction rates, as well as website interactions. The data can be exported from MAR1 by calling REST APIs. Each entity has a different endpoint.
Contoso has been using MAR1 for one year. Data from prior years is stored in Parquet files in an Amazon Simple Storage Service (Amazon S3) bucket. There are 12 files that range in size from 300 MB to 900 MB and relate to email interactions.
Existing Environment. Product Data
POS1 contains a product list and related data. The data comes from the following three tables:
Products -
ProductCategories -
ProductSubcategories -
In the data, products are related to product subcategories, and subcategories are related to product categories.
Existing Environment. Azure -
Contoso has a Microsoft Entra tenant that has the following mail-enabled security groups:
DataAnalysts: Contains the data analysts
DataEngineers: Contains the data engineers
Contoso has an Azure subscription.
The company has an existing Azure DevOps organization and creates a new project for repositories that relate to Fabric.
Existing Environment. User Problems
The VP of marketing at Contoso requires analysis on the effectiveness of different types of email content. It typically takes a week to manually compile and analyze the data. Contoso wants to reduce the time to less than one day by using Fabric.
The data engineering team has successfully exported data from MAR1. The team experiences transient connectivity errors, which causes the data exports to fail.
Requirements. Planned Changes -
Contoso plans to create the following two lakehouses:
Lakehouse1: Will store both raw and cleansed data from the sources
Lakehouse2: Will serve data in a dimensional model to users for analytical queries
Additional items will be added to facilitate data ingestion and transformation.
Contoso plans to use Azure Repos for source control in Fabric.
Requirements. Technical Requirements
The new lakehouses must follow a medallion architecture by using the following three layers: bronze, silver, and gold. There will be extensive data cleansing required to populate the MAR1 data in the silver layer, including deduplication, the handling of missing values, and the standardizing of capitalization.
Each layer must be fully populated before moving on to the next layer. If any step in populating the lakehouses fails, an email must be sent to the data engineers.
Data imports must run simultaneously, when possible.
The use of email data from the Amazon S3 bucket must meet the following requirements:
Minimize egress costs associated with cross-cloud data access.
Prevent saving a copy of the raw data in the lakehouses.
Items that relate to data ingestion must meet the following requirements:
The items must be source controlled alongside other workspace items.
Ingested data must land in the bronze layer of Lakehouse1 in the Delta format.
No changes other than changes to the file formats must be implemented before the data lands in the bronze layer.
Development effort must be minimized and a built-in connection must be used to import the source data.
In the event of a connectivity error, the ingestion processes must attempt the connection again.
Lakehouses, data pipelines, and notebooks must be stored in WorkspaceA. Semantic models, reports, and dataflows must be stored in WorkspaceB.
Once a week, old files that are no longer referenced by a Delta table log must be removed.
Requirements. Data Transformation
In the POS1 product data, ProductID values are unique. The product dimension in the gold layer must include only active products from product list. Active products are identified by an IsActive value of 1.
Some product categories and subcategories are NOT assigned to any product. They are NOT analytically relevant and must be omitted from the product dimension in the gold layer.
Requirements. Data Security -
Security in Fabric must meet the following requirements:
The data engineers must have read and write access to all the lakehouses, including the underlying files.
The data analysts must only have read access to the Delta tables in the gold layer.
The data analysts must NOT have access to the data in the bronze and silver layers.
The data engineers must be able to commit changes to source control in WorkspaceA.
You need to ensure that the data analysts can access the gold layer lakehouse.
What should you do?
Add the DataAnalyst group to the Viewer role for WorkspaceA.
Share the lakehouse with the DataAnalysts group and grant the Build reports on the default semantic model permission.
Share the lakehouse with the DataAnalysts group and grant the Read all SQL Endpoint data permission.
Share the lakehouse with the DataAnalysts group and grant the Read all Apache Spark permission.
Answer: C
The short version
C — gold-layer SQL access needs Read all SQL Endpoint data. The settled key applies least privilege for analyst querying.
Key concepts in this question
Lakehouse layers: bronze raw, silver cleansed, and gold curated for consumption.
SQL Endpoint permission: grants T-SQL read over lakehouse tables without broader compute rights.
Viewer role contrast: workspace-wide viewing that may overexpose items beyond the gold layer.
Build-reports contrast: semantic-model reporting right that does not equal direct SQL data read.
Spark permission contrast: covers notebook and Spark job data access, not SQL endpoint querying.
Why C is correct
C is correct because sharing the lakehouse plus Read all SQL Endpoint data lets DataAnalysts query gold tables through T-SQL while adhering to least privilege. Vendor prose confirms this as necessary and sufficient for the stated need. Broader roles or Spark rights would grant unneeded paths to the same data.
Why the others are wrong
A. Viewer on the workspace is broader than the targeted gold-layer SQL need.
B. Build reports enables semantic-model reporting, not direct SQL endpoint reads.
D. Read all Apache Spark covers Spark pools, not SQL endpoint querying.
DP-700 exam tip
For SQL-only analyst access, choose Read all SQL Endpoint data, nothing wider.
2You have a Fabric warehouse named DW1. DW1 contains a table that stores sales data and is used by multiple sales representatives.
You plan to implement row-level security (RLS).
You need to ensure that the sales representatives can see only their respective data.
Which warehouse object do you require to implement RLS?
STORED PROCEDURE
CONSTRAINT
SCHEMA
FUNCTION
Answer: D
The short version
D — Fabric warehouse RLS is driven by a FUNCTION. The settled key names the filtering object behind the security policy.
Key concepts in this question
Row-level security goal: each sales representative sees only personal rows in the shared DW1 table.
Predicate function: a user-defined function that returns which rows the current user may view.
Security policy binding: links the table to the function so filtering applies transparently.
Procedure and constraint contrast: execute logic or enforce integrity, not per-user row filtering.
Schema contrast: a namespace container with no filtering logic.
Why D is correct
D is correct because Fabric warehouse RLS requires creating a table-valued or scalar predicate FUNCTION that encodes the sales-rep mapping, then associating it through a security policy. At query time the engine invokes the function with user context to filter rows. Vendor prose confirms FUNCTION as the required warehouse object.
Why the others are wrong
A. stored procedure executes batch logic but cannot serve as RLS predicate.
B. constraint enforces uniqueness or checks, not user-aware filtering.
C. schema organizes objects but contains no row-filter code.
DP-700 exam tip
Hear RLS in warehouse and immediately answer FUNCTION predicate plus policy.
3You have a Fabric workspace.
You have semi-structured data.
You need to read the data by using T-SQL, KQL, and Apache Spark. The data will only be written by using Spark.
What should you use to store the data?
a lakehouse
an eventhouse
a datamart
a warehouse
Answer: B
The short version
B — Eventhouse covers T-SQL plus KQL plus Spark reads with Spark writes. Fabric eventhouses back KQL databases that ingest semi-structured telemetry and expose it via Kusto Query Language, T-SQL endpoint, and Spark connectors. That tri-engine read coverage is unique to eventhouse, while Spark ingestion preserves schema-on-read flexibility. Lakehouse and warehouse lack the same first-class KQL experience and datamarts target relational models.
Key concepts in this question
Eventhouse: KQL database optimized for time-series and nested data with auto indexing and fast ingest.
Tri-engine: KQL for exploration, T-SQL for relational tools, and Spark for distributed jobs over one copy.
Spark writes: Event-stream or Spark ingestion handles JSON payloads without rigid warehouse loads.
Lakehouse gap: Strong on Spark plus SQL over delta but without native KQL engine depth.
Why B is correct
Storing semi-structured data in an eventhouse satisfies all three reads at once under the Spark-only write constraint. Analysts use T-SQL, engineers use Spark, and real-time users use KQL against one copy with no replication. That convergence is why the Fabric decision guide routes this exact combination to eventhouse.
Why the others are wrong
A. lakehouse supports Spark and SQL well but lacks the native KQL database experience.
C. datamart is a relational semantic endpoint, not a semi-structured multi-engine store.
D. warehouse enforces structured schemas without the same KQL plus Spark flexibility.
DP-700 exam tip
KQL plus T-SQL plus Spark reads equals eventhouse every time.
4You have a Fabric deployment pipeline that uses three workspaces named Dev, Test, and Prod.
You need to deploy an eventhouse as part of the deployment process.
What should you use to add the eventhouse to the deployment process?
GitHub Actions
a deployment pipeline
an Azure DevOps pipeline
Answer: B
The short version
B — eventhouses move through Fabric deployment pipelines. The settled key uses the native Dev-Test-Prod path.
Key concepts in this question
Deployment pipeline stages: Dev, Test, and Prod workspaces with managed promotion and rules.
Eventhouse artifact: the Real-Time Intelligence query engine holding KQL databases for telemetry.
Native deployment: built-in Fabric comparison and deploy for supported items including eventhouses.
GitHub Actions contrast: useful for custom automation but not the credited native promotion route.
Azure DevOps pipeline contrast: orchestrates broader CI and CD but is not the Fabric-native artifact deployer here.
Why B is correct
B is correct because Microsoft Fabric deployment pipelines are the recommended built-in method for promoting eventhouses alongside lakehouses and reports across environments. They handle dependencies and workspace assignment with minimal effort. Vendor prose confirms this as the intended process for the Dev-Test-Prod flow.
Why the others are wrong
A. GitHub Actions can call APIs but is not the native pipeline for eventhouse promotion.
C. Azure DevOps pipeline orchestrates externally and is not the credited Fabric mechanism.
DP-700 exam tip
For Fabric item promotion across Dev-Test-Prod, choose deployment pipeline first.
5You have a Fabric workspace named Workspace1 that contains a warehouse named Warehouse1.
You plan to deploy Warehouse1 to a new workspace named Workspace2.
As part of the deployment process, you need to verify whether Warehouse1 contains invalid references. The solution must minimize development effort.
What should you use?
a database project
a deployment pipeline
a Python script
a T-SQL script
Answer: B
The short version
B — pipeline deployment validates warehouse references automatically. The settled key minimizes effort for cross-workspace moves.
Key concepts in this question
Warehouse deployment: copying Warehouse1 from Workspace1 to Workspace2 with schema and dependencies.
Invalid references: missing tables, views, or shortcuts that break queries after a move.
Pipeline validation: built-in checks during deploy that flag broken dependencies.
Database project contrast: schema-as-code with manual build and publish effort.
Script contrast: Python or T-SQL checks require custom parsing and higher maintenance.
Why B is correct
B is correct because Fabric deployment pipelines compare source and target, deploy warehouse artifacts, and surface invalid references during the process without custom code. That meets the minimize-effort requirement while ensuring Warehouse1 remains queryable. Vendor prose confirms automatic dependency checking as the pipeline benefit.
Why the others are wrong
A. database project adds source-control overhead instead of minimizing effort.
C. Python script needs bespoke dependency crawling and upkeep.
D. T-SQL script can query metadata but does not natively validate deployment.
DP-700 exam tip
Need low-effort reference check on move, use deployment pipeline validation.
6You have a Fabric workspace that contains a Real-Time Intelligence solution and an eventhouse.
Users report that from OneLake file explorer, they cannot see the data from the eventhouse.
You enable OneLake availability for the eventhouse.
What will be copied to OneLake?
only data added to new databases that are added to the eventhouse
only the existing data in the eventhouse
no data
both new data and existing data in the eventhouse
only new data added to the eventhouse
Answer: E
The short version
E — enabling OneLake availability exposes only new eventhouse data. The settled key reflects forward-only copying behavior.
Key concepts in this question
OneLake availability: toggle that mirrors eventhouse tables into OneLake folders for file-explorer access.
Forward-only scope: only data added after enablement is copied, existing data stays queryable in KQL.
New-database nuance: availability applies at eventhouse level to newly written data, not retroactively.
Cache and shortcut contrast: separate OneLake shortcut caching with 24-hour retention, not this copy rule.
E is correct because Microsoft states that enabling OneLake availability does not backfill historic eventhouse data, and existing tables remain unaffected in OneLake. Only new data written afterward appears in OneLake file explorer. Vendor prose and linked Learn guidance confirm the only-new-data outcome.
Why the others are wrong
A. new databases alone is too narrow, all new writes qualify.
B. existing data alone is opposite of documented behavior.
C. no data is wrong because new writes do appear.
D. both new and existing overstates the copy and contradicts Docs.
DP-700 exam tip
OneLake toggle for eventhouse equals future data only, past stays behind.
7You have a Fabric workspace named Workspace1.
You plan to integrate Workspace1 with Azure DevOps.
You will use a Fabric deployment pipeline named deployPipeline1 to deploy items from Workspace1 to higher environment workspaces as part of a medallion architecture. You will run deployPipeline1 by using an API call from an Azure DevOps pipeline.
You need to configure API authentication between Azure DevOps and Fabric.
Which type of authentication should you use?
service principal
Microsoft Entra username and password
managed private endpoint
workspace identity
Answer: A
The short version
A — API calls from DevOps to Fabric authenticate with a service principal. The settled key enables headless pipeline execution.
Key concepts in this question
Deployment pipeline API: REST trigger that promotes Fabric content from Workspace1 upward on demand.
Service principal auth: Microsoft Entra app identity with secret or certificate for automation.
Username-password contrast: interactive credentials that break MFA and rotation best practices.
Private endpoint contrast: a network path control, not an API identity.
Workspace identity contrast: a Fabric managed identity for workspace jobs, not the DevOps caller here.
Why A is correct
A is correct because Azure DevOps pipelines calling Fabric REST APIs should use a service principal with scoped permissions and secret rotation for unattended authentication. That supports medallion promotion from deployPipeline1 without human login. Linked guidance shows API-driven pipeline runs authenticated this way.
Why the others are wrong
B. username and password is interactive, less secure, and unsuitable for automation.
C. managed private endpoint secures network routing, not API identity.
D. workspace identity serves internal Fabric workloads, not the external DevOps caller.
DP-700 exam tip
DevOps to Fabric API equals service principal with stored secret.
8You have a Google Cloud Storage (GCS) container named storage1 that contains the files shown in the following table. You have a Fabric workspace named Workspace1 that has the cache for shortcuts enabled. Workspace1 contains a lakehouse named Lakehouse1. Lakehouse1 has the shortcuts shown in the following table. You need to read data from all the shortcuts.
Which shortcuts will retrieve data from the cache?
Stores only
Products only
Stores and Products only
Products, Stores, and Trips
Trips only
Products and Trips only
Answer: C
The short version
C — cached GCS shortcuts serve Stores and Products reads. The settled key applies shortcut caching and file-type limits.
Key concepts in this question
OneLake shortcuts: pointers to external GCS data read as if local to Lakehouse1.
Cross-cloud caching: first read pulls from GCS into Fabric cache, later reads hit cache for 24 hours.
Eligible sources: caching supports GCS, S3, and S3-compatible shortcuts under size limits.
Trips exclusion: the Trips shortcut in this row misses cache due to stated file or access conditions.
Egress benefit: cache hits avoid repeat cross-cloud transfer costs.
Why C is correct
C is correct because Stores and Products shortcuts meet caching conditions and have been read through the cache-enabled workspace, so their data comes from cache. Trips does not qualify under the given table state, whether from recency, size over 1 GB, or provider nuance. Vendor prose plus Learn caching notes support the Stores-and-Products-only outcome.
Why the others are wrong
A. Stores only omits Products, which also qualifies.
B. Products only omits Stores, which also qualifies.
D. including Trips overstates cache coverage.
E. Trips only reverses the qualified set.
F. Products and Trips wrongly includes Trips and drops Stores.
DP-700 exam tip
Check cache eligibility per shortcut: GCS plus recent plus under size equals cached.
9You have a Fabric workspace named Workspace1 that contains an Apache Spark job definition named Job1.
You have an Azure SQL database named Source1 that has public internet access disabled.
You need to ensure that Job1 can access the data in Source1.
What should you create?
an on-premises data gateway
a managed private endpoint
an integration runtime
a data management gateway
Answer: B
The short version
B — private SQL access for Spark jobs needs a managed private endpoint. The settled key bridges Fabric to locked-down Azure SQL.
Key concepts in this question
Job1 requirement: Apache Spark job definition in Workspace1 reading Source1 with public access disabled.
Managed private endpoint: Fabric-managed private link from the workspace to the PaaS data source.
Approval flow: endpoint request approved in networking, then traffic stays on the Microsoft backbone.
On-premises gateway contrast: connects to on-premises sources, not Azure PaaS with public access off.
Integration runtime contrast: Data Factory compute for hybrid movement, not Fabric Spark private access.
Why B is correct
B is correct because a managed private endpoint gives Job1 a private path to Source1 without opening public internet. Creating and approving it in Fabric satisfies the disabled-public-access constraint. Vendor prose confirms this as the correct connectivity object.
Why the others are wrong
A. on-premises data gateway targets on-premises networks, not Azure SQL private link.
C. integration runtime is Data Factory scoped and not the Fabric Spark route.
D. data management gateway is legacy hybrid wording, not managed private endpoint.
DP-700 exam tip
Spark to locked PaaS in Fabric equals managed private endpoint.
10You have an Azure Data Lake Storage Gen2 account named storage1 and an Amazon S3 bucket named storage2.
You have the Delta Parquet files shown in the following table. You have a Fabric workspace named Workspace1 that has the cache for shortcuts enabled. Workspace1 contains a lakehouse named Lakehouse1. Lakehouse1 has the following shortcuts:
A shortcut to ProductFile aliased as Products
A shortcut to StoreFile aliased as Stores
A shortcut to TripsFile aliased as Trips
The data from which shortcuts will be retrieved from the cache?
Trips and Stores only
Products and Store only
Stores only
Products only
Products, Stores, and Trips
Answer: C
The short version
C — only the S3-backed Stores shortcut is cache-served. The settled key enforces provider and freshness limits for lakehouse shortcuts.
Key concepts in this question
Shortcut provider matrix: caching currently supports GCS, S3, and S3-compatible paths, not ADLS Gen2.
Stores mapping: StoreFile on S3 qualifies when recently read and under the 1 GB per-file cap.
ADLS contrast: ProductFile on ADLS Gen2 is native Azure and not served through cross-cloud cache.
Expiry rule: files untouched for over 24 hours purge from cache and refetch from source.
Size rule: individual files over 1 GB bypass caching entirely.
Why C is correct
C is correct because Stores points to S3 StoreFile that meets caching provider, recency, and size conditions, while Products points to ADLS storage1 that is explicitly excluded from this cache path. Trips likewise fails the stated freshness or size test. Vendor prose and Learn shortcut-caching limits confirm Stores-only as the cache hit.
Why the others are wrong
A. Trips and Stores wrongly includes Trips, which misses cache.
B. Products and Stores wrongly includes ADLS-backed Products.
D. Products only selects the ADLS path that is not cached.
E. all three overstates coverage across providers.
DP-700 exam tip
Shortcut cache equals S3 or GCS plus fresh plus small: ADLS never counts.