Microsoft Updated DP-600 Exam Questions and Answers by milan

Requirements:

Parallel processing → PySpark runs distributed across Spark clusters.

Minimize duplication of data → OneLake shortcut + Spark queries avoid unnecessary copies.

Time series analysis, anomaly detection, visualization → can be done in PySpark within Fabric Notebooks.

pandas (C) is single-threaded and not efficient for billions of items.

Power BI visuals (A) are good for visualization but not for transformation or large-scale anomaly detection.

Correct: B.

When using XMLA endpoint for deployment or processing, the semantic model storage format impacts deployment times.

Small storage format allows faster metadata operations and shorter deployment times.

Large semantic model storage format is only needed for extremely large models ( > 10 GB dataset limit), and it increases deployment overhead.

The other options (B: service editing, C: cache for shortcuts) are unrelated to XMLA endpoint deployment performance.

In Microsoft Fabric, semantic models (formerly datasets) can be managed using external tools like Tabular Editor. To push or publish changes directly to a Fabric workspace from Tabular Editor, the workspace must support XMLA endpoint connectivity with read-write access.

Explanation of Each Option

A. For Workspace1, enable Git integration.

Git integration allows source control and versioning of items in a Fabric workspace. It is intended for lifecycle management of artifacts and does not provide the connectivity required for Tabular Editor to publish semantic model changes.

B. For Workspace1, create a managed private endpoint.

A managed private endpoint provides secure connectivity between Fabric and external data sources. It is not related to the ability to publish semantic models through XMLA.

C. For Model1, enable external sharing.

External sharing governs who can access the model outside the organization. This does not affect publishing workflows from developer tools.

D. For Capacity1, set XMLA Endpoint to Read Write.

This is the correct choice. The XMLA endpoint provides a programmatic connection point for external tools like Tabular Editor. By default, the XMLA endpoint is enabled only in read-only mode. Changing the setting to Read Write allows developers to push changes, update metadata, and deploy semantic models directly from Tabular Editor into the Fabric workspace.

Summary

To publish changes to a Fabric semantic model using Tabular Editor, the XMLA endpoint of the assigned capacity must be set to Read Write. Without this configuration, Tabular Editor can only connect in read-only mode and cannot deploy updates.

References

Use the XMLA endpoint in Microsoft Fabric

Manage capacities in Microsoft Fabric

Tabular Editor and XMLA endpoint