試験MC-Con-201 トピック1 問題67 スレッド

The source bank recommends starting with a single lean Data Graph and expanding it as additional campaign requirements emerge . This approach avoids building unnecessary relationships and processing large datasets before an actual personalization use case requires them.
Current Salesforce guidance supports the underlying principle. Marketing Cloud Next personalization begins with a Unified Individual-based Data Graph containing required identity/contact fields plus the additional objects and fields required for personalization . Salesforce also notes that Data Graph cost and processing depend on data-model structure, participating records, refresh frequency, and fields updated. It recommends filters so that only records required for the use case are included.
Option A risks creating an oversized graph based on speculative future requirements. Option B introduces two graphs immediately even though the first campaign doesn't establish a requirement for separate demographic and transactional graphs. In the standard Marketing Cloud Next configuration without additional Personalization capabilities, Salesforce also notes that only one default Data Graph is used at a time.
Therefore, begin with the smallest useful graph, validate the campaign, and expand the graph as real personalization requirements develop.
Study Guide Reference: Data Modeling, Identity Resolution and Segmentation # Data Graph Design # Use-Case-Driven Personalization Architecture.