Explain the common technical complexities and patterns in integration development18% of the exam
HTTP, Database, File connectors and core components
How a Mule flow is assembled from a source, connector operations and core components: HTTP Listener versus HTTP Request, Database Connector over JDBC, File Connector on a local file system, the Scheduler and the For Each scope.
Design MuleSoft applications using common features of core connectors.
~6 min read · 4 practice questions ·
What the exam expects
- Pick the component that starts a flow: an HTTP Listener for incoming requests, a Scheduler for an interval, or a connector listener for new files or rows.
- Distinguish the HTTP Listener source (server side) from the HTTP Request operation (client side).
- Explain how Database Connector reaches any JDBC relational database, including ones without a preset connection.
- Name the File Connector operations for a locally mounted file system.
- Describe the features every connector shares: sources and operations, a reusable connection configuration, namespaced connectivity errors and reconnection strategies.
- Read a flow sketch of source, operations, routers and scopes.
Key terms:
- Source (endpoint): the first component of a flow, which triggers its processing.
- Operation: a connector action run inside the flow, such as an HTTP Request or a Database Select.
- Router: a flow control component that sends the event down one or more routes.
- Scope: a component that wraps a sequence of processors and applies behaviour to it.
Key facts
Listener behaviour
- Detail
- Triggers the flow on a matching path; responds after the flow finishes
Preset database providers
- Detail
- Derby, Microsoft SQL Server, MySQL, Oracle
Other databases
- Detail
- Generic JDBC configuration with a JDBC-compliant driver
File Connector scope
- Detail
- Locally mounted file system; remote servers use FTP or SFTP Connector
New-file detection
- Detail
- Auto delete, Move to directory or Watermark
Connector roles in a flow
- Detail
- Inbound endpoint (source), message processor (operation), outbound endpoint
Connection configuration
- Detail
- Updated once without updating other parts of the app
Failed connection, default
- Detail
- Fails at once with a namespaced error such as
DB:CONNECTIVITY
Reconnection strategies
- Detail
- None (default), Standard (set attempts and interval), Forever
Sources for this section (6)
- HTTP Connectordocs.mulesoft.com (opens in a new tab)
- Database Connectordocs.mulesoft.com (opens in a new tab)
- File Connectordocs.mulesoft.com (opens in a new tab)
- New or updated filedocs.mulesoft.com (opens in a new tab)
- Connectors Overviewdocs.mulesoft.com (opens in a new tab)
- Reconnection Strategiesdocs.mulesoft.com (opens in a new tab)
- Why can a team change a system's connection details without editing every flow that uses it?
- When does a connector operation fail immediately with a connectivity error such as
FTP:CONNECTIVITY? - What happens to the rest of a collection when one element fails inside For Each?
- Which Watermark modes can the File listener use to pick new files?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Integration Foundations pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 37 lessons of the MuleSoft Integration Foundations guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (4 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