Courseiva

CCNA Maintain a Data Analytics Solution Questions

75 of 76 questions · Page 1/2 · Maintain a Data Analytics Solution · Answers revealed

1
MCQeasy

You are maintaining a Microsoft Fabric workspace that contains a semantic model. The model is used by several reports. You need to ensure that when a new measure is added to the model, it is automatically available in all reports without manual updates. What should you do?

A.Add the measure to each report individually using the report's dataset.
B.Add the measure to the semantic model and then refresh the reports.
C.Create a new semantic model that includes the measure and update all reports to use the new model.
D.Add the measure to the semantic model and save the model. Reports connected to the model will automatically see the new measure.
AnswerD

In Microsoft Fabric, reports connect live to the semantic model. When you add a measure to the model and save it, the measure becomes part of the model metadata. Any report connected to that model will see the new measure the next time it queries the model, without requiring manual updates to each report. This is the expected behavior for shared semantic models.

Why this answer

Semantic models in Microsoft Fabric are shared data sources. When you add a measure to the model and save it, the change is propagated to all reports connected to that model. Reports query the model at runtime, so they will automatically see the new measure without any manual updates.

This centralizes measure management and ensures consistency across reports.

Exam trap

The trap here is thinking that each report needs to be updated or refreshed manually when a measure is added, when in fact shared semantic models propagate changes automatically.

2
Multi-Selecthard

You are setting up a deployment pipeline for a workspace that contains sensitive financial data. Which TWO of the following permissions or conditions are required for a user to deploy content from the Test stage to the Production stage? (Select TWO)

Select 2 answers
A.The user must be an Admin or Member of both the Test and Production workspaces.
B.The user must have the 'Pipeline Admin' role or be assigned as a pipeline user with deployment permissions.
C.The user must have a Power BI Free license and be a guest user in the tenant.
D.The Production workspace must be unassigned from the capacity before the deployment begins.
E.The user must have 'Viewer' access to the Production workspace and 'Admin' access to the Test workspace.
AnswersA, B

To move content between workspaces using a pipeline, the user needs sufficient permissions to read from the source and write to the target. In Fabric, this means having at least the 'Member' or 'Admin' role in both workspaces. This ensures that only authorized individuals can modify production content and access the source metadata.

Why this answer

To deploy content in a deployment pipeline, a user must have access to the pipeline itself (Pipeline Admin or assigned user) and must be an Admin or Member of both the source and target workspaces to perform the deployment action.

Exam trap

Candidates often confuse workspace-level 'Viewer' or 'Contributor' roles with the 'Admin' or 'Member' roles required to perform deployments.

3
MCQmedium

An Analytics Engineer notices that a Spark notebook in a Fabric Lakehouse is running significantly slower than usual. After reviewing the Spark UI, the engineer sees that one executor is processing 90% of the data while others are idle. What is the most likely cause of this performance issue?

A.The input data has a significant skew in the join or partition key, leading to unbalanced partitions.
B.The Spark notebook is using a 'Small' pool instead of a 'Large' pool for the executor nodes.
C.The 'V-order' optimization has not been applied to the underlying Parquet files in the Lakehouse.
D.The engineer is using a 'Collect' statement which pulls all data to the driver node instead of the executors.
AnswerA

Data skew occurs when certain keys in the dataset have many more records than others, causing Spark to assign a massive amount of work to a single task. This creates a bottleneck as the entire job waits for that one executor to finish. Salting the key or repartitioning the data can help redistribute the load.

Why this answer

In distributed computing environments like Spark within Fabric, performance is often dictated by how evenly data is distributed across the cluster. When one executor handles the vast majority of the work, it is known as data skew. Identifying and resolving data skew is a critical maintenance task for data engineers to ensure cost-effective and timely data processing within the Lakehouse.

Exam trap

Candidates often guess 'insufficient memory' or 'cluster configuration' issues. They fail to recognize that a single executor doing all the work is a classic symptom of data skew.

4
MCQhard

You are maintaining a Microsoft Fabric capacity that hosts multiple workspaces. Users report intermittent slow performance and occasional query failures during peak hours. You suspect that a specific workspace is consuming excessive capacity. You need to identify which items are consuming the most capacity units and when. What should you do?

A.Use the Microsoft Fabric Capacity Metrics app to analyze the capacity usage and identify the top consumers by item and time.
B.Run a DAX query against the capacity's internal logging dataset to retrieve the top consumers.
C.Use the Fabric admin portal to view the 'Capacity utilization' report and filter by workspace.
D.Open each workspace's settings and review the 'Usage metrics' report to identify the top-consuming items.
AnswerA

The Microsoft Fabric Capacity Metrics app provides detailed insights into capacity consumption, including which items (such as datasets, reports, and dataflows) are consuming the most capacity units and at what times. It helps diagnose performance bottlenecks and identify overconsumption, making it the appropriate tool for this scenario.

Why this answer

The Microsoft Fabric Capacity Metrics app is designed to monitor capacity usage, providing detailed insights into which items consume the most capacity units and when. It helps identify overconsumption and performance issues. Other options either provide unrelated usage metrics or suggest unsupported methods.

Exam trap

The trap here is confusing workspace usage metrics, which track user activity, with capacity metrics, which track resource consumption.

5
Multi-Selectmedium

You are maintaining a Microsoft Fabric workspace that uses deployment pipelines to promote items from Development to Test to Production. You need to ensure that the deployment process does not overwrite certain item properties that must differ per stage, such as data source connections and parameters. Which two actions should you take? (Choose two.)

Select 2 answers
A.Use parameters in the semantic model and set their values in each stage via deployment rules.
B.Define deployment rules for the semantic model to override the data source connection string in the Test and Production stages.
C.Create separate semantic models for each stage and deploy them independently.
D.Manually edit the connection strings in the Test and Production workspaces after each deployment.
E.Configure the deployment pipeline to skip items that have stage-specific settings.
AnswersA, B

Parameters in semantic models can be overridden using deployment rules. By defining parameters for values that differ per stage (e.g., server names, database names), you can set stage-specific values in the deployment pipeline, ensuring that the correct values are applied without manual edits after deployment.

Why this answer

Deployment rules in Fabric deployment pipelines allow you to define stage-specific configurations for supported items, including semantic models. By using parameters and data source rules, you can ensure that connections and other settings are automatically adjusted for each stage, preventing overwrites and reducing manual intervention.

Exam trap

The trap here is assuming that manual edits or separate models are necessary, when deployment rules are designed exactly for this purpose.

6
MCQhard

You are monitoring a semantic model in Microsoft Fabric that is experiencing performance degradation. You suspect that the storage engine is struggling with high-cardinality columns during Direct Lake queries. Which Dynamic Management View (DMV) should you query to identify the memory usage of specific columns in the model?

A.SELECT * FROM $System.DISCOVER_SESSION_STATISTICS
B.SELECT * FROM $System.DISCOVER_STORAGE_TABLE_COLUMN_SEGMENTS
C.SELECT * FROM $System.MDSCHEMA_MEASURES
D.SELECT * FROM $System.DISCOVER_CALC_DEPENDENCY
AnswerB

This DMV provides detailed information about the segments of data stored for each column, including their size and compression characteristics. It is the primary tool for diagnosing memory pressure issues in the VertiPaq engine. Analyzing this data allows engineers to identify high-cardinality columns that should be optimized or removed to improve performance.

Why this answer

The DMV $System.DISCOVER_STORAGE_TABLE_COLUMN_SEGMENTS provides detailed information about column segments, including memory usage, cardinality, and encoding statistics. This is the correct DMV to identify high-cardinality columns and their memory consumption in a semantic model, especially for Direct Lake queries where the storage engine performance is critical.

Exam trap

DP-600 often tests DMV selection, and candidates may confuse session-level statistics with column-level storage details, leading to wrong choices.

How to eliminate wrong answers

Option A is wrong because DISCOVER_SESSION_STATISTICS returns session-level statistics such as CPU and duration, not column-level memory usage. Option C is wrong because MDSCHEMA_MEASURES returns metadata about measures, not storage or memory details. Option D is wrong because DISCOVER_CALC_DEPENDENCY shows dependencies between calculated objects, not memory usage of columns.

7
Multi-Selectmedium

You are responsible for maintaining a Microsoft Fabric deployment pipeline that promotes items from Development to Test to Production. You need to ensure that the deployment process does not overwrite certain configurations in the target stages. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Manually edit the item definitions in the target stage after each deployment.
B.Set up deployment rules for dataflows to change the data source connections per stage.
C.Enable Git integration for the workspace and use branches for each stage.
D.Use the 'Selective deploy' option to choose only the items that have changed.
E.Configure deployment rules for the semantic model to set parameters for each stage.
AnswersB, E

Dataflows also support deployment rules, allowing you to modify data source connections for each stage. This ensures that a dataflow in Production connects to the production data source, not the development one. Without such rules, deploying a dataflow would overwrite the connection settings in the target stage. Thus, configuring deployment rules for dataflows is necessary to maintain correct connections.

Why this answer

Deployment rules in Microsoft Fabric deployment pipelines allow you to specify different configurations for each stage, such as parameters and data source connections. By configuring rules for semantic models and dataflows, you ensure that stage-specific settings are preserved during deployment. This automation reduces manual effort and prevents overwrites of critical configurations.

Exam trap

The trap here is assuming that selective deploy or Git integration automatically handles stage-specific configurations, when in fact deployment rules are required to preserve them.

8
MCQmedium

You are a Fabric analytics engineer. Your team uses a deployment pipeline to promote content from a development workspace to a test workspace. After a recent deployment, users in the test workspace report that they cannot see the latest changes to a report. You need to troubleshoot the deployment pipeline. Which action should you take first?

A.Verify that the test workspace is assigned to a capacity that supports deployment pipelines.
B.Check the deployment history to see if the deployment succeeded and which items were updated.
C.Re-deploy the report from the development workspace to the test workspace.
D.Ensure that the user has at least Contributor role in the test workspace.
AnswerB

The deployment history in a Fabric deployment pipeline provides a detailed log of each deployment, including the status, timestamp, and items affected. By reviewing the history, you can quickly determine if the deployment completed successfully and whether the report was included. If the deployment failed or the report was not updated, the history will indicate the cause, such as a conflict or missing dependency. This is the first step in troubleshooting.

Why this answer

When troubleshooting a deployment pipeline issue, the first step is to review the deployment history. This log shows whether the deployment succeeded, which items were deployed, and any errors. If the report was not updated, the history will reveal if it was excluded or if the deployment failed.

Based on that information, you can take appropriate corrective action, such as resolving conflicts or re-deploying specific items. Checking capacity or user permissions is less direct and not the first step.

Exam trap

The trap here is to immediately re-deploy or check permissions, but the deployment history provides the most direct diagnostic information.

9
MCQmedium

You maintain a Microsoft Fabric workspace that contains a Dataflow Gen2 named SalesDF. The dataflow refreshes daily from an on-premises SQL Server via a VNet data gateway. External users report that the dataflow has been failing for the past three days with an authentication error. You need to ensure the dataflow refreshes successfully without embedding credentials in the dataflow. What should you do?

A.Change the dataflow's refresh schedule to run at a different time to avoid peak load.
B.Update the credentials for the connection in the dataflow's connection settings in the Fabric workspace.
C.Modify the dataflow's M queries to use a service principal with a client secret stored in the query.
D.Recreate the VNet data gateway and reassign the dataflow to the new gateway.
AnswerB

The authentication error indicates that the stored credentials for the on-premises SQL Server connection have expired or been revoked. Updating the credentials in the dataflow's connection settings re-establishes a valid authenticated connection without hardcoding credentials. This is the standard maintenance action for resolving credential expiry in Dataflow Gen2, and it aligns with the requirement to avoid embedding credentials in the dataflow logic.

Why this answer

The failure is due to expired or invalid credentials for the on-premises SQL Server connection used by the Dataflow Gen2. The correct maintenance action is to update the stored credentials in the dataflow's connection settings, which securely reauthenticates the connection without embedding secrets in the query. Other options either misdiagnose the issue or introduce insecure practices, so they do not resolve the authentication failure.

Exam trap

