1.1 Exam Blueprint, Format & Logistics

1.1 Exam Blueprint, Format & Logistics

Exam Focus: Before you study a single microflow pattern, know exactly what this exam measures. This section covers the published exam format, the eight scored sections, the twelve topic areas named in the official Mendix exam guide, the six Academy learning paths Mendix recommends, the proctoring rules that can nullify a result, and how the rest of this guide maps onto that blueprint.

The Intermediate Developer certification is the second rung of the four-level Mendix ladder (Rapid → Intermediate → Advanced → Expert). Mendix describes the holder as someone whose knowledge and skills "extend beyond the fundamentals of the Mendix platform" — ready to build more complex features, but still taking occasional guidance from more advanced developers. That positioning drives the exam design. It is broad rather than deep, it favours "which Studio Pro setting does X" over "write this algorithm", and it repeatedly tests platform behaviour that only becomes obvious once you have actually built something.

---

Published Exam Format

Mendix also publishes the preparation profile for this level: roughly 30–40 hours of self-paced Academy learning (or equivalent classroom or partner-bootcamp training), on top of about six weeks of hands-on Mendix experience.

Do not assume an expiry date. Mendix does not publish a validity period or renewal requirement for the Intermediate Developer certificate in its exam guide or on its certification pages. Treat third-party claims of a fixed "two-year validity" as unverified, and confirm current policy with Mendix Academy before you plan a recertification.

---

The Eight Scored Sections

The official exam guide states that the exam "is separated into the following sections", each carrying a varying number of questions:

1. Agile
2. Security
3. Microflows
4. Pages
5. Domain Model
6. Modules
7. Translation
8. XPath

Because there is no per-section minimum, one weak section cannot fail you on its own. But with only 50 questions, 13 wrong answers is the entire margin — two neglected sections are usually enough to sink an attempt. Section scores come back with your result, which makes a failed attempt genuinely diagnostic for the retake.

---

The Twelve Published Topic Areas

The exam guide lists the topics that are part of the exam:

• Project roles & responsibilities
• Constraining data with XPath
• Page design with AtlasUI
• Project Directory unfolded
• Structuring your project with Sub microflows
• Rules
• System members
• List operations
• Client notifications
• Multi-lingual front-end
• Anonymous users
• Security

Notice what is absent: Java actions, workflow (BPMN), OData and Data Hub publishing, performance profiling, and the Model SDK. Those belong to the Advanced and Expert levels. If you find yourself deep in a Java action tutorial, you have drifted past the blueprint.

---

Recommended Preparation Paths

Mendix recommends attending the Intermediate Developer course or a Mendix Bootcamp, or completing these Intermediate learning paths in the Academy:

---

How This Guide Maps to the Blueprint

Chapters 1–6 carry the scored blueprint end to end. Chapters 7–9 are included deliberately, because Mendix delivery work demands them and because they reinforce the microflow, page, and security behaviour that is scored — but if you are short on revision time, finish Chapters 1–6 first.

---

Proctoring Rules That Nullify Results

The exam is delivered through a proctored testing platform and recordings are reviewed by Mendix Academy. A violation does not merely cost you the attempt: results are nullified, you are barred from any Mendix exam for three months, and your employer is informed. The published prohibitions include:

• Recording the exam in any form — screenshots, photographs, video, or copying text
• Using notes, physical or virtual, or any document of questions and answers
• Using electronic devices; phones and tablets are detected in your workspace
• Wearing headphones or ear plugs
• Navigating away from the test window, or using a browser search engine
• Using a second monitor or a second computer
• Having anyone else present, or reading questions out loud
• Leaving the desk for longer than two minutes, or moving out of camera view

Practical setup: one monitor only, a working webcam and microphone, a quiet room, and a system-compatibility check run days in advance rather than minutes before. Budget 15 minutes for login. Your personal exam link arrives by email, cannot be forwarded to another address, and expires after one month.

---

A Study Plan That Matches the Blueprint

1. Build, do not just read. Almost every question is a Studio Pro scenario. Model each topic once in a scratch app — an entity with an access rule, a snippet, a sub-microflow, a Batch Translate run.
2. Weight revision by section, not by interest. Eight sections, one overall threshold: the hour you have spare belongs to your weakest section, not your favourite one.
3. Memorise the settings vocabulary. On-delete wording, security levels, error-handling names, data-source options, and log levels are all named things the exam quotes verbatim.
4. Practise reading distractors. Options are long and plausible; the wrong ones usually invert exactly one word — owner versus non-owner, client versus server, rollback versus without rollback.