The correct answer is obviously A. I mean, who needs demographics when you can just have a many-to-many relationship and call it a day, right? *wink wink*
Many-to-one, really? Unless the customer has a contact model where each person can have multiple demographic profiles, I don't see how that could possibly work.
Hold up, a one-to-one relationship? What is this, amateur hour? That would completely defeat the purpose of linking demographic data to the contact model.
A: Actually, a one-to-one relationship would not work for linking demographic information to the contact model. It should be a one-to-many relationship.
I'm not sure why anyone would even consider a many-to-many relationship for this use case. That just sounds like overkill and would make the data model unnecessarily complex.
A one-to-many relationship seems like the obvious choice here. Demographic information is usually unique to each contact, so this option makes the most sense.
Willetta
1 months agoMelinda
1 days agoGilbert
1 months agoChandra
1 months agoCarey
1 days agoChristiane
2 days agoBethanie
4 days agoChristiane
6 days agoSocorro
7 days agoRolland
2 months agoLavera
7 days agoTracie
14 days agoEmily
1 months agoJerry
2 months agoOrville
6 days agoSuzi
14 days agoIraida
15 days agoSheron
1 months agoShawna
2 months agoAlysa
3 months agoAlica
3 months ago