COF-C03 Data Collaboration Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  ALTER ACCOUNT consumer_account ADD SHARE share_name;

  Why it's wrong here

  The provider cannot alter the consumer's account to add a share. Sharing is initiated by the provider through the share object. The consumer does not need to be modified by the provider. This option reverses the direction of control and uses a command that would not work across accounts, as ALTER ACCOUNT affects only the current account.

• ✓

  ALTER SHARE share_name ADD ACCOUNT = consumer_account_locator;

  Why this is correct

  To make a share available to a specific consumer account, the provider runs ALTER SHARE ... ADD ACCOUNT using the consumer's account locator or organization-qualified account name. This creates the share relationship. Without this step, the consumer cannot see or mount the share even if privileges are granted. This is the fundamental account-to-account sharing command.

• ✗

  CREATE SHARE share_name WITH ACCOUNT = consumer_account;

  Why it's wrong here

  CREATE SHARE does not accept a WITH ACCOUNT clause. You create a share first, then add objects and accounts separately. This option invents a clause that does not exist. The correct sequence is CREATE SHARE, then ALTER SHARE ... ADD ACCOUNT. Attempting this command would result in a syntax error.

• ✗

  GRANT USAGE ON SHARE share_name TO ACCOUNT consumer_account;

  Why it's wrong here

  GRANT USAGE ON SHARE is not the syntax for sharing with an account. Shares are not granted to accounts as privileges; instead, accounts are added to shares with ALTER SHARE ... ADD ACCOUNT. This option uses a plausible-sounding but incorrect command form. It would not establish the share relationship and would fail as invalid syntax.