A user's query against a lakehouse table returns a permission error. What is the correct interpretation?
Select an answer to reveal the explanation.
Short Explanation
A permission error is a policy answer, not a data disaster. The table is exactly where it was; the identity running the query just isn't entitled to it.
Full Explanation
The permission-denial interpretation is correct: authorization was evaluated and denied. The statement reached the platform, the object was resolved, and policy declined the request—none of which implies anything about the data's existence or integrity. The lost-table interpretation is incorrect because a missing table produces a resolution error, not a denial, and treating every failure as data loss leads to unnecessary and risky restores. The undersized-engine interpretation is incorrect because capacity limits present as queuing, timeouts or resource errors, not as access denials. The offline-source interpretation is incorrect because an unavailable source produces a connectivity error; it does not manifest as a permission failure. For the exam, read the error class first—permission, resolution, syntax or connectivity—because it names the area to investigate.