Which describes the CDM transformation flow in the described architecture?

Which describes the CDM transformation flow in the described architecture?

• A. One transformation from Experience API to the CDM and one transformation from the CDM to an external system via the System API
• B. Two transformations directly from the Experience API to the external system
• C. Three transformations including extra mapping to a database
• D. No transformations are required

Answer: (A)

In an API-led architecture using a Canonical Data Model (CDM), data is first transformed into the CDM at the edge (Experience API) and then transformed from the CDM into the target system’s format by the System API. This pattern decouples the client-facing data shape from the internal system-specific models, making it easier to reuse the same CDM for multiple systems and to adapt to changes in external APIs without touching the Experience API logic. So the described flow—one transformation into the CDM, followed by a transformation from the CDM to the external system via the System API—best matches this approach. Directly mapping from the Experience API to the external system bypasses the CDM, which reduces reusability and increases coupling. Adding an extra database mapping isn’t part of the canonical CDM flow unless there’s a persistence requirement, and having no transformations would defeat the purpose of normalizing data with the CDM.

In an API-led architecture using a Canonical Data Model (CDM), data is first transformed into the CDM at the edge (Experience API) and then transformed from the CDM into the target system’s format by the System API. This pattern decouples the client-facing data shape from the internal system-specific models, making it easier to reuse the same CDM for multiple systems and to adapt to changes in external APIs without touching the Experience API logic. So the described flow—one transformation into the CDM, followed by a transformation from the CDM to the external system via the System API—best matches this approach. Directly mapping from the Experience API to the external system bypasses the CDM, which reduces reusability and increases coupling. Adding an extra database mapping isn’t part of the canonical CDM flow unless there’s a persistence requirement, and having no transformations would defeat the purpose of normalizing data with the CDM.