Mendix Advanced Developer exam-day guide
Mendix Advanced Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Use a passport or national ID card with a photo and signature. The name must match your registration record exactly - including accents and middle names. Confirm the accepted ID types and name-change procedure with the provider before booking.
Exam appointment confirmation and access link
Have the confirmation email, your candidate/registration number, and the launch link open in a tab or saved offline. Note your appointment time in both your local time zone and UTC so a daylight-saving shift cannot make you late.
Laptop with charger plugged in
A proctored Mendix certification exam runs long enough that battery-only is risky. Plug into mains power, disable sleep and automatic OS updates, and close Slack, Teams, and any background sync clients before launch.
Webcam, microphone, and browser compatibility check
Run the proctoring vendor's system test at least 24 hours ahead - test camera, mic, screen share, and browser version. If the test fails, fix it that day rather than on exam morning. Confirm the supported browser with the provider.
Stable internet with a backup connection
Prefer a wired connection. Have a phone hotspot ready as a fallback and know how to switch to it quickly. A drop mid-exam is the most common cause of lost time; save the provider's technical support number in your phone.
Private, quiet, well-lit room with a clean desk
Clear the desk of notes, books, second monitors, printers, and phones. The proctor may ask for a 360-degree room scan with the webcam. Tell household members you are unavailable and put a do-not-disturb sign on the door.
Clarify the allowed-materials policy in advance
Mendix exams are typically closed-book, but rules on second screens, printed notes, and the Mendix documentation site vary by delivery method. Ask the provider in writing and assume the strictest reading if you cannot get an answer.
Clarify the scratch-paper and whiteboard policy
Some proctored exams permit a blank sheet or erasable whiteboard shown to the camera first; others forbid all writing materials. Confirm before exam day, since domain-model and XPath sketching is much easier on paper.
Your own weak-domain list
Bring a one-page summary (to review before launch, not during the exam) of the topics you missed on practice questions - typically entity access vs. module roles, microflow vs. nanoflow constraints, association ownership, and retrieve/index performance.
Water in a clear container and any approved medication
Small comforts reduce mid-exam distraction, but containers and medications may need to be shown to the proctor. Confirm the policy with the provider rather than assuming.
Provider support contact and incident procedure
Write down the technical support number and the process for reporting a disconnection or proctor issue. Know that you should stay on camera and contact support rather than restarting the exam yourself.
Plan the day
Do one full timed practice run under exam conditions to find your pacing. Then spend the remaining time only on weak domains: entity access rules and XPath constraints, microflow vs. nanoflow capabilities, association ownership and delete behavior, indexes and retrieve performance, validation via event handlers, and error handling with custom error types. Build a single A4 summary sheet you will review, then discard before the exam.
Stop learning new topics. Re-read your summary sheet and walk through the Mendix model concepts you get wrong most often - for example, why a calculated attribute cannot be used in a retrieve XPath, or why a nanoflow cannot call a Java action. Do a final pass on integration basics (REST/SOAP calls, import/export mappings, JSON structure) since these appear as scenario questions rather than syntax questions.
Run the proctoring system test again, confirm your ID, appointment time, and access link, and check the provider's rules on materials, breaks, and retakes. Charge devices, tidy the exam room, and set two alarms. Get a normal night's sleep rather than cramming - recall on scenario questions degrades sharply when you are tired.
Eat, hydrate, and skim only your summary sheet - no new material. Set up the room, close all other applications, plug in power, and have your ID and confirmation ready. Join the check-in 15-20 minutes early to absorb proctor verification and room scanning without eating into exam time.
Read the instructions and note the total question count and time limit, then compute your per-question budget. Do a first pass answering what you know quickly, flagging long scenario questions. For Mendix scenario items, eliminate options that are technically impossible (a nanoflow calling a Java action, an entity access rule bypassed by a microflow) before reasoning about which remaining option is best practice.
Stick to your per-question budget: if a question takes more than about 90 seconds, flag it and move on. Watch for wording traps - 'best practice', 'most efficient', 'least privilege', 'NOT'. When two options are both workable, choose the one that is idiomatic in Mendix: reuse via sub-microflows, validation on the entity, security at the entity-access level rather than in microflows.
Return to flagged questions, confirm none are unanswered, and sanity-check any changed answers - first instincts are usually right on well-known concepts. Submit deliberately, wait for the confirmation screen, and note the result or where the score will be published before closing the browser.
Rules to check
Identity: present the original government-issued photo ID you registered with, and be ready to show it to the camera on request. If the name on your ID does not match your registration, contact the provider before exam day - do not attempt check-in hoping it will pass.
Environment: you must be alone in the room for the entire session, with no second screen, phone, smartwatch, notes, or other people visible or audible. Reading questions aloud or talking to yourself can be flagged as suspicious behaviour, so read silently.
Materials: treat the exam as closed-book unless the provider has told you otherwise in writing. Do not open a second browser tab, the Mendix documentation, Studio Pro, or an AI assistant during the session; doing so is grounds for invalidation and possible suspension from future certifications.
Breaks: assume no unscheduled breaks are permitted during a proctored session, and that leaving the camera view pauses or ends your exam. If you need an accommodation or a scheduled break, request it from the provider well before the appointment.
Scoring and results: the exam is scored pass/fail against a passing score set by the provider, not published as a simple percentage of correct answers, and individual question feedback is normally not released. Confirm the passing score, result timing, and retake/waiting-period policy with the provider rather than relying on forum reports.
Technical incidents: if the connection drops or the proctor chat becomes unresponsive, stay calm, do not restart the exam or open other applications, and contact provider support with your registration number. Report the incident immediately - retrospective claims are much harder to resolve.
Confidentiality: do not copy, photograph, screenshot, record, or later reproduce exam questions, including in study groups or online forums. Certification agreements typically prohibit this and it can void your result.
Time management: the clock runs continuously once the exam starts and does not pause for technical issues in most delivery setups. Confirm whether any time adjustment is granted for verified incidents before assuming you will get lost minutes back.