COF-C03 Account Management and Data Governance Practice Question
A user with the role DATA_ANALYST has been granted the USAGE privilege on a database and schema, but when they try to query a table in that schema, they receive an error that the table does not exist. The table exists and is owned by the role DATA_ENGINEER. What is the most likely cause of this issue?
⚠ Common exam trap
The trap here is interpreting the 'table does not exist' error literally, when it often indicates a missing privilege rather than a missing object.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The DATA_ANALYST role lacks the SELECT privilege on the table.
In Snowflake, to query a table, a role must have the SELECT privilege on that table. Having USAGE on the database and schema only allows navigation and listing. Without SELECT, the table is effectively inaccessible, and Snowflake returns a 'table does not exist' error to avoid leaking information. Granting SELECT to DATA_ANALYST resolves the problem. Ownership by another role does not prevent granting privileges.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The table is owned by DATA_ENGINEER, and ownership transfers all privileges, so DATA_ANALYST cannot access it.
Why it's wrong here
Ownership does not automatically grant privileges to other roles; it simply means DATA_ENGINEER has full control over the table. However, privileges can be granted to other roles. The issue is not ownership itself but the lack of explicit grant. If DATA_ANALYST had been granted SELECT, they could query the table regardless of ownership. Thus, this is not the cause.
- ✓
The DATA_ANALYST role lacks the SELECT privilege on the table.
Why this is correct
In Snowflake, having USAGE on a database and schema allows you to see the schema and potentially list objects, but to query a table, you need the SELECT privilege on that table. Without SELECT, the table appears as if it does not exist when queried. The error message 'table does not exist' is often misleading; it can also mean the user lacks privileges. Granting SELECT on the table to DATA_ANALYST would resolve the issue.
- ✗
The DATA_ANALYST role does not have USAGE on the database and schema.
Why it's wrong here
The scenario states that the user has been granted USAGE on the database and schema. Therefore, this cannot be the cause. If they lacked USAGE, they would not even be able to see the schema or list tables. The error would be different, such as 'Schema does not exist' or 'Database does not exist'. Hence, this option is incorrect.
- ✗
The table is a secure view, and secure views require additional privileges.
Why it's wrong here
Secure views do not require additional privileges beyond SELECT on the view itself. The scenario does not mention that the table is a secure view; it is described as a table. Even if it were a secure view, the user would still need SELECT on the view. The lack of SELECT is the root cause, not the secure view property.
Visual reference
About these practice questions
One of 280 original COF-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Snowflake exam blueprint
This COF-C03 practice question is part of Courseiva's free Snowflake certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the COF-C03 exam.