Designing APIs using System, Process, and Experience Layers12% of the exam
DataGraph Composition and Runtime Behavior
Assess DataGraph as a managed composition interface over reachable REST implementations. Distinguish links, enrichment and schema consolidation, then plan mutations, usage allocation and persisted-query caching without assuming it replaces provider behavior.
Select DataGraph only for suitable roles in an application network, according to its high-level features.
~7 min read · 7 practice questions
What the exam expects
- Select DataGraph for suitable application-network composition requirements.
- Distinguish its managed endpoint from the underlying API implementations.
- Choose links, merges and mutations according to the required meaning.
- Plan licensed downstream usage and persisted-query delivery appropriately.
A unified schema combines exposed API types; a link connects related entities; an extension merge enriches the same records; a mutation invokes a write operation; a persisted query associates a query document with an identifier.
Key facts
Source descriptions
- Detail
- Documented sources are REST APIs described with RAML or OAS.
Provider execution
- Detail
- DataGraph calls underlying API implementations.
Hosting distinction
- Detail
- The graph is fully managed; provider hosting does not deploy the graph engine.
Writes
- Detail
- Mutations use input types mapped from REST write operations.
Baseline evidence
- Detail
- March 21, 2022 announces mutations and persisted-query/CDN support.
Related objects
- Detail
- Link them rather than treat the foreign key as identical entity identity.
Same records
- Detail
- Extension merge enriches compatible representations of the same records.
Input consolidation
- Detail
- All fields and field counts must match; collaboration is not enabled.
Local field visibility
- Detail
- A shared field is visible when either local source field is visible.
Licensed calls
- Detail
- Count downstream REST calls rather than client queries alone.
Allocation recovery
- Detail
- Correct the environment allocation and reapply changes.
Query delivery
- Detail
- Persist document/ID, then use GET through a configured CDN where eligible.
- Source
- APQ (opens in a new tab)
Sources for this section (7)
- Overviewdocs.mulesoft.com (opens in a new tab)
- Networkingdocs.mulesoft.com (opens in a new tab)
- Schemasdocs.mulesoft.com (opens in a new tab)
- Release notesdocs.mulesoft.com (opens in a new tab)
- Linkingdocs.mulesoft.com (opens in a new tab)
- Mergingdocs.mulesoft.com (opens in a new tab)
- APQdocs.mulesoft.com (opens in a new tab)
- Why can adding a type earlier matter when inspecting a merged type's resulting name?
- When two input definitions otherwise qualify for a merge, what collaboration setup should the designer add?
- Which visibility results when a common field is hidden in one locally merged object type and visible in the other?
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 (7 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