A query worked yesterday and now returns an object-not-found error, with no infrastructure changes. What is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
Resolution errors are naming problems: something moved, got renamed, or the session's pointing at a different catalog or schema context. Look at the identifier and the context around it.
Full Explanation
The correct answer is that the object was renamed, dropped, or is being referenced from a different catalog or schema context than before. An object-not-found error is a resolution failure. Either the object no longer exists under that name, or the session's catalog and schema context differs so the identifier resolves elsewhere - a very common cause when a connection's defaults change.
The claim that the engine has run out of memory and cannot resolve names is incorrect because memory exhaustion produces resource errors during execution, not name resolution failures.
The claim that the storage bucket has reached its capacity limit is incorrect because a full bucket affects writes; it does not hide existing table definitions.
The claim that the query history retention period expired for that statement is incorrect because history retention concerns the record of past executions and has no effect on whether an object resolves.
For the exam, treat resolution errors as questions about names and context, not about capacity.