COF-C03 Data Collaboration Practice Question
A provider shares a secure view named SALES_VIEW with a consumer. The view references a table in the provider's database. The provider later renames the underlying table. What is the impact on the consumer's access to SALES_VIEW?
⚠ Common exam trap
The trap here is assuming that renaming a base table breaks a dependent view, when Snowflake resolves views through internal object IDs rather than by name.
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 consumer's access is unaffected because the view continues to resolve to the renamed table.
Views in Snowflake reference base objects by internal object identifiers, not by name. Renaming a table therefore does not invalidate dependent views, and a shared secure view continues to function for the consumer. The consumer's access remains intact without any action on either side, which is the key behavior tested here.
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 consumer must recreate the database from the share to see the renamed table through the view.
Why it's wrong here
Recreating the database from the share is unnecessary because the view remains valid after the rename. The share and its grants are unchanged, and the consumer's existing mounted database continues to resolve the view correctly. This action would be redundant and would not address any actual issue.
- ✗
The consumer loses access because the view definition becomes invalid and must be re-created.
Why it's wrong here
Renaming a table does not invalidate a view that references it. Snowflake stores object references by internal identifiers, so the view continues to resolve to the renamed table. The consumer's access is unaffected, and no re-creation is needed, making this option incorrect for the scenario.
- ✓
The consumer's access is unaffected because the view continues to resolve to the renamed table.
Why this is correct
Snowflake views bind to underlying objects by internal object ID rather than by name. Renaming the base table does not break the view's definition, so the shared secure view remains valid and the consumer retains access. This is the expected behavior and the reason the rename has no impact on the consumer.
- ✗
The consumer sees an error only if the renamed table is also granted directly in the share.
Why it's wrong here
Direct grants of the table are independent of the view's validity. Renaming the table does not break direct grants either, since grants follow the object's internal identity. The presence or absence of a direct grant has no bearing on whether the view resolves, so this condition is irrelevant.
About these practice questions
Courseiva writes every COF-C03 question from scratch — 280 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.