The trap here is assuming that a gateway or query modification is needed, when the error specifically points to an authentication problem that is resolved by updating connection credentials.

10
MCQeasy

You manage a Microsoft Fabric workspace that contains a Lakehouse and a semantic model. The semantic model is refreshed daily from the Lakehouse. A user reports that the semantic model refresh failed last night with an error indicating that a column was not found. You need to resolve the refresh failure with minimal disruption. What should you do first?

A.Modify the Lakehouse to add back the missing column with the same name and data type.
B.Change the semantic model's data source to point to a different Lakehouse that has the column.
C.Check the refresh history in the Fabric workspace to view the error details.
D.Recreate the semantic model from scratch to ensure it matches the current Lakehouse schema.
AnswerC

The first step in troubleshooting a refresh failure is to review the refresh history, which provides detailed error messages, including the specific column name and the step where the failure occurred. This information is crucial to determine whether the column was renamed, removed, or if there is a schema mismatch. Without this, any fix would be guesswork. The refresh history is accessible from the semantic model's settings and is the standard diagnostic tool.

Why this answer

When a semantic model refresh fails due to a missing column, the first action should be to examine the refresh history for detailed error information. This reveals the exact column and step that failed, enabling a precise fix. Recreating the model, altering the Lakehouse, or switching data sources are premature and potentially disruptive.

Diagnosis through refresh history is the standard, minimal-disruption first step.

Exam trap

The trap here is jumping to recreate or modify components without first checking the refresh history, which provides the specific error details needed to resolve the issue efficiently.

11
Multi-Selectmedium

You are managing a Microsoft Fabric workspace that uses Git integration with Azure DevOps. You need to ensure that developers can collaborate on a Lakehouse and a semantic model without overwriting each other's changes. You must also ensure that changes can be reviewed before being merged into the main branch. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Configure the workspace to sync with a feature branch and require pull requests for merges into the main branch.
B.Grant all developers the Admin role on the workspace to allow them to resolve conflicts.
C.Use deployment pipelines to move changes from development to production.
D.Enable Git integration for the workspace and connect it to the Azure DevOps repository.
E.Create a separate workspace for each developer and synchronize them manually.
AnswersA, D

Syncing the workspace with a feature branch allows developers to work in isolation, and requiring pull requests for merges into the main branch enforces review before changes are integrated. This supports collaboration and prevents overwriting by ensuring changes are reviewed and merged in a controlled manner.

Why this answer

To enable collaborative development with review, the workspace must be connected to Azure DevOps via Git integration, and developers should work on feature branches with pull requests required for merging into the main branch. This combination provides isolation, prevents overwrites, and enforces review before integration.

Exam trap

The trap here is assuming that deployment pipelines or workspace roles can enforce code review, when Git branching and pull requests are the mechanisms for collaboration and review.

12
MCQmedium

You are a Fabric analytics engineer managing a workspace that contains a Lakehouse and a warehouse. A new compliance policy requires that users cannot query data from the warehouse using T-SQL if they are not members of a specific Microsoft Entra ID security group. You need to enforce this restriction without affecting access to the Lakehouse. What should you do?

A.Use SQL permissions on the warehouse to grant CONNECT to the security group and deny CONNECT to PUBLIC.
B.Assign the workspace Admin role only to the security group and remove all other users.
C.Set the warehouse's sensitivity label to 'Highly Confidential' and restrict access via Microsoft Purview.
D.Configure row-level security (RLS) on the warehouse tables to filter rows based on the user's group membership.
AnswerA

In a Fabric warehouse, T-SQL access is controlled through SQL permissions. By granting CONNECT to the specific security group and denying CONNECT to PUBLIC, you ensure that only members of that group can connect and query the warehouse. This does not affect the Lakehouse, which uses OneLake security and workspace roles, thus meeting the requirement precisely.

Why this answer

To restrict T-SQL access to a Fabric warehouse, you must use SQL permissions because the warehouse exposes a T-SQL endpoint. Granting CONNECT to the designated security group and denying CONNECT to PUBLIC ensures that only group members can connect. Other methods either affect the entire workspace or do not block connection attempts, so they fail to meet the specific requirement.

Exam trap

The trap here is assuming that workspace roles or sensitivity labels control T-SQL access to a warehouse, when in fact SQL permissions govern connection-level authorization.

13
MCQmedium

You are using the Microsoft Fabric deployment pipeline. You have successfully deployed a semantic model from Development to Test. You now realize that you need to change the 'Data Source' rule for the Test stage. What will happen to the existing items in the Test stage if you update the rule?

A.The items in the Test stage will be updated immediately to reflect the new rule.
B.The new rule will only apply the next time you deploy from Development to Test.
C.The deployment will fail because rules cannot be changed once an item is deployed.
D.The rule change will automatically trigger a refresh of the Semantic Model in Test.
AnswerB

Deployment rules are execution-time logic. To apply a modified rule to items that are already in the target stage, you must perform a 're-deployment'. This process triggers the pipeline to read the new rule and apply the specified transformations to the items as they are pushed into the Test workspace.

Why this answer

Understanding how deployment rules behave is critical for maintaining consistent environments. Rules are applied during the deployment process, not retroactively. Knowing when and how rules take effect helps engineers avoid situations where the environment is in an inconsistent state or where manual intervention is required to fix a botched deployment.

Exam trap

Candidates frequently believe that updating a deployment rule automatically triggers a re-deployment or retroactively updates existing items in the target workspace, which is incorrect as rules only apply during the deployment process.

14
MCQmedium

You manage a Microsoft Fabric workspace that contains a Dataflow Gen2 which ingests data from an on-premises SQL Server using a data gateway. The dataflow has been running successfully for months, but after a network change, it now fails with a gateway connectivity error. You need to resolve the issue with minimal administrative effort. What should you do first?

A.Restart the on-premises data gateway service on the gateway machine.
B.Reinstall the on-premises data gateway and reconfigure all data sources.
C.Verify that the gateway machine can connect to the SQL Server instance using the same credentials and network path.
D.Change the dataflow's connection to use DirectQuery instead of import.
AnswerC

Since the failure started after a network change, the first step is to validate connectivity from the gateway machine to the SQL Server. This confirms whether the network change blocked the required ports or altered routing. Using the same credentials tests authentication as well. This targeted check quickly identifies the root cause before attempting other fixes.

Why this answer

After a network change, connectivity between the gateway and the data source is the prime suspect. Validating that the gateway machine can reach the SQL Server with the correct credentials directly tests the affected path. This approach is efficient and non-disruptive.

Other actions either do not address the network change or are too invasive for a first step.

Exam trap

The trap here is assuming that restarting the gateway service will fix any connectivity error, when the error is likely due to a network change that requires configuration updates.

15
MCQhard

You are updating a semantic model in Fabric. You need to ensure that the model supports incremental refresh without duplicating data. What is the most effective approach to configure this?

A.Use an M-query to filter data by the current date.
B.Create RangeStart and RangeEnd parameters with Date/Time types.
C.Set the refresh policy to 'Full' every time.
D.Use a custom SQL query in the Power Query editor.
AnswerB

Defining parameters named RangeStart and RangeEnd with the Date/Time type is the mandatory requirement for enabling incremental refresh in Power BI. These parameters allow the engine to dynamically generate filter clauses for the data source, ensuring that only the relevant data partitions are refreshed during the automated refresh process.

Why this answer

While RangeStart and RangeEnd parameters are necessary, they are not sufficient on their own to prevent data duplication. The model must also be configured with a specific 'Incremental refresh' policy in the Power BI service/Fabric that defines the storage partition ranges and the 'Detect data changes' column (if applicable) to ensure existing data is updated rather than appended.

Exam trap

Candidates often assume that simply creating the parameters is enough to enable incremental refresh.

16
MCQmedium

You manage a Microsoft Fabric workspace containing a Lakehouse and several semantic models. You need to implement a data lineage solution that traces data transformations from the original source files ingested into the OneLake landing zone down to the Power BI reports consumed by business users. Which Fabric feature should you use to achieve this requirement natively?

A.Configure Azure Monitor workbook alerts to capture and map incoming data streaming events from OneLake to downstream reports.
B.Deploy custom Python scripts inside a Fabric notebook to extract workspace metadata using REST APIs and store relationships in an external SQL database.
C.Open the workspace lineage view to inspect visual relationships and downstream dependencies across all connected items automatically.
D.Export Power BI Desktop template files (.pbit) and analyze the data source connection strings using XMLA endpoints.
AnswerC

The workspace lineage view provides an automated visual representation showing how data flows from sources through items like notebooks and Lakehouses to final semantic models and reports, enabling effective impact analysis without writing extra code.

Why this answer

Microsoft Fabric provides built-in lineage views that automatically trace dependencies and relationships between data sources, OneLake artifacts, notebooks, and Power BI semantic models. This native integration eliminates the need for external tools and ensures governance and impact analysis can be performed seamlessly across the entire analytical lifecycle, which is vital when debugging broken pipelines or planning structural workspace modifications.

Exam trap

Candidates often assume they need to write custom Python scripts or configure external Azure Purview accounts to view basic data lineage in Fabric.

17
MCQeasy

You are a Fabric administrator for a workspace that contains a Lakehouse and a Warehouse. You need to grant a new team member the ability to read data from all items in the workspace but prevent them from modifying any data or workspace settings. What should you do?

A.Assign the team member the Contributor role in the workspace.
B.Assign the team member the Viewer role in the workspace.
C.Assign the team member the Admin role in the workspace.
D.Assign the team member the Member role in the workspace.
AnswerB

The Viewer role in a Microsoft Fabric workspace grants read-only access to all items, including Lakehouses and Warehouses. Viewers can view reports, read data, but cannot modify data, create items, or change workspace settings. This role perfectly matches the requirement to allow reading without modification.

Why this answer

In Microsoft Fabric, workspace roles define permissions. The Viewer role is designed for read-only access, allowing users to view and read data without making changes. Contributor, Member, and Admin roles all include write or manage permissions, which would not satisfy the requirement to restrict modifications.

Assigning the Viewer role ensures the team member can read data from all items but cannot alter them.

Exam trap

The trap here is confusing the Viewer role with other roles that also allow reading but include additional permissions, leading to over-provisioning.

18
MCQmedium

Refer to the exhibit. You are reviewing the Git configuration for a Microsoft Fabric workspace. A developer reports that they cannot see their latest changes in the 'dev' branch within the workspace. Based on the exhibit, what is the most likely cause of this issue?

A.The workspace is connected to a repository that does not exist in the ContosoCorp organization.
B.The developer has committed changes to the repository but the workspace has not been updated.
C.The 'directoryName' in the JSON configuration is incorrect and should be the root directory.
D.The workspace is currently in a 'Read-only' state because it is connected to a Git branch.
AnswerB

In Fabric Git integration, synchronization is not always automatic in both directions for every change. Even if the status is 'Synced', a user may need to click 'Update all' in the source control panel to pull the latest commits from the remote branch into the workspace. This manual step ensures developers control when their workspace environment changes.

Why this answer

When a workspace is synced with Git, the 'syncStatus' indicates the connection health, but the workspace must still be manually updated or 'pulled' to reflect changes made in the remote repository. Maintenance of a synced environment requires understanding that the 'Synced' status confirms the link is active, but individual items must be updated to match the branch's latest commit.

Exam trap

Candidates often assume that if a workspace is 'Synced' with Git, the workspace automatically pulls the latest changes from the remote branch, forgetting that the 'Update' action must be triggered manually.

19
Multi-Selectmedium

You need to monitor the performance of your Fabric SQL endpoint. Which two metrics should you track to ensure long-running queries are identified and optimized?

Select 2 answers
A.Total query execution time.
B.The number of users logged into the workspace.
C.CPU time consumed by individual queries.
D.The number of files in the OneLake delta table.
E.The number of dashboards generated.
AnswersA, C

Total execution time is the primary indicator of query performance. By tracking this metric, you can establish a baseline and identify outliers that exceed the expected duration, which helps in focusing optimization efforts on the most resource-intensive operations that impact the overall user experience during peak usage hours.

Why this answer

