Question 120
For Orion Network Services, an operational assessment affecting subscriber applications and remote operations uncovers: A new team cannot create tables because it attempts to write directly into another department's restricted catalog. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
The team creates a table in its authorized namespace while writes to the restricted catalog are denied. The observation provides evidence that the proposed fix (Provision an appropriate catalog or schema and scoped object-creation rights for the team's workload.) addressed the reported issue (A new team cannot create tables because it attempts to write directly into another department's restricted catalog.) for Orion Network Services and its subscriber applications and remote operations. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
An authorized job reads the governed volume path while an unrelated principal is denied. This is suitable evidence for another condition (A team stores unstructured model files in an unmanaged notebook workspace folder instead of an access-controlled governed location.) after a different response (Create an appropriate Unity Catalog volume for non-tabular files with scoped access.). For Orion Network Services, it does not prove the required result: The team creates a table in its authorized namespace while writes to the restricted catalog are denied.
A catalog inventory shows distinct governed namespaces and queries resolve to the intended team's objects. This is suitable evidence for another condition (Two product teams create tables with ambiguous unqualified names and repeatedly query the wrong customer dataset.) after a different response (Organize data into appropriate Unity Catalog schemas and use qualified catalog schema table references.). For Orion Network Services, it does not prove the required result: The team creates a table in its authorized namespace while writes to the restricted catalog are denied.
A production job reads the correct qualified table and an identically named test table remains untouched. This is suitable evidence for another condition (A team creates a new schema with an existing business name in a different catalog and clients accidentally use the wrong target.) after a different response (Require complete three-level object names and update job configuration to reference the intended catalog and schema.). For Orion Network Services, it does not prove the required result: The team creates a table in its authorized namespace while writes to the restricted catalog are denied.