In API-led design, an Experience API is enhanced to improve how data is delivered to end-user applications. One primary reason to enhance an Experience API is when new data standards, such as a Canonical Data Model, are adopted. Here's why:
Canonical Data Model (CDM):
Adopting a CDM standardizes data representations across the organization, making APIs more consistent and easier to consume across various services and applications.
Updating the Experience API ensures that it delivers data in this standardized format, improving interoperability and reusability.
of Correct Answer (D):
A CDM impacts the structure and types of data the API provides, and this update would be directly relevant to an Experience API, as it is the primary point of interaction for applications.
of Incorrect Options:
Option A involves adapting to consumer-specific standards, which is against API-led design principles.
Option B involves changes in System APIs, which don't directly mandate changes to the Experience API unless data formatting adjustments are required.
Option C (IP Allowlist) relates to security rather than API design and would not motivate a functional enhancement of the API.
Reference
For more details on the use of Canonical Data Models in API-led architecture, refer to MuleSoft's guidelines on data standardization and Experience API best practices.