What the published objective requires
- Distinguish System, Process and Experience API responsibilities
- Select reusable assets and C4E practices
- Configure the correct HTTP consumption pattern for a REST resource
Domain 1 of 12 · 7% of the official blueprint
Creating Application Networks practice lesson
Classify API responsibilities and select a reusable API-led boundary for the Northstar order flow.
The misconception to eliminate
Choosing a layer from the protocol or product name. Layering follows ownership, functional focus and rate of change.
Practice allocation: 4 of 60 questions in our whole-question mock blueprint.
Decision rules
Retrieve these without looking before attempting the question.
Rule 1
A System API unlocks a system of record; it does not encode every channel journey.
Rule 2
A Process API composes domain logic across systems; an Experience API adapts that capability to a consumer.
Rule 3
Reuse requires a discoverable contract, ownership and documentation—not merely a shared endpoint.
Rule 4
A C4E enables federated teams with assets and guardrails; it should not implement every integration.
Worked Northstar scenario
Scenario
Mobile and partner channels both need order status, but the partner needs EDI codes and the mobile app needs simplified labels.
Reasoning
Expose ERP order data once through an Orders System API. Put common status composition in an Order Status Process API. Adapt only the representation in separate Experience APIs; do not duplicate ERP access.
Free practice question
Two channels need the same ERP customer record but different response shapes. Which design minimizes system coupling?
- One System API plus separate consumer adaptations
- A direct ERP connection per channel
- One shared database view exposed to every client
- Duplicate System APIs for each response shape
Reveal answer and reasoning
Answer: A. Unlock the ERP once, then adapt at the process or experience boundary. Direct and duplicated access multiplies coupling.
The complete program contains five guided drills for this domain, an 80% mastery gate, saved progress and a separate 60-question timed mock.
Get Domain MasteryHands-on proof preview
Draw the three boundaries
Map the Northstar status journey before opening Studio.
- List the ERP and CRM capabilities that remain stable across channels.
- Place cross-system status composition in one Process API.
- Write one consumer-specific change for mobile and one for partners.
- Verify that neither Experience API connects directly to the ERP database.
Evidence to keep: A three-layer map with an owner, consumer and reason-to-change written beside every API.
Primary sources
Questions about this domain
How much of the MuleSoft Developer exam is Creating Application Networks?
Salesforce publishes a weight of 7% for this domain. In a 60-question practice allocation, that is represented here by 4 questions.
Is this Creating Application Networks question from the real exam?
No. It is original independent practice material written only from public exam objectives and product documentation.