Question 470 A data steward drops an external Unity Catalog table but another authorized system still needs its underlying files. What is the important expected distinction? The metastore must delete all catalogs in the account DROP TABLE is always the same as recursively deleting its cloud container Dropping external table metadata does not inherently delete external storage data A warehouse restart restores the dropped table definition automatically Explanation Correct Answer C:The external table registration and underlying cloud files have separable lifecycles. Incorrect Answers A:Removing one table does not require changing unrelated catalogs. B:Automatic deletion of external storage files is not the general external-table lifecycle contract. D:Compute restarts do not serve as authoritative metadata recovery.
Question 471 A cloud administrator has created a storage credential. The data team needs an authorized binding between that credential and a specific object-storage path. Which Unity Catalog securable is appropriate? An SQL dashboard tile An external location referencing the credential and approved path Grant SELECT on an existing external table but do not define a credential-to-path external location Define a storage credential without scoping the cloud path to the required external location Explanation Correct Answer B:An external location combines a cloud storage URL with a storage credential under centrally managed permissions. Incorrect Answers A:A dashboard tile is a presentation object, not a storage access boundary. C:Table SELECT controls table reads, while the requested governed binding between a storage credential and a cloud path requires an external location. D:A credential alone is not the governed path binding needed to authorize access to a specific cloud-storage prefix.
Question 472 A new external table is to be created at a registered location. The engineer has schema CREATE TABLE but no right to use the storage location. What else should be checked? The required external location privilege and storage authorization Ownership of every job that might later read the table MANAGE on every catalog in the metastore EXECUTE on all SQL functions in the workspace Explanation Correct Answer A:External table creation needs relevant location access in addition to schema-level object creation rights. Incorrect Answers B:Downstream job ownership does not grant creation access to a cloud path. C:Other catalogs' privileges are not needed for an approved single external location. D:Function execution is not a blanket authorization for storage-backed table creation.
Question 473 A platform team must allow applications to read flat files stored under a governed directory path using Unity Catalog volumes. Which privilege is directly relevant? MODIFY on all schemas SELECT on a nearby table only READ VOLUME on the relevant volume with required parent usage CREATE CATALOG across the metastore Explanation Correct Answer C:Volume file reads are controlled through volume-specific access grants, distinct from table SELECT. Incorrect Answers A:Table data modification privileges are not equivalent to volume reading. B:SELECT on a table does not directly grant reading arbitrary volume file paths. D:Catalog creation is unrelated to reading approved files.
Question 474 An ML preprocessing job must write checkpoint files to an approved Unity Catalog volume but must not modify business tables. Which narrow grant is needed? CREATE EXTERNAL LOCATION on the metastore WRITE VOLUME for the target volume, with required parent usage Ownership of the schema MODIFY on every table in the schema Explanation Correct Answer B:Volume writes can be allowed independently from broad table MODIFY privileges. Incorrect Answers A:The job does not need to register new cloud storage locations. C:Schema ownership gives more governance control than writing one volume. D:Writing checkpoint files does not require the ability to update all tables.
Question 475 A job fails reading `/Volumes/team/raw/input/file.csv` even though it can SELECT from a table in the same schema. Which distinction matters? Grant SELECT on the table again without granting read privileges on the volume Queries against tables always authorize file systems The file must be converted to a notebook Volume paths require volume access privileges independent from table SELECT Explanation Correct Answer D:Data table SELECT does not automatically authorize raw file operations through Unity Catalog volumes. Incorrect Answers A:Table SELECT is a different securable privilege from READ VOLUME for files under a governed volume path. B:Relational object grants and file access are distinct securable permissions. C:File conversion is unnecessary when the underlying authorization is corrected.
Question 476 An analyst wants to know which source tables contributed to a curated sales table after a scheduled SQL transformation. Which governance capability should they inspect? Unity Catalog lineage where supported capture is available Consult job schedule timestamps alone without table dependency metadata Inspect only the latest SQL query string without the captured upstream/downstream lineage Only a cloud object's modification timestamp Explanation Correct Answer A:Lineage relationships can show upstream and downstream table dependencies for supported operations. Incorrect Answers B:Run times do not identify the specific table lineage captured by supported governed transformations. C:A query text sample may mention a source, but does not provide the supported recorded asset dependency chain requested. D:File timestamps alone do not establish complete data transformation lineage.
Question 477 A privacy officer needs to identify which downstream tables may inherit sensitive source attributes before an upstream schema change. Which tool is best suited? Review only table-level lineage and assume it identifies every affected downstream field Unscoped grant of all catalogs to the officer Notebook spelling checker Column-level lineage information where available Explanation Correct Answer D:Column lineage can reveal derived downstream fields and the possible reach of an upstream change. Incorrect Answers A:Table-level dependencies can miss which particular columns propagate a sensitive attribute; column-level lineage is more precise. B:Broader permissions do not themselves identify column dependencies. C:Code spelling does not map downstream column derivations.
Question 478 A data engineer sees a governance lineage graph missing one transformation executed outside supported capture paths. What should the engineer avoid claiming? That any captured edge proves a downstream dependency That impact review can use lineage plus other system evidence That the lineage graph is necessarily exhaustive across every external operation That source and target names can be associated in tracked jobs Explanation Correct Answer C:Lineage capture depends on supported execution and integration context; omissions cannot be ruled out solely from the graph. Incorrect Answers A:An existing captured edge can be useful evidence of a documented relationship. B:Combining lineage with other operational records can strengthen an investigation. D:Tracked SQL workflows can produce useful origin relationships.
Question 479 An organization must redact national identity numbers for most consumers while letting a restricted team see full values. Which governance technique addresses column values? Grant storage-path access to all workspace members instead of to the intended identity A Unity Catalog column mask policy for the sensitive column Turning off audit logging for analysts Grant the restricted team a separate SQL warehouse without masking the source column Explanation Correct Answer B:Column masking can apply governed expressions to restrict sensitive values according to the applicable policy context. Incorrect Answers A:Broad path rights violate the least-privilege requirement and do not preserve the intended scoped data access. C:Less audit visibility does not implement value-level data protection. D:Compute isolation does not redact identity-number values for other principals who still have SELECT on the shared column.
Question 480 Regional sales representatives should see only their assigned territory records from a shared governed table. What governance control most directly addresses row visibility? A row filter on the protected table based on authorized context One global SELECT grant with no filter Only a column comment on territory Apply a column mask to the territory field while returning all rows Explanation Correct Answer A:Row filters can restrict visible records at query time according to implemented policy logic. Incorrect Answers B:Broad unfiltered access would not enforce regional record restrictions. C:Comments document a field but do not filter the data returned. D:Column masking can hide or transform a field, but does not restrict which territory records the query returns.