Transit partners require an open table format for a shared lake while city pipelines remain Azure Databricks–native. What should the data engineer evaluate?

Evaluating whether Iceberg interoperability is required for partners versus Delta-native pipelines inside Azure Databricks is the correct decision frame when transit partners require an open table format for a shared lake while city pipelines remain Databricks-native. Table-format choice is an interoperability and operations tradeoff: partner-shared lakes may mandate Iceberg (or another open format), whereas internal Databricks pipelines often standardize on Delta for native features—unless UniForm/compatibility features or dual publishing are explicitly designed.

Whether Parquet standardisation meets needs for partners versus Delta-native pipelines inside Azure Databricks falls short because Parquet is only a file format without table management, so it cannot satisfy the stem's requirement for an open table format with reliable reads for partners in the shared lake. Whether Hudi copy-on-write fits use for partners versus Delta-native pipelines inside Azure Databricks misses the stem's specific interoperability question because it evaluates a different open table format rather than whether Iceberg interoperability is required for partners alongside Delta-native city pipelines. Whether Delta standardisation serves needs for partners versus Delta-native pipelines inside Azure Databricks assumes internal Databricks-native pipelines settle the shared lake, but it does not evaluate the partners' stated need for an open, partner-readable table format.

Exam caveat: “Databricks-native Delta” and “partner Iceberg” are not automatically exclusive if the platform’s interoperability features meet both needs, but the engineer must evaluate that requirement explicitly rather than assuming one format. Exam distractors often push single-format standardisation assumptions (Parquet standardisation, Hudi copy-on-write, Delta standardisation) when the real issue is open table format selection for multi-party lakes.

Operational check: Document partner open-format requirements, inventory city Databricks pipelines’ Delta dependencies, decide on Iceberg, Delta, or an interoperability layer that satisfies both, and validate a pilot partner read against the shared lake before citywide rollout.