Question

question 32 (2 points) saved listen a surrogate key should be considered when 1) a relationship is m:n 2) a composite key is required 3) the key contains a lengthy text field 4) the key contains a number

Explanation:

A surrogate key is an artificial key (like a unique ID) used when the natural key (e.g., a lengthy text field) is not suitable (e.g., too long, complex, or unstable). Option 1: M:N relationships use junction tables with composite keys (not surrogate key reason). Option 2: Composite keys are multiple natural keys, not a surrogate key trigger. Option 4: A key with a number could be a natural key (e.g., employee ID number) or not a reason for surrogate. So the correct option is 3 as lengthy text fields are problematic for keys, so surrogate keys are considered.

Answer:

1. the key contains a lengthy text field