Hello @Michael_Soprano ,
Our goal is to exclude customers who have already applied for a credit card. To achieve this, we must devise a method to identify all customers who have submitted an application with a specific offer ID. The most effective strategy for managing offers as a lookup schema and linking it to the application submission event is to establish a relationship between the two datasets. This approach is detailed in option 4.
Its important here to know that normalization can be achieved when you are link a profile schema with a lookup schema to avoid data redundancy. But in this case de-normalization makes more sense because a same person can have multiple credit card orders which can be easily maintained in experience event schema.
Thanks,
Arpan