DP-700 Implement and Manage an Analytics Solution Practice Question
Your enterprise requires strict compliance tracking for all data pipeline executions inside a Microsoft Fabric workspace. You need to implement a monitoring solution that captures detailed activity logs, pipeline run statuses, and capacity consumption metrics over a 180-day retention period for auditing purposes. What is the most effective native mechanism to achieve this?
⚠ Common exam trap
Candidates often rely on the built-in 'Monitoring' tab inside the Fabric workspace, forgetting that it has limited retention periods and is not suitable for long-term compliance auditing.
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
✓
Configure a diagnostic setting in Azure to stream Fabric workspace logs and capacity metrics to a Log Analytics workspace.
Configuring a diagnostic setting in the Azure portal routes Fabric workspace logs and capacity metrics to an Azure Log Analytics workspace or Azure Storage account. This native integration enables long-term retention beyond the default Fabric limits and provides advanced querying capabilities via Kusto Query Language for rigorous compliance auditing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Export the run history manually from the Fabric monitoring hub every thirty days into a shared SharePoint folder.
Why it's wrong here
Manual exports are prone to human error, lack automation, and do not scale for enterprise auditing requirements. Relying on manual processes fails compliance standards that demand continuous, tamper-evident log collection and centralized storage.
- ✓
Configure a diagnostic setting in Azure to stream Fabric workspace logs and capacity metrics to a Log Analytics workspace.
Why this is correct
Diagnostic settings provide enterprise-grade telemetry routing, allowing administrators to centralize monitoring data, enforce custom retention policies up to years, and run complex KQL queries to satisfy stringent regulatory compliance frameworks.
- ✗
Rely solely on the default Fabric monitoring hub retention period to store pipeline execution telemetry.
Why it's wrong here
The default retention period in the Fabric monitoring hub is limited and insufficient for compliance policies requiring a 180-day retention window. Relying on default behavior risks data loss when historical logs are automatically purged.
- ✗
Write custom Spark notebooks in a lakehouse to query the internal workspace metadata APIs and append logs to Delta tables daily.
Why it's wrong here
While custom notebooks can capture pipeline metadata, maintaining a custom orchestration solution introduces unnecessary complexity and operational overhead. Native diagnostic settings provide a fully managed, secure, and robust telemetry pipeline.
About these practice questions
Courseiva writes every DP-700 question from scratch — 152 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.