DP-700 Monitor and Optimize an Analytics Solution Practice Question
You are troubleshooting a slow-running Power BI report connected to a Fabric Semantic Model. What is the most effective way to identify the bottleneck?
⚠ Common exam trap
Candidates often suggest checking the Fabric Capacity Metrics app. While it shows overall workspace health, it does not identify which specific visual or DAX measure is the culprit in the report.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the Power BI Performance Analyzer
Performance analysis in Power BI involves tracking how long each visual, DAX query, and storage engine operation takes. By using the Performance Analyzer, you can pinpoint exactly which visual or measure is causing the delay. This allows you to focus on optimizing specific DAX measures or data model relationships rather than guessing, which is vital for maintaining responsive reports in production environments.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use the Power BI Performance Analyzer
Why this is correct
Performance Analyzer records the time taken for each visual to refresh, including DAX query execution and visual rendering. It provides a detailed breakdown of where time is spent, making it the most effective tool for identifying bottlenecks within a report's specific components.
- ✗
View the workspace storage metrics
Why it's wrong here
Storage metrics provide information on how much data is consumed by items in a workspace but do not show query execution times or visual performance. They are useful for managing capacity footprint but irrelevant for troubleshooting slow report rendering or inefficient DAX code.
- ✗
Check the Fabric capacity SKU settings
Why it's wrong here
SKU settings define the compute limits for the entire capacity. While an undersized SKU can lead to throttling, it is unlikely to be the cause of a single report being slow while others function normally. The bottleneck is usually the report design, not the SKU.
- ✗
Rebuild the semantic model from scratch
Why it's wrong here
Rebuilding the model is a destructive and time-consuming process that does not guarantee improved performance. Without first identifying the root cause of the slowness using diagnostic tools, you may simply recreate the same performance issues in the new model.
About these practice questions
This DP-700 question is part of Courseiva's 152-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-700 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-700 exam.