Databricks-DE-Pro Data Security and Compliance Practice Question
When migrating an existing Hive metastore to Unity Catalog, what is the most important security consideration regarding object naming?
⚠ Common exam trap
Candidates often focus solely on permission remapping while ignoring that Unity Catalog enforces a strict three-level namespace structure.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The object names must fit the catalog.schema.table structure.
In Unity Catalog, the three-level namespace (catalog.schema.table) is mandatory. Existing Hive metastore objects often lack this structure and may contain characters or naming patterns that are incompatible with Unity Catalog's standards. Ensuring a clean naming convention during migration is not just a structural requirement; it is a security necessity to ensure that existing access policies can be correctly migrated and enforced in the new, more rigorous governance environment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Table names must be all uppercase.
Why it's wrong here
Unity Catalog does not require uppercase table names. While it is good practice to follow consistent naming conventions, there is no technical requirement for uppercase. Names must simply be unique and adhere to the syntax rules defined in the Unity Catalog documentation for object identifiers.
- ✓
The object names must fit the catalog.schema.table structure.
Why this is correct
Unity Catalog requires a strict three-level namespace. During migration, existing objects must be mapped to this structure. Failure to do so will prevent the object from being accessible within the new governed environment, potentially leading to downtime or security gaps during the transition from the legacy Hive metastore.
- ✗
Legacy object owners must be deleted.
Why it's wrong here
Deleting owners is not a migration requirement and would be highly disruptive. Unity Catalog allows for the reassignment of ownership during the migration process. It is important to map existing ownership to the new Unity Catalog principals, but this does not require deleting the legacy user accounts themselves.
- ✗
All tables must be converted to Parquet.
Why it's wrong here
While Parquet is a common and efficient format, Unity Catalog supports various formats including Delta Lake. Migration to Unity Catalog does not mandate a file format change. The primary focus of the migration is on metadata mapping, namespace structure, and ensuring that access control policies are correctly translated and applied.
About these practice questions
One of 267 original Databricks-DE-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Pro exam.