Question 560 A table's column-level lineage shows a confidential input transformed into a derived metric. What should a steward evaluate before downgrading the metric classification? Only whether the SQL query ran quickly Only whether the derived table is smaller Whether the derivation can reveal sensitive information and what downstream consumers can access Only whether its column name avoids the word confidential Explanation Correct Answer C:A derived metric may remain sensitive depending on granularity, transformations and reidentification risks. Incorrect Answers A:Compute performance is not an information-disclosure assessment. B:Row count or storage size does not prove privacy of a derived value. D:Renaming a column does not establish safe declassification.
Question 561 A team applies a governed tag to a managed table but later moves the data into a separately registered external table. What should the migration checklist include? Only copying the Delta files Only matching the warehouse size Only retaining the old table nickname Explicit verification of classification, table grants, and tag-based policy coverage on the new securable Explanation Correct Answer D:Governed policy applicability cannot be assumed to transfer automatically between independently registered objects. Incorrect Answers A:Files alone do not establish all securable metadata and enforced grants. B:Compute size does not carry policy metadata. C:Names do not independently preserve classification and authorization.
Question 562 A company needs department-level chargeback for sensitive datasets, but the billing reports should not expose individual transaction rows. What design respects governance? Grant finance analysts full SELECT on every sensitive fact table Aggregate usage and cost metadata separately from protected underlying business records Publish raw customer records in an unrestricted shared catalog Disable permissions to generate accurate invoices Explanation Correct Answer B:Financial allocation can be reported with minimized operational metadata rather than broad raw data exposure. Incorrect Answers A:Cost reporting does not require disclosure of all transaction contents. C:Public detailed records are unrelated to the requested summarized cost accounting. D:Removing governance is not a necessary chargeback prerequisite.
Question 563 A production job writes to an external Delta path. It can update catalog metadata but cloud permissions deny writes to the underlying location. What distinction explains failure? Renaming the job task changes its storage credential rights Catalog object grants and underlying cloud storage credentials are both part of the access path Catalog metadata permission always grants cloud IAM access Increasing Spark partitions creates cloud IAM privileges Explanation Correct Answer B:Authorization at the metastore layer cannot override a missing cloud file-write permission. Incorrect Answers A:Task names do not change the underlying cloud permission. C:Storage IAM permissions are evaluated by the underlying cloud access path. D:Partition counts change computation, not storage authorization.
Question 564 An engineer wants to share a view that joins a permitted table with an internal restricted reference table. What must the provider validate? A joined view can never contain sensitive values Every source table must automatically be granted raw SELECT to recipients The shared object is supported and exposes only approved data under the provider's governance rules Only the notebook author's workspace role Explanation Correct Answer C:Sharing a derived object requires verification of supported sharing behavior and the actual output data boundary. Incorrect Answers A:Joins can reveal sensitive information depending on keys and selected fields. B:Recipient permissions should not expand to unrelated source records by default. D:Notebook workspace roles do not fully describe share object and source policy.
Question 565 A service principal with broad SELECT permissions is used by an orchestration system to produce customer extracts. The organization wants to limit what an accidental bug can export. Which change is most direct? Reduce only the destination export file size while keeping source table access unrestricted Narrow source privileges and constrain approved target destinations for the service identity Disable audit logging Limit the job compute size but retain broad customer-data SELECT privileges Explanation Correct Answer B:Reducing readable data and possible egress targets limits blast radius of faulty extraction logic. Incorrect Answers A:Smaller output chunks do not restrict which customer rows the service identity is authorized to read or where those rows are exported. C:Hiding activity increases risk and does not reduce data reachable by the principal. D:Compute quotas do not implement least-privilege source access or approved egress destinations for the extraction principal.
Question 566 An analyst reports two tables with identical names in different catalogs. How should a governed query avoid using the wrong one? Assume the notebook chooses the business-approved catalog automatically Rely on column sort order alone Use a fully qualified catalog.schema.table reference and validate privileges Rename all catalogs to a shared identifier Explanation Correct Answer C:Full qualification identifies the intended securable within the Unity Catalog namespace. Incorrect Answers A:Session defaults may differ; explicit qualification avoids accidental cross-catalog reads. B:Sorting does not distinguish identically named tables in different namespaces. D:Removing namespace distinction defeats separation and can create conflicts.
Question 567 A pipeline stores raw files in Unity Catalog volumes but the data steward wants SQL access to standardized rows. What additional governed asset is generally needed? Only a volume display name A public object bucket instead of the volume A registered table or view produced by approved ingestion/transformation from the files Only a workspace folder for the scripts Explanation Correct Answer C:Volumes govern file access; SQL table semantics for normalized rows normally require a table or suitable view. Incorrect Answers A:A filename namespace does not automatically define the relational schema and query object. B:Public file storage does not create the requested governed SQL dataset. D:Workspace folders organize code rather than expose transformed data as a governed table.
Question 568 A security reviewer sees that a pipeline can read a restricted table because of a broad group grant inherited from the catalog, not a direct table grant. What is the appropriate remediation? Only reduce the cluster worker count Adjust the overly broad ancestor/group grant while preserving necessary scoped access Repeatedly revoke SELECT on the single table without changing the ancestor Only rename the catalog to restricted Explanation Correct Answer B:Effective inherited grants must be narrowed at their actual source; removing a nonexistent direct grant will not fix exposure. Incorrect Answers A:Compute resources do not change effective SELECT rights. C:Inheritance may continue to authorize the pipeline even when local grants are absent. D:Renaming does not narrow inherited privileges.
Question 569 A catalog is bound to a development workspace in read/write mode and to a production analytics workspace in read-only mode. What should a governance acceptance test verify? Confirm only that both workspaces can SELECT from the catalog That job retries bypass read-only mode Every workspace can create and overwrite tables equally Writes are permitted only in allowed workspaces while approved reads work as intended Explanation Correct Answer D:Workspace binding modes can limit allowed operations independently of principal table grants. Incorrect Answers A:Read success does not test the required difference between read-only and read/write workspace bindings. B:Retrying a denied operation does not remove an enforced binding constraint. C:That conflicts with an explicitly read-only workspace binding.
Question 570 A compliance officer requests access to audit logs containing user identifiers. What least-privilege principle should guide granting that access? Give public SELECT to show transparency Publish raw tokens from logs to dashboards Allow all users to delete audit records Limit audit-data readership to authorized reviewers and the necessary retention scope Explanation Correct Answer D:Audit datasets can contain sensitive identity and activity records and should themselves be governed. Incorrect Answers A:Public audit log access may expose sensitive operational information. B:Raw credentials must not be exposed through audit reports. C:Deletion could destroy evidence needed for investigations.