Expose production-ready Anypoint Platform-managed APIs from Mule applications13% of the exam
API policies and gateway enforcement
Choose, apply and order Mule Gateway policies while separating runtime enforcement from platform management. Account for resource matching, automation, distributed quotas and cached policy artifacts.
Configure custom or out-of-the-box (OOTB) API policies.
~7 min read · 9 practice questions ·
What the exam expects
- Match a security, traffic or transformation requirement to a policy capability.
- Apply included or published custom policies without changing implementation code.
- Distinguish environment automation, API-level ordering and resource filtering.
- Explain online enforcement, offline limitations and cached artifact cleanup.
- Relate an SLA quota's distribution to the actual runtime topology.
Policy means an enforced API rule; automated policy is configured for APIs in an environment; resource-level policy matches selected requests; SLA contract links a registered client application to allowed consumption; policy artifact contains executable logic and configuration metadata (Policy types, Resource scope, SLA policy, Policy architecture).
Key facts
Runtime enforcement
- Detail
- Injected policies execute without a per-request API Manager call.
Online custom application
- Detail
- Publish the policy to Exchange, then apply through API Manager.
Publication classifier
- Detail
- Mule Maven Plugin identifies the policy with
mule-policy.
Fixed precedence
- Detail
- CORS precedes automated policies and API-level policies.
Automation conflict
- Detail
- The automated configuration prevails over the same API-level type.
Resource matching
- Detail
- Use Java regex against real path values and selected methods.
Duplicate allowlists
- Detail
- A request must satisfy both applied allowlists.
Distributed quota
- Detail
- Mule runtime quota sharing requires HA cluster mode.
Offline limitations
- Detail
- No startup gatekeeper protection or client credentials validation.
Artifact cleanup
- Detail
- Enable the startup cleanup property rather than assuming unapply deletes files.
Sources for this section (8)
- Architecturedocs.mulesoft.com (opens in a new tab)
- Custom policiesdocs.mulesoft.com (opens in a new tab)
- Maven publishingdocs.mulesoft.com (opens in a new tab)
- Orderingdocs.mulesoft.com (opens in a new tab)
- Automationdocs.mulesoft.com (opens in a new tab)
- Resource policiesdocs.mulesoft.com (opens in a new tab)
- SLA policydocs.mulesoft.com (opens in a new tab)
- Policy typesdocs.mulesoft.com (opens in a new tab)
- Why might otherwise similar policies differ in download size?
- When is an automated external-identity-provider policy enforced on a particular API?
- What enables Preview Resource Matching for documented endpoints?
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 (9 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