Why are CSV/JSON files not discovered in a Dataplex curated zone?
You are managing a Dataplex environment with raw and curated zones. A data engineering team is uploading JSON and CSV files to a bucket asset in the curated zone but the files are not being automatically discovered by Dataplex. What should you do to ensure that the files are discovered by Dataplex?
Community Votes
66% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests whether you know the supported file formats for Dataplex curated zones; the common trap is assuming auto-discovery is the fix when the real issue is that CSV/JSON files are not valid for curated zones.
In Google Cloud Dataplex, curated zones support only specific analytics-optimized formats like Parquet, Avro, ORC, and BigQuery tables. Community consensus indicates that moving CSV/JSON files to a raw zone is the correct action, since enabling auto-discovery alone cannot catalog unsupported formats in a curated zone.
Option B (Enable auto-discovery of files for the curated zone) is the most common wrong answer. Auto-discovery cannot make Dataplex catalog formats that curated zones are not designed to support; the root cause is the zone's format restriction, not a discovery setting.
Community Discussion (19 comments)
GCP001
👍 26
Selected: A
Should be A. Curated zone need Parquet, Avro, ORC format not CSV or JSON. Check the ref - https://cloud.google.com/dataplex/docs/add-zone#curated-zones
raaad
👍 8
Selected: B
- Auto-Discovery Feature: Dataplex has an auto-discovery feature that, when enabled, automatically discovers and catalogs data assets within a zone. - Appropriate for Both Raw and Curated Zones: This feature is applicable to both raw and curated zones, and it should be tailored to the specific data governance and cataloging needs of the organization.
MBNR
👍 1
Selected: A
Answer is A Data Format supported: Data in curated zones is typically columnar, Hive-partitioned, and stored in formats like Parquet, Avro, or ORC Restrictions: Dataplex does NOT allow users to create CSV files within a "curated zone
juliorevk
👍 1
Selected: A
- Raw zones store structured data, semi-structured data such as CSV files and JSON files, and unstructured data in any format from external sources. Raw zones are useful for staging raw data before performing any transformations. Data can be stored in Cloud Storage buckets or BigQuery datasets. - Curated Zones do not support JSON / CSV
Pime13
👍 2
Selected: B
Auto-discovery needs to be enabled for the curated zone to ensure that Dataplex can scan and register the files. You can configure this setting at the zone or asset level. Option A, moving the JSON and CSV files to the raw zone, would not solve the issue of automatic discovery in the curated zone. The problem lies in the configuration of the curated zone, not the location of the files.
SamuelTsch
👍 1
Selected: A
Raw zones store structured data, semi-structured data such as CSV files and JSON files, and unstructured data in any format from external sources. Curated zones store structured data. Data can be stored in Cloud Storage buckets or BigQuery datasets. Supported formats for Cloud Storage buckets include Parquet, Avro, and ORC.
rajnairds
👍 2
Selected: B
Discovery configuration Discovery is enabled by default when you create a new zone or asset. You can disable Discovery at the zone or asset level. For each Dataplex asset with Discovery enabled, Dataplex does the following: Scans the data associated with the asset. Groups structured and semi-structured files into tables. Collects technical metadata, such as table name, schema, and partition definition. For unstructured data, such as images and videos, Dataplex Discovery automatically detects and registers groups of files sharing media type as filesets. For example, if gs://images/group1 contains GIF images, and gs://images/group2 contains JPEG images, Dataplex Discovery detects and registers two filesets. For structured data, such as Avro, Discovery detects files only if they are located in folders that contain the same data format and schema. Reference : https://cloud.google.com/dataplex/docs/discover-data#exclude-files-from-Discovery
hussain.sain
👍 2
Selected: B
While JSON and CSV can technically be stored in curated zones, it is not a common practice due to the reasons mentioned above. no where in the mention link its mention that there is a restriction.
Anudeep58
👍 4
Selected: A
While none of the original options (A, B, C, or D) directly address the issue, the closest solution is: Move the JSON and CSV files to a raw zone. (This was previously marked as the most voted option, but it's not ideal due to data organization disruption) Here's why this approach might be necessary (but not ideal): Dataplex curated zones currently don't support native processing of JSON and CSV formats. They are designed for structured data formats like Parquet, Avro, or ORC.
chrissamharris
👍 1
Selected: A
Option A https://cloud.google.com/dataplex/docs/add-zone#raw-zones Raw zones are the only zones that support CSV & JSON
joao_01
👍 1
Its B guys, i encounter this in my job, and I had to do B to make it work
demoro86
👍 2
Selected: A
GCP001 agree with him
Moss2011
👍 2
Selected: A
The answer can be found reading a common config of Dataplex in this URL: https://medium.com/google-cloud/google-cloud-dataplex-part-1-lakes-zones-assets-and-discovery-5f288486cb2f
kck6ra4214wm
👍 1
Selected: A
Dataplex does not allow users to create CSV files within a “curated zone”
daidai75
👍 2
Selected: B
According to this URL: https://cloud.google.com/dataplex/docs/discover-data, the auto-discovery can support CSV and Json in both Raw-Zone and Curated-Zone. I also open a console the verify it, both Raw and Curated zone can set up csv&json auto-discovery.
dungct
👍 3
Selected: B
Discovery raises the following administrator actions whenever data-related issues are detected during scans : Inconsistent data format in a table. For example, files of different formats exist with the same table prefix. Inconsistent data format in a table. For example, files of different formats exist with the same table prefix.
Matt_108
👍 4
Selected: B
I'd go for Option B, auto-discovery is enabled by default for any zone, including curated ones, so if a file is not automatically discovered it's due to the disabled auto-discovery
Sofiia98
👍 3
Selected: A
I will go with A, check the ref. Curated zones only store Parquet, Avro, and ORC in CS, and well-defined schema and Hive-style partitions in the BigQuery: https://cloud.google.com/dataplex/docs/add-zone#curated-zones
scaenruy
👍 2
Selected: A
A. Move the JSON and CSV files to the raw zone.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Dataplex curated zones are intended for data that has been transformed and organized for analytics. According to official documentation, curated zones support only Parquet, Avro, ORC, and BigQuery tables. CSV and JSON are semi-structured formats that are not in this allowed list. Therefore, when CSV/JSON files are placed in a curated zone, Dataplex cannot automatically discover and catalog them. Moving the files to a raw zone, which supports any file format including CSV and JSON, is the correct way to ensure discovery. This aligns with the highest-voted community answer and the official reference cited in the comments.Why the Other Options Are Wrong
Option B is incorrect because enabling auto-discovery does not relax the curated zone format restrictions; Dataplex will still not catalog unsupported formats. Option C is wrong because using the bq command-line tool loads data into BigQuery tables, which does not address automatic file discovery in the bucket asset. Option D is wrong because granting object-level access controls permissions, not discovery; the files are not discovered due to format incompatibility, not authorization.Community Comment Notes
The community is split, with 66% favoring option A and 34% favoring option B. Comment 1 correctly points out that curated zones require Parquet, Avro, or ORC format, referencing the official docs. Comment 6 reinforces this by citing the same limitation. Comment 7 argues for option B but misunderstands the core issue: enabling auto-discovery only affects scanning, not whether a file format is eligible for cataloging in a curated zone. Overall, the weighted usefulness of the comments favors the format-restriction explanation.Official Reference
Exam Strategy
When a Dataplex question mentions discovery failures, first check the file formats against the zone type. Remember: raw zones accept almost any format, while curated zones only accept Parquet, Avro, ORC, and BigQuery tables. If you see CSV or JSON in a curated zone, the solution is to move the data to a raw zone, not to toggle discovery settings.