In Snowflake, how does the implementation of primary keys for tables contribute to data integrity?

Question

Options

• AEnforces uniqueness in table rows
• BOnly works on specific data types
• CRequires data redundancy
• DLimits data access for users

• A
  87% (20)
• B
  4% (1)
• C
  4% (1)
• D
  4% (1)

Explanation

Primary keys in Snowflake are defined to enforce uniqueness across rows in a table - each row must have a distinct key value, which is the foundation of relational data integrity. However, it's important to note that Snowflake's primary keys are not enforced at the database engine level (they are metadata constraints only), but conceptually and for exam purposes, their purpose is uniqueness enforcement, making A correct.

Why the distractors are wrong:

• B is false - primary keys work on any data type that supports equality comparison, not a restricted subset.
• C is the opposite of truth - primary keys eliminate redundancy by ensuring no duplicate rows.
• D confuses primary keys with access control mechanisms like roles or row-level security, which are separate features.

Memory tip: Think "Primary = One and Only One" - a primary key's entire job is to uniquely identify each row. If you see "uniqueness" in an answer about primary keys and data integrity, that's almost always correct.

No community discussion yet for this question.