Mendix Advanced Developer study materials
Mendix Advanced Developer study resources

Mendix Advanced Developer study plan

Mendix Advanced Developer · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Advanced domain modeling and data structure

  • Model a generalization hierarchy with at least two specialized entities and justify in writing where inheritance is better than a one-to-one association.

  • Configure reference and reference-set associations, set delete behavior for each relation, and record the cascade consequences for five sample records.

  • Normalize a denormalized event-registration dataset into at least six entities and check the result against three user stories.

  • Replace stored duplicated values with calculated attributes or non-persistent entities, and verify the values on a page.

Your checkpoint

A case-management sample domain model with 8+ entities, 2 generalization hierarchies, 3 associations, a one-page ERD, and a delete-behavior table validated against 5 sample records.

Week 2

Advanced domain modeling and data structure & Security and access control

  • Define four module roles and write entity access rules with XPath constraints for create, read, update, and delete.

  • Configure page access and microflow access per module role, then verify allowed and denied paths with demo users.

  • Implement an owner-based XPath constraint so users see only records they created, and test it with two users.

  • Document the role-permission matrix and identify three rules that could leak data if left at default.

Your checkpoint

A role-permission matrix covering 4 module roles and 12 entity access rules, plus a tested login script showing allowed and denied actions for each role.

Week 3

Security and access control & Microflow and nanoflow logic, validation and error handling

  • Implement five custom validation rules in microflows with specific error messages and member-level feedback.

  • Add error handling around a multi-step microflow using error events, rollback behavior, and structured logging for three failure paths.

  • Build a nanoflow validation path for an offline-capable form and confirm it behaves the same as the online microflow.

  • Write ten unit-test microflows using the Mendix Unit Testing module and run them as a suite.

Your checkpoint

A validation and error-handling module with 10 passing unit-test microflows, 5 custom validation rules, and a documented rollback/logging pattern for 3 failure paths.

Week 4

Microflow and nanoflow logic, validation and error handling & Integration: REST, SOAP, OData and mapping

  • Consume two REST endpoints using import mappings and handle success, 4xx, and timeout responses explicitly.

  • Publish one OData or REST service with authentication and test it with six request cases.

  • Map nested JSON arrays into related entities and verify parent-child records after import.

  • Add integration error handling that logs the request identifier, rolls back partial data, and returns a user-safe message.

Your checkpoint

An integration slice with 2 consumed REST endpoints, 1 published OData service, import/export mappings, and a test log of 6 request/response cases including 2 error responses.

Week 5

Integration: REST, SOAP, OData and mapping

  • Consume a SOAP service from a WSDL and map the response into the domain model with fault handling.

  • Design a JSON structure and export mapping for an outbound payload used by two different consumers.

  • Implement retry, timeout, and idempotency behavior around one integration and document the limits.

  • Publish a REST service with role-based authentication and validate three unauthorized access attempts.

Your checkpoint

Integration module with 1 consumed SOAP service, 1 published REST service, 1 published OData service, 4 mappings, and a failure-handling runbook covering timeout, 4xx, and 5xx.

Week 6

Performance and scalability tuning & Application architecture and reusable module design

  • Profile three list pages and reduce database queries by changing retrieve patterns and adding indexes where supported.

  • Refactor a duplicated microflow into reusable sub-microflows with a documented interface and error contract.

  • Design a reusable module with exposed entities, microflows, module roles, and a README describing its public API.

  • Import the reusable module into a second app and verify the exposed interface works without changes.

Your checkpoint

A performance report showing before/after query counts and load times for 3 pages, plus a reusable module with a README, exposed API, and versioned release imported into a second app.

Week 7

Deployment, environments and operations & Java actions and runtime extensibility

  • Configure a deployment with environment-specific constants and secrets, and document the promotion path from test to acceptance.

  • Implement one Java action that parses a JSON payload or calls a REST service, including exception handling and logging.

  • Set up structured logging, a health check, and a rollback procedure, then rehearse the rollback once.

  • Document backup/restore expectations and the scaling limits observed in the test environment.

Your checkpoint

A deployed test environment with 3 environment-specific constants, 1 custom Java action, structured logging, a health check, and a deploy/rollback runbook rehearsed once.

Week 8

Advanced domain modeling and data structure & Security and access control & Microflow and nanoflow logic, validation and error handling & Integration: REST, SOAP, OData and mapping & Performance and scalability tuning & Application architecture and reusable module design & Deployment, environments and operations & Java actions and runtime extensibility

  • Re-run every weak objective from weeks 1-7 and close each gap with a hands-on change, not a reread.

  • Complete a timed 60-question mock exam spanning all eight domains and review every wrong answer.

  • Rebuild one end-to-end slice covering domain, security, validation, integration, and deployment without notes.

  • Finalize a one-page architecture decision record for the sample app covering trade-offs and known limits.

Your checkpoint

A timed 60-question mock scored at or above 80%, a remediation list of 10 weak objectives each closed with a hands-on exercise, and a one-page architecture decision record.

Milestones

Week 2: Entity access rules produce the expected allow/deny result for all 4 roles in a 12-case test script, including the owner-based XPath constraint.

Week 4: The validation suite and REST integration pass 10 automated tests, and one rollback path is verified in the logs with no orphaned records.

Week 6: Two list pages show at least 30% fewer queries after tuning, and the reusable module imports into a second app and exposes a working API.

Week 8: Mock exam score is at least 80%, and every one of the 8 domains has at least one verified hands-on artifact in the sample app.