Mendix Advanced Developer study guide
Mendix Advanced Developer · Work through your exam, one topic at a time.
The Mendix Advanced Developer credential is the second-tier certification for professionals who already build Mendix applications confidently and now need to show they can design them for scale, security and reuse. It targets developers with roughly a year or more of hands-on project work - people who model domain logic daily, wire up integrations, and are moving from "make it work" to "make it maintainable." The exam is scenario driven: item stems describe a realistic application problem and ask you to choose the best approach. The Mendix Advanced Developer study guide has 9 sections and about 2,883 words.
01Advanced Domain Modeling and Data Structure
This domain checks whether you can shape a domain model that survives change: inheritance, association choice, constraints, indexes and event handlers. Questions are usually scenario-based - a model is described and you pick the design that keeps queries fast and data consistent.
368 words, about 2 min02Security and Access Control
Project security has three levels: Off, Prototype and Production. Prototype allows demo users and belongs in development; Production enforces every rule and is required for a real deployment.
348 words, about 2 min03Microflow and Nanoflow Logic
Microflow variables are typed and scoped to the flow; a loop body sees the iterator plus any variable created before the loop. Use Create variable for constants and counters and Change variable for accumulation.
323 words, about 2 min04Validation and Error Handling
Required and unique are model-level rules evaluated at commit; a violation throws an exception, not a friendly message. Validation feedback is an activity that attaches a message to an object attribute and adds it to the object's validation set.
316 words, about 2 min05Integration: REST, SOAP, OData and Mapping
Call REST supports GET, POST, PUT, PATCH and DELETE, with URL parameters, headers and a body that can be a string, a file or an export mapping. Response handling is configured per status-code range: return nothing, store the body in a string variable, or import it with a mapping.
320 words, about 2 min06Performance and Scalability Tuning
Retrieve only what is needed: constrain with XPath, sort inside the retrieve so the database orders rows, and use range for pagination. XPath contains() , not equal and functions applied to attributes prevent index use.
307 words, about 2 min07Application Architecture and Reusable Module Design
A module owns its domain model. Other modules should reach it through microflows that form a published interface, or through entities explicitly designed as shared contracts - never by editing another module's attributes directly.
300 words, about 2 min08Deployment, Environments and Operations
A Mendix app typically runs in Development, Acceptance/Test and Production. Each environment has its own database, file storage, constants and admin account.
303 words, about 2 min09Java Actions and Runtime Extensibility
A Java action is a class extending CustomJavaAction<T with a constructor taking IContext plus the declared parameters, and an executeAction() method that throws CoreException . Parameter and return types map to Mendix types: String , Long , Boolean (use the wrapper classes so null is representable), IMendixObject , List<IMendixObject and member types.
298 words, about 1 min