Comprehensive Detailed Explanation
Requirement
Tenant: Fabric tenant Tenant1
Data target: Lakehouse1
Data source: CSV file in an Azure Storage account (outside of Fabric)
Requirement: Minimize development effort
Step 1: Understand options
A). Dataflow Gen2
Used for ETL (transformations, cleansing, ingestion).
More effort because you need to build Power Query transformations.
Not minimal effort for simply exposing a file.
B). Shortcut
Fabric supports creating shortcuts to external data sources (OneLake, ADLS Gen2, Azure Blob, Dataverse, etc.).
Shortcut directly exposes external files/tables inside the lakehouse without copying or moving data.
This is the lowest-effort solution to access external CSV.
C). Copy job
Pipelines have a copy activity to physically copy data into Fabric.
Requires setup and execution. More development effort than a shortcut.
D). Pipeline
Used for orchestrating complex ETL workflows.
Overhead for this scenario.
Step 2: Correct Answer
Since the goal is simply to access a CSV in external storage with minimal development effort, the right solution is:
B). a shortcut
References
Shortcuts in Microsoft Fabric OneLake
Dataflow Gen2 overview

Step 1: Understand the scenario
Workspace1 contains a semantic model and two Power BI reports.
A Microsoft 365 Data Loss Prevention (DLP) policy (DLP1) already exists.
Requirement: Apply DLP1 to the workspace items.
In Microsoft Fabric and Power BI, DLP policies are enforced through Microsoft Purview Information Protection (MIP) sensitivity labels.
Step 2: Evaluate each option
A). Apply a master data endorsement to the semantic model.
Endorsements (promoted, certified) help users find and trust datasets but do not enforce DLP policies.
Not correct.
B). Apply a certified endorsement to the semantic model.
Certification improves discoverability and trust, but again, it does not trigger DLP policy enforcement.
Not correct.
C). Create a workspace identity.
Workspace identity (service principal) is used for connecting to external resources with managed identity.
It does not relate to DLP policy application.
Not correct.
D). Apply sensitivity labels to the semantic model and reports.
Sensitivity labels (from Microsoft Purview) integrate with Microsoft 365 DLP policies.
When sensitivity labels are applied to Power BI datasets, reports, dashboards, and workspaces, DLP1 can enforce protections such as preventing sharing or exporting sensitive data.
This is the correct answer.
Step 3: Correct Action
To apply DLP1 to Workspace1 items, you must:
Configure sensitivity labels in Microsoft Purview.
Apply those sensitivity labels to the semantic model and reports inside Workspace1.
The existing DLP1 policy will then govern data handling for those items.
References
Sensitivity labels in Power BI
Apply sensitivity labels to Power BI items
DLP policies in Microsoft Purview

VACUUM in Delta Lake removes unreferenced files older than a retention period (default 7 days, but configurable, e.g., 30 days).
It ensures that the transaction log remains consistent and ACID properties are maintained.
OPTIMIZE with V-Order or Z-Order improves file organization and query performance, but it does not remove unused files.
Deleting files manually from OneLake would break the transaction log consistency.
Correct answer: C. Run the VACUUM command.
Reference: VACUUM in Delta Lake

Explanation:

Comprehensive Detailed Explanation
Step 1: Reviewing the provided DAX expression
SWITCH(
SELECTEDVALUE(Metric[Metric]),
" # of Customers " , " # " ,
" Gross Margin % " , " 0.00% " ,
" #,### "
)
This is applied as a dynamic format string.
It changes the display formatting of the Value measure depending on the selected metric.
Step 2: Identify the feature
The screenshot shows Format = Dynamic in the Power BI Modeling tab.
This confirms that a dynamic format string has been applied.
So, for the first blank # dynamic format string.
Step 3: Identify the output formats
If the metric = # of Customers # format is " # " # whole numbers.
If the metric = Gross Margin % # format is " 0.00% " # percentages.
Fallback # " #,### " # also whole numbers.
Thus, the measure supports both whole numbers and percentages.
So, for the second blank # percentages or whole numbers.
References
Dynamic format strings in Power BI
SWITCH function in DAX

Explanation:

We are optimizing model1 in Fabric with two very large columns:
TransactionKey
Cardinality: 2.5 billion
Size: 160 GB
Description: surrogate key for SalesTransaction fact table.
SaleDateTime
Cardinality: 6.8 million
Size: 120 GB
Description: datetime (to the second) of when a sale occurred.
Goal:
Reduce model size.
Improve refresh performance (Import mode).
Ensure datetime values remain available.
Analysis per column
1. TransactionKey (very high cardinality)
Surrogate keys with extremely high cardinality do not add analytical value in a semantic model because they are not used in measures or grouping.
They take a lot of memory and reduce refresh performance.
Best practice: remove the column from the model.
2. SaleDateTime
Needed to analyze transactions by date and time.
However, storing the full datetime at second-level cardinality causes huge memory usage.
To optimize: split the column into Date and Time columns.
Reduces cardinality significantly.
Preserves full datetime information (can recombine if needed).
Improves compression and refresh speed.
Final Answer:
TransactionKey: Remove the column.
SaleDateTime: Split the column.
References:
Microsoft Fabric optimization guidance - reduce cardinality
Best practices for datetime optimization in semantic models
# Answer Selection:
TransactionKey # Remove the column
SaleDateTime # Split the column