MARKETING-CLOUD-CONSULTANT practice question 1 of 25

Northern Tril Outfitters wants to connect relational data into their Journey without overloading the entry data. How should they connect the data?

Full set: 154 questions
Answer options
A: Entry Source Data Extension
B: Data Relationships
C: Data Designer Correct answer
D: Contact Configuration
Correct Answer:
C. Data Designer
Explanation

Data Designer, a tool within Contact Builder, is the correct way to establish the data model for contacts. It allows you to link multiple data extensions (attribute groups) to the contact record via relationships. Once these relationships are defined in Data Designer, Journey Builder can access this related data for personalization and in decision splits using the 'Contact Data' path, without needing all the data present in the entry source data extension.

Why Incorrect

A. The question explicitly states the goal is to avoid overloading the Entry Source Data Extension, making this option the opposite of the desired solution.
B. Data Relationships is a legacy feature in Email Studio primarily for segmentation and filtering, not the modern method for enriching contact data for Journey Builder.
D. Contact Configuration in Journey Builder settings defines how a journey identifies a contact (e.g., using Contact Key from the entry source), but it is not the tool for linking relational data tables.

References

1. Salesforce Help, Data Designer, Document ID: sf.mccvdatadesigner.html. "Use Data Designer to define information about your contacts and how data extensions relate to those contacts... After you link data extensions, that information becomes available for use in other Marketing Cloud apps, such as Journey Builder".

2. Salesforce Help, Create a Journey Builder Entry Source, Document ID: sf.mcjbcreateanentrysource.html. This document implicitly supports the use of Contact Data (defined in Data Designer) as separate from Journey Data (from the entry source).

Scroll to Top