Designing APIs using System, Process, and Experience Layers12% of the exam
Layer Responsibilities and Team Ownership
Assign business and technical accountability according to the capability, shared semantics, consumer relationship and expected change impact. Preserve stewardship as teams, versions and organizational needs evolve.
Assign APIs to layers according to ownership, functional focus, and rate of change.
~7 min read · 8 practice questions
What the exam expects
- Distinguish business ownership from technical stewardship.
- Select ownership candidates from data, capability and consumer responsibilities.
- Resolve cross-platform and cross-department accountability without changing API responsibilities.
- Adapt ownership to organizational norms and continued change.
A business owner directs the API's business scope and evolution; a technical owner implements and operates it; an SLA states service commitments; an OLA supports operational objectives; stewardship keeps assets healthy beyond immediate feature delivery.
Key facts
Business accountability
- Detail
- Scope, SLA, release direction and evolution.
Technical accountability
- Detail
- Implementation, OLA and underlying dependencies.
Definitions authority
- Detail
- Governs entities, attributes and relationships.
Data-quality authority
- Detail
- Maintains quality of actual records.
Composite business ownership
- Detail
- Value-stream owner or continuing cross-organizational group.
Composite technical ownership
- Detail
- Consider expected platform impact or integration services.
Experience business owner
- Detail
- Align with the consumer/partner relationship.
Shared technical owner
- Detail
- Possible when the Process service team also owns the consumer relationship.
Change without continuity
- Detail
- Assign current technical ownership when the API changes.
Stewardship support
- Detail
- Guidelines, financing and incentives address long-term asset health.
- Why can stewardship need an explicit funding arrangement even for a useful API?
- When selecting a promising leader for a complex composite service, how can the organization support that candidate?
- Why is growing the API count an insufficient investment justification outside experimentation?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 47 lessons of the MuleSoft Platform Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both