Unity Catalog Development Isolation with Shared Catalog and Team Schemas
Short answer
D Create a shared development catalog, enforce a standardized naming convention, and assign each development team its own schema.
Question
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions. When you are ready to answer a question, select the “Question” button to return to the question.
Overview
Company Information
Contoso, Inc. is a renewable energy provider that operates solar and wind farms across North America.
Existing Environment
Azure Environment
Contoso has a single Azure Databricks workspace named Workspace1 in the West US Azure region. Workspace1 is enabled for Unity Catalog.
Workspace1 contains all-purpose clusters for both development and production workloads.
The company's Azure environment contains:
In the West US, Central US, and East US Azure regions, Azure event hubs that stream telemetry data and an Azure Data Lake Storage Gen2 account in each region for each hub
A single Azure SQL database in the West US region that hosts enterprise resource planning (ERP) data
An Azure Database for PostgreSQL server in the West US region that stores operational maintenance data
Data Environment
Contoso ingests the following operational and business data:
Telemetry data: More than 40,000 IoT sensors across 28 sites emit JSON telemetry events every few seconds. Each site sends the events to the nearest event hub, which writes the data into the corresponding Data Lake Storage Gen2 account. These files frequently experience schema drift.
Maintenance logs: Maintenance systems generate historical repair logs, daily incremental updates, technician notes, and unstructured attachments that are stored in the Data Lake Storage Gen2 accounts.
Operational maintenance data: Structured operational maintenance data is stored on the Azure Database for PostgreSQL server.
External weather data: Hourly weather forecasts are retrieved from a REST API and written to the Data Lake Storage Gen2 accounts.
ERP data: Daily CSV extracts of 50 to 100 GB contain equipment metadata, work orders, and purchase order information.
Problem Statements
The company’s existing analytics environment has several issues:
Ingestion
Telemetry pipelines fall behind during peak loads.
Telemetry ingestion fails when schema drift occurs.
Streaming pipelines reprocess events after a pipeline restarts.
Compute
Production and development workloads run on the same all-purpose clusters.
Production and development workloads do NOT support autoscaling or workload isolation.
Governance
The ERP data is duplicated across systems and development teams.
Naming conventions are inconsistent across development teams, regions, and products.
Ownership of the IoT sensors changes over time, and analysts must track the full history of the ownership.
Occasionally, equipment manufacturers must correct data-entry mistakes in equipment names. Historical values are NOT required.
Pipeline operations
Pipelines lack resiliency, alerting, and centralized scheduling.
Requirements
Planned Changes
Contoso plans to implement the following changes:
Implement scalable data pipeline orchestration.
Create a managed analytics catalog in Unity Catalog.
Implement a consistent approach to creating curated datasets.
Establish a centralized governance model across ingestion, cleansed, and curated layers.
Grant data engineers access to the ERP tables by using minimal development effort.
Adopt a compute strategy that isolates production workloads and supports autoscaling.
Adopt a slowly changing dimension (SCD) approach to address current data modeling issues.
Technical Requirements
Contoso identifies the following environment and compute requirements:
Ensure that production ingestion workloads run on compute clusters that can scale automatically during telemetry spikes.
Provide fast and consistent performance for business intelligence (BI) workloads.
Prevent development activity from affecting production pipelines.
Production ingestion workloads must run as scheduled, non-interactive pipelines rather than on shared interactive development clusters.
Contoso identifies the following data ingestion and processing requirements:
Auto-scale ingestion pipelines to handle bursty workloads.
Handle schema drift for the maintenance and telemetry data.
Ingest file-based telemetry data by using minimal operational effort.
Store all the ingested data in a format that supports incremental processing.
Support the continuous ingestion of telemetry data from the event hubs by using exactly-once semantics.
Support the ingestion of the structured maintenance data from the Azure Database for PostgreSQL server.
Build a new telemetry pipeline that ingests raw events from the event hubs, cleanses the data, and publishes curated tables to Unity Catalog.
Ensure that the Apache Spark Structured Streaming pipelines reading from the event hubs write the data into a managed Delta table named telemetry.raw_events. The pipelines must support schema drift and resume processing after failures without reprocessing the data.
Contoso identifies the following data modeling and optimization requirements:
Build curated tables that standardize business logic.
Overwrite equipment metadata attributes, such as name, manufacturer, model, and commissioning date, when the attributes change. Historical values are NOT required.
Contoso identifies the following pipeline deployment and operation requirements:
Orchestrate multi-step ingestion and transformation workflows.
Define a clear execution order and dependencies.
Automatically retry failed steps and notify operators.
Schedule ingestion and transformation workloads consistently.
Governance Requirements
Contoso identifies the following governance requirements:
Centralize the metadata catalog.
Provide isolated development areas that follow standard naming conventions.
Establish a consistent structure for organizing raw, cleansed, and curated data.
Provide a read-only mechanism to reference the ERP data through a foreign catalog.
Business Requirements
Contoso identifies the following business requirements:
Improve ingestion reliability and reduce operational effort.
Standardize data definitions across development teams.
You need to organize Unity Catalog. The solution must meet the governance requirements.
What should you do?
Key Takeaways
The exam tests whether you can map Unity Catalog's catalog/schema hierarchy to team isolation and naming standards, and the trap is assuming table-level grants alone create an isolated development area.
Unity Catalog development organization requires a shared, governed catalog rather than uncontrolled per-team namespaces. This page establishes that a shared development catalog with standardized naming and one schema per team (D) satisfies isolation and consistency.
Common mistake: The most plausible wrong answer is C, because separate catalogs sound more isolated; however, letting each team choose its own schema names violates the required naming convention and consistent structure.
Expert Analysis
Namespace boundaries, not just grants
The requirement asks you to organize Unity Catalog while preserving centralized metadata, isolated development areas, standardized names, and a consistent raw/cleansed/curated structure. In Unity Catalog, catalogs and schemas are the namespaces and permission boundaries; table-level grants are useful for fine-grained access but do not create clean team workspaces. Option D uses a shared development catalog with a schema assigned to each development team and an enforced naming convention. That gives each team an isolated schema namespace while the catalog remains the common, centrally governed container for development objects.
Why D satisfies all governance requirements
The shared catalog keeps metadata centralized and avoids a sprawl of team-controlled catalogs. Assigning one schema per team creates a predictable place for each team's tables, views, and volumes, and enforcing a standard naming convention supplies the consistency the current environment lacks. The same convention can carry the raw, cleansed, and curated layer structure, so objects remain discoverable across regions and products. A shared schema with table-level permissions (A) is weaker because it does not prevent name collisions, permission sprawl, or accidental object creation in a common namespace. Letting teams create objects in the default catalog and schema (B) is effectively unmanaged. A separate catalog per team (C) sounds isolated. A comment noted D is the only option meeting all governance requirements: C lets each team pick schema names, breaking the naming-convention requirement, while A and B provide no real isolation. The correct answer is D.
Adjacent decision and what would flip it
The adjacent decision is where to put the environment boundary. Here, development is a shared governed area, so catalog = development and schema = team. If the company later required separate billing, regional data residency, or hard security domains per team, separate catalogs with centrally assigned, standardized names could become appropriate. If naming standardization disappeared from the requirements, C would still be weaker for consistent structure but less obviously wrong. The exam wording keeps naming and centralized metadata explicit, so D remains the defensible design.
Operational consequence
Getting this wrong shows up as duplicated or colliding table names, unclear ownership, failed pipeline references after a team renames a schema, and permissions that must be repaired table by table. A schema-per-team boundary makes grants, audits, and cleanup predictable and prevents development activity from leaking into another team's namespace, while the shared catalog preserves Unity Catalog's centralized governance model.
Official Reference
https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a governance scenario asks how to organize Unity Catalog, translate each requirement into a securable boundary before reading options. Team isolation typically maps to a schema inside a shared development catalog, while centralized metadata remains at the catalog or metastore level and naming standards must be enforced globally. Test each option against all stated requirements—isolation, naming, layer structure, and centralization—and eliminate any choice that delegates naming to teams or leaves objects in default namespaces.
Frequently Asked Questions
Why not create a separate Unity Catalog for each development team?
What Unity Catalog object provides each development team's isolated area?
Does table-level permission in a shared schema satisfy development isolation?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
pietjapie 👍 1 Answered DD is the only option that meets all the governance requirements. A shared development catalog with a schema per team gives each team an isolated area while keeping metadata centralized, and enforcing a naming convention satisfies the standardization requirement. A and B provide no real isolation, and C lets each team choose its own schema names, which breaks the naming-convention requirement.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DP-750 Questions
Access 139 questions with complete answers and detailed explanations.
View Full DP-750 Practice Test →