Pass Your Microsoft DP-600 Exam Easy!

This action is appropriate when an engineer stores a production database password as a literal in a notebook committed to Git. Source code is not a secure place for long-lived production credentials. However, the question instead requires Create a Fabric connection with the supported source type and authorized credentials. because a connection specifies source endpoint and authentication information for governed reuse.

This action is appropriate when a connector returns encrypted-transport errors after a database certificate changes. TLS trust failures require secure endpoint remediation rather than disabling verification. However, the question instead requires Create a Fabric connection with the supported source type and authorized credentials. because a connection specifies source endpoint and authentication information for governed reuse.

This action is appropriate when a gateway-based source works for one developer but fails when a scheduled service job runs. Interactive success does not prove that the unattended job has equivalent access. However, the question instead requires Create a Fabric connection with the supported source type and authorized credentials. because a connection specifies source endpoint and authentication information for governed reuse.

This action is appropriate when a BI engineer wants to discover lakehouse tables without copying their data into a local folder. Data discovery should precede unnecessary duplication of a managed dataset. However, the question instead requires Search the OneLake catalog and inspect item ownership and endorsements. because catalog metadata and endorsement help locate the intended governed data product.

This action is appropriate when a team sees a catalog entry but its table is not readable under the user's identity. Being able to discover metadata does not automatically authorize reading restricted rows. However, the question instead requires Search the OneLake catalog and inspect item ownership and endorsements. because catalog metadata and endorsement help locate the intended governed data product.

This action is appropriate when a data steward wants consumers to find a trusted data product using consistent terminology. Catalog discoverability depends on reliable metadata, not only technical file paths. However, the question instead requires Search the OneLake catalog and inspect item ownership and endorsements. because catalog metadata and endorsement help locate the intended governed data product.

This action is appropriate when a streaming feed is present but the analyst cannot identify its event schema or owner. Stream discovery needs schema and ownership verification before downstream transformations. However, the question instead requires Use Real-Time hub to locate the supported streams and event sources. because real-Time hub provides a discovery surface for streaming data sources.

This action is appropriate when an events team wants to query continuously ingested sensor records with KQL. Eventhouse is designed for streaming/time-series analytics with KQL queries. However, the question instead requires Use Real-Time hub to locate the supported streams and event sources. because real-Time hub provides a discovery surface for streaming data sources.

This action is appropriate when a reporting requirement depends on second-level telemetry but the engineer selects a nightly CSV export. A batch snapshot cannot satisfy continuous event-arrival latency. However, the question instead requires Use Real-Time hub to locate the supported streams and event sources. because real-Time hub provides a discovery surface for streaming data sources.

This action is appropriate when a shortcut points to an external object store but users are unexpectedly denied file access. Virtualized paths depend on authorization to the actual backing storage. However, the question instead requires Create an authorized OneLake shortcut to the source table or folder. because shortcuts expose referenced data paths while avoiding a second physical copy.

This action is appropriate when a source table updates but consumers assume a shortcut creates an independent point-in-time snapshot. Shortcuts are references rather than automatic historical backups. However, the question instead requires Create an authorized OneLake shortcut to the source table or folder. because shortcuts expose referenced data paths while avoiding a second physical copy.

This action is appropriate when a data steward wants to know which OneLake tables are shortcuts to another owner. Downstream consumers need to identify the authoritative underlying dataset. However, the question instead requires Create an authorized OneLake shortcut to the source table or folder. because shortcuts expose referenced data paths while avoiding a second physical copy.

This action is appropriate when a team wants to retain raw binary source files alongside curated Delta tables for exploration. Lakehouse Files and Tables support raw assets and managed analytical tables together. However, the question instead requires Choose a Fabric lakehouse for Spark-oriented Delta and file workloads. because lakehouses combine OneLake tables and files with Spark-centric engineering workflows.

This action is appropriate when an architect selects Eventhouse to store all financial dimensional tables without an event-analytics need. Eventhouse is primarily for event and time-series KQL scenarios. However, the question instead requires Choose a Fabric lakehouse for Spark-oriented Delta and file workloads. because lakehouses combine OneLake tables and files with Spark-centric engineering workflows.

This action is appropriate when a finance team uses relational SQL modeling and stored procedures for a dimensional reporting store. Warehouses are optimized for relational SQL analytics and supported database objects. However, the question instead requires Choose a Fabric lakehouse for Spark-oriented Delta and file workloads. because lakehouses combine OneLake tables and files with Spark-centric engineering workflows.

This action is appropriate when a team ingests event records but assumes SQL stored procedures are the standard KQL database transformation interface. KQL databases have different query and transformation semantics from T-SQL warehouses. However, the question instead requires Use an Eventhouse KQL database suited to telemetry queries. because kQL storage and indexing support operational time-series exploration.

