A data analyst at a logistics company is exploring Databricks Marketplace to acquire a public geospatial reference dataset and a Databricks notebook demonstrating geospatial analysis patterns. The analyst has a Unity Catalog-enabled Databricks workspace. Which set of statements about Databricks Marketplace behavior and capabilities is ACCURATE?
Answer & explanation
Correct answer: C
WHY C: This matches the documented behavior across two separate actions. The Open Marketplace (marketplace.databricks.com) is browsable without a Databricks account or workspace, which lets the analyst pre-evaluate listings. To request and install a data product, the consumer works from a Databricks workspace. For datasets shared through Delta Sharing, the approved product appears as a catalog in the consumer's Unity Catalog metastore, queryable with standard SQL like internal data but read-only (the consumer does not write back to the provider's source). A notebook listing is installed to the workspace and can be run or cloned straight away. Some listings are available instantly on terms acceptance; others need explicit provider approval first.
WHY NOT A: Provider and consumer identities are separate in Marketplace. A consumer does not register as a provider to browse or request data products; the consumer workflow (browsing, requesting, querying) is independent of the provider workflow (listing, sharing, approving). Requiring provider registration would make the platform unusable as a broad data exchange.
WHY NOT B: Marketplace uses Delta Sharing, an open standard that interoperates with Apache Spark outside Databricks, pandas, Power BI and other tools. Shared data is not converted to a proprietary format; open, format-agnostic interoperability is a design goal of Delta Sharing, and data stays in its original Delta, Parquet or other format.
WHY NOT D: Not every listing is instant or unconditional: some require provider approval, and listings require the consumer to accept terms of use. Shared catalogs are read-only for consumers, so nothing is written back to the provider's data source; allowing that would violate the provider's data sovereignty, which the Delta Sharing protocol prevents.
WHY NOT E: Marketplace notebooks are real installable, executable Databricks notebooks, not static PDF exports; an acquired notebook is installed to the workspace in runnable, editable form. Datasets and notebooks differ in how they are delivered (a Unity Catalog catalog versus a workspace notebook object), not in executability or governance.