Expose production-ready Anypoint Platform-managed APIs from Mule applications13% of the exam
Versioning API specifications, assets and implementations
Separate consumer compatibility from Exchange publication versions and managed API identity. Plan specification changes, recover publishing conflicts and complete policy implementation updates.
Implement versioning of specific API-related artifacts.
~7 min read · 7 practice questions ·
What the exam expects
- Classify a proposed API change by its effect on existing consumers.
- Keep the consumer contract version aligned with the Exchange publication family.
- Update a managed instance deliberately and plan separate instances for incompatible contracts.
- Distinguish an implementation deployment from specification and policy updates.
- Diagnose a reserved publication version without overwriting release history.
API version identifies the consumer contract; asset version identifies an Exchange publication; API instance is the managed API whose asset version is selected in API Manager; policy definition exposes policy configuration; policy implementation supplies its executable behavior. These are related release concerns with different update procedures (API versions, Instance versions, Policy updates).
Key facts
Publication identity
- Detail
- Exchange Version and API version are separate fields.
Compatible release
- Detail
- Minor and patch publications preserve the API version.
Breaking release
- Detail
- Required arguments and removed operations require a major change.
Consumer route
- Detail
- Use a simple major API identifier rather than dotted asset versions.
Managed selection
- Detail
- Update the instance's asset selection after publication.
Cross-major migration
- Detail
- A different major asset family requires a new API instance.
Deleted coordinates
- Detail
- A recently deleted GAV can conflict; publish the correction at a higher free version.
Policy patch
- Detail
- Definition selection needs a manual implementation-update check.
- Why should an editor select a minor asset version before changing its documentation pages?
- When uploading a specification ZIP, where must the main specification file reside?
- How does the asset portal separate minor-version and patch-version selection?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Developer II pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 29 lessons of the MuleSoft Developer II 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