CERTIFIED-DATA-ANALYST-ASSOCIATE Question #78: Real Exam Question with Answer & Explanation

Question

A database was created in Databricks SQL using the following statement: CREATE SCHEMA accounting LOCATION 'dbfs:/accounting/data'; Where will data for this database be stored?

Options

• Adbfs:/accounting/data/accounting.db
• Bdbfs:/accounting/data
• Cdbfs:/accounting/data.db
• Ddbfs:/user/hive/warehouse/accounting.db

Explanation

When you specify a LOCATION in CREATE SCHEMA, Databricks uses that exact path as-is for storing the database's data - making B (dbfs:/accounting/data) correct. The location clause is a direct override that tells Databricks exactly where to put data, with no path transformation applied.

Why the distractors are wrong:

• A (dbfs:/accounting/data/accounting.db) - Databricks does not append the schema name plus .db to a custom location; that suffix pattern is a Hive artifact, not how explicit LOCATION paths work.
• C (dbfs:/accounting/data.db) - Same misconception: Databricks does not append .db to a custom LOCATION path.
• D (dbfs:/user/hive/warehouse/accounting.db) - This is where data would be stored if no LOCATION was specified (the default Hive metastore path). Specifying LOCATION explicitly overrides this default entirely.

Memory tip: Think of LOCATION as GPS coordinates - you're telling Databricks the exact destination, and it goes there directly without adding anything to the address. Only when you give no directions at all does it fall back to the default warehouse route.

No community discussion yet for this question.