Enabling XMLA Read-Write Access in Microsoft Fabric
You have a Fabric tenant named Tenant1 that contains a workspace named WS1. WS1 uses a capacity named C1 and contains a dataset named DS1. You need to ensure read-write access to DS1 is available by using XMLA endpoint. What should be modified first?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the distinction between enabling the XMLA feature (tenant level) and configuring its access mode (capacity level), with the common trap being confusion over which layer controls read-write permissions.
This question addresses how to configure read-write access to a dataset via the XMLA endpoint in Microsoft Fabric. It establishes that capacity-level settings must be modified to switch from read-only to read-write connectivity.
Many candidates select D (Tenant1 settings) because they believe tenant configuration is the prerequisite step. However, since the XMLA endpoint is already implied to be active, the specific action for read-write access lies at the capacity level.
Community Discussion (20 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Read-write access to datasets via the XMLA endpoint in Microsoft Fabric is controlled by the capacity settings. By default, Premium capacities often have XMLA endpoints enabled but set to read-only to protect data integrity. To allow write operations (such as DirectQuery updates or Import mode refreshes via external tools), you must modify the specific capacity (C1) settings to enable 'XMLA read-write' connectivity.Why the Other Options Are Wrong
Option D (Tenant1 settings) is incorrect because it governs global features like whether the XMLA endpoint is available to the organization at all. Since the question implies the endpoint exists and focuses on 'read-write access', the tenant setting is not the primary modifier here. Options A (DS1 settings) and B (WS1 settings) are incorrect because XMLA access modes are inherited from the capacity and cannot be overridden at the dataset or workspace level.Community Comment Notes
The community largely agrees with C, noting that while tenant settings enable the feature, capacity settings control the read-write state. One commenter noted that if the endpoint were not enabled at all, D would be first, but for read-write specifically, it is C. Another user highlighted that this is a common point of confusion in Microsoft's documentation wording.Official Reference
Exam Strategy
When asked about 'read-write' vs 'read-only' access for XMLA, always look to the Capacity settings first. If the question asks about enabling the endpoint itself for the organization, look to Tenant settings.
Frequently Asked Questions
Why isn't the Tenant setting the first step?
Tenant settings enable the XMLA endpoint globally. Since the endpoint is already present, the specific read-write toggle is managed at the Capacity level.
Can I enable read-write on a specific dataset?
No. XMLA read-write access is a property of the Capacity hosting the dataset, not individual datasets or workspaces.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →