What the published objective requires
- Bind database inputs safely
- Select connector operations and event sources
- Combine connector results without losing the current event
Domain 6 of 12 · 10% of the official blueprint
Using Connectors practice lesson
Configure safe database, file-transfer and service calls while predicting connector outputs and errors.
The misconception to eliminate
Choosing a connector only by endpoint type while ignoring whether the component must be a source, operation or enrichment target.
Practice allocation: 6 of 60 questions in our whole-question mock blueprint.
Decision rules
Retrieve these without looking before attempting the question.
Rule 1
Use named input parameters for SQL values; do not concatenate untrusted values into query text.
Rule 2
Connector operations can replace payload or write to a target variable—choose deliberately.
Rule 3
Listeners create Mule events; operations consume or modify resources inside an existing flow.
Rule 4
Design for typed connector errors such as connectivity, query execution and missing files.
Worked Northstar scenario
Scenario
Select an order using an inbound orderId and keep the request payload for audit.
Reasoning
Bind :orderId with an input parameter map and store the Select output in vars.orderRows via target. The payload remains available for the audit record.
Free practice question
Why is an input-parameter map preferred to concatenating a customer id into SQL?
- It makes every query asynchronous
- It binds data separately and reduces injection risk
- It stores results in Object Store
- It creates the database schema
Reveal answer and reasoning
Answer: B. Prepared-statement parameters separate values from SQL structure and support safer execution.
The complete program contains five guided drills for this domain, an 80% mastery gate, saved progress and a separate 60-question timed mock.
Get Domain MasteryHands-on proof preview
Parameterize and enrich
Repair a query built with string concatenation.
- Replace concatenated SQL with WHERE order_id = :orderId.
- Bind orderId from attributes.uriParams.orderId.
- Set target to orderRows.
- Verify malicious input is treated as a value and the original payload survives.
Evidence to keep: The logger shows unchanged payload plus vars.orderRows; the SQL text contains no inbound string concatenation.
Primary sources
Questions about this domain
How much of the MuleSoft Developer exam is Using Connectors?
Salesforce publishes a weight of 10% for this domain. In a 60-question practice allocation, that is represented here by 6 questions.
Is this Using Connectors question from the real exam?
No. It is original independent practice material written only from public exam objectives and product documentation.