COF-C03 Data Collaboration Practice Question
A provider's account is named PROVIDER_ACCT and it has created a share named PARTNER_SHARE that already contains a secure view. The provider now runs: ALTER SHARE PARTNER_SHARE ADD ACCOUNTS = CONSUMER_ACCT; What is the effect of this command in the provider's environment?
⚠ Common exam trap
The trap here is assuming that adding a consumer account to a share also creates the shared database in that consumer account, when the consumer must perform the CREATE DATABASE ... FROM SHARE step.
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
✓
It grants CONSUMER_ACCT the ability to read the share, but a database must still be created in CONSUMER_ACCT before any shared data is visible there.
A share is only an authorization container; adding a consumer account simply permits that account to see an inbound share. Consumers must then create a database from the share with a role that has CREATE DATABASE before any tables become queryable. The provider cannot perform that step on the consumer's behalf, which is why the data is not instantly usable after the ALTER SHARE command.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It fails because the ADD ACCOUNTS clause is only valid at share creation time and cannot be used on an existing share.
Why it's wrong here
ALTER SHARE ... ADD ACCOUNTS is a supported, routine operation used to extend an existing share to additional consumer accounts. Shares are mutable: providers add and remove accounts as partnerships change. The clause is not restricted to the CREATE SHARE statement, so the command succeeds rather than failing.
- ✓
It grants CONSUMER_ACCT the ability to read the share, but a database must still be created in CONSUMER_ACCT before any shared data is visible there.
Why this is correct
Adding an account to a share only authorizes that consumer account and places a share object in its 'inbound' area; nothing is readable until a consumer-side role with CREATE DATABASE runs CREATE DATABASE ... FROM SHARE. Until that database is created, the consumer sees only an available share, not tables. This is exactly how data sharing provisioning works.
- ✗
It immediately creates a read-only database in CONSUMER_ACCT containing all objects in the share, usable without any further consumer action.
Why it's wrong here
Sharing never auto-creates objects in the consumer account. The consumer must explicitly run CREATE DATABASE ... FROM SHARE using a role holding CREATE DATABASE on the account. The provider cannot create databases in another account, so no read-only database appears automatically as a result of this ALTER SHARE statement.
- ✗
It converts the share into a listing that is publicly discoverable on the Snowflake Marketplace by all Snowflake accounts.
Why it's wrong here
Adding a consumer account to a direct share keeps the share private between the two named accounts. Marketplace publication requires a listing, which involves separate provider-profile and listing-creation steps. A direct share is not discoverable by other accounts, and the ALTER SHARE statement does not create any listing object.
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.