DP-700 Practice Test 11 — 15 Questions

Question 1

You are monitoring a Data Factory pipeline. What is the best way to be notified when a pipeline fails during an execution?

Accepted Answer

Use the alerts in the monitoring hub. Fabric pipeline monitoring can be enhanced using alerts configured within the monitoring hub or by utilizing Microsoft Fabric's integration with Azure Monitor/Log Analytics. By setting up alert rules based on pipeline status, you ensure proactive notification, allowing for rapid response and troubleshooting. This is a critical operational practice for maintaining high-reliability data systems, as it reduces downtime and ensures data quality standards are consistently met.

Answer

Manually refresh the monitor tab

Answer

Check the SQL database logs

Answer

Run a daily Notebook to check status

Question 2

Which Fabric tool allows you to visually track the total compute usage of your workspace over a specific timeframe?

Accepted Answer

Capacity Metrics app. The Fabric Capacity Metrics app is the central dashboard for monitoring compute utilization. It provides visualizations that track usage against your provisioned capacity, making it easy to identify spikes and sustained high-load periods. This tool is vital for administrators to ensure that their capacity is sized correctly and that they are not consistently hitting their resource limits, which would cause throttling and performance degradation across the organization's analytical workloads.

Answer

OneLake monitoring dashboard

Answer

Pipeline monitoring view

Answer

Azure Advisor

Question 3

You are monitoring an ingestion pipeline and notice it frequently fails with a 'Timeout' error. What is the most likely cause?

Accepted Answer

The source system is taking too long to respond.. Timeout errors in ingestion pipelines are usually caused by source systems failing to respond within the expected time window or the copy activity reaching the default threshold. Increasing the timeout duration or optimizing the data fetch process can resolve this. This is a common operational hurdle when dealing with heterogeneous source systems that may have variable performance characteristics or intermittent network connectivity, requiring careful tuning of the pipeline's connection parameters.

Answer

The target table schema has changed.

Answer

The pipeline has incorrect user credentials.

Answer

The data is already in the target table.

Question 4

Refer to the exhibit. The refresh operation for a Power BI semantic model took 45 minutes to complete. What is the most efficient way to reduce the refresh time for this specific model?

Accepted Answer

Configure incremental refresh.. Incremental refresh is the most effective strategy for large datasets. Instead of reloading all 5 million rows every time, you configure the model to load only new or updated data based on a date/time column. This dramatically reduces the amount of data processed per refresh, lowering execution time and resource utilization on the Fabric capacity while keeping reports up to date.

Answer

Upgrade to a higher capacity SKU.

Answer

Use Power BI Desktop to manually refresh.

Answer

Delete all historical data.

Question 5

Which configuration would you adjust to improve the performance of a Spark job that is consistently failing due to 'Out of Memory' (OOM) errors during aggregation?

Accepted Answer

Increase the executor memory configuration.. OOM errors during aggregation occur because the data partition is too large to fit in the executor's memory during the shuffle or group-by operation. Increasing the memory per executor or increasing the number of partitions (to make each partition smaller) are standard fixes. By spreading the load, you prevent any single executor from being overwhelmed, ensuring that the aggregation can complete without hitting the rigid memory limits of the compute nodes.

Answer

Increase the driver memory.

Answer

Change the table compression to None.

Answer

Switch to a different Spark pool version.

Question 6

You are managing a large-scale data ingestion pipeline that runs every hour. Recently, the pipeline has started to fail with 'Concurrency Limit Exceeded' errors. You have several other pipelines running in the same workspace. How should you optimize the environment to resolve this error?

Accepted Answer

Implement a staggered schedule for the pipelines in the workspace.. Fabric capacities have limits on the number of concurrent operations that can run. When multiple pipelines or activities start simultaneously, they can exceed these limits. Implementing a more staggered schedule or using pipeline concurrency settings ensures that the workload stays within the allowed limits of the capacity SKU without failing.

Answer

Use the 'Invoke Pipeline' activity with 'Wait on completion' disabled.

Answer

Increase the 'Max concurrent runs' setting in the pipeline properties.

Answer

Switch all pipelines to use the 'Small' Spark pool size.

Question 7

You need to monitor the historical performance of queries in a Fabric Warehouse to identify which ones frequently use the most CPU time. Which Dynamic Management View (DMV) should you query?

Accepted Answer

queryinsights.exec_requests_history. Fabric Warehouse provides several DMVs to monitor query execution. The 'sys.dm_exec_requests' view shows currently running queries, but for historical analysis, 'queryinsights.exec_requests_history' (or similar views in the queryinsights schema) provides the necessary data on completed queries, including their duration and resource consumption over time.

Answer

sys.dm_pdw_nodes_os_performance_counters

Answer

sys.dm_tran_active_transactions

Answer

sys.dm_exec_sessions

Question 8

You are monitoring a Dataflow Gen2 refresh that is failing intermittently. You need to identify if the failure is caused by a data type mismatch or a timeout from the source system. Which TWO actions will help you find the specific error details? (Choose two.)

Accepted Answer