Monitoring query duration and resource consumption is essential for maintaining a healthy Fabric environment. By identifying long-running queries, you can pinpoint inefficient T-SQL code or missing indexes. Tracking these metrics enables proactive performance tuning, ensuring that the SQL endpoint remains responsive to users while keeping resource consumption within the allocated capacity limits for the workspace.

Exam trap

Candidates tend to select storage or memory capacity metrics instead of execution time and CPU consumption when diagnosing slow queries.

20
MCQeasy

You are maintaining a Microsoft Fabric workspace that contains a Lakehouse and a semantic model. You need to ensure that when new data is added to the Lakehouse, the semantic model automatically reflects the changes without manual intervention. What should you configure?

A.Set up a scheduled refresh for the semantic model every 15 minutes.
B.Create a Dataflow Gen2 that copies data from the Lakehouse to the semantic model.
C.Enable Direct Lake mode for the semantic model.
D.Configure an event stream to trigger a pipeline that refreshes the semantic model.
AnswerC

Direct Lake mode allows the semantic model to query Delta tables in the Lakehouse directly, so any changes to the underlying data are immediately visible without refresh. This provides near real-time data access and eliminates the need for scheduled refreshes, meeting the requirement for automatic reflection of new data.

Why this answer

Direct Lake mode in Microsoft Fabric enables a semantic model to read Delta tables directly from the Lakehouse, so data changes are immediately available to queries without a refresh. This is the most efficient and automatic way to keep the model in sync with the Lakehouse. Other options involve scheduled or triggered refreshes, which are not automatic and introduce latency.

Exam trap

The trap here is assuming that a scheduled refresh is sufficient for automatic updates, when it actually introduces delay and is not event-driven.

21
MCQeasy

You are a Fabric administrator for a workspace that contains a semantic model used by many reports. You need to ensure that when a user opens a report, they only see data they are authorized to view, based on their department. The semantic model already has a role named 'Department' with a DAX filter on the Department column. What should you do next?

A.Enable 'Row-level security' in the workspace settings and publish the semantic model again.
B.Create a new role named 'Department' in the workspace and add the users to that role.
C.Assign users to the 'Department' role in the semantic model and configure the role to use the USERPRINCIPALNAME() function for dynamic filtering.
D.Assign users to the 'Department' role in the semantic model and verify that they have at least Read permission on the workspace.
AnswerD

Row-level security in a semantic model requires that users be assigned to the appropriate role. Additionally, users must have at least Read permission on the workspace or be granted Build permission on the semantic model to access it. Assigning users to the role and ensuring they have the necessary workspace permission completes the RLS configuration.

Why this answer

Row-level security in a semantic model requires that users be assigned to the defined roles. Since the role already exists with the appropriate DAX filter, the next step is to assign users to that role. Additionally, users need at least Read permission on the workspace or Build permission on the model to consume the data, so verifying that permission is essential.

Exam trap

The trap here is confusing workspace roles with semantic model roles; workspace roles control item access, while model roles control row-level data access.

22
Multi-Selectmedium

You are managing a Microsoft Fabric workspace integrated with Azure DevOps. You have several developers working on the same Lakehouse and Semantic Model. Which TWO actions are required to successfully resolve a merge conflict when synchronizing changes from the remote repository to the workspace?

Select 2 answers
A.Resolve the conflict in the Azure DevOps repository or a local Git client.
B.Select the 'Update all' button in the Fabric workspace after the remote conflict is resolved.
C.Delete the conflicting items from the workspace and re-import them.
D.Use the 'Undo changes' command in the Source Control side pane.
E.Change the workspace connection to a new empty branch.
AnswersA, B

The Fabric web interface does not currently support line-by-line code merging for complex conflicts. Resolving the conflict in the repository ensures that the JSON or BIML definitions are syntactically correct and logically sound. Once the conflict is resolved in Git, the workspace can then be updated successfully.

Why this answer

Git integration in Microsoft Fabric necessitates a clear strategy for handling conflicts that arise when multiple developers modify the same items. When the workspace and the remote branch diverge, the system cannot automatically reconcile the differences. Engineers must use external tools and specific Fabric sync commands to ensure the workspace reflects the desired state without losing critical work.

Exam trap

Candidates often try to resolve Git conflicts inside the Fabric workspace interface, failing to realize that Fabric only acts as a client and cannot perform the actual merge of conflicting code.

23
MCQeasy

You need to update a sensitivity label for a high-priority dataset in a Microsoft Fabric workspace. You want the new label to automatically apply to all reports and dashboards that use this dataset. Which feature should you ensure is enabled?

A.Mandatory labeling policy
B.Lineage-based inheritance
C.Workspace default labeling
D.Service Principal authentication
AnswerB

Lineage-based inheritance allows sensitivity labels to flow from the data source to the downstream items. When you apply or change a label on a semantic model, Fabric automatically updates the labels on associated reports and dashboards. This ensures consistent data governance across the entire lifecycle of the data.

Why this answer

Maintaining security at scale in Microsoft Fabric requires automated tools to ensure data protection policies are consistent. Downstream inheritance for sensitivity labels significantly reduces the administrative burden and the risk of human error. This feature ensures that if a dataset is classified as 'Highly Confidential', all derivative works inherit that same level of protection automatically.

Exam trap

Test-takers often assume sensitivity labels propagate automatically by default, failing to realize that specific inheritance settings must be enabled for downstream assets.

24
MCQmedium

You are managing a Fabric solution and need to identify if a specific notebook is consuming excessive memory. Which Fabric tool should you use?

A.The Power BI 'Performance Analyzer'.
B.The Fabric Capacity Metrics app.
C.The Azure Monitor Log Analytics.
D.The 'Manage Gateways' interface.
AnswerB

The Capacity Metrics app provides granular visibility into the resource consumption of all Fabric items, including notebooks. It allows you to drill down into specific compute-intensive activities, making it the correct tool for identifying which processes are contributing most to the capacity's memory and CPU load.

Why this answer

The Fabric Capacity Metrics app provides detailed monitoring of capacity usage, including memory consumption by notebooks and other workloads. It aggregates metrics across the capacity and allows you to drill down to specific items, such as notebooks, to identify excessive memory usage.

Exam trap

The trap is confusing Power BI performance tools with Fabric capacity monitoring; candidates might pick Performance Analyzer because it's familiar, but it doesn't cover notebooks.

How to eliminate wrong answers

Option A is wrong because Performance Analyzer is a Power BI Desktop tool for analyzing report performance, not for monitoring Fabric notebook memory. Option C is wrong because Azure Monitor Log Analytics is for Azure resources, not directly for Fabric notebooks unless integrated, but it's not the primary tool. Option D is wrong because Manage Gateways is for on-premises data gateway management, not for monitoring notebook memory.

25
Multi-Selectmedium

You are configuring a deployment pipeline in Microsoft Fabric to manage the lifecycle of a Lakehouse and several related reports. Which TWO actions can you perform using deployment pipelines to ensure consistency across environments?

Select 2 answers
A.Apply deployment rules to change the data source connection of a semantic model.
B.Automatically convert a Power BI report into a Paginated report during the deployment.
C.Restore a deleted workspace by reverting to a previous pipeline deployment stage.
D.Compare the items in the source and target stages to identify differences before deploying.
E.Encrypt individual columns in a Lakehouse table using a custom key during the sync.
AnswersA, D

Deployment rules allow you to automatically update parameters or connection strings as items move between stages. This ensures that the test environment queries the test database while the production environment queries the production database. Without this feature, developers would have to manually update connections, which is a major source of production errors.

Why this answer

Deployment pipelines in Microsoft Fabric are designed to automate the movement of items between development, test, and production stages. They ensure that configurations are applied consistently and reduce the risk of manual errors. This automation is a cornerstone of maintaining a reliable data analytics solution, allowing for rapid iteration while preserving the stability of the production environment.

Exam trap

Candidates often mistake deployment pipelines for automated backup solutions or version control systems, failing to realize they are primarily for promoting items between stages rather than managing individual item historical versions.

26
MCQhard

You are managing a Microsoft Fabric workspace that contains a Lakehouse with sensitive data. Your organization requires that data access be audited and that users can only see data relevant to their region. You have implemented row-level security (RLS) in a semantic model. However, you discover that users can still access the underlying Lakehouse tables directly via the OneLake explorer. What should you do to enforce data security at the storage level?

A.Configure OneLake data access roles to restrict access to specific folders or tables based on user identity.
B.Use Microsoft Purview to scan and classify the data, then apply access policies.
C.Apply RLS to the Lakehouse tables using SQL security policies.
D.Enable sensitivity labels on the Lakehouse items.
AnswerA

OneLake data access roles allow you to define granular permissions on folders and tables within a Lakehouse. You can assign roles to users or groups, restricting their access to only the data they are authorized to see. This enforces security at the storage layer, independent of the semantic model. By using OneLake data access roles, you ensure that even if users bypass the semantic model, they cannot access unauthorized data directly in the Lakehouse.

Why this answer

To enforce data security at the storage level in Microsoft Fabric, you must use OneLake data access roles. These roles allow you to define granular permissions on folders and tables within a Lakehouse, ensuring that users can only access data they are authorized to see. This is separate from semantic model RLS, which only applies when querying through the model.

By configuring OneLake data access roles, you prevent direct access to sensitive data via the OneLake explorer.

Exam trap

The trap here is assuming that semantic model RLS or sensitivity labels provide storage-level security, but they do not restrict direct access to OneLake data.

27
MCQeasy

You are maintaining a Microsoft Fabric workspace that contains a Data Warehouse. You need to ensure that users can only see data relevant to their region, based on their Azure Active Directory group membership. The Data Warehouse contains a table named Sales with a column Region. You want to implement row-level security (RLS) at the Data Warehouse level. What should you do?

A.Enable dynamic data masking on the Region column to hide values based on user permissions.
B.Use Power BI row-level security (RLS) on a semantic model that connects to the Data Warehouse.
C.Create a security policy using CREATE SECURITY POLICY with a predicate function that filters rows based on the user's group membership.
D.Create a database role and assign users to it, then grant SELECT permissions on a view that filters rows by region.
AnswerC

In Microsoft Fabric Data Warehouse, row-level security is implemented using the CREATE SECURITY POLICY statement with an inline table-valued function that acts as a predicate. The function can check the user's group membership via functions like IS_MEMBER or USER_NAME, and the policy applies the filter to the specified table. This is the standard T-SQL approach for RLS in Fabric Warehouse.

Why this answer

In Microsoft Fabric Data Warehouse, row-level security is implemented using the CREATE SECURITY POLICY statement with a predicate function. This function can evaluate the user's identity and group membership to filter rows. This is the correct T-SQL-based approach and ensures that RLS is enforced regardless of how the data is accessed.

Exam trap

The trap here is confusing Power BI RLS with Data Warehouse RLS, or thinking that views or masking provide row-level security.

28
MCQhard

Refer to the exhibit. You are troubleshooting a failed automated deployment in a Microsoft Fabric environment. The deployment pipeline is triggered by a Service Principal via the REST API. Based on the error log, which maintenance action is required to resolve this issue?

A.Enable the 'Allow service principals to use Power BI APIs' setting in the tenant admin portal.
B.Generate a new client secret for the Service Principal as the current one has expired.
C.Assign the Service Principal the 'Contributor' role in the Azure subscription.
D.Add the Service Principal to the target workspace with the 'Admin' or 'Member' role.
AnswerD

The error message explicitly states that the Service Principal lacks the necessary workspace-level permissions. To perform deployment tasks, a Service Principal needs at least 'Member' or 'Admin' rights to manage items and trigger pipeline stages. Adding the principal to the workspace role list is the direct solution to resolve this specific authorization error.

Why this answer

The error log indicates that the Service Principal is failing to perform deployment pipeline operations due to insufficient permissions in the target workspace. For a Service Principal to deploy content via the Fabric REST API, it must be added to the target workspace with either the Admin or Member role, which grants the necessary rights to create and modify items. This is the required maintenance action to resolve the permission-related failure.

Exam trap

The trap is assuming that enabling tenant-level API access for Service Principals is sufficient — candidates often pick option A because they know the tenant setting is required, but they forget that workspace-level membership is also mandatory, and the error log specifically points to a workspace permission issue.

