Mendix Advanced Developer

Expect a proctored, computer-delivered test of multiple-choice items, each with one correct answer, built around realistic scenarios rather than definitions. Many items describe a project situation and ask which approach you would take. It is knowledge-based, so there is no hands-on build task. The current item count and time limit are published by Mendix on its certification pages.

Notably harder. Entry-level items ask what a feature does; advanced items ask which of several defensible-sounding options fits a specific architecture, security or performance constraint. Candidates who pass usually have shipped at least one multi-module application and have debugged a real integration. Guessing is expensive because the distractors are designed to look plausible.

You need to read and reason about Java actions, not write production-grade Java from scratch. Expect questions on when a Java action is the right tool versus a microflow, how Java actions exchange data with the domain model, and how exceptions surface and get handled. Basic Java syntax and an understanding of exception propagation cover most items.

Start with domain modeling and security, because access rules and entity structure shape almost every other answer. Move to microflow and nanoflow logic, validation and error handling, then integration patterns and mapping. Finish with performance, module architecture and deployment, which are easier to absorb once you understand runtime behaviour. Build a small app alongside each topic.

Three recurring traps: conflating module roles, entity access and page visibility when reasoning about security; choosing a nanoflow where server-side logic is required; and designing integrations that only handle the happy path. Another is picking a performance fix that trades memory for database load without identifying the actual bottleneck first.

Retake rules, waiting periods and validity periods are set by Mendix and have changed over time. Check the certification section of the Mendix website for the terms in force when you book. If you need a second attempt, spend the gap working on your weakest domain rather than re-reading the same material.

Most working developers need somewhere between a few weeks of evening study and a couple of months, depending on how much of the blueprint their day job already covers. The variable that matters is exposure, not hours: if you have never tuned a large dataset or configured a deployment, budget extra time for those areas specifically.

No course is a prerequisite, though instructor-led training helps if you learn best with structure. Independent study works if you build deliberately: a layered app with a published REST service, a consumed OData contract, entity access rules for several roles, and one Java action. Documentation, release notes and the community forum are enough reference material.

Registration goes through Mendix's own certification or academy portal, and pricing varies by region, bundle and whether training is included. The official site lists the current fee and available slots. This page deliberately does not quote a figure, because those numbers change and a stale one is worse than none.