問題文
A retailer wants to extend the standard customer model to capture a few retailer-specific attributes not covered by the standard fields. What is the sound approach at the data-model level?
選択肢
- Extend the model with custom fields or objects on the product that owns that data, keeping the standard objects as the backbone and adding only what the requirement needs.
- Store the extra attributes only in the marketing platform regardless of which product owns the data, so the send tool ends up holding values that stay invisible to the owning product that is supposed to be looking after them.
- Avoid storing the attributes at all, since only standard fields are ever allowed, so the requirement is met by squeezing the value into an unrelated description field instead that nobody else on the team can interpret.
- Replace all standard objects with entirely custom ones so that the product's built-in behavior no longer applies, discarding the standard model completely just to add a handful of retailer-specific attributes to it.