How to eliminate wrong answers

Option A is wrong because enabling 'Allow service principals to use Power BI APIs' in the tenant admin portal is a prerequisite for API access but does not grant workspace-level permissions — the Service Principal still needs to be added to the workspace. Option B is wrong because an expired client secret would cause an authentication failure (401 Unauthorized), not a permission error during deployment; the error log would typically indicate token acquisition failure. Option C is wrong because assigning the Contributor role in the Azure subscription grants Azure resource management permissions, not Fabric workspace permissions, and is irrelevant to deployment pipeline operations.

29
MCQhard

Refer to the exhibit. You receive this JSON response when checking the Git status of a Fabric workspace. What is the most appropriate next step to maintain the integrity of the Semantic Model named 'SalesModel'?

A.Commit the local changes using the 'Override Remote' flag in the Fabric API.
B.Perform a manual merge in the Git provider to consolidate the branch history.
C.Disconnect the workspace from Git and reconnect it to a fresh repository.
D.Restart the Microsoft Fabric capacity to clear the synchronization lock.
AnswerB

Since the conflict is detected at the commit level, the best practice is to resolve the logic within the Git provider. By merging the branches and resolving differences in the metadata files, you create a clean commit history. This allows the Fabric workspace to then sync to a unified state.

Why this answer

The exhibit indicates a Git synchronization conflict where changes exist in both the workspace and the remote repository. Maintenance of a production-grade solution requires resolving these discrepancies in a controlled environment. Understanding the status codes helps engineers diagnose synchronization failures and apply the correct remediation steps to ensure that the production environment remains stable and version-aligned.

Exam trap

Candidates often attempt to resolve Git conflicts directly within the Fabric workspace UI, not realizing that Fabric does not provide native tools to merge code branches and requires external Git provider intervention.

30
Multi-Selecthard

A Microsoft Fabric capacity is frequently experiencing 'Interactive Delay' during peak hours. You need to implement maintenance strategies to mitigate this without increasing the SKU size. Which TWO strategies should you prioritize?

Select 2 answers
A.Schedule large Warehouse and Lakehouse refreshes during off-peak hours.
B.Review and optimize long-running DAX queries in the most popular reports.
C.Enable 'DirectQuery' for all semantic models to reduce memory load.
D.Increase the 'Refresh Frequency' of all reports to ensure data freshness.
E.Disable the 'Smoothing' feature in the Fabric Admin portal.
AnswersA, B

Background operations like data refreshes consume capacity units that are smoothed over a 24-hour period. However, if too many occur simultaneously, they can contribute to the overall exhaustion of the capacity. Moving these tasks to quiet periods reduces the peak load, leaving more headroom for interactive user queries.

Why this answer

Managing capacity performance is essential for maintaining a responsive analytics environment. Interactive delays occur when the capacity is over-utilized, and the system throttles new requests. By optimizing the distribution of background tasks and improving query efficiency, engineers can maximize the utility of their current SKU and ensure that high-priority interactive reports remain performant.

Exam trap

Candidates often suggest scaling up the SKU as a primary maintenance strategy, ignoring the requirement to mitigate delays without increasing costs through optimization and scheduling of background tasks.

31
Multi-Selectmedium

Your organization is scaling its Microsoft Fabric implementation. You need to establish a maintenance plan for workspace administration. Which TWO practices should you implement to manage workspace security and lifecycle effectively?

Select 2 answers
A.Assign individual user permissions to each item within the workspace for granular control.
B.Use Microsoft Entra ID (formerly Azure AD) groups for workspace role assignments.
C.Create a separate capacity for every workspace to isolate resource consumption.
D.Disable the 'Tenant settings' for all users except for one global administrator.
E.Implement a workspace naming convention that includes the department and environment.
AnswersB, E

Using security groups allows administrators to manage access at scale. When a user's role changes, updating their group membership automatically updates their access across all relevant Fabric workspaces. This practice ensures consistency, simplifies auditing, and aligns with enterprise identity management standards, making it much easier to maintain a secure environment over time.

Why this answer

Option B is correct because assigning workspace roles (Admin, Member, Contributor, Viewer) to Microsoft Entra ID security groups rather than individual users centralizes access management, so onboarding, offboarding, and permission changes are handled by group membership and scale cleanly as the Fabric deployment grows. Option E is correct because a consistent workspace naming convention that encodes department and environment (for example, Finance-Prod or HR-Dev) makes workspaces discoverable, supports governance and lifecycle operations such as archival or deletion, and reduces the risk of provisioning or modifying the wrong workspace. Option A is not recommended because per-item permissions create fragmented, hard-to-audit access that does not scale; workspace-level roles inherited through groups are the supported granularity model.

Option C is wrong because dedicating a capacity per workspace multiplies cost and administrative overhead; capacities are meant to be shared by multiple workspaces with governance via domains and workspace roles. Option D is wrong because broadly disabling tenant settings for everyone except one global administrator blocks legitimate self-service and admin scenarios; tenant settings should be scoped to specific security groups that need them.

Exam trap

The trap is to over-engineer with per-item permissions or per-workspace capacities, when the exam expects scalable, group-based RBAC and standardized naming for lifecycle management.

32
MCQmedium

You have a Fabric workspace with multiple reports. You need to ensure that the dataset is shared across reports without creating multiple copies. What is the correct approach?

A.Copy the PBIX file and publish it multiple times.
B.Connect new reports to the existing published semantic model.
C.Use the 'Import' mode for every report created.
D.Embed each report in a separate workspace.
AnswerB

This approach implements a 'live connection' to the central semantic model. By decoupling the report visuals from the data, you ensure that all reports use the same metrics and data structure, simplifying updates and ensuring consistency, which is a core requirement for a well-maintained analytics environment.

Why this answer

In Microsoft Fabric, a semantic model (dataset) can be shared across multiple reports by connecting new reports to the existing published semantic model. This avoids duplicating the dataset and ensures a single source of truth. Copying the PBIX and publishing multiple times creates separate datasets, Import mode creates a new copy of the data for each report, and embedding in separate workspaces does not share the model.

Exam trap

DP-600 often tests the difference between Import mode (copies data) and DirectQuery/Live Connection (uses shared model); candidates may choose Import mode thinking it shares the model, but it actually creates a separate copy.

How to eliminate wrong answers

Option A is wrong because copying the PBIX file and publishing it multiple times creates multiple independent semantic models, leading to data duplication and maintenance overhead. Option C is wrong because using Import mode for every report means each report imports its own copy of the data, resulting in multiple datasets and potential inconsistencies. Option D is wrong because embedding each report in a separate workspace does not share the semantic model; it isolates the reports and their models, defeating the purpose of a shared dataset.

33
MCQmedium

You are a Fabric analytics engineer at a retail company. A data pipeline in your Fabric workspace loads sales data daily into a Lakehouse. Recently, the pipeline started failing intermittently with a 'Capacity limit exceeded' error. You need to ensure the pipeline runs reliably without manual intervention. What should you do first?

A.Increase the Fabric capacity SKU to a higher tier.
B.Move the pipeline to a different workspace with dedicated capacity.
C.Review the Fabric Capacity Metrics app to identify the throttling pattern and adjust pipeline schedules or optimize queries.
D.Enable autoscale for the Fabric capacity.
AnswerC

The Fabric Capacity Metrics app provides detailed telemetry on capacity usage, including which items consume the most resources and when throttling occurs. By analyzing this data, you can pinpoint whether the pipeline failures align with peak usage from other workloads or inefficient queries. Adjusting schedules to avoid overlaps or optimizing expensive operations can resolve the issue without additional cost.

Why this answer

Intermittent capacity limit errors in Fabric often stem from overlapping workloads or inefficient queries that spike resource consumption. The Fabric Capacity Metrics app is the primary tool to monitor and diagnose such issues. By examining the metrics, you can identify peak usage times and the specific items causing high consumption.

Adjusting pipeline schedules to run during off-peak hours or optimizing queries can mitigate throttling without immediate scaling.

Exam trap

The trap here is assuming that increasing capacity or enabling autoscale is the first step, but Fabric does not support autoscale and scaling should be data-driven.

34
MCQeasy

You are monitoring a Microsoft Fabric capacity and notice that certain operations are being throttled during peak hours. You need to identify which workloads are consuming the most capacity units (CUs) to optimize their usage. What should you use?

A.The Fabric admin portal's usage metrics report.
B.The Microsoft Fabric Capacity Metrics app.
C.Azure Monitor metrics for the Fabric capacity.
D.Power BI Premium Capacity Metrics app.
AnswerB

The Microsoft Fabric Capacity Metrics app provides detailed insights into capacity consumption, including CU usage by item and operation. It helps identify the top consumers and throttling events. By analyzing the reports, you can determine which workloads are causing high usage and take optimization actions. This is the recommended tool for monitoring and managing Fabric capacity.

Why this answer

The Microsoft Fabric Capacity Metrics app is designed to monitor Fabric capacity usage, providing detailed CU consumption by item and operation. It helps identify throttling causes and top consumers. This tool is essential for maintaining performance and optimizing capacity.

Other tools lack the specific granularity needed for Fabric workloads.

Exam trap

The trap here is confusing the Power BI Premium Capacity Metrics app with the Microsoft Fabric Capacity Metrics app, which are different tools for different platforms.

35
MCQmedium

Your team is adopting a Git-based workflow in Microsoft Fabric. You need to ensure that local changes made by developers in their individual workspaces do not overwrite the work of others when syncing to the shared Azure DevOps repository. Which strategy should you implement to maintain version control integrity?

A.Enable the 'Auto-commit' feature in the Fabric workspace settings for the main branch.
B.Grant all developers 'Admin' permissions on the production workspace to resolve sync conflicts.
C.Assign each developer a separate workspace connected to their own feature branch in Git.
D.Use a single shared workspace for all developers and perform manual exports of .pbip files.
AnswerC

Isolating developers in separate workspaces connected to unique feature branches prevents them from interfering with each other's work. This setup enables a clean development-to-test-to-production lifecycle where changes are merged only after validation. It supports modern DevOps practices by ensuring that the shared repository acts as the single source of truth for the project.

Why this answer

In Microsoft Fabric Git integration, each developer should work in their own workspace that is connected to a dedicated feature branch in the Git repository. This isolates local changes, allows pull requests and code review before merging into main, and prevents one developer's sync from overwriting another's work — the standard branching strategy for collaborative development.

Exam trap

DP-600 often tests whether candidates confuse workspace permissions with version control isolation, leading them to pick permission-based answers instead of the correct branch-per-developer workspace strategy.

How to eliminate wrong answers

Option A is wrong because auto-commit to the main branch would push every change directly to the shared branch, eliminating review and increasing the risk of overwriting teammates' work. Option B is wrong because granting Admin permissions does not resolve sync conflicts — permissions control access, not version control behavior, and broader permissions actually increase risk. Option D is wrong because a single shared workspace with manual .pbip exports is an anti-pattern that bypasses Git integration entirely and creates file-based conflicts rather than proper branch merges.

36
Multi-Selecthard

You are a Fabric administrator for a workspace that uses a deployment pipeline to promote content from Development to Test to Production. You need to ensure that the deployment process follows best practices for data and security. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Configure deployment rules to parameterize data source connections for each stage.
B.Use the same data source for all stages to simplify configuration and reduce errors.
C.Assign workspace permissions to users based on their role in each stage (e.g., developers have Contributor in Development, viewers have Viewer in Production).
D.Grant all users in the workspace the Admin role to ensure they can troubleshoot issues in any stage.
E.Enable automatic deployment after each successful data refresh in Development.
AnswersA, C

Deployment rules allow you to change data source connections and parameters per stage, ensuring that Test and Production use their respective data sources. This prevents Development data from being used in Production and is a best practice for deployment pipelines. It also supports environment-specific configurations without manual edits.

Why this answer

Best practices for deployment pipelines include using deployment rules to parameterize connections per stage and assigning stage-specific permissions. These actions ensure data isolation and security. Automatic deployment and uniform data sources are not recommended, and broad admin rights should be avoided.

Exam trap

The trap here is assuming that simplifying configuration by using the same data source or granting broad permissions is acceptable, when it undermines security and isolation.

37
MCQmedium

Refer to the exhibit. You are reviewing an organization's Fabric security policy. Based on the provided JSON snippet, what is the impact of this policy on your data analytics solution?

A.Users can export data from individual reports if they have Owner permissions.
B.The policy prevents users from exporting data from all reports within the workspace.
C.The policy allows exporting if the data is anonymized.
D.The policy only affects users with the Guest role.
AnswerB

The policy explicitly targets the DataExport action across the entire workspace for all users. This effectively disables the export functionality in the Power BI user interface, ensuring that sensitive data used in reports cannot be extracted into external files, thereby maintaining strict control over data distribution policies.

Why this answer

This policy implements a governance guardrail that prevents users from exporting data out of the Fabric workspace. In an enterprise environment, this is crucial for maintaining compliance and preventing data exfiltration. By controlling the export action at the workspace level, you ensure that sensitive insights remain contained within the secure Microsoft Fabric boundary, regardless of user permissions.

Exam trap

Candidates sometimes misinterpret workspace security policies as affecting row-level data security or dataset refresh schedules instead of their actual governance scope.

38
MCQmedium

Your organization uses a Fabric workspace for sensitive financial reporting. You need to implement Row-Level Security (RLS) to ensure that regional managers only see data from their own regions. Where should you define this security logic?

A.Define the RLS in each individual Power BI report.
B.Define the RLS in the workspace security settings.
C.Define the RLS in the Power BI semantic model.
D.Define the RLS at the SQL endpoint of the Lakehouse.
AnswerC

The semantic model is the centralized location for RLS definitions. Applying security at this level ensures that all reports and tools consuming the model respect the filtering rules. This centralized approach guarantees consistency, simplifies management, and provides a clear audit trail for compliance requirements regarding sensitive data access.

Why this answer

Defining RLS within the semantic model is the industry standard for ensuring consistency across all reports that connect to that model. By centralizing security logic, you ensure that no matter which report or dashboard a user accesses, the data filtering is applied uniformly. This provides a robust security layer that is easy to audit and manage, preventing accidental exposure of sensitive financial information.

Exam trap

Candidates might mistakenly believe that RLS can be configured at the workspace level or directly on the Lakehouse SQL endpoint, as these are common locations for other types of access control.

39
MCQhard

Refer to the exhibit. An engineer receives this JSON response when checking the status of a Fabric workspace. What is the most appropriate next step to resolve the 'SyncingError' while ensuring that the workspace and the remote repository are aligned?

A.Use the Azure DevOps UI to create a Pull Request that merges the conflicting changes into the main branch.
B.Disconnect the workspace from Git and then immediately reconnect it to force a hard reset of the metadata.
C.Increase the Fabric Capacity size to allow for more concurrent synchronization threads to handle the conflict.
D.Change the 'branch' value in the Git configuration to a new empty branch and then sync the workspace.
AnswerA

When Fabric identifies a conflict that prevents synchronization, the most reliable method is to use Azure DevOps to manage the merge. This allows the engineer to view the specific JSON differences in the report or dataset definition. Once the merge is completed and the branch is updated, the workspace can successfully sync.

Why this answer

This exhibit shows a common synchronization error where the Fabric workspace and the Git repository have diverged. To maintain a healthy analytics solution, the engineer must reconcile these differences. In this scenario, the 'SyncingError' indicates that the Fabric UI cannot resolve the path automatically.

The engineer needs to use the Git provider's tools to perform a manual merge of the metadata files.

Exam trap

Candidates often try to resolve Git synchronization conflicts directly inside the read-only Fabric workspace UI rather than handling merges via the external Git repository provider.

40
MCQmedium

You are a Fabric administrator for a workspace that contains a Lakehouse, a Warehouse, and several semantic models. A developer reports that a scheduled refresh of a semantic model failed with a 'credentials expired' error. You need to resolve this issue with the least administrative effort. What should you do?

A.Recreate the semantic model and rebind the reports to the new model.
B.In the semantic model settings, update the data source credentials and then refresh the model.
C.Restart the Fabric capacity that hosts the workspace.
D.Modify the gateway connection used by the semantic model to use a different gateway.
AnswerB

Updating the data source credentials in the semantic model settings directly addresses the expired credentials. This is the least administrative effort because it targets the specific failing component without affecting other items. After updating, a manual refresh validates the fix. This approach is standard for credential-related refresh failures in Microsoft Fabric.

Why this answer

The refresh failure is due to expired credentials for the data source. The most direct and least effort solution is to update the credentials in the semantic model settings and then refresh. Other options involve unnecessary recreation, capacity restart, or gateway changes that do not address the credential expiration and may cause additional disruption.

Exam trap

The trap here is assuming that a broader infrastructure change, such as restarting the capacity or switching gateways, will resolve a credential-specific error.

41
MCQhard

You are optimizing a Fabric Lakehouse that contains a large Delta table named FactSales, which is partitioned by Year and Month. Users frequently run queries that filter on Year and Month, but also on a column named Region. You notice that queries filtering on Region alone perform poorly because they scan all partitions. You need to improve performance for Region-based queries without duplicating data. What should you do?

A.Create a materialized view that aggregates FactSales by Region and refresh it on a schedule.
B.Enable Z-Ordering on the Region column using the OPTIMIZE command with ZORDER BY.
C.Add a columnstore index on the Region column.
D.Repartition the Delta table by Region instead of Year and Month.
AnswerB

Z-Ordering on Region co-locates related data within each partition, improving data skipping for Region filters without changing the partition scheme. This maintains Year/Month partitioning while enhancing Region query performance. It does not duplicate data and is a native Delta Lake optimization supported in Fabric.

Why this answer

Z-Ordering on the Region column using OPTIMIZE with ZORDER BY reorganizes data within each partition to co-locate similar values. This allows Delta Lake's data skipping to prune files more effectively when filtering on Region, without changing the partition structure. It is the correct native optimization for this scenario.

Exam trap

The trap here is thinking that repartitioning is the only way to improve filter performance, or that indexes are available in Lakehouse.

42
Multi-Selectmedium

You are responsible for maintaining the performance of a Microsoft Fabric capacity. You need to identify which items are causing 'Throttling' and 'Rejection' of queries. Which THREE metrics should you prioritize in the Microsoft Fabric Capacity Metrics app?

Select 3 answers
A.CU (Capacity Unit) consumption by item and operation type.
B.The total number of guest users invited to the Fabric tenant.
C.The 'Burndown' of overages and the current 'Smoothing' window status.
D.The percentage of 'Background' vs 'Interactive' rejection events.
E.The storage size of all Delta tables across all Lakehouses in the capacity.
AnswersA, C, D

Tracking CU consumption allows you to identify which specific reports, notebooks, or dataflows are using the most resources. By breaking this down by operation type (interactive vs. background), you can see if the load is coming from user queries or scheduled data processing tasks. This is the first step in diagnosing why a capacity might be reaching its limits.

Why this answer

To identify throttling and rejection, you must monitor the 'Throttling' and 'Rejection' charts specifically provided in the Fabric Capacity Metrics app. Option A helps identify the source item, Option C explains why the capacity is in a state where it might throttle (overages/smoothing), and Option D directly addresses the rejection events. The explanation should explicitly mention these specific charts/metrics.

Exam trap

Candidates often confuse general capacity monitoring (storage/users) with performance-specific throttling metrics.

43
MCQhard

You are managing a Microsoft Fabric capacity that hosts multiple workspaces. A critical Power BI report in one workspace is experiencing performance degradation during peak hours. You suspect that another workspace's Spark job is consuming excessive capacity resources. You need to identify which item is causing the high resource usage and when it occurs. What should you use?

A.The Fabric admin portal's usage metrics report, sorting by user and activity.
B.Azure Monitor metrics for the Fabric capacity, reviewing the CPU and memory utilization over time.
C.The Microsoft Fabric Capacity Metrics app, filtering by workspace and item, and analyzing the timepoints for high CU usage.
D.Power BI Premium Capacity Metrics app, filtering by dataset and refresh history.
AnswerC

The Microsoft Fabric Capacity Metrics app provides detailed consumption data at the workspace and item level, including timepoint analysis. By filtering for the affected workspace and examining the timepoints with high capacity unit (CU) usage, you can pinpoint the Spark job or other item causing the bottleneck during peak hours. This directly addresses the need to identify the culprit and its timing.

Why this answer

The Microsoft Fabric Capacity Metrics app is designed to monitor capacity consumption across all Fabric items, including Spark jobs. It provides granular data by workspace, item, and timepoint, allowing you to correlate high CU usage with specific activities. Filtering by the affected workspace and analyzing timepoints reveals the Spark job causing the bottleneck during peak hours.

Exam trap

The trap here is confusing Azure Monitor or Power BI-specific metrics apps with the Fabric Capacity Metrics app, which is the only tool that provides item-level CU consumption for all Fabric workloads.

44
MCQmedium

You need to automate the deployment of Fabric items across Development, Test, and Production environments. Which tool is the standard for managing these lifecycle stages?

A.Power BI Desktop export files.
B.Fabric Deployment Pipelines.
C.Manual copy-paste of items in the workspace.
D.Azure Data Factory pipelines.
AnswerB

Deployment pipelines are specifically designed to manage the promotion of Fabric items across development, test, and production stages. They provide a native, integrated interface for comparing workspace content and deploying changes, which is the standard approach for ensuring a controlled and reliable release management process for data projects.

Why this answer

Deployment pipelines are the integrated tool within Fabric for managing the lifecycle of your analytics solution. By automating the promotion of content across different stages, you reduce manual errors and ensure that your production environment remains stable and consistent. This is a fundamental practice in professional data engineering, ensuring that updates are tested thoroughly before they affect the end users in the production environment.

Exam trap

Candidates often suggest using external CI/CD tools like Azure DevOps or GitHub Actions manually without considering the native Fabric lifecycle tool.

45
MCQmedium

You are the administrator of a Microsoft Fabric workspace that contains a Lakehouse, a Warehouse, and several semantic models. A new data engineer joins the team and needs to be able to create and modify items in the workspace but must not be able to grant permissions to other users or delete the workspace. Which workspace role should you assign?

A.Admin
B.Member
C.Viewer
D.Contributor
AnswerD

Contributor can create and edit items in the workspace but cannot manage access or delete the workspace. This matches the requirement: the engineer can work with Lakehouse, Warehouse, and semantic models, but cannot grant permissions to others or delete the workspace. Contributor is the least privileged role that still allows item creation and modification.

Why this answer

The Contributor role allows creating and editing workspace items such as Lakehouse, Warehouse, and semantic models, but does not allow managing workspace access or deleting the workspace. Admin and Member are too permissive because they can grant permissions, while Viewer cannot create or modify items. Contributor satisfies the least-privilege requirement.

Exam trap

The trap here is assuming that Member is the least privileged role that can create items, when in fact Member can also share and grant permissions.

46
Multi-Selecthard

You are auditing security in a Fabric workspace. You need to identify which two actions are required to ensure that a user can view a report without having access to the underlying Lakehouse files. Which two actions should you perform?

Select 2 answers
A.Assign the user the Viewer role in the workspace.
B.Grant the user the Contributor role in the workspace.
C.Share the semantic model with 'Build' permission.
D.Grant the user access to the Lakehouse folder via OneLake.
E.Add the user to the workspace Admin role.
AnswersA, C

The Viewer role provides read-only access to the items within the workspace, such as Power BI reports and semantic models, without granting the user the ability to browse or download the files located in the underlying Lakehouse storage. This effectively isolates the reporting content from raw storage access.

Why this answer

Restricting access requires a separation of concerns between the reporting layer and the data storage layer. By leveraging workspace roles and specific semantic model permissions, you enforce the principle of least privilege. This ensures that business users can consume data through Power BI visuals while the sensitive raw data files in OneLake remain protected from direct file-level access.

Exam trap

Candidates frequently grant workspace Contributor or Admin rights to users who only need to view reports, violating the principle of least privilege regarding underlying files.

47
MCQmedium

You are maintaining a Microsoft Fabric workspace that contains a Lakehouse with many Delta tables. You need to optimize the storage and query performance of these tables. You notice that many small files are being created due to frequent incremental loads. Which action should you take to improve performance?

A.Use the VACUUM command to remove old files and reduce storage.
B.Run the OPTIMIZE command on the Delta tables to compact small files.
C.Enable partitioning on the Delta tables by a high-cardinality column.
D.Convert the Delta tables to Parquet format.
AnswerB

The OPTIMIZE command in Delta Lake compacts small files into larger ones, reducing the number of files and improving query performance. In Fabric Lakehouse, you can run OPTIMIZE on Delta tables using Spark notebooks or the Lakehouse API. This is the standard maintenance operation to address the small file problem caused by frequent incremental loads.

Why this answer

The OPTIMIZE command is designed to compact small files in Delta tables, which directly addresses the performance degradation caused by frequent incremental loads creating many small files. It improves query performance by reducing the number of files that need to be read.

Exam trap

The trap here is confusing VACUUM with OPTIMIZE, or thinking that partitioning or format conversion solves the small file problem.

48
MCQhard

You maintain a Fabric capacity that hosts a real-time streaming workload and several Power BI semantic models. Users report intermittent report timeouts during peak hours, while the streaming workload continues without errors. You need to identify whether the semantic models are being throttled due to capacity limits. Which tool should you use?

A.The Fabric Capacity Metrics app to review throttling and overload patterns.
B.The semantic model's Performance Analyzer in Power BI Desktop.
C.Azure Monitor metrics for the Fabric capacity resource.
D.The Fabric admin portal's usage metrics reports.
AnswerA

The Microsoft Fabric Capacity Metrics app provides detailed telemetry on capacity utilization, including throttling events, overload minutes, and per-item consumption. It shows which workloads are being throttled and when, allowing you to correlate report timeouts with capacity pressure. This is the designated tool for diagnosing capacity-level performance issues, making it the correct choice for identifying whether semantic models are affected by throttling.

Why this answer

The Fabric Capacity Metrics app is purpose-built to monitor capacity health, showing throttling, overload, and consumption by item and workload. It lets you pinpoint whether semantic models are being throttled during peak hours and correlate that with user-reported timeouts. Other tools either focus on client-side performance, provide limited capacity-level detail, or track usage rather than throttling.

Exam trap

The trap here is assuming that Azure Monitor or Performance Analyzer can reveal capacity throttling, when only the Capacity Metrics app provides the required item-level throttling telemetry.

49
MCQeasy

You are setting up a new Fabric workspace that will contain sensitive financial data. You need to ensure that only specific users can view the data in reports, and that row-level security (RLS) is enforced for all consumers. What should you configure?

A.Apply sensitivity labels to the reports and semantic models.
B.Create security groups in Microsoft Entra ID and assign them to workspace roles.
C.Enable OneLake data access roles on the lakehouse.
D.Define RLS roles and rules in the semantic model and assign users to those roles.
AnswerD

Row-level security is implemented within the semantic model by defining roles with DAX filter expressions and then assigning users or groups to those roles. When consumers view reports, the model filters data according to their role membership. This directly enforces that each user sees only the rows they are permitted to see, meeting the requirement for sensitive financial data. It works in Fabric for semantic models in Import, DirectQuery, and Direct Lake modes.

Why this answer

Enforcing row-level security requires defining roles and DAX filter rules in the semantic model and assigning users to those roles. This ensures that each consumer sees only the data they are authorized to view, regardless of report design. Workspace roles, sensitivity labels, and OneLake data access roles address access, classification, or storage permissions but do not filter rows within reports.

Exam trap

The trap here is confusing workspace roles or sensitivity labels with row-level security, when only RLS roles in the semantic model filter rows by user identity.

50
Multi-Selecthard

You are optimizing a Lakehouse for performance. Which three actions help improve the query performance for users accessing the SQL endpoint?

Select 3 answers
A.Enable V-Order on the Delta tables.
B.Increase the number of small files in the table.
C.Apply partition columns to heavily filtered fields.
D.Convert all tables to CSV format.
E.Run the OPTIMIZE command periodically.
AnswersA, C, E

V-Order is a technique in Delta Lake that optimizes the Parquet file structure for read operations. It improves the performance of reads by aligning data in a way that allows the engine to skip unnecessary data blocks, which significantly accelerates query execution for users accessing the SQL endpoint.

Why this answer

Optimizing the SQL endpoint performance involves physical data design choices. By utilizing efficient file formats, partition strategies, and optimization tools, you reduce the workload on the query engine. These steps are crucial for ensuring that the SQL endpoint can handle high-concurrency analytical workloads, providing users with fast data access and a responsive reporting experience in the Fabric ecosystem.

Exam trap

Examinees often overlook V-Order and rely solely on traditional indexing, forgetting that Fabric Lakehouse query performance heavily depends on Delta-specific optimizations.

51
MCQmedium

A data engineer is working in a Microsoft Fabric workspace integrated with an Azure DevOps Git repository. After making several changes to a semantic model, the engineer attempts to commit the changes, but a conflict is detected because another team member modified the same model. What is the recommended workflow to resolve this conflict and maintain the integrity of the workspace?

A.Resolve the conflict in the Azure DevOps repository by performing a merge or rebase, then update the Fabric workspace.
B.Delete the local workspace item and pull the latest version from the Git repository to overwrite your local changes.
C.Select the 'Auto-Merge' button in the Fabric Source Control pane to allow the service to reconcile the JSON differences.
D.Create a new workspace, connect it to the same branch, and manually copy the changes from the old workspace to the new one.
AnswerA

Conflict resolution must occur in the remote repository like Azure DevOps by performing a merge or rebase operation. Fabric cannot automatically merge logical conflicts within the Power BI report's visual layout or underlying model definitions. This process ensures that all changes are intentionally integrated before the workspace is synchronized with the latest commit.

Why this answer

Git integration in Microsoft Fabric allows multiple developers to work on the same workspace items concurrently. When conflicts occur because two developers modified the same report metadata, the Fabric service requires manual intervention via the Git provider. This ensures version control integrity and prevents accidental overwrites of complex JSON definitions, which is critical for maintaining a stable production environment in collaborative engineering teams.

Exam trap

Candidates often assume they can resolve Git conflicts directly within the Fabric UI. They forget that Fabric requires the source control provider (Azure DevOps) to handle the actual merge logic.

52
MCQhard

You are maintaining a Microsoft Fabric capacity that hosts several semantic models with Direct Lake mode. Users report intermittent query failures and slow performance during peak hours. You observe that the capacity is frequently throttled. You need to identify the cause and implement a solution that minimizes impact on critical reports. What should you do?

A.Configure workload isolation by assigning critical reports to a separate workspace with its own capacity.
B.Enable autoscale for the Fabric capacity to handle peak loads.
C.Use the Microsoft Fabric Capacity Metrics app to identify the top consumers and optimize or reschedule their workloads.
D.Increase the capacity size by purchasing a higher SKU.
AnswerC

The Capacity Metrics app provides detailed insights into resource consumption, including which items and users are consuming the most capacity units. By identifying top consumers, you can optimize inefficient queries, reduce refresh frequency, or reschedule non-critical workloads to off-peak hours. This directly addresses throttling by reducing overall load and ensuring critical reports have sufficient resources, aligning with the need to minimize impact on critical reports.

Why this answer

Throttling occurs when the Fabric capacity exceeds its allowed resource consumption. The most effective maintenance action is to use the Capacity Metrics app to pinpoint which items or users are driving high consumption, then optimize or reschedule those workloads. This reduces overall load and preserves capacity for critical reports, directly resolving the intermittent failures and slowness without unnecessary cost or architectural changes.

Exam trap

The trap here is assuming that scaling up the capacity or isolating workloads is the only way to resolve throttling, when in fact identifying and optimizing top consumers is the recommended first step.

53
MCQmedium

You are managing a Microsoft Fabric workspace. You notice that a specific Power BI report is failing to refresh due to a performance bottleneck in the underlying DirectLake semantic model. Which action should you take to optimize the query execution without changing the data source?

A.Switch the storage mode to Import for all tables.
B.Enable Query Caching in the semantic model settings.
C.Remove unused columns from the semantic model schema.
D.Increase the workspace capacity SKU level.
AnswerC

DirectLake performance is heavily impacted by the number of columns loaded into memory. Removing unused columns minimizes the memory footprint and reduces the data transfer overhead from OneLake, which directly improves query response times and prevents refresh failures caused by memory-intensive operations during complex analytical processing.

Why this answer

DirectLake mode does not 'refresh' data in the traditional sense; it reads data directly from OneLake Parquet files. The performance bottleneck in DirectLake is typically related to memory pressure or inefficient DAX queries scanning too many columns. Removing unused columns reduces the memory footprint and improves scan performance, which is the correct optimization strategy for DirectLake.

Exam trap

Candidates often confuse DirectLake with Import mode, assuming that 'refresh' is the issue. DirectLake performance is about query execution efficiency, not data ingestion/refresh.

54
MCQmedium

You manage a Fabric workspace with a lakehouse that stores Delta tables. A data engineer accidentally deletes a folder containing several Parquet files from the lakehouse. You need to recover the deleted files as quickly as possible. What should you do?

A.Recreate the deleted folder and copy the files from a backup in Azure Blob Storage.
B.Use the Delta table time travel feature to query the previous version.
C.Restore the lakehouse from a workspace version history snapshot.
D.Recover the files from the OneLake recycle bin within the retention period.
AnswerD

OneLake soft delete retains deleted files and folders in a recycle bin for a configurable period, typically 7 days by default. You can restore them directly from the recycle bin via the Lakehouse explorer or OneLake APIs. This is the fastest and most direct method to recover the accidentally deleted Parquet files, provided the deletion occurred within the retention window and the files have not been permanently purged.

Why this answer

OneLake soft delete provides a recycle bin that retains deleted files and folders for a configurable retention period, enabling quick restoration. This is the native and fastest way to recover accidentally deleted Parquet files. Workspace version history restores item definitions, Delta time travel reads historical table versions but cannot restore missing files, and external backups may not exist.

Exam trap

The trap here is conflating Delta time travel or workspace version history with file-level recovery, when only the OneLake recycle bin restores deleted files to their original location.

55
MCQhard

A Lakehouse in your Fabric environment has grown significantly over time, and you notice that query performance on the Delta tables is decreasing. You also want to minimize storage costs by removing older versions of data files that are no longer needed for 'Time Travel'. Which maintenance strategy should you implement?

A.Run a Spark notebook that executes the 'REORG' command on all tables.
B.Schedule a notebook to run 'OPTIMIZE' followed by 'VACUUM' on the tables.
C.Enable the 'Auto-shrink' property in the Lakehouse settings to manage storage.
D.Delete the Lakehouse and recreate it from the original data sources weekly.
AnswerB

This is the standard maintenance pattern for Delta tables. 'OPTIMIZE' consolidates small files into larger ones to speed up reads, and 'VACUUM' deletes files that are older than a specific retention period (default 7 days). This combination addresses both the performance degradation caused by many small files and the increased storage costs from excessive historical data versions.

Why this answer

Regular maintenance of Delta tables is essential for both performance and cost management in Microsoft Fabric. The OPTIMIZE command improves data layout for faster reads, while the VACUUM command removes obsolete files. Together, these operations keep the Lakehouse efficient by ensuring that only necessary, well-structured data is retained and processed during queries, preventing 'file sprawl' in the underlying storage.

Exam trap

Candidates often suggest only running OPTIMIZE or only running VACUUM, failing to recognize that OPTIMIZE improves read performance while VACUUM is specifically required to physically remove the old, unneeded data files.

56
MCQmedium

You have a Microsoft Fabric workspace with a Lakehouse that contains a Delta table. You need to ensure that when new data is appended, the table's metadata is automatically updated and the changes are immediately visible to queries without manual intervention. What should you do?

A.Use the OPTIMIZE command after each append.
B.Enable schema evolution on the table.
C.Write data using the Delta format and rely on the transaction log.
D.Create a materialized view on the table.
AnswerC

Delta Lake maintains a transaction log that automatically records all changes, including appends. When new data is written in Delta format, the log is updated atomically, and queries immediately see the new data. This satisfies the requirement without manual intervention.

