# HTTP, Database, File connectors and core components

*MuleSoft Integration Foundations Study Guide · Explain the common technical complexities and patterns in integration development · Last updated November 2, 2026 · https://www.certifyforce.com/study-guide/mulesoft-integration-foundations/technical-complexities-and-patterns-in-integration-development/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.

- Certification: Salesforce MuleSoft Integration Foundations
- Exam section: Explain the common technical complexities and patterns in integration development
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-integration-foundations

**Official exam objective:**

> Design MuleSoft applications using common features of core connectors.

## 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

| Fact | Detail | Source |
|---|---|---|
| Listener behaviour | Triggers the flow on a matching path; responds after the flow finishes | [HTTP Connector](https://docs.mulesoft.com/http-connector/latest/) |
| Preset database providers | Derby, Microsoft SQL Server, MySQL, Oracle | [Database Connector](https://docs.mulesoft.com/db-connector/latest/) |
| Other databases | Generic JDBC configuration with a JDBC-compliant driver | [Database Connector](https://docs.mulesoft.com/db-connector/latest/) |
| File Connector scope | Locally mounted file system; remote servers use FTP or SFTP Connector | [File Connector](https://docs.mulesoft.com/file-connector/latest/) |
| New-file detection | Auto delete, Move to directory or Watermark | [New or updated file](https://docs.mulesoft.com/file-connector/latest/file-on-new-file) |
| Connector roles in a flow | Inbound endpoint (source), message processor (operation), outbound endpoint | [Connectors Overview](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) |
| Connection configuration | Updated once without updating other parts of the app | [Connectors Overview](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) |
| Failed connection, default | Fails at once with a namespaced error such as `DB:CONNECTIVITY` | [Reconnection Strategies](https://docs.mulesoft.com/mule-runtime/latest/reconnection-strategy-about) |
| Reconnection strategies | None (default), Standard (set attempts and interval), Forever | [Reconnection Strategies](https://docs.mulesoft.com/mule-runtime/latest/reconnection-strategy-about) |

## Check yourself

- 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?

## Sources

- [HTTP Connector](https://docs.mulesoft.com/http-connector/latest/)
- [Database Connector](https://docs.mulesoft.com/db-connector/latest/)
- [File Connector](https://docs.mulesoft.com/file-connector/latest/)
- [To Trigger a Flow When a New File is Created or Modified](https://docs.mulesoft.com/file-connector/latest/file-on-new-file)
- [Core Components](https://docs.mulesoft.com/mule-runtime/latest/about-components)
- [Scheduler Endpoint (Trigger)](https://docs.mulesoft.com/mule-runtime/latest/scheduler-concept)
- [For Each Scope](https://docs.mulesoft.com/mule-runtime/latest/for-each-scope-concept)
- [Anypoint Connectors Overview](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)
- [Reconnection Strategies](https://docs.mulesoft.com/mule-runtime/latest/reconnection-strategy-about)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 4 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Integration Foundations pack (USD $19): https://www.certifyforce.com/practice-exams