Using Connectors10% of the exam
Database Connector operations, parameters and transactions
Which Database Connector operation returns what (Select, Query Single, Insert, Bulk Insert), how input parameters and dynamic queries keep SQL safe, how to connect with Generic Connection and a pooling profile, and how operations join a transaction.
Apply correct processors/syntax to connect to databases, and predict outcomes.
~7 min read · 11 practice questions ·
What the exam expects
- Write a Select whose WHERE values come from input parameters, and build a dynamic table name with DataWeave interpolation without giving up the parameters.
- Predict what Select, Query Single, Insert and Bulk Insert put in the payload, including generated keys and the case where a later processor needs the original payload.
- Choose a connection type (Generic Connection plus a JDBC driver for an unsupported database) and tune the pooling profile.
- Predict what each
transactionalActionvalue does on a Database operation, how operations join a Try scope transaction, and why a streamed Select fails after its transaction closes. - Key terms: input parameters (a map bound on the JDBC prepared statement, referenced as
:name); dynamic query (SQL text built with a#[ ]string and$( )interpolation); Statement Result (Insert/Update output with affected rows and generated keys); pooling profile (settings for the connection pool); transactional action (how an operation relates to an active transaction).
Key facts
Input parameters
- Detail
- Map bound on the JDBC prepared statement; referenced as
:namein the SQL
Select output
- Detail
- Array of Object, streamed automatically
Query Single output
- Detail
- Object; first record only when several match; no streaming
Insert / Update output
- Detail
- Statement Result (Affected Rows, Generated Keys)
Auto Generate Keys
- Detail
- Default
false
Keep records after Bulk Insert
- Detail
- Store its result in a target variable
Unsupported database
- Detail
- Generic Connection with URL and Driver class name
Test Connection On Checkout
- Detail
- Default true; deselect it to improve pooled performance
Max Wait
- Detail
- Default 0, which means wait indefinitely
Default transactional action
- Detail
JOIN_IF_POSSIBLE;ALWAYS_JOINerrors with no transaction
Sources for this section (5)
- Query a Database Examplesdocs.mulesoft.com (opens in a new tab)
- Database Connector Reference 1.16docs.mulesoft.com (opens in a new tab)
- Enrich Data with Target Variablesdocs.mulesoft.com (opens in a new tab)
- Configure a Database Connectiondocs.mulesoft.com (opens in a new tab)
- Configure Database Transactions Exampledocs.mulesoft.com (opens in a new tab)
- Why does Query Single not exhaust a small connection pool?
- What happens to rows beyond Max Rows on a Select?
- When does a Max Wait of
0matter? - What does Acquire Increment control?
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 (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams