Explanation:
The correct scenario to use an external table is when the data must be stored in a specific external location (e.g., cloud storage) and retain the data even if the table is dropped. Managed tables store data in a system-managed location, and their data is deleted upon table deletion. Here, the engineer wants explicit control over the storage path in an external location.
LOCATION path in an external storage. This ensures the data resides in the specified path and persists after table deletion.LOCATION clause is used instead.LOCATION; specifying a custom path implicitly creates an external table, not a managed one.Ultimate access to all questions.
A Data Engineer must create a Parquet bronze table that persists in a designated external storage path.
Which type of table should be created in this situation?
A
An external table where the location is pointing to specific path in external location.
B
An external table where the schema has managed location pointing to specific path in external location.
C
A managed table where the catalog has managed location pointing to specific path in external location.
D
A managed table where the location is pointing to specific path in external location.
No comments yet.