After a table is registered in Data manager, an analyst still cannot query it through the engine they use. What should be checked first?
Select an answer to reveal the explanation.
Short Explanation
Registration only makes the table exist. It doesn't make it reachable from your engine or grant you access. Check whether the table's catalog is associated with your engine and whether policy grants you access.
Full Explanation
The correct answer is the option about whether the catalog containing that table is associated with the analyst's engine and whether policy grants them access. Registration, association, and entitlement are three separate steps. A registered table is invisible to an engine whose catalog list does not include it, and invisible to a user whose policies do not permit it. Checking both explains the great majority of these cases.
The option about re-uploading the table's data files after registration is incorrect because registration does not require the files to be rewritten. The catalog entry references the data where it already sits.
The option about clearing query history is incorrect because query history is a record of past executions and plays no part in resolving a table.
The option about moving the bucket to a faster storage tier is incorrect because storage tier affects read latency and cost, never visibility.
For the exam, run the sequence in order when a table cannot be queried: registered, associated, permitted.