Home / Data Analyst practice test / Understanding of Databricks Data Intelligence Platform / Question

Databricks Data Analyst Associate · free practice question

A data analyst at a logistics company is exploring Databricks Marketplace to acquire a public geospatial reference dataset and a Databricks notebook…

Exam-style question on Understanding of Databricks Data Intelligence Platform from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Understanding of Databricks Data Intelligence Platform

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?

  1. ATo browse Marketplace listings, the analyst first applies to become a registered Marketplace provider, as provider and consumer identities share one registration workflow. Read-only consumer browsing is unlocked once Databricks approves the application and assigns a provider profile to the workspace; after that, the geospatial dataset and the notebook can be requested from the workspace like any other listing.
  2. BMarketplace delivers data in a Databricks-proprietary format: a dataset acquired through a listing is converted from its original Parquet, CSV or JSON files into an encrypted binary archive before delivery. The analyst can query the converted dataset inside the workspace, but it is not readable from Apache Spark running outside Databricks or from other downstream analytics tools, and the conversion is not reversible.
  3. CThe Open Marketplace at marketplace.databricks.com can be browsed without logging in to a Databricks workspace, so the analyst can evaluate listings first. To request access and install the dataset or notebook, the analyst uses Marketplace inside the Unity Catalog-enabled workspace; once the provider approves, the dataset appears as a read-only Unity Catalog catalog that can be queried with SQL, and the notebook is installed to the workspace.
  4. DMarketplace listings, datasets and notebooks alike, are delivered as soon as a Databricks user clicks 'Get', with no provider approval step, no terms-of-use acceptance and no workspace permission requirement. Once acquired, the dataset appears as a writable catalog in the analyst's Unity Catalog, and local transformations can be written back through it to the provider's original data source.
  5. ENotebooks in Marketplace are static, read-only PDF exports of notebook code that are not importable into a workspace; to use one, the analyst copies the code from the PDF into a new blank notebook. Datasets, by contrast, are delivered as live queryable catalogs. The difference reflects that Databricks treats structured tabular data as the asset type with enough governance controls for live delivery.
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.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →