In the data model, how do Addresses relate to Recipients?

In the data model, how do Addresses relate to Recipients?

• A. One-to-one
• B. Many-to-one from Addresses to Recipients
• C. Many-to-many
• D. No relation

Answer: (B)

In this data model, a recipient can have multiple addresses, while each address is tied to a single recipient. That makes the relationship from Addresses to Recipients many-to-one. Practically, the Addresses table stores a foreign key pointing to the Recipients table, so several address records can reference the same recipient. This lets a person have multiple addresses (home, work, billing) without giving an address to more than one recipient. The other options don’t fit because a one-to-one pairing would overly restrict users to a single address, no relation would ignore the actual link between an address and its owner, and a many-to-many setup would allow an address to belong to multiple recipients, which isn’t typically desired unless you explicitly model shared addresses.

In this data model, a recipient can have multiple addresses, while each address is tied to a single recipient. That makes the relationship from Addresses to Recipients many-to-one. Practically, the Addresses table stores a foreign key pointing to the Recipients table, so several address records can reference the same recipient. This lets a person have multiple addresses (home, work, billing) without giving an address to more than one recipient. The other options don’t fit because a one-to-one pairing would overly restrict users to a single address, no relation would ignore the actual link between an address and its owner, and a many-to-many setup would allow an address to belong to multiple recipients, which isn’t typically desired unless you explicitly model shared addresses.