Check the 'Refresh history' in the Dataflow settings.. Dataflow Gen2 in Fabric provides multi-layered monitoring. The refresh history provides a high-level status, while the 'Request ID' can be used to trace the operation in more detail. For row-level errors, Dataflow Gen2 uses a specific mechanism to log transformation failures, allowing engineers to pinpoint exactly which record caused the process to fail.

Answer

Enable 'Stage query' for all transformations.

Answer

View the 'DataflowRefreshHistory' table in the Lakehouse.

Answer

Use the 'Performance Analyzer' in Power BI Desktop.

Question 9

You want to monitor the health and performance of your Microsoft Fabric pipelines. Which tool should you use to view detailed execution logs and identify bottlenecks in your data movement?

Accepted Answer

Fabric Monitoring Hub. The Fabric Monitoring Hub provides a centralized view of all activities, including pipeline executions. It allows you to track status, duration, and failures for all items within your workspace. By accessing the execution details of a specific pipeline run, you can inspect activity-level durations, which is essential for identifying bottlenecks in your ELT/ETL processes and ensuring your data workflows remain within expected performance windows.

Answer

Power BI Desktop

Answer

Azure Resource Graph

Answer

Microsoft Purview

Question 10

You are monitoring a Spark notebook in Microsoft Fabric that is taking longer than expected to process a large dataset. You notice that a single executor is processing significantly more data than others. Which tool or feature should you use to identify the specific partition causing this data skew?

Accepted Answer

The Spark Advisor and Spark UI. Spark Advisor is integrated directly into Fabric notebooks to provide real-time performance suggestions. It analyzes job execution patterns and can detect common issues like data skew or sub-optimal file sizes. By using the Spark UI alongside Advisor, engineers can pinpoint the exact stage and partition that is causing a bottleneck in the distributed processing pipeline.

Answer

Fabric Monitoring Hub

Answer

The Capacity Metrics App

Answer

The OneLake Explorer

Question 11

A Data Factory pipeline in Fabric fails during the execution of a Copy activity. You need to find the specific error message and the number of rows successfully written before the failure. Where should you look?

Accepted Answer

The pipeline run details in the Monitoring Hub. Data Factory in Fabric provides detailed execution logs for every activity within a pipeline. Accessing the output of a specific activity allows you to see the error codes and performance metrics like rows read and written. This is the first step in troubleshooting data movement issues and identifying data quality problems.

Answer

The Spark UI environment logs

Answer

The OneLake data access logs

Answer

The Capacity Metrics 'Overages' view

Question 12

You are using a KQL Database in a Microsoft Fabric Eventhouse to analyze streaming data. You need to monitor the performance of your Kusto queries and identify which ones are consuming the most resources. Which TWO methods should you use?

Accepted Answer

Run the '.show queries' command in the KQL queryset.. Monitoring KQL performance requires specialized tools within the Eventhouse and Fabric environment. The '.show queries' command provides immediate insights into currently running and recently completed queries, while the Capacity Metrics app provides the high-level view of how these queries impact the overall cost and resource allocation of the Fabric capacity.

Answer

Check the Spark UI for Kusto connector logs.

Answer

Review the OneLake access logs in the Azure Portal.

Answer

Monitor the 'Dataflow Gen2' refresh history.

Question 13

You are tasked with optimizing the performance of a Delta table in a Fabric Lakehouse that is queried frequently by both Spark notebooks and the SQL Analytics Endpoint. Which TWO techniques should you use to improve data skipping and read performance?

Accepted Answer

Enable V-Order on the Delta table.. Optimizing Delta tables in Fabric involves managing file sizes and metadata. V-Order is a Fabric-specific optimization that sorts data to improve read speeds for Power BI and SQL, while the OPTIMIZE command consolidates small files. Together, these techniques ensure that the engine can effectively skip irrelevant data during a scan operation.

Answer

Convert the table to a CSV format.

Answer

Increase the Spark executor memory only.

Answer

Disable the use of shortcuts to the data.

Question 14

When a Spark notebook job finishes, what is the best practice for managing the underlying compute cluster resources?

Accepted Answer

Configure automatic termination for idle sessions. Proper cluster management is vital to avoid unnecessary costs. In Fabric, dynamic allocation and efficient session management ensure that resources are released as soon as they are idle. Keeping a cluster running unnecessarily consumes capacity units, which directly impacts your budget and availability for other concurrent workloads that may need those same resources to function properly.

Answer

Keep the cluster running for 24 hours

Answer

Manually restart the cluster every hour

Answer

Increase the cluster size to max nodes

Question 15

You are configuring a Spark pool in Microsoft Fabric for a workload with highly variable data volumes. You want to ensure that the pool can handle peak loads without over-provisioning resources during quiet periods. Which setting should you adjust?

Accepted Answer

Autoscale on the Spark pool. Autoscale is the key feature for managing variable workloads in Spark pools. It allows the cluster to dynamically add or remove nodes based on the number of pending tasks in the queue. This balances the need for performance during peak times with cost-efficiency during periods of low activity, ensuring Capacity Units are used effectively.

Answer

Dynamic Allocation of executors

Answer

The Max Memory per node setting

Answer

The default Spark version