External vs managed tables in Hadoop - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference in data deletion behavior

When you drop a managed table in Hadoop, what happens to the underlying data files?

A The data files are moved to a backup location automatically.

B Only the table metadata is deleted; data files remain untouched.

C The data files are archived but not deleted.

D The data files are deleted along with the table metadata.

💡 Hint

Think about who controls the data lifecycle in managed tables.

Managed tables control both metadata and data. Dropping them deletes both.

🧠 Conceptual

intermediate

Location of data for external tables

Where is the data stored for an external table in Hadoop?

A In a user-specified location outside the warehouse directory.

B In the default warehouse directory managed by Hadoop.

C In a temporary directory that is deleted after use.

D In the Hadoop system memory only.

💡 Hint

External tables allow you to keep data where you want.

External tables point to data stored outside the default warehouse directory.

❓ data_output

advanced

Effect of dropping external table

Given an external table pointing to data at /user/data/sales, what happens to the data files if you run DROP TABLE external_sales;?

Hadoop

CREATE EXTERNAL TABLE external_sales(id INT, amount FLOAT) LOCATION '/user/data/sales';
-- Then run:
DROP TABLE external_sales;

A An error occurs because external tables cannot be dropped.

B Only table metadata is deleted; data files remain at /user/data/sales.

C Data files are moved to a temporary backup folder.

D Data files at /user/data/sales are deleted.

💡 Hint

Dropping external tables affects metadata only.

Dropping an external table deletes only metadata; data files remain intact.

🔧 Debug

advanced

Unexpected data loss after dropping table

A user created a managed table and loaded data into it. After dropping the table, the data files are missing. What is the most likely cause?

A The table was external, but the data was manually deleted.

B The DROP TABLE command only deletes metadata, so data loss is impossible.

C The table was managed, so dropping it deleted the data files.

D The data files were stored outside the warehouse directory.

💡 Hint

Recall the difference in data handling between managed and external tables.

Managed tables control data lifecycle; dropping them deletes data files.

🚀 Application

expert

Choosing table type for data sharing

You want to create a table in Hadoop that allows multiple teams to access shared data without risk of accidental deletion of the data files. Which table type should you choose?

A External table, because it keeps data files separate from metadata management.

B Managed table, because it handles data lifecycle automatically.

C Temporary table, because it is session-specific and safe.

D Partitioned managed table, because partitions isolate data.

💡 Hint

Think about which table type protects data files from deletion when dropped.

External tables keep data files outside Hadoop's control, preventing accidental deletion.

Practice

1. What is the main difference between a managed table and an external table in Hadoop?

easy

A. Managed tables do not store any data, external tables store all data inside Hadoop.

B. External tables store data inside Hadoop, managed tables store data outside Hadoop.

C. Managed tables store and manage data files within Hadoop, while external tables only manage metadata and keep data files outside Hadoop.

D. There is no difference; both manage data files the same way.

Solution

1. Step 1: Understand managed table behavior

   Managed tables store data files inside Hadoop's warehouse directory and Hadoop controls their lifecycle.

2. Step 2: Understand external table behavior

   External tables only manage metadata in Hadoop but keep data files at an external location you specify.

3. Final Answer:

   Managed tables store and manage data files within Hadoop, while external tables only manage metadata and keep data files outside Hadoop. -> Option C

4. Quick Check:

   Managed = data + metadata, External = metadata only [OK]

Hint: Managed = Hadoop controls data; External = you control data location [OK]

Common Mistakes:

• Confusing where data files are stored
• Thinking external tables delete data on drop
• Assuming managed tables don't store data

2. Which of the following is the correct HiveQL syntax to create an external table?

easy

A. CREATE TABLE my_table (id INT, name STRING) LOCATION '/user/data' EXTERNAL;

B. CREATE TABLE my_table EXTERNAL (id INT, name STRING) LOCATION '/user/data';

C. CREATE TABLE my_table (id INT, name STRING) EXTERNAL LOCATION '/user/data';

D. CREATE EXTERNAL TABLE my_table (id INT, name STRING) LOCATION '/user/data';

Solution

1. Step 1: Recall correct syntax for external table creation

   The keyword EXTERNAL comes immediately after CREATE and before TABLE.

2. Step 2: Check location clause placement

   The LOCATION clause specifies the external data path and comes after the column definitions.

3. Final Answer:

   CREATE EXTERNAL TABLE my_table (id INT, name STRING) LOCATION '/user/data'; -> Option D

4. Quick Check:

   EXTERNAL after CREATE, LOCATION after columns [OK]

Hint: EXTERNAL goes right after CREATE in HiveQL [OK]

Common Mistakes:

• Placing EXTERNAL after TABLE keyword
• Misplacing LOCATION clause
• Omitting EXTERNAL keyword for external tables

3. Consider the following Hive commands:

CREATE EXTERNAL TABLE ext_table (id INT) LOCATION '/data/ext';
CREATE TABLE man_table (id INT);

What happens if you drop ext_table and man_table respectively?

medium

A. Dropping ext_table deletes data files; dropping man_table deletes only metadata.

B. Dropping ext_table deletes only metadata; dropping man_table deletes both metadata and data files.

C. Both drops delete only metadata, data files remain.

D. Both drops delete metadata and data files.

Solution

1. Step 1: Understand drop behavior for external tables

   Dropping an external table removes only metadata; data files at '/data/ext' remain untouched.

2. Step 2: Understand drop behavior for managed tables

   Dropping a managed table removes metadata and deletes data files stored in Hadoop's warehouse.

3. Final Answer:

   Dropping ext_table deletes only metadata; dropping man_table deletes both metadata and data files. -> Option B

4. Quick Check:

   External drop = metadata only, Managed drop = metadata + data [OK]

Hint: External drop keeps data; managed drop deletes data [OK]

Common Mistakes:

• Assuming external drop deletes data files
• Thinking managed drop keeps data files
• Confusing metadata and data deletion

4. You created an external table but accidentally omitted the LOCATION clause. What will happen when you try to query this table?

medium

A. Query will fail because LOCATION is mandatory for external tables.

B. Query will succeed using default warehouse location, behaving like a managed table.

C. Query will succeed but return no data.

D. Hive will automatically assign a random external location.

Solution

1. Step 1: Check requirement of LOCATION for external tables

   External tables require LOCATION to specify where data files reside outside Hadoop's warehouse.

2. Step 2: Understand consequence of missing LOCATION

   Without LOCATION, Hive cannot find external data, so query fails with an error.

3. Final Answer:

   Query will fail because LOCATION is mandatory for external tables. -> Option A

4. Quick Check:

   External tables need LOCATION [OK]

Hint: External tables must have LOCATION clause [OK]

Common Mistakes:

• Assuming default location is used for external tables
• Thinking query returns empty data silently
• Believing Hive auto-assigns external location

5. You have important data files stored in HDFS at /user/hadoop/data. You want to create a table in Hive to query this data but ensure that deleting the table does NOT delete the data files. Which table type should you create and what is the correct approach?

hard

A. Create an external table with LOCATION '/user/hadoop/data' so Hive manages metadata only and leaves data intact on drop.

B. Create a managed table and copy data files into Hive warehouse; data will be deleted on drop.

C. Create a managed table with LOCATION '/user/hadoop/data' to keep data files safe on drop.

D. Create an external table without specifying LOCATION; Hive will manage data safely.

Solution

1. Step 1: Identify requirement to keep data files safe on table drop

   Only external tables keep data files untouched when the table is dropped.

2. Step 2: Use external table with explicit LOCATION

   Specify LOCATION '/user/hadoop/data' so Hive knows where data files are stored externally.

3. Step 3: Understand managed table behavior

   Managed tables store data in warehouse and delete data files on drop, so not suitable here.

4. Final Answer:

   Create an external table with LOCATION '/user/hadoop/data' so Hive manages metadata only and leaves data intact on drop. -> Option A

5. Quick Check:

   External + LOCATION = safe data on drop [OK]

Hint: Use external table with LOCATION to protect data files [OK]

Common Mistakes:

• Using managed table and losing data on drop
• Omitting LOCATION for external table
• Assuming managed table can protect external data