Deploying and Managing APIs and Integrations7% of the exam
API Autodiscovery and API proxies
Pair a Mule app with an API Manager instance through API Autodiscovery (apiId, an HTTP Listener flowRef, environment credentials), predict Gatekeeper's 503 after a redeploy, and choose a basic endpoint or a generated API proxy and its type.
Manage APIs using separate proxies and auto-discovery.
~8 min read · 7 practice questions ·
What the exam expects
- Write the
api-gateway:autodiscoveryelement:apiIdis the API ID API Manager generated for the instance,flowRefnames a flow whose source is an HTTP Listener. - Configure the runtime's Anypoint Platform credentials and explain why environment credentials only pair with APIs in that environment.
- Explain the
503clients receive right after a redeploy of a paired app. - Choose a basic endpoint (the Mule app is its own proxy) or a deployed proxy application (non-Mule or closed-code backends).
- Name what a RAML/OAS proxy adds over an HTTP proxy.
Key terms:
- API instance: a managed API in API Manager, identified by its generated API ID.
- Autodiscovery: the element that pairs ("tracks") a deployed Mule app with one API instance so it downloads policies and sends analytics.
- Basic endpoint: the Connect to existing application option; your own Mule app acts as the proxy.
- API proxy: a Mule app that API Manager generates and deploys in front of a backend.
- Gatekeeper: the runtime mechanism that blocks a tracked resource until its policies are applied.
Everything here is Mule Gateway, the runtime API Manager uses for APIs on Mule; Omni Gateway is a separate gateway instance type and not what these questions test (Add API Instances).
Sources for this section (1)
Key facts
apiId value- Detail
- API ID generated by API Manager for the instance
flowRef flow- Detail
- Must use an HTTP Listener
One API, one autodiscovery
- Detail
- Only one at a time
Recommended credentials
- Detail
- Environment client ID and secret
CloudHub credential properties
- Detail
anypoint.platform.client_id,anypoint.platform.client_secret
Gatekeeper status code
- Detail
503 - Service Unavailable
Gatekeeper default
- Detail
flexiblefor Mule 4.1.0 and later
CloudHub proxy default size
- Detail
- 0.1 vCores, 500 MB
Proxy Upstream URL
- Detail
- Required for Deploy a proxy application
Sources for this section (6)
- Configuring Autodiscovery in Mule 4docs.mulesoft.com (opens in a new tab)
- API Autodiscoverydocs.mulesoft.com (opens in a new tab)
- Organization Credentials in Mule 4docs.mulesoft.com (opens in a new tab)
- Enhancing Security with Gatekeeperdocs.mulesoft.com (opens in a new tab)
- Deploy Your API Proxydocs.mulesoft.com (opens in a new tab)
- Adding a Mule Gateway API Instancedocs.mulesoft.com (opens in a new tab)
- Why does a malformed policy leave a paired app answering
503? - When must you also set
anypoint.platform.base_uriandanypoint.platform.analytics_base_uri? - What does Gatekeeper do with a resource that is not linked to an API instance?
- Why can one API be paired with only one autodiscovery instance at a time?
- What are the default vCores and memory of a CloudHub proxy?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Developer 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
- Unlimited timed practice exams