COMPREHENSIVE CERTIFICATION EXAMINATION | 150 VERIFIED QUESTIONS & RATIONALES | NEWEST EXAM 2026/2027
MENDIX
ADVANCED DEVELOPER CERTIFICATION
MENDIX ACADEMY 2026/2027
150 QUESTIONS ADVANCED DEV RATIONALES 2026/2027 NEWEST
, EXAM COVERAGE AREAS
Domain 1: Domain Model, Associations, Security & Validation
• Entities attributes types generalization specialization
• Associations 1-1 1-many many-many owner both vs reference set one commit
• Security module roles entity access XPath constraints
• Validation uniqueness
Domain 2: Microflows Nanoflows Logic & Error Handling
• Microflow server DB access vs nanoflow client offline UI
• Activities retrieve create change commit delete decision merge loops
• Error handling rollback custom
• Best practices
Domain 3: Pages, Atlas UI, Widgets & Navigation
• Pages layouts Atlas UI building blocks
• Data widgets list view data grid template
• Visibility conditions
• Navigation
Domain 4: Integration REST SOAP OData
• REST consume import JSON call GET POST publish expose microflow export JSON
• SOAP WSDL
• OData publish
• External entities
Domain 5: Performance Deployment Advanced
• Performance retrieve via association memory fast vs from database query slower
• Deployment Mendix Cloud DTAP
• Java actions
• Best practices advanced
Mendix Advanced Developer Certification 2026/2027 150 Questions Page 2
, QUESTION 1: Mendix association owner both vs reference set?
A) Owner both objects need commit to store association, reference set only owner side needs commit,
default reference, many-many needs both
B) No difference
C) Only owner
D) Only reference
CORRECT ANSWER: A) Owner both objects need commit to store association,
reference set only owner side needs commit, default reference, many-many needs both
RATIONALE: Associations: default reference owner stored in child reference one side commit enough.
Owner both need commit to persist association stored separately. Many-many needs both. Best practice
use reference set for performance, owner when needed. Delete behavior cascade.
QUESTION 2: Microflow vs nanoflow when to use?
A) Microflow server logic database access commit retrieve cannot offline, nanoflow client browser
offline UI logic responsive no direct DB
B) Same
C) Only microflow
D) Only nanoflow
CORRECT ANSWER: A) Microflow server logic database access commit retrieve
cannot offline, nanoflow client browser offline UI logic responsive no direct DB
RATIONALE: Microflow server-side logic access database commit retrieve cannot run offline. Nanoflow
client-side runs in browser device offline capable UI logic responsive no direct commit needs microflow for
DB. Use microflow for DB, nanoflow for UI offline.
QUESTION 3: Entity access vs XPath constraint security?
A) Entity access module role level defines create read write delete XPath row level [Dept='Sales']
enforced all, XPath constraint retrieve activity additional filter specific action
B) Same
C) Only entity access
D) Only XPath
CORRECT ANSWER: A) Entity access module role level defines create read write delete
XPath row level [Dept='Sales'] enforced all, XPath constraint retrieve activity additional
filter specific action
RATIONALE: Security: module roles user roles entity access defines CRUD rights XPath constraints row
level security enforced everywhere e.g., [Department='Sales']. XPath constraint in retrieve activity additional
filter specific action only. Always define entity access, use XPath for row security.
QUESTION 4: REST consume vs publish?
A) Consume import JSON structure import mapping call REST GET POST PUT DELETE, publish
expose microflow as REST with export mapping JSON authentication Basic OAuth
B) No difference
C) Only consume
D) Only publish
Mendix Advanced Developer Certification 2026/2027 150 Questions Page 3
, CORRECT ANSWER: A) Consume import JSON structure import mapping call REST
GET POST PUT DELETE, publish expose microflow as REST with export mapping
JSON authentication Basic OAuth
RATIONALE: Integration: Consume REST import JSON structure map to entities import mapping call REST
activity GET POST. Publish REST create published REST service expose microflow with export mapping
JSON. Authentication Basic OAuth. Error handling HTTP status.
QUESTION 5: Retrieve via association vs database performance best practice?
A) Via association uses loaded object memory fast no query, from database executes SQL slower use
association when parent loaded use database with XPath when filter needed
B) Same
C) Only database
D) No difference
CORRECT ANSWER: A) Via association uses loaded object memory fast no query, from
database executes SQL slower use association when parent loaded use database with
XPath when filter needed
RATIONALE: Performance: retrieve via association uses object already in memory fast no DB query, from
database executes SQL query slower. Best practice use association when parent already retrieved, use
database with XPath when need filter. Avoid retrieve all, use indexes, limit.
QUESTION 6: Mendix association owner both vs reference set?
A) Owner both objects need commit to store association, reference set only owner side needs commit,
default reference, many-many needs both
B) No difference
C) Only owner
D) Only reference
CORRECT ANSWER: A) Owner both objects need commit to store association,
reference set only owner side needs commit, default reference, many-many needs both
RATIONALE: Associations: default reference owner stored in child reference one side commit enough.
Owner both need commit to persist association stored separately. Many-many needs both. Best practice
use reference set for performance, owner when needed. Delete behavior cascade.
QUESTION 7: Microflow vs nanoflow when to use?
A) Microflow server logic database access commit retrieve cannot offline, nanoflow client browser
offline UI logic responsive no direct DB
B) Same
C) Only microflow
D) Only nanoflow
CORRECT ANSWER: A) Microflow server logic database access commit retrieve
cannot offline, nanoflow client browser offline UI logic responsive no direct DB
RATIONALE: Microflow server-side logic access database commit retrieve cannot run offline. Nanoflow
client-side runs in browser device offline capable UI logic responsive no direct commit needs microflow for
DB. Use microflow for DB, nanoflow for UI offline.
Mendix Advanced Developer Certification 2026/2027 150 Questions Page 4
MENDIX
ADVANCED DEVELOPER CERTIFICATION
MENDIX ACADEMY 2026/2027
150 QUESTIONS ADVANCED DEV RATIONALES 2026/2027 NEWEST
, EXAM COVERAGE AREAS
Domain 1: Domain Model, Associations, Security & Validation
• Entities attributes types generalization specialization
• Associations 1-1 1-many many-many owner both vs reference set one commit
• Security module roles entity access XPath constraints
• Validation uniqueness
Domain 2: Microflows Nanoflows Logic & Error Handling
• Microflow server DB access vs nanoflow client offline UI
• Activities retrieve create change commit delete decision merge loops
• Error handling rollback custom
• Best practices
Domain 3: Pages, Atlas UI, Widgets & Navigation
• Pages layouts Atlas UI building blocks
• Data widgets list view data grid template
• Visibility conditions
• Navigation
Domain 4: Integration REST SOAP OData
• REST consume import JSON call GET POST publish expose microflow export JSON
• SOAP WSDL
• OData publish
• External entities
Domain 5: Performance Deployment Advanced
• Performance retrieve via association memory fast vs from database query slower
• Deployment Mendix Cloud DTAP
• Java actions
• Best practices advanced
Mendix Advanced Developer Certification 2026/2027 150 Questions Page 2
, QUESTION 1: Mendix association owner both vs reference set?
A) Owner both objects need commit to store association, reference set only owner side needs commit,
default reference, many-many needs both
B) No difference
C) Only owner
D) Only reference
CORRECT ANSWER: A) Owner both objects need commit to store association,
reference set only owner side needs commit, default reference, many-many needs both
RATIONALE: Associations: default reference owner stored in child reference one side commit enough.
Owner both need commit to persist association stored separately. Many-many needs both. Best practice
use reference set for performance, owner when needed. Delete behavior cascade.
QUESTION 2: Microflow vs nanoflow when to use?
A) Microflow server logic database access commit retrieve cannot offline, nanoflow client browser
offline UI logic responsive no direct DB
B) Same
C) Only microflow
D) Only nanoflow
CORRECT ANSWER: A) Microflow server logic database access commit retrieve
cannot offline, nanoflow client browser offline UI logic responsive no direct DB
RATIONALE: Microflow server-side logic access database commit retrieve cannot run offline. Nanoflow
client-side runs in browser device offline capable UI logic responsive no direct commit needs microflow for
DB. Use microflow for DB, nanoflow for UI offline.
QUESTION 3: Entity access vs XPath constraint security?
A) Entity access module role level defines create read write delete XPath row level [Dept='Sales']
enforced all, XPath constraint retrieve activity additional filter specific action
B) Same
C) Only entity access
D) Only XPath
CORRECT ANSWER: A) Entity access module role level defines create read write delete
XPath row level [Dept='Sales'] enforced all, XPath constraint retrieve activity additional
filter specific action
RATIONALE: Security: module roles user roles entity access defines CRUD rights XPath constraints row
level security enforced everywhere e.g., [Department='Sales']. XPath constraint in retrieve activity additional
filter specific action only. Always define entity access, use XPath for row security.
QUESTION 4: REST consume vs publish?
A) Consume import JSON structure import mapping call REST GET POST PUT DELETE, publish
expose microflow as REST with export mapping JSON authentication Basic OAuth
B) No difference
C) Only consume
D) Only publish
Mendix Advanced Developer Certification 2026/2027 150 Questions Page 3
, CORRECT ANSWER: A) Consume import JSON structure import mapping call REST
GET POST PUT DELETE, publish expose microflow as REST with export mapping
JSON authentication Basic OAuth
RATIONALE: Integration: Consume REST import JSON structure map to entities import mapping call REST
activity GET POST. Publish REST create published REST service expose microflow with export mapping
JSON. Authentication Basic OAuth. Error handling HTTP status.
QUESTION 5: Retrieve via association vs database performance best practice?
A) Via association uses loaded object memory fast no query, from database executes SQL slower use
association when parent loaded use database with XPath when filter needed
B) Same
C) Only database
D) No difference
CORRECT ANSWER: A) Via association uses loaded object memory fast no query, from
database executes SQL slower use association when parent loaded use database with
XPath when filter needed
RATIONALE: Performance: retrieve via association uses object already in memory fast no DB query, from
database executes SQL query slower. Best practice use association when parent already retrieved, use
database with XPath when need filter. Avoid retrieve all, use indexes, limit.
QUESTION 6: Mendix association owner both vs reference set?
A) Owner both objects need commit to store association, reference set only owner side needs commit,
default reference, many-many needs both
B) No difference
C) Only owner
D) Only reference
CORRECT ANSWER: A) Owner both objects need commit to store association,
reference set only owner side needs commit, default reference, many-many needs both
RATIONALE: Associations: default reference owner stored in child reference one side commit enough.
Owner both need commit to persist association stored separately. Many-many needs both. Best practice
use reference set for performance, owner when needed. Delete behavior cascade.
QUESTION 7: Microflow vs nanoflow when to use?
A) Microflow server logic database access commit retrieve cannot offline, nanoflow client browser
offline UI logic responsive no direct DB
B) Same
C) Only microflow
D) Only nanoflow
CORRECT ANSWER: A) Microflow server logic database access commit retrieve
cannot offline, nanoflow client browser offline UI logic responsive no direct DB
RATIONALE: Microflow server-side logic access database commit retrieve cannot run offline. Nanoflow
client-side runs in browser device offline capable UI logic responsive no direct commit needs microflow for
DB. Use microflow for DB, nanoflow for UI offline.
Mendix Advanced Developer Certification 2026/2027 150 Questions Page 4
