Mendix Certified Developer Intermediate
Exam ACTUAL EXAM 2026/2027 | Mendix
Academy Certification | Verified Q&A | Pass
Guaranteed - A+ Graded
[Domain 1: Domain Modeling & Data Management – 18 Questions]
Q1: A domain model has an Order entity and OrderLine entity. Each Order can have multiple OrderLines,
and OrderLines cannot exist without their parent Order. Which relationship type should be used?
A. One-to-many association
B. Many-to-many association
C. One-to-many composition
D. Generalization
C. One-to-many composition [CORRECT]
Correct Answer: C
Rationale: Composition (indicated by filled diamond) represents a strong "whole-part" relationship
where child objects (OrderLines) cannot exist independently of the parent (Order); deleting an Order
automatically deletes its OrderLines. An association (A) would allow orphaned OrderLines. Many-to-
many (B) is incorrect cardinality. Generalization (D) represents inheritance, not containment.
Composition enforces referential integrity at the database level.
Q2: Which XPath constraint correctly retrieves all Customer entities where the Name attribute contains
the substring "Smith"?
A. [Name == 'Smith']
B. [Name = 'Smith']
C. [contains(Name, 'Smith')]
D. [Name like '%Smith%']
C. [contains(Name, 'Smith')] [CORRECT]
Correct Answer: C
,Rationale: The contains() function is the correct XPath function for substring matching in Mendix; it
returns true if the first argument contains the second. Option A uses invalid double equals (==) syntax.
Option B tests for exact equality, not substring. Option D uses SQL-like syntax which is invalid in Mendix
XPath. XPath syntax requires single quotes for string literals and uses specific functions for string
manipulation.
Q3: An entity has a validation rule ensuring Email attribute is not empty. A microflow creates a
Customer object, sets the Email, but the commit fails with validation error. What is the most likely
cause?
A. The Email format is invalid
B. The object was committed before the Email was set
C. The validation rule is incorrectly configured
D. The Email attribute is set to the empty string ''
B. The object was committed before the Email was set [CORRECT]
Correct Answer: B
Rationale: If the object is committed before setting required attributes, validation rules trigger and fail.
The correct sequence is: Create → Set attributes → Commit. Option A would require a format validation
rule, not just "not empty." Option C is unlikely if the rule saved successfully. Option D would fail
validation, but the scenario describes setting the Email, suggesting a sequencing issue where commit
occurred before the set action.
Q4: Which attribute type should be used to store a password hash securely?
A. String
B. HashString
C. Binary
D. EncryptedString
B. HashString [CORRECT]
Correct Answer: B
Rationale: HashString is specifically designed for password storage; it automatically hashes the value
using bcrypt and never returns the original value, even to microflows. String (A) stores plaintext. Binary
(C) could store hash bytes but lacks built-in security features. EncryptedString (D) is reversible
encryption, inappropriate for passwords (should be hashed, not encrypted). HashString attributes
display as asterisks and cannot be retrieved, only compared.
,Q5: A Retrieve activity uses XPath constraint [Status = 'Open' and Total > 1000]. Which logical operator
is being used?
A. OR
B. AND
C. NOT
D. XOR
B. AND [CORRECT]
Correct Answer: B
Rationale: The 'and' keyword requires both conditions to be true: Status must equal 'Open' AND Total
must exceed 1000. OR (A) would use 'or' keyword and return records meeting either condition. NOT (C)
uses 'not()' function. XOR (D) is not a standard XPath operator in Mendix. Multiple constraints without
operators default to AND, but explicit 'and' improves readability.
Q6: Which statement about calculated attributes is correct?
A. Calculated attributes are always stored in the database
B. Calculated attributes are computed on-the-fly when accessed
C. Calculated attributes cannot use associations in their expressions
D. Calculated attributes improve performance over stored attributes
B. Calculated attributes are computed on-the-fly when accessed [CORRECT]
Correct Answer: B
Rationale: Calculated attributes (also called "non-persisted") compute their value using a microflow
each time they are accessed, rather than storing in the database. This ensures current data but can
impact performance if complex. Option A describes stored attributes. Option C is incorrect—calculated
attributes can traverse associations. Option D is incorrect—calculated attributes often reduce
performance due to repeated computation.
Q7: Which XPath retrieves all Orders created in the last 7 days?
A. [CreatedDate >= addDays([%CurrentDateTime%], -7)]
B. [CreatedDate <= addDays([%CurrentDateTime%], -7)]
C. [CreatedDate >= addDays([%CurrentDateTime%], 7)]
D. [CreatedDate = [%CurrentDateTime%] - 7]
A. [CreatedDate >= addDays([%CurrentDateTime%], -7)] [CORRECT]
Correct Answer: A
, Rationale: addDays([%CurrentDateTime%], -7) calculates the date 7 days ago; '>= retrieves records from
that date forward. Option B uses <= (less than or equal), retrieving older records. Option C adds 7 days
(future dates). Option D uses invalid syntax—XPath requires functions for date arithmetic.
[%CurrentDateTime%] is the system variable for current timestamp.
Q8: An entity uses AutoNumber for its ID. Which statement is true?
A. AutoNumber values can be manually changed
B. AutoNumber guarantees sequential values with no gaps
C. AutoNumber is generated by the database when committing
D. AutoNumber can be used for multiple attributes in the same entity
C. AutoNumber is generated by the database when committing [CORRECT]
Correct Answer: C
Rationale: AutoNumber values are assigned by the database upon commit, ensuring uniqueness across
the system. They cannot be changed (A). Gaps may occur due to rolled-back transactions (B). Only one
AutoNumber attribute is allowed per entity (D). AutoNumber is ideal for human-readable identifiers like
order numbers, separate from the internal Mendix object ID (Long).
Q9: Which relationship allows an Employee to work on multiple Projects, and each Project to have
multiple Employees?
A. One-to-one association
B. One-to-many association
C. Many-to-many association
D. Generalization
C. Many-to-many association [CORRECT]
Correct Answer: C
Rationale: Many-to-many associations model bidirectional multiplicity where both entities can relate to
multiple instances of the other. Mendix implements this via a join table. One-to-one (A) and one-to-
many (B) don't support this cardinality. Generalization (D) is inheritance, not association. Many-to-many
associations can have attributes (since Mendix 9) to store relationship metadata like assignment date or
role.
Q10: A microflow creates an Order object but does not commit it. Another microflow tries to retrieve
this Order by XPath. What happens?
Exam ACTUAL EXAM 2026/2027 | Mendix
Academy Certification | Verified Q&A | Pass
Guaranteed - A+ Graded
[Domain 1: Domain Modeling & Data Management – 18 Questions]
Q1: A domain model has an Order entity and OrderLine entity. Each Order can have multiple OrderLines,
and OrderLines cannot exist without their parent Order. Which relationship type should be used?
A. One-to-many association
B. Many-to-many association
C. One-to-many composition
D. Generalization
C. One-to-many composition [CORRECT]
Correct Answer: C
Rationale: Composition (indicated by filled diamond) represents a strong "whole-part" relationship
where child objects (OrderLines) cannot exist independently of the parent (Order); deleting an Order
automatically deletes its OrderLines. An association (A) would allow orphaned OrderLines. Many-to-
many (B) is incorrect cardinality. Generalization (D) represents inheritance, not containment.
Composition enforces referential integrity at the database level.
Q2: Which XPath constraint correctly retrieves all Customer entities where the Name attribute contains
the substring "Smith"?
A. [Name == 'Smith']
B. [Name = 'Smith']
C. [contains(Name, 'Smith')]
D. [Name like '%Smith%']
C. [contains(Name, 'Smith')] [CORRECT]
Correct Answer: C
,Rationale: The contains() function is the correct XPath function for substring matching in Mendix; it
returns true if the first argument contains the second. Option A uses invalid double equals (==) syntax.
Option B tests for exact equality, not substring. Option D uses SQL-like syntax which is invalid in Mendix
XPath. XPath syntax requires single quotes for string literals and uses specific functions for string
manipulation.
Q3: An entity has a validation rule ensuring Email attribute is not empty. A microflow creates a
Customer object, sets the Email, but the commit fails with validation error. What is the most likely
cause?
A. The Email format is invalid
B. The object was committed before the Email was set
C. The validation rule is incorrectly configured
D. The Email attribute is set to the empty string ''
B. The object was committed before the Email was set [CORRECT]
Correct Answer: B
Rationale: If the object is committed before setting required attributes, validation rules trigger and fail.
The correct sequence is: Create → Set attributes → Commit. Option A would require a format validation
rule, not just "not empty." Option C is unlikely if the rule saved successfully. Option D would fail
validation, but the scenario describes setting the Email, suggesting a sequencing issue where commit
occurred before the set action.
Q4: Which attribute type should be used to store a password hash securely?
A. String
B. HashString
C. Binary
D. EncryptedString
B. HashString [CORRECT]
Correct Answer: B
Rationale: HashString is specifically designed for password storage; it automatically hashes the value
using bcrypt and never returns the original value, even to microflows. String (A) stores plaintext. Binary
(C) could store hash bytes but lacks built-in security features. EncryptedString (D) is reversible
encryption, inappropriate for passwords (should be hashed, not encrypted). HashString attributes
display as asterisks and cannot be retrieved, only compared.
,Q5: A Retrieve activity uses XPath constraint [Status = 'Open' and Total > 1000]. Which logical operator
is being used?
A. OR
B. AND
C. NOT
D. XOR
B. AND [CORRECT]
Correct Answer: B
Rationale: The 'and' keyword requires both conditions to be true: Status must equal 'Open' AND Total
must exceed 1000. OR (A) would use 'or' keyword and return records meeting either condition. NOT (C)
uses 'not()' function. XOR (D) is not a standard XPath operator in Mendix. Multiple constraints without
operators default to AND, but explicit 'and' improves readability.
Q6: Which statement about calculated attributes is correct?
A. Calculated attributes are always stored in the database
B. Calculated attributes are computed on-the-fly when accessed
C. Calculated attributes cannot use associations in their expressions
D. Calculated attributes improve performance over stored attributes
B. Calculated attributes are computed on-the-fly when accessed [CORRECT]
Correct Answer: B
Rationale: Calculated attributes (also called "non-persisted") compute their value using a microflow
each time they are accessed, rather than storing in the database. This ensures current data but can
impact performance if complex. Option A describes stored attributes. Option C is incorrect—calculated
attributes can traverse associations. Option D is incorrect—calculated attributes often reduce
performance due to repeated computation.
Q7: Which XPath retrieves all Orders created in the last 7 days?
A. [CreatedDate >= addDays([%CurrentDateTime%], -7)]
B. [CreatedDate <= addDays([%CurrentDateTime%], -7)]
C. [CreatedDate >= addDays([%CurrentDateTime%], 7)]
D. [CreatedDate = [%CurrentDateTime%] - 7]
A. [CreatedDate >= addDays([%CurrentDateTime%], -7)] [CORRECT]
Correct Answer: A
, Rationale: addDays([%CurrentDateTime%], -7) calculates the date 7 days ago; '>= retrieves records from
that date forward. Option B uses <= (less than or equal), retrieving older records. Option C adds 7 days
(future dates). Option D uses invalid syntax—XPath requires functions for date arithmetic.
[%CurrentDateTime%] is the system variable for current timestamp.
Q8: An entity uses AutoNumber for its ID. Which statement is true?
A. AutoNumber values can be manually changed
B. AutoNumber guarantees sequential values with no gaps
C. AutoNumber is generated by the database when committing
D. AutoNumber can be used for multiple attributes in the same entity
C. AutoNumber is generated by the database when committing [CORRECT]
Correct Answer: C
Rationale: AutoNumber values are assigned by the database upon commit, ensuring uniqueness across
the system. They cannot be changed (A). Gaps may occur due to rolled-back transactions (B). Only one
AutoNumber attribute is allowed per entity (D). AutoNumber is ideal for human-readable identifiers like
order numbers, separate from the internal Mendix object ID (Long).
Q9: Which relationship allows an Employee to work on multiple Projects, and each Project to have
multiple Employees?
A. One-to-one association
B. One-to-many association
C. Many-to-many association
D. Generalization
C. Many-to-many association [CORRECT]
Correct Answer: C
Rationale: Many-to-many associations model bidirectional multiplicity where both entities can relate to
multiple instances of the other. Mendix implements this via a join table. One-to-one (A) and one-to-
many (B) don't support this cardinality. Generalization (D) is inheritance, not association. Many-to-many
associations can have attributes (since Mendix 9) to store relationship metadata like assignment date or
role.
Q10: A microflow creates an Order object but does not commit it. Another microflow tries to retrieve
this Order by XPath. What happens?
