What is the main limitation of using XMLA endpoints for the Microsoft Power BI deployment process?

• A. A PBIX file cannot be downloaded from the Power BI service
• B. Only the user that deployed the report can make changes
• C. Table partitioning is impossible
• D. You cannot use parameters for incremental refresh

Answer: (A)

XMLA endpoints give external tools access to the Power BI dataset’s tabular model in the service, so you can inspect and script changes to the model without using the Power BI UI. The main limitation here is that a PBIX file cannot be downloaded from the Power BI service when a dataset is exposed via XMLA endpoints. This matters for deployment workflows because your source control and build/release processes often rely on having the PBIX artifact to re-create or promote changes. Without the ability to download the PBIX, you must manage changes through the live model with external tooling (and keep a local PBIX copy for development to re-publish when needed). Other statements don’t capture this fundamental constraint: you can still apply changes via tooling with proper permissions, and partitioning or incremental refresh capabilities are not inherently blocked by XMLA endpoints in the same way.