Why should a cardinality setting of 1:M be set for objects such as Contact Point Phone, Email, or Party Identification?

• A. Allows a relationship to multiple objects
• B. Is the default field for all relationship definitions
• C. Requires the same cardinality as the Individual object
• D. Allows a relationship to multiple records

Answer: (D)

The main idea is that a 1:M relationship lets one record on the primary side be linked to many records on the related side. For objects like Contact Point Phone, Email, or Party Identification, this matches reality: a single person or party can have multiple phone numbers, multiple email addresses, and multiple IDs. Setting the relationship to one-to-many ensures you can create and associate multiple related records under one party, while each related record remains specific to a single contact detail. This is why it’s the best fit—the pattern explicitly supports multiple related records for one parent. The other options describe conditions that aren’t accurate: the cardinality is not a universal default, it isn’t about relating to multiple object types, and it doesn’t require matching cardinality with the Individual object.