Terminology clarity: Is an “enterprise key” simply a primary key that is unique within a single relation, or is it intended to be globally unique across the enterprise?

Introduction / Context:
Different key terms capture different scopes of uniqueness. A primary key uniquely identifies rows within a single table. An enterprise key, by contrast, is a key whose values are unique across the entire organization—across all relevant tables and systems—so that the same identifier consistently refers to the same real-world entity everywhere.

Given Data / Assumptions:

• A primary key enforces per-table uniqueness and not-null constraints.
• An enterprise key indicates cross-system, cross-table uniqueness.
• Organizations often use enterprise identifiers (e.g., global customer_id) that are propagated across databases.

Concept / Approach:
The statement claims an enterprise key is “a primary key whose value is unique for a given relation.” That description matches an ordinary primary key, not an enterprise key. Therefore, the statement is incorrect. Enterprise keys enable master data consistency and referential clarity across multiple data stores, not just within a single relation.

Step-by-Step Solution:
Distinguish per-table uniqueness (primary key) from cross-enterprise uniqueness (enterprise key).Identify use cases: a customer_number shared by billing, CRM, and support systems.Recognize governance needs: enterprise key management ensures no collisions across domains.Implement synchronization and validation mechanisms to maintain global uniqueness.Map enterprise keys into local schemas (as primary keys or alternate keys) consistently.

Verification / Alternative check:
Examine data integration architectures (MDM systems). Enterprise keys serve as a common join key across applications, demonstrating their broader scope beyond one relation.

Why Other Options Are Wrong:
Correct: would wrongly equate enterprise keys with ordinary per-table primary keys.True only in OLTP: scope is organizational, not workload-specific.True only with GUIDs: GUIDs are one implementation, not the definition.

Common Pitfalls:
Confusing enterprise keys with surrogate keys; thinking any unique value qualifies as “enterprise” without organizational governance.

Final Answer:
Incorrect