With XMLA Endpoint set to Read Write, what is the main limitation of using XMLA endpoints for the Microsoft Power BI deployment process when deploying changes to only one table from the data model?

With XMLA Endpoint set to Read Write, what is the main limitation of using XMLA endpoints for the Microsoft Power BI deployment process when deploying changes to only one table from the data model?

• A. XMLA endpoints support only read operations.
• B. XMLA endpoints can deploy to multiple tables simultaneously.
• C. A PBIX file cannot be downloaded from the Power BI service.
• D. XMLA endpoints require Premium capacity.

Answer: (C)

XMLA endpoints give programmatic access to the dataset model for deployment and management, but a practical limitation when you want to push changes to only one table is that you cannot download a PBIX file from the Power BI service. Because the PBIX source isn’t retrievable from the service after deployment, you can’t grab a local copy that reflects just a single-table change and re-publish it. This means you can’t perform a true, granular, table-by-table deployment from a standalone PBIX; you’d have to deploy the entire model from Desktop or manage changes directly through the model via the XMLA/Tabular Object Model. Other statements aren’t the main constraint here—the read/write capability is available, you can deploy changes, and the need for Premium capacity is a deployment detail rather than the fundamental limitation discussed.

XMLA endpoints give programmatic access to the dataset model for deployment and management, but a practical limitation when you want to push changes to only one table is that you cannot download a PBIX file from the Power BI service. Because the PBIX source isn’t retrievable from the service after deployment, you can’t grab a local copy that reflects just a single-table change and re-publish it. This means you can’t perform a true, granular, table-by-table deployment from a standalone PBIX; you’d have to deploy the entire model from Desktop or manage changes directly through the model via the XMLA/Tabular Object Model. Other statements aren’t the main constraint here—the read/write capability is available, you can deploy changes, and the need for Premium capacity is a deployment detail rather than the fundamental limitation discussed.