This action is appropriate when a developer must retain raw event details while creating a reusable normalized event representation. Ingestion transformations should be observable and consistent with event schema contracts. However, the question instead requires Use an Eventhouse KQL database suited to telemetry queries. because kQL storage and indexing support operational time-series exploration.

This action is appropriate when a KQL query returns enormous results and an operator wants to inspect only recent high-severity events. Early filtering narrows scanned and returned event records. However, the question instead requires Use an Eventhouse KQL database suited to telemetry queries. because kQL storage and indexing support operational time-series exploration.

This action is appropriate when a data engineer wants a transformation notebook to run only after ingestion has finished. Dependency ordering prevents consumers from reading half-landed data. However, the question instead requires Configure a supported Fabric pipeline Copy activity with scheduling and validation. because data Factory pipelines orchestrate repeatable bounded source-to-target transfers.

This action is appropriate when a scheduled copy fails intermittently and an engineer manually reruns it with duplicate output rows. Reliable ingestion must distinguish transient retries from duplicate business records. However, the question instead requires Configure a supported Fabric pipeline Copy activity with scheduling and validation. because data Factory pipelines orchestrate repeatable bounded source-to-target transfers.

This action is appropriate when a pipeline reports success but a source export was only partially delivered. Task success does not establish that the business extract was complete. However, the question instead requires Configure a supported Fabric pipeline Copy activity with scheduling and validation. because data Factory pipelines orchestrate repeatable bounded source-to-target transfers.

This action is appropriate when a Power Query step casts a locale-specific date incorrectly and the dataflow writes nulls. Parsing rules must match source format rather than accepting silent type corruption. However, the question instead requires Use Dataflow Gen2 with suitable Power Query transformations and an approved destination. because dataflow Gen2 provides low-code shaping of supported source data.

This action is appropriate when a dataflow appends the same weekly extract twice after an operator replay. Re-running an ingestion flow must not accidentally multiply source records. However, the question instead requires Use Dataflow Gen2 with suitable Power Query transformations and an approved destination. because dataflow Gen2 provides low-code shaping of supported source data.

This action is appropriate when a Dataflow Gen2 transformation succeeds in preview but fails when publishing to a destination. Editing a preview does not prove the deployed sink is writable. However, the question instead requires Use Dataflow Gen2 with suitable Power Query transformations and an approved destination. because dataflow Gen2 provides low-code shaping of supported source data.

This action is appropriate when a modeling team connects a semantic model to a lakehouse but assumes every new source table is automatically modeled. Data existence in OneLake does not guarantee its inclusion in the model. However, the question instead requires Evaluate Direct Lake integration with supported OneLake-backed tables. because direct Lake queries Delta-backed columns without a full scheduled Import processing copy.

This action is appropriate when a Direct Lake table updates in Delta but a user still sees an older framed version. Direct Lake model metadata must recognize an updated source snapshot to surface it predictably. However, the question instead requires Evaluate Direct Lake integration with supported OneLake-backed tables. because direct Lake queries Delta-backed columns without a full scheduled Import processing copy.

This action is appropriate when an analyst expects a model to include a KQL stream directly without supported integration. Source-to-model compatibility determines which event data can be consumed. However, the question instead requires Evaluate Direct Lake integration with supported OneLake-backed tables. because direct Lake queries Delta-backed columns without a full scheduled Import processing copy.

This action is appropriate when an on-premises SQL connection works on the author's laptop but fails from Fabric cloud execution. Fabric cloud execution requires an approved route to private on-premises systems. However, the question instead requires Replace person-bound authentication with an approved stable service identity where supported. because shared production refreshes should not rely on an employee's account lifecycle.

This action is appropriate when a source password rotates and several downstream refresh tasks fail together. Centralized credential management simplifies restoring multiple consumers. However, the question instead requires Replace person-bound authentication with an approved stable service identity where supported. because shared production refreshes should not rely on an employee's account lifecycle.

This action is appropriate when an administrator grants a gateway operator broad database permissions to fix an access error. Gateway administration is different from permission to read or modify source data. However, the question instead requires Replace person-bound authentication with an approved stable service identity where supported. because shared production refreshes should not rely on an employee's account lifecycle.

This action is appropriate when an operations team needs a parameterized sequence of supported SQL updates run as one controlled operation. Stored procedures encapsulate supported parameterized T-SQL operations. However, the question instead requires Create a supported SQL view over the curated warehouse tables. because views centralize a reusable query definition without manually copying results.

This action is appropriate when a developer writes a view and assumes its definition guarantees a materialized daily snapshot. A logical view generally runs a query against underlying data rather than storing a scheduled copy. However, the question instead requires Create a supported SQL view over the curated warehouse tables. because views centralize a reusable query definition without manually copying results.

This action is appropriate when a finance calculation returns a scalar tax category based on customer region in many SQL queries. Reusable functions can package common deterministic expressions for SQL consumers. However, the question instead requires Create a supported SQL view over the curated warehouse tables. because views centralize a reusable query definition without manually copying results.