Designing and sharing APIs10% of the exam
Bounded Context Relationships and Power
Choose context-mapping strategies from delivery dependence, influence and model ownership. Use a realistic context map to distinguish coordination, shared models, upstream conformity and protective translation.
Given a specific power relationship between two Bounded Contexts, choose the most appropriate strategy for mapping between the API data models of these Bounded Contexts.
~6 min read · 5 practice questions
What the exam expects
- Distinguish mutual delivery dependence from an upstream/downstream relationship.
- Select a collaboration strategy from the teams' influence and commitments.
- Separate a deliberately shared model subset from translation between models.
- Decide whether a downstream context adopts the upstream model or protects its own.
- Read the existing context relationships before proposing an integration design.
A bounded context defines where a model applies; upstream can affect downstream success while succeeding independently; translation maps between models; a context map records their relationships; a ubiquitous language connects the team's model, communication and code.
Key facts
Partnership
- Detail
- Coordinate planning and integration for mutually dependent deliveries.
Shared Kernel
- Detail
- Keep the jointly shared model/code subset small and explicit.
Kernel changes
- Detail
- Consult the other team and coordinate integration.
Customer/Supplier
- Detail
- Factor downstream priorities into upstream planning.
Acceptance tests
- Detail
- Joint tests validate the downstream interface expectation upstream.
Conformist
- Detail
- Downstream accepts the upstream model to simplify integration.
Anticorruption Layer
- Detail
- Translate upstream functionality into the downstream's own model.
Current map
- Detail
- Record existing contexts and relationships before transformations.
Sources for this section (1)
- Why should a context map start with the relationships that teams actually work under?
- When a neighboring subsystem is not object-oriented, what still belongs in the map?
- Which shared vocabulary should include the bounded contexts' names?
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 (5 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