Mendix Rapid Developer study guide
Mendix Rapid Developer · Work through your exam, one topic at a time.
The Mendix Rapid Developer certification is an entry-level credential for people who build applications on the Mendix low-code platform in Studio Pro. It suits aspiring citizen developers, junior consultants, business analysts moving into delivery roles, and anyone who needs to prove they can model data, build pages, and write microflows without a traditional programming background. The Mendix Rapid Developer study guide has 9 sections and about 3,340 words.
01Mendix Platform and Studio Pro Fundamentals
This domain checks that you know where things live in the Mendix toolchain: the Portal, Studio Pro, the runtime, and how a project is split into modules and documents. Questions are mainly about structure, terminology, and which tool owns which responsibility.
389 words, about 2 min02Domain Model and Data Modeling
This domain tests entity design: persistency, attribute types and validation rules, associations and their delete behavior, generalization, and reuse of System module entities. Persistent entities are stored in the database; non-persistent entities exist only in memory and are ideal as page helper objects or REST payload holders.
386 words, about 2 min03Pages, Layouts, and User Interface
This domain covers how the UI is assembled: layouts and placeholders, snippets versus building blocks, data containers, widget binding, page parameters, navigation profiles, and the action a button or link triggers. Every page is placed on a layout.
390 words, about 2 min04Microflows and Business Logic
This domain tests server-side logic: microflow versus nanoflow, the standard activity set, parameters and return values, error handling, and the entity-access setting that changes what a microflow may do. Microflows run in the runtime: they can commit, log, call Java actions and REST services, and raise errors.
353 words, about 2 min05Security and Access Control
This domain tests the security model end to end: security levels, the distinction between app roles and module roles, entity access with XPath constraints, page and microflow access, anonymous users, and demo users. Off – no checks at all; anyone with the URL is effectively administrator.
373 words, about 2 min06Integration and REST/SOAP Services
This domain tests how the app talks to other systems: consumed REST services, published REST services, SOAP web services, import and export mappings, authentication, and error handling on outbound calls. A consumed REST service document holds the base URL and a list of operations: HTTP method, path, query parameters, headers, request body, response handling, and authentication (none, basic with credentials, or custom).
367 words, about 2 min07XPath, Validation, and Events
This domain tests three connected areas: writing XPath constraints correctly, enforcing validation, and hooking entity events with microflows. XPath appears in retrieve activities and in entity access constraints.
339 words, about 2 min08Deployment, Version Control, and Environment Management
This domain tests the path from model to running app, plus how model changes are versioned and promoted between environments. You create a deployment package in Studio Pro, which builds the model into a deployable artifact.
353 words, about 2 min09Agile Development, Team Server, and Feedback Management
This domain tests how a Mendix team plans work and closes the loop with users: backlog and sprint structure in the Portal, Team Server roles and version control, and the feedback process that turns user reports into stories. The Portal (historically called Sprintr) holds the project's backlog.
390 words, about 2 min