DP-600 - Prepare Data (46% of the exam) - Section 2.1
Create data connections and manage gateways and credentials to source data into Microsoft Fabric.
Create and manage cloud connections and on-premises data gateway connections to source data into Microsoft Fabric. Understand when an on-premises data gateway is required and how to configure connection credentials securely for use in Dataflows Gen2 and pipelines.
data connectionon-premises data gatewaycloud connectionconnection credentialsDataflows Gen2 connections
Practice question for this objective
lock_openFree samplePrepare Datamedium
An analytics engineer must ingest data from a SQL Server instance that runs on a server inside the company data centre, with no public endpoint, into a "Lakehouse" using "Dataflows Gen2". The "Microsoft Fabric" service in the cloud cannot reach the server directly. Which component must be installed and configured so that the connection can reach the on-premises database?
AAn on-premises data gateway installed on a machine inside the company network, registered to the tenant and bound to the connection.check_circle Correct
BA cloud connection defined in the "Microsoft Fabric" portal, which routes the query to the private server using the engineer's stored organisational account credentials.
CA virtual network data gateway provisioned in the tenant, which peers with the on-premises subnet and forwards each query to the local SQL Server instance.
DA personal gateway in standard mode shared across the workspace, which lets every workspace member reuse one connection to the local SQL Server instance.
Source data from a private on-premises database into Fabric by installing and binding an on-premises data gateway to the connection. The on-premises data gateway is the relay that sits inside the corporate network and tunnels query and result traffic between the cloud Fabric service and a source that has no public endpoint, which is why it is mandatory for on-premises ingestion.
Why A is correct: The on-premises data gateway runs inside the private network and relays queries between the cloud service and the local server, which is exactly the bridge a non-public source requires.
Why B is wrong: A cloud connection only reaches sources that already have a public or service endpoint, so it cannot by itself bridge into a private on-premises network that the service cannot see.
Why C is wrong: A virtual network data gateway reaches sources inside an Azure virtual network, not a physical on-premises data centre, so it does not bridge to a server with no cloud presence.
Why D is wrong: The personal mode gateway is single-user and cannot be shared across a workspace, so it is the wrong gateway type for a team ingestion pipeline.
Answers that look right on this material and are not. Each one is a distractor from a different question in the DP-600 bank for this domain.
The on-premises data gateway in personal mode, installed by each author on their own workstation for their individual scheduled dataflow refreshes
errorWhy it is wrong: Personal mode binds to a single user and cannot be shared, so each author would need their own gateway, which contradicts the requirement for one shared gateway.
An on-premises data gateway installed on an Azure virtual machine that fronts the database and relays Fabric's queries to the public endpoint
errorWhy it is wrong: The database is publicly reachable and not on-premises, so installing and maintaining a gateway adds operational overhead that provides no connectivity benefit here.
The Owner role on the connection, so the engineer can manage every aspect of the connection while building dataflows on it
errorWhy it is wrong: Owner grants full control including editing settings, changing credentials, and deleting, which exceeds the use-only access the engineer is meant to have.