Career upgrade: Learn practical AI skills for better jobs and higher pay.
Level up
PracticeVideosBlogFlashcardsEspañol
All Practice Exams

100+ Free Mendix Intermediate Developer Practice Questions

Pass your Mendix Certified Intermediate Developer exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

In Mendix, when is it appropriate to use a 'Non-persistent entity' instead of a persistent one?

A
B
C
D
to track
Same family resources

Explore More Mendix Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

Mendix Certified Advanced Developer

Practice Questions

Mendix Certified Expert Developer

Practice Questions

Mendix Certified Rapid Developer

Practice Questions
2026 Statistics

Key Facts: Mendix Intermediate Developer Exam

60

Exam Questions

Mendix Academy

90 min

Exam Duration

Mendix Academy

70%

Passing Score

Mendix Academy

$25

Exam Fee

Mendix Academy (free with subscription)

2 years

Validity Period

Mendix Academy

Intermediate

Difficulty Level

Mid-level certification

The Mendix Intermediate Developer exam has 60 questions in 90 minutes with a 70% passing score. Key domains: complex microflows, REST/SOAP integration, advanced UI, debugging, and mobile development. Exam fee is $25 (free with Mendix subscription). Certification valid for 2 years.

Sample Mendix Intermediate Developer Practice Questions

Try these sample questions to test your Mendix Intermediate Developer exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1In Mendix, what is the key advantage of using a 'Sub-microflow' compared to inline logic?
A.Sub-microflows run faster because they use a separate thread
B.Sub-microflows encapsulate reusable logic, improving maintainability and reducing duplication
C.Sub-microflows bypass entity access rules for better performance
D.Sub-microflows are the only way to call external REST services
Explanation: Sub-microflows encapsulate a block of business logic that can be called from multiple places. This reduces code duplication, makes microflows easier to read and maintain, and allows changes to be made in a single location that propagates everywhere the sub-microflow is called.
2In Mendix Studio Pro, how do you call an external REST API from a microflow?
A.Use the 'Call REST service' activity with a configured REST operation
B.Use the 'HTTP request' activity with the endpoint URL
C.Use the 'External call' activity from the Integration menu
D.Use a Java action with the Mendix HTTP client library
Explanation: Mendix provides the 'Call REST service' activity in microflows for calling external REST APIs. You configure the URL, HTTP method, headers, request body, and response mapping. The response can be imported into Mendix objects using an import mapping.
3What is the purpose of an 'Import mapping' in Mendix REST/SOAP integration?
A.It maps Mendix entity attributes to database column names
B.It defines how incoming JSON or XML data maps to Mendix entities and attributes
C.It imports a Mendix module (.mpk) from the Marketplace into a project
D.It configures authentication credentials for consuming external services
Explanation: An Import mapping in Mendix defines how incoming JSON or XML from an external service (REST response, SOAP response, or imported file) is mapped to Mendix entity instances and their attributes. It is used with the 'Import with mapping' activity or as the response mapping in 'Call REST service'.
4In Mendix, what is an 'Export mapping' used for?
A.Exporting the domain model as an XSD schema for documentation
B.Converting Mendix objects into JSON or XML to send to an external service
C.Exporting application data to a CSV file for reporting
D.Mapping Mendix enumeration values to integer codes in the database
Explanation: An Export mapping in Mendix converts Mendix entity objects and their attributes into a JSON or XML structure for sending to external services. It is used with 'Export with mapping' activity or as the request body mapping in a 'Call REST service' or published REST/SOAP service.
5What is the difference between 'Commit with events' and 'Commit without events' in Mendix?
A.Commit with events saves to the database; Commit without events only saves to memory
B.Commit with events triggers 'Before commit' and 'After commit' event microflows; Commit without events skips them
C.Commit with events sends a notification email to users; Commit without events does not
D.Commit with events validates XPath constraints; Commit without events skips validation
Explanation: In Mendix, entities can have 'Before commit' and 'After commit' event microflows that run automatically when objects are committed. 'Commit with events' (the default) triggers these event microflows. 'Commit without events' explicitly skips them, useful for bulk operations or when you need to bypass event-driven logic.
6In Mendix, how do you expose a microflow as a REST endpoint that external systems can call?
A.Add the microflow to a 'Published REST service' and configure resource operations
B.Set the microflow's access level to 'Public' in security settings
C.Create a 'Web service' and bind the microflow to it using WSDL
D.Enable 'REST mode' in the microflow properties panel
Explanation: To expose microflows as REST endpoints, you create a 'Published REST service' in Mendix Studio Pro, add resources (URL paths), define operations (GET, POST, etc.), and map each operation to a microflow. The service is then automatically available at the configured URL path.
7Which Mendix feature allows you to catch and handle a specific Java exception type within a microflow error handler?
A.Using an 'Exclusive split' to check the $latestError variable type
B.The 'Error handling' configuration on the activity allows specifying exception type filters
C.Custom error handling requires setting error type in a Java action wrapper
D.Mendix does not support catching specific exception types; all errors are handled uniformly
Explanation: When using custom error handling in Mendix, the $latestError variable is available in the error flow. You can use an Exclusive split checking $latestError/type or $latestError/message to distinguish between different error types or messages and handle them differently.
8In Mendix, what is the 'XPath constraint' used for in a 'Retrieve' activity?
A.Filtering which objects to retrieve from the database based on conditions
B.Defining the traversal path for navigating through entity associations
C.Validating XML data received from an external service
D.Specifying which attributes of the retrieved object to include
Explanation: XPath constraints in Mendix's Retrieve activity filter which objects are returned from the database. The constraint evaluates against the entity's attributes and associated entities, allowing precise data retrieval without loading unnecessary objects.
9A Mendix microflow calls an external REST service that sometimes returns HTTP 404 or 500 status codes. What is the correct approach to handle these error responses?
A.Use the 'HTTP status code' output variable of the 'Call REST service' activity and handle non-200 codes with an Exclusive split
B.Wrap the call in a try-catch block within the microflow
C.Enable the 'Fail on non-200' option in Call REST service to automatically throw an error
D.Check the response body for error keywords using string operations
Explanation: The 'Call REST service' activity has an 'HTTP response' output that includes the HTTP status code. You can store the response and then use an Exclusive split on the status code variable to route to success handling (2xx) or error handling (4xx/5xx), implementing graceful error recovery.
10What is the purpose of the Mendix 'Consumed web service' (SOAP) document?
A.Defines the WSDL for a web service you are publishing for others to use
B.Imports a WSDL from an external SOAP service so you can call it from microflows
C.Converts a REST service to a SOAP-compatible format
D.Manages OAuth tokens for secure API calls
Explanation: A 'Consumed web service' document in Mendix is created by importing a WSDL from an external SOAP service. Mendix generates the necessary operation activities, message structures, and mappings so you can call the SOAP service from microflows using the 'Call web service' activity.

