The Implementing Analytics Solutions Using Microsoft Fabric (DP-600)

When creating a OneLake shortcut to Amazon S3, authentication uses the standard AWS access key ID + secret access key pair.

SAS token is for Azure Storage, not AWS.

Certificate thumbprint is not used for S3.

Access ID is incorrect naming; the correct term is access key ID .

Correct answers: B and D .

For a Type 1 SCD, you should include actions that update rows when non-key attributes have changed (A), and insert new records when the natural key is a new value in the table (D). A Type 1 SCD does not track historical data, so you always overwrite the old data with the new data for a given key. References = Details on Type 1 slowly changing dimension patterns can be found in data warehousing literature and Microsoft ' s official documentation.

Scenario:

Dev = Workspace1 with Dataflow Gen2 (source = blob storage CSV).

Prod = Workspace2, different storage account.

Need: ensure deployed dataflow points to the production storage location .

Analysis:

Data source rules : used to remap data sources between environments (e.g., blob storage dev → blob storage prod).

Parameter rules : used when the data source location is parameterized (for example, a parameter storing the file path or connection string).

Best practice: use parameters in the dataflow for connection strings, then apply parameter rules in deployment pipelines.

In this case, since the requirement is about ensuring the reference updates correctly, only parameter rules are needed (not data source rules).

Correct Answer:

B. Create a parameter rule only.

The df.explain() method does not meet the goal of evaluating data to calculate statistical functions. It is used to display the physical plan that Spark will execute. References = The correct usage of the explain() function can be found in the PySpark documentation.

The command:

DESCRIBE DETAIL Customer

Returns metadata about the Delta table, such as format, schema, partitioning, size, number of files, and creation/modification timestamps.

However, it does not provide information about whether maintenance tasks (such as OPTIMIZE , VACUUM , or Z-Ordering) were performed on the table.

To check maintenance history, you would typically use:

DESCRIBE HISTORY Customer

which shows operations executed on the table (e.g., OPTIMIZE, VACUUM, MERGE).

Since DESCRIBE DETAIL does not satisfy the requirement, the solution does not meet the goal.

The requirement is to copy data from CSV files in Azure Storage into a Fabric Lakehouse, and it must support Power Query M formula language .

Dataflow activity in Fabric pipelines allows you to use Power Query Online , which is based on the M formula language.

Notebook uses Spark (Python, PySpark, Scala, SQL), not M.

Copy data activity moves data but does not support Power Query M transformations.

Script is for T-SQL or stored procedure execution, not M.

Therefore, the correct activity is Dataflow .

When using XMLA endpoints to manage and update semantic models in Microsoft Fabric, the performance of write operations (such as processing, structural changes, or metadata deployments from Tabular Editor) is directly influenced by the storage format and how the model is persisted.

Why Option A is Correct

By default, Fabric semantic models use the Small semantic model storage format.

To improve write operations performance through XMLA, you must change the workspace setting to use the Large semantic model storage format.

The large format uses more efficient storage techniques, supports partitioning, and handles larger models with optimized write capabilities.

This setting is applied at the workspace level and impacts all semantic models within that workspace, including Model1.

This is explicitly documented in Microsoft’s guidance: Large semantic model storage format is required when using XMLA write operations for large or frequently updated models.

Why the Other Options Are Incorrect

B. Configure Model1 to use the Direct Lake storage format.

Direct Lake mode is designed for query performance (reading data directly from OneLake in delta format without import/duplication).

It improves query latency and freshness but does not improve XMLA write operations, which deal with model metadata and structural updates.

C. Delete any unused semantic models from Workspace1.

Deleting unused semantic models helps manage capacity and storage but does not increase the speed of XMLA endpoint write operations.

Workspace storage overhead does not directly impact the write throughput of XMLA operations.

D. Delete any unused columns from Model1.

Removing unused columns reduces the memory footprint and can improve query performance.

However, it does not directly improve the speed of XMLA write operations. The bottleneck in XMLA writes is tied to the storage format, not the model size alone.

Summary

To increase the speed of XMLA write operations on semantic models, you must enable the Large semantic model storage format at the workspace level. This setting ensures better handling of writes and metadata operations via the XMLA endpoint.

References

Large models in Power BI and Microsoft Fabric

Use the XMLA endpoint in Microsoft Fabric

Manage capacities in Microsoft Fabric

The PoC is planned to be completed using a Fabric trial capacity, which implies that users involved in the PoC should be able to try paid features. However, this should be limited to specific security groups involved in the PoC to prevent the entire organization from accessing these features before the trial is proven successful (A). The ability for users to create Fabric items should also be enabled for specific security groups to ensure that only the relevant team members participating in the PoC can create items in the Fabric environment (E).

Both a dataflow (A) and a Stored procedure activity in a pipeline (B) are capable of creating and populating a date dimension table. A dataflow can perform the transformation needed to create the date dimension, and it aligns with the preference for using low-code tools for data ingestion when possible. A Stored procedure could be written to generate the necessary date dimension data and executed within a pipeline, which also adheres to the technical requirements for the PoC.