Why this answer

Delta Lake's transaction log automatically tracks all data modifications, including appends, and ensures atomicity and immediate visibility. Writing in Delta format leverages this behavior. OPTIMIZE, schema evolution, and materialized views do not provide automatic metadata updates and immediate visibility for appends.

Exam trap

The trap here is thinking that OPTIMIZE or schema evolution automatically updates metadata for new data, when Delta's transaction log already handles it.

57
MCQhard

You are managing a Fabric solution and need to move a workspace between capacities to optimize costs. What is the impact of this operation on your existing DirectLake reports?

A.The reports will automatically switch to Import mode.
B.The operation is seamless and has no impact on report performance.
C.The reports may experience performance degradation if the new capacity is smaller.
D.The reports will be deleted and must be recreated.
AnswerC

DirectLake performance is directly tied to the memory and compute available in the assigned capacity. Moving to a smaller capacity reduces the available resources, which can lead to slower query response times or memory-related errors when the engine processes large analytical queries against the underlying Parquet files in OneLake.

Why this answer

Moving a workspace between capacities in Microsoft Fabric can impact DirectLake reports because DirectLake relies on the capacity's resources to query Delta tables directly. If the new capacity is smaller (e.g., fewer compute resources), report performance may degrade due to reduced throughput and higher latency. The operation itself is seamless in terms of not requiring report recreation, but performance is not guaranteed to be unaffected.

Exam trap

DP-600 often tests the implications of capacity changes on different storage modes, and candidates may incorrectly assume that moving a workspace has no impact or that reports will switch modes automatically.

How to eliminate wrong answers

Option A is wrong because DirectLake reports do not automatically switch to Import mode; they remain in DirectLake mode unless manually changed. Option B is wrong because the operation is not guaranteed to have no impact; performance can degrade if the new capacity is smaller. Option D is wrong because reports are not deleted; they remain intact and continue to function, albeit possibly with different performance characteristics.

58
MCQmedium

You are monitoring a Microsoft Fabric capacity. You notice that during peak hours, the capacity is frequently throttled, causing delays in report rendering and data refreshes. You need to identify which workloads are consuming the most capacity units (CUs) and optimize them. Which tool should you use?

A.The Fabric admin portal's usage metrics.
B.Azure Monitor metrics for the Fabric capacity.
C.The Microsoft Fabric Capacity Metrics app.
D.The Power BI usage metrics report.
AnswerC

The Microsoft Fabric Capacity Metrics app provides detailed insights into capacity usage, including CU consumption by workload, item, and operation. It helps identify the top consumers during peak times, enabling targeted optimization. This is the designated tool for monitoring and analyzing capacity performance in Fabric.

Why this answer

The Microsoft Fabric Capacity Metrics app is specifically designed to monitor capacity usage, providing detailed breakdowns of CU consumption by workload, item, and operation. It helps identify the most resource-intensive operations during peak periods. Other tools like Azure Monitor or the admin portal do not offer the same level of detail for Fabric workloads, making the Capacity Metrics app the correct choice.

Exam trap

The trap here is assuming that Azure Monitor or the admin portal provides the same granular CU analysis as the dedicated Capacity Metrics app.

59
MCQmedium

You are troubleshooting a scheduled refresh failure for a Dataflow Gen2 in Microsoft Fabric. The error log indicates that the destination lakehouse is inaccessible. What is the most likely cause?

A.The dataflow is missing the required compute capacity.
B.The gateway connection string is incorrectly formatted.
C.The dataflow identity lacks the necessary permissions to write to the Lakehouse.
D.The source data is too large for the dataflow to process.
AnswerC

Dataflows require explicit write permissions to the destination Lakehouse. If the user or service principal running the dataflow does not have at least 'Contributor' or 'Member' rights in the workspace where the Lakehouse resides, the refresh operation will fail to write data, triggering the access error.

Why this answer

Dataflow Gen2 in Microsoft Fabric uses the workspace identity or the user's credentials to write to a destination Lakehouse. If the destination is inaccessible, the most common cause is that the Dataflow's identity (or the service principal/user configured for the connection) lacks the 'Contributor' or 'Member' role on the workspace containing the Lakehouse, or specific write permissions on the Lakehouse item itself.

Exam trap

Candidates often confuse Dataflow Gen2 with Dataflow Gen1, which relies on On-premises Data Gateways. Dataflow Gen2 in Fabric is cloud-native and does not use gateway connection strings for internal Fabric Lakehouse destinations.

60
MCQeasy

You need to perform maintenance on a shared Lakehouse in Microsoft Fabric. Before making schema changes, you want to identify which downstream reports and semantic models will be affected. Which tool should you use?

A.The Capacity Metrics app to check for active user sessions on the Lakehouse.
B.The SQL analytics endpoint to query the system metadata tables for dependencies.
C.The 'Monitor' hub to view the history of data refresh operations for all items.
D.The Lineage view in the workspace to perform an impact analysis on the Lakehouse.
AnswerD

Lineage view provides a graphical representation of the relationships between all items in a workspace and across workspaces. By selecting the Lakehouse and viewing its impact analysis, you can see every downstream semantic model and report. This is the standard method in Fabric for identifying dependencies before performing maintenance or updates.

Why this answer

Lineage view and impact analysis are essential for maintaining data integrity in a complex Fabric ecosystem. They provide a visual map of dependencies, allowing engineers to understand the consequences of their changes. This proactive approach prevents breaking downstream assets and helps in communicating maintenance windows to the appropriate stakeholders who rely on the affected data.

Exam trap

Candidates often search for code-based or Spark auditing utilities rather than using the built-in visual dependency tracking tools available directly in the Fabric workspace.

61
MCQhard

You are managing a Microsoft Fabric capacity that hosts multiple workspaces. Users report intermittent slow performance in Power BI reports. You need to identify which workload is consuming the most capacity resources during peak hours. What should you use?

A.The Power BI usage metrics report.
B.The Microsoft Fabric Capacity Metrics app.
C.The Fabric admin portal audit logs.
D.The workspace lineage view.
AnswerB

The Microsoft Fabric Capacity Metrics app provides detailed insights into capacity usage, including which workloads (e.g., Power BI, Data Factory) consume the most resources over time. It helps identify bottlenecks and optimize performance. This is the designated tool for monitoring capacity consumption and meets the requirement to identify the top consumer.

Why this answer

The Microsoft Fabric Capacity Metrics app is specifically designed to monitor and analyze capacity usage across workloads. It provides detailed reports on resource consumption, enabling administrators to pinpoint which items or workloads are causing performance issues. This directly addresses the need to identify the top capacity consumer during peak hours.

Exam trap

The trap here is confusing usage metrics (who viewed reports) with capacity metrics (which workloads consume resources).

62
MCQhard

You are troubleshooting a Microsoft Fabric Lakehouse that is experiencing slow query performance when using SQL endpoints. You notice that many small Parquet files are being generated by frequent data ingestion jobs. What should you do to improve query performance?

A.Enable V-Order optimization on the Lakehouse.
B.Partition the Delta tables by ingestion date.
C.Increase the capacity size of the Fabric capacity.
D.Run the OPTIMIZE command on the Delta tables to compact small files.
AnswerD

The OPTIMIZE command in Delta Lake compacts small files into larger ones, reducing the number of files and improving query performance by minimizing overhead. This directly addresses the issue of many small Parquet files caused by frequent ingestion, making it the correct solution.

Why this answer

Frequent data ingestion can create many small Parquet files in Delta tables, leading to slow queries due to file overhead. The OPTIMIZE command compacts these small files into larger ones, significantly improving read performance. While V-Order, capacity scaling, and partitioning have their uses, they do not directly address the small file problem.

Therefore, running OPTIMIZE is the correct action.

Exam trap

The trap here is assuming that partitioning or increasing capacity will solve small file issues, when compaction is the targeted remedy.

63
MCQmedium

Refer to the exhibit. A notebook in your Fabric workspace is failing with the provided error. What is the most likely cause?

A.The file does not exist in the specified path.
B.The notebook identity lacks read access to the OneLake item.
C.The capacity SKU is out of memory.
D.The notebook syntax is incorrect.
AnswerB

The 403 Forbidden error is a classic authorization failure. It confirms that the identity performing the request is authenticated but does not have the required permissions granted at the workspace or item level to read from the requested path in OneLake, necessitating an update to the access policies.

Why this answer

The error shown in the exhibit is likely an access denied or unauthorized error when the notebook attempts to read from OneLake. This indicates that the notebook's identity (either the user's identity or the workspace identity) lacks the necessary read permissions on the OneLake item. The most likely cause is that the notebook identity lacks read access to the OneLake item.

Exam trap

DP-600 often tests OneLake security and identity concepts; candidates may overlook that the notebook's identity needs explicit permissions, assuming that workspace membership is sufficient.

How to eliminate wrong answers

Option A is wrong because if the file did not exist, the error would typically be 'File not found' or 'Path does not exist', not an access denied error. Option C is wrong because an out-of-memory error would produce a different message, such as 'OutOfMemoryError' or 'Capacity limit exceeded'. Option D is wrong because a syntax error would be caught at compile time and would not relate to OneLake access.

64
MCQmedium

You are maintaining a Microsoft Fabric workspace that uses Git integration with Azure DevOps. A developer accidentally commits a change to a semantic model that breaks downstream reports. You need to revert the workspace to the previous working version of the semantic model. What should you do?

A.In the workspace, use the 'Undo' button to revert the last change.
B.In the Fabric admin portal, restore the workspace to a previous point in time using the workspace restore feature.
C.In Azure DevOps, revert the commit that introduced the breaking change, then sync the workspace to the updated branch.
D.In the workspace, delete the semantic model and recreate it from a backup.
AnswerC

With Git integration, the workspace reflects the state of the connected branch. To revert a change, you revert the offending commit in Azure DevOps, which creates a new commit that undoes the changes. Then you update the workspace from Git to apply the reverted state. This restores the semantic model to the previous working version.

Why this answer

Git integration in Microsoft Fabric connects a workspace to a branch in Azure DevOps. To revert a breaking change, you use Git to revert the commit that caused the issue, then update the workspace from the branch. This applies the reverted state to the workspace, restoring the semantic model to the previous working version.

This method is consistent with version control best practices.

Exam trap

The trap here is thinking that workspace UI controls like 'Undo' can revert committed changes, when Git operations are required.

65
MCQeasy

A data engineer wants to optimize the storage and read performance of Delta tables in a Microsoft Fabric Lakehouse. Which built-in Fabric feature should be enabled to ensure that Parquet files are written using a proprietary sorting and compression algorithm for faster Power BI engine access?

A.V-order
B.Z-Order
C.Auto-Optimize
D.Gzip Compression
AnswerA

V-order is a 'shuffle-less' sorting technique that rearranges data within Parquet files during the write process. This optimization allows the Power BI VertiPaq engine to read the data much faster, as it aligns the storage format with the engine's internal memory structures. It is a critical setting for high-performance Fabric analytics solutions.

Why this answer

Microsoft Fabric introduces V-order as a write-time optimization for Parquet files. This is specifically designed to maximize the performance of the Power BI engine when accessing data via Direct Lake mode or the SQL endpoint. Maintaining optimized storage is a key responsibility for an analytics engineer to ensure that the solution remains performant as data volumes grow.

Exam trap

Candidates often select 'Z-Ordering' or 'Partitioning' because they are familiar with general Spark optimization. However, V-order is the specific Fabric-native feature for Power BI Direct Lake performance.

66
Multi-Selecthard

A large semantic model using Direct Lake mode is experiencing slow query performance. You want to optimize the model's maintenance and performance. Which THREE actions should you take?

Select 3 answers
A.Convert all calculated columns in the semantic model to Power Query M columns.
B.Run the OPTIMIZE command on the underlying Delta tables in the Lakehouse.
C.Set the 'Direct Lake behavior' property to 'Direct Lake only' to prevent fallback.
D.Increase the 'Max Intermediate Rows' setting in the Power BI capacity settings.
E.Ensure that the Delta tables use V-Order to improve the reading speed of Parquet files.
AnswersB, C, E

