An analytics engineer tries to enable the large semantic model storage format on an import "semantic model" that lives in a workspace backed by shared capacity under Power BI Pro licensing. The option to switch the model to the large format is unavailable. They need the model to be able to grow past the small default per-model size limit. What must change first so the format can be enabled?
- AThe model must first be set to DirectQuery storage, because the large format is offered only once a model no longer caches any of its rows in memory on the shared tier.
- BThe tenant XMLA endpoint must be switched from read-write back to read-only, since the large format is only exposed for models whose metadata cannot be written externally.
- CA sensitivity label of at least Confidential must be applied to the workspace, because the large format becomes selectable only after the workspace content is classified for information protection.
- DThe workspace must be assigned to a dedicated Fabric or Premium capacity, because the large semantic model storage format is available only to models hosted on such a capacity rather than on shared Pro capacity. Correct
Why A is wrong: The large format applies to in-memory import models, not DirectQuery, and changing storage mode does not unlock the format on shared capacity, so this addresses neither the tier nor the size ceiling.
Why B is wrong: Read-write XMLA is required for external metadata writes, not a blocker for the large format, so forcing the endpoint to read-only would restrict tooling without making the format available on shared capacity.
Why C is wrong: Sensitivity labels govern information protection and have no link to storage format availability, so labelling the workspace does nothing to expose the large format on shared capacity.
Why D is correct: The large format is a capacity feature, so the workspace must sit on a dedicated Fabric or Premium capacity; on shared Pro capacity the option is simply not offered, which is why it appears unavailable.