Mendix Expert Developer study plan

Model a normalized domain for a small case system (customers, orders, order lines) with correct associations, ownership, and delete behavior, then justify each cardinality choice in writing.

Build both a persistent and a non-persistent entity and explain in your own notes when each is appropriate and what happens to data at runtime.

Create at least two entity generalizations and one calculated attribute, then document the trade-offs versus duplicating attributes.

Configure an entity with a system attribute set (created date, changed by) and verify the values populate correctly at runtime.

Implement a multi-step microflow that validates input, creates related objects in a single transaction, and rolls back cleanly on failure.

Replace at least three nested if/else chains with decision or split logic and record why readability improved.

Build a reusable sub-microflow with typed parameters and a return value, and call it from two different parent microflows.

Add error handling with custom validation feedback and confirm the user sees a meaningful message rather than a technical error.

Profile one microflow with the built-in performance tools and list every avoidable database retrieve you find.

Refactor a flat model into at least two modules with explicit module roles and documented dependencies in one direction only.

Convert three repeated retrieve-and-filter patterns into reusable microflow or database-level logic and measure the difference.

Design and implement an index strategy for the entities most frequently filtered in your case system, then verify query plans or explain the expected effect.

Write a short architecture note explaining how domain model boundaries align with microflow ownership.

Define module roles, map them to user roles, and demonstrate entity access rules that restrict both read and write per role.

Implement XPath-based access constraints on at least two entities and prove with two test users that restricted records are invisible.

Configure an identity provider or SSO-style sign-in path and document the attribute mapping used for user provisioning.

Test a privilege escalation attempt (user calling a microflow they should not access) and confirm the platform blocks it.

Publish a REST endpoint that exposes a domain entity with correct HTTP verbs, status codes, and pagination parameters.

Consume an external REST service, map the JSON to entities, and handle timeouts, non-2xx responses, and malformed payloads explicitly.

Add authentication to an outbound call (header-based token or basic auth) and confirm the credential is not hardcoded in the model.

Model one SOAP or XML-based integration and document the mapping decisions versus your REST approach.

Write an error-handling standard for integrations and apply it to both flows.

Identify the five slowest pages or microflows in your case system and fix at least three using lazy loading, paging, or reduced retrieves.

Configure environment-specific settings (constants, database, storage) so the same deployment package runs in two environments without code changes.

Deploy the app to a cloud environment, then verify logs, health, and restart behavior after a simulated failure.

Measure and record baseline response times before and after your tuning changes.

Extract a reusable module (with its own domain model and published interface) and consume it from the main app without direct entity coupling.

Set up a repository with a branching strategy, then simulate a merge conflict and resolve it deliberately.

Build a CI/CD pipeline that runs on commit, produces a deployment package, and blocks on failure.

Document a versioning and release convention for the reusable module.

Write and run automated unit tests for at least five microflows, including two negative cases.

Reproduce and fix two deliberately introduced defects, documenting the diagnostic path for each.

Run a full timed practice exam and categorize every missed question by domain.

Re-study your two weakest domains using the missed-question list and re-test those areas.