Creating Application Networks7% of the exam
API-led connectivity layers and benefits
What System, Process and Experience APIs each own, how to place new orchestration or formatting logic in the right layer, and the reuse, agility, self-service and governance benefits that API-led connectivity delivers.
Identify features of an API-led approach.
~7 min read · 6 practice questions ·
What the exam expects
- Match System, Process and Experience APIs to their responsibilities and reject options that put a job in the wrong layer.
- Decide where new logic belongs: combining data from several sources goes in a Process API; shaping output for one consumer goes in an Experience API.
- Diagnose a design that buries back-end access or business rules in an Experience API and so blocks reuse.
- List the benefits API-led connectivity delivers (reuse, agility, self-service, security and governance) and reject claimed benefits that contradict them.
Key terms:
- API-led connectivity: a methodical way to connect data to applications through reusable and purposeful APIs.
- System API: unlocks data from a core system of record and shields it from consumers.
- Process API: orchestrates System APIs and other Process APIs into reusable business logic.
- Experience API: adapts Process API output for a specific interface such as a mobile app or portal.
Key facts
Three layers
- Detail
- System, Process, Experience
System API connects to
- Detail
- Core systems such as databases, ERPs, CRMs; shields systems of record
Process API calls
- Detail
- Multiple System APIs and other Process APIs
Process API examples
- Detail
- Customer 360 view, order fulfillment, shipment status
Experience API input
- Detail
- Adapts Process API output for a specific consumer
New channel on existing layers
- Detail
- Rewiring instead of recreating
Self-service benefit
- Detail
- Developers discover and consume APIs, less dependency on central IT
Security benefit
- Detail
- APIs are secured and monitored; IT keeps visibility and control
Reported averages
- Detail
- 64% productivity, 78% faster launches, 74% lower maintenance costs
- Why can many teams use a System API without learning the system behind it?
- Why do Process APIs not need to worry about where data originates or how it is delivered?
- Which two sources does Trailhead's Mule United Airport Process API merge with real-time inventory?
- When teams adopt API-led connectivity, what does MuleSoft's blog say a new initiative does with existing building blocks instead of building solution components?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (6 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams