Refer to the exhibit.
An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.
The data is available partially in a database and partially in a 3rd-party CRM system.
What APIs should be created to best fit these design requirements?
To meet the design requirements of enabling access to customer data from both a mobile app and a web application, it's essential to have separate Experience APIs for the mobile and web apps. This allows each app to have tailored experiences and access specific fields as needed. However, a common Process API is practical for handling the integration and business logic, ensuring consistency and reusability. This Process API can then invoke separate System APIs that interact with the database and the CRM system to retrieve the necessary data. This setup ensures modularity and flexibility, enabling future scalability without significant changes to the API structure.
C. Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system
C. Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system
Answer: C
C is correct