Understand How Cardinality Impacts Data Modeling. MARKETING-CLOUD-ENGAGEMENT-CONSULTANT Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A company has a data model where each customer can have multiple email addresses (e.g., personal and work). They want to send communications to the preferred email address. What is the best way to model this?

   • AStore all email addresses in a single field separated by commas
   • BAdd multiple email fields to the customer data extension (e.g., personal_email, work_email)
   • CCreate a separate email address data extension with a relationship to the customer and a field for 'is_preferred'
   • DCreate a new customer data extension for each email address
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   In a data model with a one-to-one relationship between 'Subscriber' and 'Profile', how does this cardinality impact personalization?

   • AEach subscriber can have only one profile, so personalization can use profile attributes directly without worrying about multiple records.
   • BPersonalization must use only the subscriber key, not profile attributes.
   • CPersonalization is not possible because one-to-one relationships are not supported in Marketing Cloud.
   • DPersonalization is limited to the first profile record found, which may be inconsistent.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Why is understanding cardinality important when designing a data model in Contact Builder?

   • AIt determines the color coding of data extensions in the Contact Builder canvas.
   • BIt determines the type of relationship between data extensions, which affects how data can be joined and used.
   • CIt controls the permission settings for data extensions.
   • DIt specifies the exact storage size of each data extension.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is a potential impact on data retrieval efficiency when a data model uses a many-to-many relationship without a junction data extension?

   • AData retrieval becomes faster because there are fewer data extensions to query.
   • BQueries may become complex and slower because the relationship is not clearly defined.
   • CData retrieval is unaffected because cardinality does not impact performance.
   • DData retrieval becomes impossible because Marketing Cloud does not support many-to-many relationships.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A company has a customer data extension with 500,000 records. They want to store each customer's loyalty points balance, which changes frequently. They also want to store a history of loyalty point transactions. What is the most efficient data modeling approach?

   • ACreate a separate data extension for the balance and another for transactions, without linking to the customer
   • BStore the current balance in the customer data extension and create a separate transaction data extension
   • CStore the balance and all transactions in the customer data extension
   • DStore only the transaction history and calculate the balance on the fly
   Reveal Solution Discussion Select an answer first