The OPTIMIZE command performs file compaction (bin-packing) on Delta tables, which reduces the number of small files and improves read performance. Since Direct Lake reads Parquet files from the Lakehouse, having optimized, appropriately sized files is essential for fast memory loading and efficient query execution within the semantic model's engine.

Why this answer

Optimizing Direct Lake models requires a combination of data engineering and model configuration. Direct Lake relies on the ability to load Parquet files directly into memory, so the physical layout of the files and the complexity of the DAX measures are critical factors. Maintaining these aspects ensures that the model can stay in 'Direct Lake' mode without falling back to 'DirectQuery'.

Exam trap

Candidates often overlook the 'Direct Lake only' setting, incorrectly assuming that the system will automatically maintain top performance without explicit configuration to prevent fallback to DirectQuery mode.

67
MCQmedium

You are maintaining a Microsoft Fabric workspace that uses a deployment pipeline to promote content from development to test to production. A developer accidentally deleted a semantic model in the development stage. You need to restore the semantic model to the development stage without affecting the test or production stages. What should you do?

A.Restore the semantic model from the Fabric recycle bin for the development workspace.
B.Reassign the semantic model from the test stage to the development stage using the deployment pipeline settings.
C.Use the deployment pipeline to redeploy the semantic model from the test stage to the development stage.
D.Use the Fabric REST API to recreate the semantic model from a backup stored in Azure Storage.
AnswerA

Microsoft Fabric provides a recycle bin for each workspace, where deleted items are retained for a period. You can restore a deleted semantic model from the recycle bin of the development workspace. This action only affects the development stage, leaving test and production untouched. It is the simplest and most direct way to recover a deleted item.

Why this answer

The Fabric recycle bin retains deleted items for a specified period, allowing restoration. Each workspace has its own recycle bin, so restoring the semantic model from the development workspace's recycle bin recovers it only in that stage. This avoids impacting the test or production stages and is the intended recovery method for accidental deletions.

Exam trap

The trap here is assuming that deployment pipelines can move content backward or that you need to use complex backup methods, when the recycle bin is the straightforward solution for restoring deleted items within a single stage.

68
Multi-Selecthard

You are a Fabric analytics engineer responsible for maintaining a Microsoft Fabric workspace. You need to ensure that the workspace is compliant with your organization's data governance policies. The policies require that you can identify the lineage of data from source to report and that you can classify sensitive data automatically. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Apply sensitivity labels manually to each report and semantic model.
B.Enable Microsoft Purview integration with the Fabric tenant to scan and classify data.
C.Use the Fabric lineage view to visualize data flow across items.
D.Configure OneLake data access roles to restrict access to sensitive data.
E.Enable audit logs in the Fabric admin portal to track user activities.
AnswersB, C

Integrating Microsoft Purview with Fabric allows you to scan Fabric items, automatically classify sensitive data using built-in or custom classifiers, and apply sensitivity labels. Purview provides a unified data map that shows lineage across Fabric and other sources. This directly addresses the requirement to classify sensitive data automatically and to understand data lineage from source to report. Enabling this integration is a key step for governance.

Why this answer

To meet the governance policies, you need both data lineage and automatic data classification. The Fabric lineage view provides a visual representation of data flow across items, satisfying the lineage requirement. Microsoft Purview integration enables automated scanning, classification, and sensitivity labeling of data, satisfying the classification requirement.

Together, these actions provide the necessary governance capabilities. Other options address security or auditing but not the specific requirements.

Exam trap

The trap here is to focus on access control or auditing instead of the specific governance needs of lineage and automatic classification.

69
MCQhard

You are troubleshooting a failure in a Microsoft Fabric Data Factory pipeline. The error log indicates a 'Timeout' occurred during a 'Copy Data' activity from an on-premises SQL Server. Which maintenance action is most likely to resolve the issue?

A.Check the On-premises Data Gateway logs for 'System Load' or 'Concurrency' issues.
B.Increase the 'Max Parallelism' setting in the Fabric workspace properties.
C.Convert the SQL Server table to a Delta table before the copy activity.
D.Switch the authentication method from 'Basic' to 'OAuth2'.
AnswerA

If a gateway is overloaded with too many simultaneous requests, it may fail to process a new 'Copy Data' activity within the allotted time. Reviewing the gateway's performance counters and logs can reveal if it needs to be scaled out (adding more members to a cluster) or if the host machine is resource-constrained.

Why this answer

Maintaining hybrid data solutions involves managing the connection between cloud and on-premises environments. Timeouts during data movement often point to issues with the On-premises Data Gateway or the network path. Effective troubleshooting requires checking the health of the gateway and the resources of the source system to ensure they can handle the requested load.

Exam trap

Candidates might incorrectly assume that increasing parallelism (Option B) will resolve a timeout, when in fact it often exacerbates resource contention on the gateway or source SQL Server.

70
Multi-Selecteasy

A Microsoft Fabric administrator is using the Microsoft Fabric Capacity Metrics app to investigate performance issues. Which TWO metrics should they prioritize to identify if the capacity is currently experiencing throttling or rejection of requests? (Select TWO)

Select 2 answers
A.Background Rejection
B.Interactive Rejection
C.Total Workspace Count
D.Average User Tenure
E.Sensitivity Label Count
AnswersA, B

Background rejection occurs when the capacity has exhausted its available smoothed CU (Capacity Unit) resources for background tasks like scheduled refreshes. Monitoring this metric is essential for understanding why data processing jobs might be failing or delaying. It indicates that the organization may need to optimize its scheduling or increase its capacity size.

Why this answer

Capacity metrics are vital for monitoring the health of a Fabric environment and ensuring that workloads do not exceed provisioned limits. Monitoring 'Background Rejection' and 'Interactive Rejection' events helps identify when the capacity is over-utilized. Understanding these metrics allows engineers to scale resources appropriately or optimize inefficient queries to maintain a high level of service for all users.

Exam trap

Candidates often confuse 'throttling' with 'overloading' or 'capacity pause'. They frequently select general 'CPU usage' or 'Memory' metrics, failing to realize that rejection specifically indicates requests being dropped due to capacity limits.

71
MCQmedium

You are maintaining a data analytics solution that requires Row-Level Security (RLS) on a semantic model. You need to ensure that the RLS rules continue to function correctly even when the model is switched to Direct Lake mode. What is a key requirement for maintaining RLS in this scenario?

A.RLS must be configured at the Lakehouse level using SQL Views instead of in the model.
B.The RLS roles must be defined in the semantic model using DAX filter expressions.
C.Single Sign-On (SSO) must be disabled for the Lakehouse connection to support RLS.
D.The semantic model must be moved to a Pro capacity to support Direct Lake RLS.
AnswerB

For Direct Lake models, RLS is maintained and enforced by the Power BI engine using DAX. This allows the model to leverage high-performance in-memory processing while still restricting data access based on user identity. It is the standard way to ensure that security is consistent with traditional Import mode models while gaining the benefits of Fabric.

Why this answer

Maintaining security in Direct Lake mode requires careful consideration of how RLS is applied. Because Direct Lake bypasses the SQL endpoint and reads Parquet files directly, RLS must be defined within the semantic model itself. Understanding these requirements ensures that sensitive data remains protected regardless of the storage mode or the performance optimizations being applied to the data solution.

Exam trap

Candidates often believe RLS is inherited from the underlying Lakehouse or SQL endpoint, failing to realize that for Direct Lake models, RLS must be explicitly defined within the semantic model itself.

72
MCQmedium

You are maintaining a Fabric workspace and need to grant a colleague the ability to commit changes to the Git repository but prevent them from deleting the workspace itself. Which workspace role should you assign?

A.Viewer
B.Contributor
C.Admin
D.Member
AnswerB

The Contributor role allows users to create, edit, and delete items within the workspace, as well as interact with Git integration to commit changes. Crucially, Contributors cannot delete the workspace or modify its settings, making it the ideal role for a developer who needs to manage the data solution's code.

Why this answer

Role-based access control (RBAC) is fundamental to maintaining a secure and functional Fabric environment. Each role provides a different level of authority. For developers who need to interact with Git integration, the role must allow for item modification and synchronization while adhering to the principle of least privilege to protect the workspace infrastructure.

Exam trap

Candidates often choose the 'Admin' role because it grants Git sync permissions, failing to realize that Admin also grants workspace deletion rights, violating the principle of least privilege.

73
Multi-Selectmedium

You plan to rename a column in a gold-layer table within a Fabric Lakehouse. Which THREE actions should you perform to assess and mitigate the impact on the existing analytics solution? (Select THREE)

Select 3 answers
A.Open the Lineage view to identify downstream semantic models and reports that use the table.
B.Use the Impact Analysis side pane for the table to see the number of affected items and workspaces.
C.Notify the contact persons listed for the downstream items about the scheduled change.
D.Delete the Lakehouse and recreate it with the new schema to ensure all metadata is refreshed.
E.Change the workspace name to include 'DEPRECATED' until the column rename is completed.
AnswersA, B, C

The Lineage view provides a visual representation of how data flows from the source to the final report. By checking this view, an engineer can see exactly which semantic models will be broken by a column rename. This is the first step in understanding the scope of the change within the Fabric workspace.

Why this answer

Impact analysis and lineage views are critical for maintaining data integrity when underlying schemas change. Before modifying a column name in a Lakehouse table, an engineer should use these tools to identify downstream dependencies. This proactive approach prevents broken reports, failed data pipelines, and ensures that all stakeholders are notified of upcoming breaking changes in the data architecture.

Exam trap

Candidates often select technical remediation steps like rewriting DAX or dropping tables instead of prioritizing the required assessment and stakeholder notification actions.

74
MCQmedium

You are maintaining a Microsoft Fabric workspace that contains a Lakehouse, a Data Warehouse, and several semantic models. The capacity administrator reports that interactive queries from Power BI reports sometimes fail with 'Capacity exceeded' errors during peak hours, even though the capacity has sufficient compute. You suspect that background operations are consuming resources. Which action should you take to identify the top resource-consuming items?

A.Enable verbose logging on the capacity and analyze the Azure Monitor logs for CPU and memory spikes.
B.Query the sys.dm_exec_requests DMV in the Data Warehouse to see currently running queries and their resource usage.
C.Open the Microsoft Fabric Capacity Metrics app and review the 'Items' page, filtering by operation type and sorting by CU consumption.
D.Use the Fabric REST API to list all items in the workspace and retrieve their last refresh timestamps.
AnswerC

The Capacity Metrics app provides detailed CU consumption per item and operation. The Items page lets you filter by operation type (interactive vs background) and sort by CU usage, directly identifying top consumers causing throttling. This is the recommended tool for capacity monitoring in Fabric.

Why this answer

The Microsoft Fabric Capacity Metrics app is the primary tool for monitoring capacity usage. Its Items page aggregates CU consumption by item and operation type, allowing administrators to identify which background jobs or interactive queries are causing throttling. This directly addresses the need to find top resource-consuming items during peak hours.

Exam trap

The trap here is assuming that Data Warehouse DMVs or Azure Monitor logs provide the same item-level CU consumption details as the Capacity Metrics app.

75
Multi-Selectmedium

You plan to change the data type of a column in a gold-layer Lakehouse table. You need to use the 'Impact Analysis' feature to identify the potential consequences. Which THREE types of downstream items will be identified by this feature?

Select 3 answers
A.Semantic models
B.Reports
C.Dashboards
D.Data Pipelines
E.Gateway connections
AnswersA, B, C

Semantic models sit directly on top of Lakehouse tables and are highly sensitive to schema changes. If a data type changes, measures or relationships within the model may break. Impact analysis identifies these models so developers can update the metadata and DAX calculations to align with the new schema.

Why this answer

Impact Analysis is a critical governance tool for maintaining data integrity across a Fabric tenant. It allows engineers to see how changes to a data source propagate through the environment. By identifying affected items before making changes, you can proactively notify stakeholders and update dependent logic, preventing broken reports and ensuring a reliable user experience.

Exam trap

Test-takers frequently select lower-level data assets like 'Lakehouses' or 'Files' as downstream items, forgetting that Impact Analysis focuses specifically on analytics consumption layers.

Page 1 of 2 · 76 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Maintain a Data Analytics Solution questions.