Salesforce-MuleSoft-Platform-Architect Practice Test
152 Questions
Refer to the exhibits.
Which architectural constraint is compatible with the API-led connectivity architectural style?
A. Always use a tiered approach by creating exactly one API for each of the three layers (Experience, Process, and System)
B. Use a Process API to-orchestrate calls to multiple System APIs but not to other Process APIs:
C. Allow System APIs to return data that is not currently required by the identified Process or Experience APIs
D. Handle customizations for the end-user application at the Process layer rather than at the Experience layer
Explanation:
API-led connectivity prescribes clear separation of concerns:
1. System APIs unlock and encapsulate core system data.
2. Process APIs combine and shape that data for business processes.
3. Experience APIs tailor it for specific UIs or channels.
To maintain this modularity and prevent circular dependencies, a Process API should orchestrate only System APIs—and never call other Process APIs. This ensures each layer remains independently versionable, testable, and reusable. Allowing Process-to-Process calls would blur layer boundaries and introduce coupling that undermines API governance and clarity.
| Salesforce-MuleSoft-Platform-Architect Practice-Test - Home | Previous |
| Page 20 out of 152 Pages |