Governing web APIs on Anypoint Platform17% of the exam
Gateways Proxies and Service Mesh
Compare embedded gateways, proxies, historical Service Mesh and Spring 2024 Flex modes while preserving runtime and policy compatibility boundaries.
Select an approach to API policy enforcement based on specific preferences and constraints, including, but not limited to, API proxies/API gateways and Anypoint Service Mesh.
~6 min read · 5 practice questions
What the exam expects
- Select an enforcement point for Mule and non-Mule implementations.
- Compare direct embedded enforcement, a separate proxy and historical service-mesh interception.
- Explain Spring '24 Flex Gateway configuration modes and custom-policy portability.
- Diagnose the prerequisites of an existing Anypoint Service Mesh installation.
A gateway mediates requests before a backend; an API proxy forwards requests through a separately deployed enforcement application; Mule Gateway is embedded in Mule runtime; Flex Gateway is the Envoy-based gateway described by the Spring '24 references; an Envoy sidecar intercepts mesh service communication; the Mule adapter performs Anypoint policy checks for the historical mesh (Mule Gateway, Spring '24 gateways, Historical mesh).
Key facts
Embedded gateway
- Detail
- Mule runtime includes Mule Gateway.
Non-Mule backend
- Detail
- A Mule proxy can supply the Mule enforcement hop.
Custom artifact portability
- Detail
- Mule Gateway policies do not run unchanged on Flex.
Flex Connected Mode
- Detail
- API Manager supplies policy configuration.
Flex Local Mode
- Detail
- Local declarative files; connections for registration and usage metrics.
Mesh interception
- Detail
- Envoy, Istio mixer and Mule adapter participate in checks.
Existing pods
- Detail
- Restart after injection labeling when the Envoy sidecar is missing.
Policy catalog
- Detail
- Mesh supports a finite subset; XML Threat Protection uses Mule Gateway.
Sources for this section (7)
- Mule Gatewaydocs.mulesoft.com (opens in a new tab)
- Spring '24 gatewaysraw.githubusercontent.com (opens in a new tab)
- Historical Flex 1.5raw.githubusercontent.com (opens in a new tab)
- Historical meshraw.githubusercontent.com (opens in a new tab)
- Mesh troubleshootingraw.githubusercontent.com (opens in a new tab)
- Mesh policiesraw.githubusercontent.com (opens in a new tab)
- XML protectiondocs.mulesoft.com (opens in a new tab)
- Why is a numeric port value insufficient in the historical mesh service definition?
- When policy traffic continues after binding deletion, which residual resource should be checked?
- When adapter logs confirm an expired-license failure, which recovery steps are documented?
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