# Layer Responsibilities and Team Ownership

*MuleSoft Platform Architect Study Guide · Designing APIs using System, Process, and Experience Layers · Last updated November 13, 2026 · https://www.certifyforce.com/study-guide/mulesoft-platform-architect/designing-apis-using-system-process-and-experience-layers/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.

- Certification: Salesforce MuleSoft Platform Architect
- Exam section: Designing APIs using System, Process, and Experience Layers
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-platform-architect

**Official exam objective:**

> Assign APIs to layers according to ownership, functional focus, and rate of change.

## 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

| Fact | Detail | Source |
|---|---|---|
| Business accountability | Scope, SLA, release direction and evolution. | [Framework](https://blogs.mulesoft.com/api-integration/strategy/api-ownership-enterprise/) |
| Technical accountability | Implementation, OLA and underlying dependencies. | [Framework](https://blogs.mulesoft.com/api-integration/strategy/api-ownership-enterprise/) |
| Definitions authority | Governs entities, attributes and relationships. | [System](https://blogs.mulesoft.com/api-integration/strategy/system-api-ownership/) |
| Data-quality authority | Maintains quality of actual records. | [System](https://blogs.mulesoft.com/api-integration/strategy/system-api-ownership/) |
| Composite business ownership | Value-stream owner or continuing cross-organizational group. | [Process](https://blogs.mulesoft.com/api-integration/strategy/process-api-ownership/) |
| Composite technical ownership | Consider expected platform impact or integration services. | [Process](https://blogs.mulesoft.com/api-integration/strategy/process-api-ownership/) |
| Experience business owner | Align with the consumer/partner relationship. | [Experience](https://blogs.mulesoft.com/api-integration/strategy/experience-api-ownership/) |
| Shared technical owner | Possible when the Process service team also owns the consumer relationship. | [Experience](https://blogs.mulesoft.com/api-integration/strategy/experience-api-ownership/) |
| Change without continuity | Assign current technical ownership when the API changes. | [Framework](https://blogs.mulesoft.com/api-integration/strategy/api-ownership-enterprise/) |
| Stewardship support | Guidelines, financing and incentives address long-term asset health. | [Framework](https://blogs.mulesoft.com/api-integration/strategy/api-ownership-enterprise/) |

## Check yourself

- 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?

## Sources

- [API Ownership for the Modern Enterprise](https://blogs.mulesoft.com/api-integration/strategy/api-ownership-enterprise/)
- [System API Ownership](https://blogs.mulesoft.com/api-integration/strategy/system-api-ownership/)
- [Process API Ownership](https://blogs.mulesoft.com/api-integration/strategy/process-api-ownership/)
- [Experience API Ownership](https://blogs.mulesoft.com/api-integration/strategy/experience-api-ownership/)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 8 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Platform Architect pack (USD $19): https://www.certifyforce.com/practice-exams