COF-C03 Data Collaboration Practice Question
A provider is preparing to share data with a consumer using a direct share. The provider wants to ensure that the consumer can query a specific table and also see any future columns added to that table without additional grants. Which two actions must the provider take? (Choose two.)
⚠ Common exam trap
The trap here is thinking that future columns require additional grants or a view, when in fact a table-level SELECT grant covers all current and future columns.
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
✓
Grant USAGE on the database and schema containing the table to the share.
To share a table and automatically include future columns, the provider must grant USAGE on the database and schema to the share, and grant SELECT on the table to the share. SELECT on a table applies to all columns, including those added later. No column-level grants are needed. A secure view is not required for this purpose.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Grant USAGE on the database and schema containing the table to the share.
Why this is correct
Granting USAGE on the database and schema to the share is required so that the consumer can access the schema and see the table. Without these grants, the consumer cannot navigate to the table even if SELECT is granted on the table itself. This is a foundational step for any share.
- ✗
Grant REFERENCES on the table to the share to allow future columns to be visible.
Why it's wrong here
REFERENCES is used for foreign key constraints, not for granting query access or making columns visible. It does not enable SELECT access. Granting REFERENCES would not allow the consumer to query the table or see new columns. This privilege is irrelevant to data sharing for query purposes.
- ✗
Grant SELECT on each future column to the share as they are added.
Why it's wrong here
Snowflake does not support column-level grants for shares. Privileges are granted at the table level. When SELECT is granted on a table, all current and future columns are included. There is no need to grant privileges on individual columns. This option describes an unnecessary and unsupported action.
- ✓
Grant SELECT on the table to the share.
Why this is correct
Granting SELECT on the table to the share allows the consumer to query the table. This is the core privilege that enables data access. When new columns are added to the table, they are automatically included in the share because the SELECT privilege applies to the entire table, not specific columns. This satisfies the requirement for future columns.
- ✗
Create a secure view that selects all columns from the table and grant SELECT on the view to the share.
Why it's wrong here
While a secure view can be used to share data, it is not required to automatically include future columns. A secure view would need to be altered to include new columns if it explicitly lists them. If the view uses SELECT *, it might include new columns, but that is not guaranteed and depends on the view definition. This adds complexity and is not a mandatory step.
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.