About the Mendix Intermediate Developer Exam

The Mendix Certified Intermediate Developer certification validates skills in building more complex Mendix applications, including REST and SOAP integrations, advanced microflow patterns, mobile development with nanoflows, debugging techniques, and advanced UI components.

Questions

60 scored questions

Time Limit

90 minutes

Passing Score

70%

Exam Fee

$25 (free with subscription) (Mendix Academy)

Mendix Intermediate Developer Exam Content Outline

~25%

Complex Microflows

Sub-microflows and reuse, list operations (union, intersect, subtract), aggregate list, parallel split, deep clone, complex error handling with $latestError, before/after commit events

~25%

REST and SOAP Integration

Call REST service activity, import/export mappings, JSON and XML profiles, published REST services, consumed SOAP web services, authentication (basic, token), HTTP status codes

~20%

Advanced UI

Data grid search bar with association search, conditional visibility, Data view association source, page URL configuration, deep linking, client-side validation rules, row-level security with XPath

~15%

Debugging and Quality

Microflow debugger breakpoints and step-through, consistency checks in Studio Pro, Log message activity, entity validation rules, Mendix ATS basics

~15%

Mobile Development

Mendix Native Mobile with React Native, nanoflows vs. microflows, offline data model, Synchronize activity, native mobile capabilities (camera, GPS, push notifications)

How to Pass the Mendix Intermediate Developer Exam

What You Need to Know

  • Passing score: 70%
  • Exam length: 60 questions
  • Time limit: 90 minutes
  • Exam fee: $25 (free with subscription)

Keys to Passing

  • Complete 500+ practice questions
  • Score 80%+ consistently before scheduling
  • Focus on highest-weighted sections
  • Use our AI tutor for tough concepts

Mendix Intermediate Developer Study Tips from Top Performers

1Build a real REST integration end-to-end: Call REST service → Import mapping → consume response
2Practice import/export mappings for both JSON and XML formats
3Understand row-level security with XPath: [Association/Entity = '[%CurrentUser%]']
4Know when to use sub-microflows for reuse vs. inline logic
5Practice debugging with breakpoints in the microflow debugger
6Understand the difference between microflows (server) and nanoflows (client) and their limitations
7Know how to handle 404 and 500 HTTP responses from REST calls gracefully

Frequently Asked Questions

What is the cost of the Mendix Intermediate Developer exam?

The Mendix Intermediate Developer exam costs $25 USD. However, it is free if you have an active Mendix subscription (MxEagle or higher). Check Mendix Academy for current pricing and subscription options.

What is the difference between Mendix Rapid and Intermediate Developer certifications?

The Rapid Developer covers fundamentals: basic domain model, simple pages, basic microflows, and security. The Intermediate Developer adds: REST/SOAP integration, complex microflow patterns, advanced UI (deep linking, row-level security), mobile development with nanoflows, and debugging skills. It requires more practical experience.

How should I study for REST integration on the Mendix Intermediate exam?

Build hands-on REST integrations in Studio Pro: create a Call REST service activity, build import and export mappings for JSON responses, expose a process as a Published REST service, and handle HTTP error codes with Decision shapes. Practice with real public REST APIs (JSONPlaceholder, OpenWeather) to build confidence.