Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Automatic Data Lineage in Microsoft Purview
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An enterprise uses Azure Synapse Analytics and Azure Data Factory to orchestrate and transform data across several cloud data stores. The data governance and compliance team needs a solution to track the end-to-end journey of the data, including its origin, transformations, and final destinations.
How does Microsoft Purview integrate with these Azure services to meet this requirement?
Explanations
By migrating all source databases into a single Azure Synapse dedicated SQL pool
By migrating all source databases into a single Azure Synapse dedicated SQL pool
What Database Consolidation Is
Database consolidation involves physically moving disparate databases—such as Azure SQL Database, Azure Cosmos DB, and on-premises databases—into a centralized data warehouse or Azure Synapse dedicated SQL pool using database migration tools.
Why It Doesn't Meet the Requirement
The scenario asks how Microsoft Purview provides governance and tracking across existing data pipelines, not how to physically consolidate storage architectures:
- Non-Invasive Governance: Microsoft Purview governs data where it already resides without requiring database migration or relocation.
- Disregards Pipeline Tracking: Relocating databases does not provide automated data lineage, transformation mapping, or classification across the enterprise.
- Unnecessary Overhead: Moving enterprise databases is costly, disruptive, and unnecessary for tracking data origins.
Key Characteristics and Limitations
- Physical database migration is typically performed using Azure Database Migration Service (DMS) or ETL pipelines.
- Microsoft Purview operates as a unified governance overlay across heterogeneous, distributed data stores.
- Data remains in place while Purview catalogs schema, sensitivity, and movement history.
This Answer Would Be Correct If
The organization had a requirement to consolidate multiple distributed SQL relational databases into a centralized enterprise data warehouse for high-performance analytical queries.
Additional Context
Microsoft Purview is designed specifically to prevent the architectural limitation of needing all data in one place. It supports multicloud, hybrid, and polyglot persistence models while maintaining unified oversight.
By automatically deploying network security groups and firewalls around data stores
By automatically deploying network security groups and firewalls around data stores
What Network Security Groups and Firewalls Are
Network Security Groups (NSGs) and Azure Firewalls are foundational network security controls in Azure. They filter network traffic, restrict IP ranges, and establish virtual network perimeters to protect infrastructure and PaaS resources from unauthorized network access.
Why It Doesn't Meet the Requirement
Automating network perimeter security does not solve the governance requirement of understanding data origin, movement, and transformations:
- Infrastructure vs. Data Governance: NSGs operate at Layer 4 of the OSI model (IPs and ports) and have no insight into data lineage, schema evolution, or pipeline logic.
- Different Azure Services: Network security rules are provisioned using Azure Virtual Network, Azure Policy, or Azure Firewall, not Microsoft Purview.
- Misses Lineage Requirements: Firewalls do not track how data moves through pipeline activities or how datasets relate to each other.
Key Characteristics and Limitations
- NSGs control ingress and egress traffic based on IP address, port, and protocol.
- Microsoft Purview connects to secured networks via private endpoints and managed virtual networks rather than managing network security infrastructure.
- Network controls protect transport channels but do not catalog or govern data assets.
This Answer Would Be Correct If
The scenario required restricting network access to Synapse workspaces or SQL databases using subnet-level filtering rules.
Additional Context
While Microsoft Purview can scan resources protected by private endpoints and firewalls, its purpose is data governance, classification, and cataloging rather than network infrastructure administration.
By replacing pipeline execution engines with dedicated Purview compute clusters
By replacing pipeline execution engines with dedicated Purview compute clusters
What Dedicated Compute Replacement Is
This option suggests that Microsoft Purview provides an execution engine that supersedes and replaces data processing engines like Azure Synapse Spark pools, SQL pools, or Azure Data Factory integration runtimes.
Why It Doesn't Meet the Requirement
Microsoft Purview is strictly a metadata management and governance platform, not an execution or data processing engine:
- No Compute Replacement: Purview does not replace or host ETL/ELT execution workflows.
- Metadata Extraction Only: Pipelines continue to run inside Azure Synapse Analytics or Azure Data Factory; Purview merely receives and visualizes the generated execution metadata.
- Separation of Concerns: Data processing workloads remain within their dedicated analytics environments while governance is centralized.
Key Characteristics and Limitations
- Purview processes metadata and access policies rather than raw data transformations.
- It relies on connected services to report runtime metadata upon pipeline completion.
- It does not provision replacement compute clusters for business logic execution.
This Answer Would Be Correct If
The objective were migrating legacy ETL scripts to a new unified compute runtime such as Azure Synapse Spark or Azure Databricks, rather than governing data flows across existing pipelines.
Additional Context
A common misconception is that Microsoft Purview stores or processes customer workload data directly. In reality, customer data remains in its native storage and compute tiers, while Purview manages only structural and operational metadata.
By capturing and mapping data lineage automatically when pipeline activities execute
By capturing and mapping data lineage automatically when pipeline activities execute
What Data Lineage Integration in Microsoft Purview Is
Microsoft Purview is a unified data governance service that helps organizations manage and govern their on-premises, multicloud, and software-as-a-service (SaaS) data. A foundational capability of Microsoft Purview is data lineage tracking, which maps the movement, transformations, and relationships of data assets across an entire enterprise estate.
How It Meets the Requirements
When integrated with Azure Synapse Analytics and Azure Data Factory, Microsoft Purview connects directly to these orchestration engines:
- Automated Lineage Capture: As pipeline activities (such as Copy activities and Data Flow activities) execute, lineage metadata is automatically pushed to Microsoft Purview.
- End-to-End Visibility: Purview records the source dataset, the processing steps applied, and the destination storage location.
- Root Cause Analysis: Data stewards and compliance officers can visualize upstream dependencies and downstream impacts across complex data workflows.
Key Advantages and Capabilities
- Zero-Code Instrumentation: Lineage capture occurs seamlessly during native pipeline runs without requiring manual logging scripts.
- Centralized Cataloging: Connects multiple Synapse workspaces and Data Factory instances into a single holistic data map.
- Asset Discovery: Allows analysts to search for assets and understand data origins and trustworthiness before consuming them.
- Metadata Enrichment: Enhances governance by associating data classifications and sensitivity labels with lineage graphs.
Why This Is Optimal
Integrating Microsoft Purview with Azure Synapse Analytics and Azure Data Factory directly solves the enterprise challenge of data visibility across complex pipelines. Rather than maintaining custom documentation or external tracking logs, the automated lineage push ensures accurate, real-time metadata governance across the entire analytics ecosystem.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Microsoft Purview Data Governance
Describe the purpose of Microsoft Purview in Azure
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Microsoft Purview Compliance Manager
Describe the purpose of Microsoft Purview in Azure
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Microsoft Purview Data Governance
Describe the purpose of Microsoft Purview in Azure
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Microsoft Entra Conditional Access
Describe Microsoft Entra Conditional Access
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Infrastructure as a Service
Describe infrastructure as a service (IaaS)
IntermediateAZ-204 Developing Solutions for Microsoft Azure Exam
Azure Blob System Properties vs User-Defined Metadata
Set and retrieve properties and metadata
Last updated Validated