Creating Application Networks7% of the exam
Application networks and modern API concepts
What an application network is and why each reusable API makes the next project faster, the three qualities of a modern API, how a web service differs from an API, and when an API is internal, partner or external.
Identify core architectural concepts of the Application Network and modern APIs.
~7 min read · 5 practice questions ·
What the exam expects
- Pick the correct definition of an application network and reject look-alikes (a message broker, a VPN, nightly file copies).
- Explain why delivery speeds up as an application network grows: each API becomes a reusable asset for the next project.
- Name the three qualities of a modern API and spot options that contradict them.
- Separate APIs from web services: every web service is an API, not every API is a web service.
- Choose internal, partner or external access for an API from who must call it.
Key terms:
- Application network: applications, data and devices connected through reusable, governed APIs that other consumers can discover and use.
- Modern API: an API that is discoverable and accessible, productized and reusable, and managed for security and performance.
- Web service: a specific type of API that communicates over a network using web protocols.
- Partner API: an API that specific outside organizations reach with exclusive permissions.
Key facts
Application network definition
- Detail
- Connects applications, data and devices in a reusable, scalable, governed way
Network building blocks
- Detail
- APIs, used as standardized, reusable building blocks instead of single-use integrations
Network is not an architecture
- Detail
- A set of building blocks on top of which architectures are built
Agility measure
- Detail
- How many consumers get value, not how many assets exist
Three modern API qualities
- Detail
- Discoverable and accessible; productized and reusable; managed for security and performance
API forms in the network
- Detail
- REST, SOAP and database APIs
Web service vs API
- Detail
- All web services are APIs; not all APIs are web services
SOAP transports
- Detail
- HTTP, and also JMS, FTP and SMTP
Partner API
- Detail
- Specific outside organizations, exclusive permissions
External API
- Detail
- Third-party developers, self-service basis
- Why does MuleSoft say counting the assets on an application network is the wrong measure of agility?
- Why does a custom Salesforce-to-SAP integration that is on time and on budget still add no leverage?
- Which example list names XML-RPC services, and what does that list describe?
- When is an API internal rather than external?
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 (5 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams