1
MENDIX INTERMEDIATE CERTIFICATION EXAM
2026/2027 | Actual Questions Verified | Grade A |
Complete Solutions | Pass Guaranteed - A+ Graded
Section 1: Domain Modeling & Entity Relationships (Q1-15)
Q1. In Mendix, when you configure a many-to-many association between two
entities, what structure is created in the underlying database?
A. A foreign key column is added to the child entity table
B. A separate junction table is created to store the associations [CORRECT]
C. A primary key composite is formed across both entity tables
D. A calculated attribute is generated to maintain the relationship
Rationale: Many-to-many associations in Mendix cannot be represented by a single
foreign key column; instead, the platform automatically generates a junction (link)
table containing the identifiers of both associated entities. One-to-many associations
use a foreign key column in the child table.
Correct Answer: B
Q2. An entity "Employee" is configured to generalize from "Person". Which of the
following is true regarding this inheritance relationship?
A. The Employee entity can only inherit attributes, not associations
B. The Employee entity contains all attributes and associations defined on the Person
entity [CORRECT]
C. The Employee entity must be non-persistable if Person is persistable
D. Generalization prevents the Employee entity from having its own attributes
Rationale: In Mendix, generalization (inheritance) causes the specialized entity to
inherit all attributes, associations, and event microflows from the generalized entity.
The specialized entity can also define its own additional attributes and associations.
,2
Persistability is inherited from the parent.
Correct Answer: B
Q3. A calculated attribute on a Mendix entity is defined with a microflow. When is
this microflow executed?
A. Only when the object is explicitly committed to the database
B. Every time the attribute value is retrieved or displayed [CORRECT]
C. Once per user session upon first access
D. Only during application startup to cache the value
Rationale: Calculated attributes are non-persistable and computed on-the-fly. The
associated microflow executes whenever the attribute is accessed (e.g., displayed on
a page, used in a microflow, or retrieved via XPath). This ensures the value is always
current but can impact performance if the calculation is complex.
Correct Answer: B
Q4. A business requirement states that one Department can have many Employees,
and each Employee belongs to exactly one Department. Which association
configuration is correct?
A. One-to-one association from Department to Employee
B. One-to-many association from Department to Employee [CORRECT]
C. Many-to-many association between Department and Employee
D. Self-referencing association on the Employee entity
Rationale: A one-to-many association from Department (one side) to Employee
(many side) correctly models this relationship. The multiplicity is set to 1 on the
Department side and * (many) on the Employee side. One-to-one would restrict each
department to a single employee, while many-to-many would allow employees to
belong to multiple departments.
Correct Answer: B
,3
Q5. You configure a validation rule on the OrderNumber attribute of the Order entity
and set it to "Required". When does this validation rule trigger?
A. When the user opens the create Order page
B. When the object is committed to the database [CORRECT]
C. When the microflow begins execution
D. Only when the attribute is first entered, not on updates
Rationale: Entity validation rules in Mendix are evaluated when an object is
committed (either explicitly via a Commit activity or implicitly via a "Save" button that
commits). The validation prevents the database transaction from completing if the
attribute is empty. Page-level validation can occur earlier, but entity-level "Required"
rules trigger at commit.
Correct Answer: B
Q6. A non-persistable entity in Mendix is best described as:
A. An entity that stores data in the database but encrypts it automatically
B. An entity that holds temporary data only during the user session [CORRECT]
C. An entity that cannot be used in microflows or on pages
D. An entity that automatically synchronizes with external REST APIs
Rationale: Non-persistable entities exist only in memory and are not stored in the
underlying database. They are ideal for temporary data, search criteria, wizard steps,
or intermediate calculation results. They can be used on pages and in microflows but
are lost when the session ends or when no longer referenced.
Correct Answer: B
Q7. In the domain model, an association between Customer and Address is
configured with multiplicity "1" on both sides. What does this represent?
, 4
A. One Customer can have many Addresses
B. One Customer can have exactly one Address [CORRECT]
C. Many Customers can share one Address
D. The association is unidirectional from Address to Customer only
Rationale: When both sides of an association have multiplicity 1, it establishes a
one-to-one relationship. Each Customer is linked to exactly one Address, and each
Address is linked to exactly one Customer. This differs from one-to-many (1 on one
side, * on the other) and many-to-many (* on both sides).
Correct Answer: B
Q8. When using generalization in Mendix, if you delete the generalized (parent)
entity from the domain model, what happens to the specialized (child) entities?
A. The specialized entities become standalone root entities
B. The specialized entities are also deleted from the domain model [CORRECT]
C. The specialized entities automatically generalize from System.User
D. The specialized entities lose all their attributes but remain
Rationale: Deleting a generalized entity removes the entire inheritance hierarchy,
including all specialized entities that depend on it. Mendix warns about this
dependency before deletion. The specialized entities cannot exist without their
parent in the inheritance chain.
Correct Answer: B
Q9. You need to ensure that every Product in your system has a unique SKU value.
Which domain model configuration accomplishes this?
A. Set the SKU attribute to "Required"
B. Add a "Unique" validation rule on the SKU attribute [CORRECT]
C. Create a microflow that checks for duplicates manually
D. Set the SKU attribute type to Autonumber
MENDIX INTERMEDIATE CERTIFICATION EXAM
2026/2027 | Actual Questions Verified | Grade A |
Complete Solutions | Pass Guaranteed - A+ Graded
Section 1: Domain Modeling & Entity Relationships (Q1-15)
Q1. In Mendix, when you configure a many-to-many association between two
entities, what structure is created in the underlying database?
A. A foreign key column is added to the child entity table
B. A separate junction table is created to store the associations [CORRECT]
C. A primary key composite is formed across both entity tables
D. A calculated attribute is generated to maintain the relationship
Rationale: Many-to-many associations in Mendix cannot be represented by a single
foreign key column; instead, the platform automatically generates a junction (link)
table containing the identifiers of both associated entities. One-to-many associations
use a foreign key column in the child table.
Correct Answer: B
Q2. An entity "Employee" is configured to generalize from "Person". Which of the
following is true regarding this inheritance relationship?
A. The Employee entity can only inherit attributes, not associations
B. The Employee entity contains all attributes and associations defined on the Person
entity [CORRECT]
C. The Employee entity must be non-persistable if Person is persistable
D. Generalization prevents the Employee entity from having its own attributes
Rationale: In Mendix, generalization (inheritance) causes the specialized entity to
inherit all attributes, associations, and event microflows from the generalized entity.
The specialized entity can also define its own additional attributes and associations.
,2
Persistability is inherited from the parent.
Correct Answer: B
Q3. A calculated attribute on a Mendix entity is defined with a microflow. When is
this microflow executed?
A. Only when the object is explicitly committed to the database
B. Every time the attribute value is retrieved or displayed [CORRECT]
C. Once per user session upon first access
D. Only during application startup to cache the value
Rationale: Calculated attributes are non-persistable and computed on-the-fly. The
associated microflow executes whenever the attribute is accessed (e.g., displayed on
a page, used in a microflow, or retrieved via XPath). This ensures the value is always
current but can impact performance if the calculation is complex.
Correct Answer: B
Q4. A business requirement states that one Department can have many Employees,
and each Employee belongs to exactly one Department. Which association
configuration is correct?
A. One-to-one association from Department to Employee
B. One-to-many association from Department to Employee [CORRECT]
C. Many-to-many association between Department and Employee
D. Self-referencing association on the Employee entity
Rationale: A one-to-many association from Department (one side) to Employee
(many side) correctly models this relationship. The multiplicity is set to 1 on the
Department side and * (many) on the Employee side. One-to-one would restrict each
department to a single employee, while many-to-many would allow employees to
belong to multiple departments.
Correct Answer: B
,3
Q5. You configure a validation rule on the OrderNumber attribute of the Order entity
and set it to "Required". When does this validation rule trigger?
A. When the user opens the create Order page
B. When the object is committed to the database [CORRECT]
C. When the microflow begins execution
D. Only when the attribute is first entered, not on updates
Rationale: Entity validation rules in Mendix are evaluated when an object is
committed (either explicitly via a Commit activity or implicitly via a "Save" button that
commits). The validation prevents the database transaction from completing if the
attribute is empty. Page-level validation can occur earlier, but entity-level "Required"
rules trigger at commit.
Correct Answer: B
Q6. A non-persistable entity in Mendix is best described as:
A. An entity that stores data in the database but encrypts it automatically
B. An entity that holds temporary data only during the user session [CORRECT]
C. An entity that cannot be used in microflows or on pages
D. An entity that automatically synchronizes with external REST APIs
Rationale: Non-persistable entities exist only in memory and are not stored in the
underlying database. They are ideal for temporary data, search criteria, wizard steps,
or intermediate calculation results. They can be used on pages and in microflows but
are lost when the session ends or when no longer referenced.
Correct Answer: B
Q7. In the domain model, an association between Customer and Address is
configured with multiplicity "1" on both sides. What does this represent?
, 4
A. One Customer can have many Addresses
B. One Customer can have exactly one Address [CORRECT]
C. Many Customers can share one Address
D. The association is unidirectional from Address to Customer only
Rationale: When both sides of an association have multiplicity 1, it establishes a
one-to-one relationship. Each Customer is linked to exactly one Address, and each
Address is linked to exactly one Customer. This differs from one-to-many (1 on one
side, * on the other) and many-to-many (* on both sides).
Correct Answer: B
Q8. When using generalization in Mendix, if you delete the generalized (parent)
entity from the domain model, what happens to the specialized (child) entities?
A. The specialized entities become standalone root entities
B. The specialized entities are also deleted from the domain model [CORRECT]
C. The specialized entities automatically generalize from System.User
D. The specialized entities lose all their attributes but remain
Rationale: Deleting a generalized entity removes the entire inheritance hierarchy,
including all specialized entities that depend on it. Mendix warns about this
dependency before deletion. The specialized entities cannot exist without their
parent in the inheritance chain.
Correct Answer: B
Q9. You need to ensure that every Product in your system has a unique SKU value.
Which domain model configuration accomplishes this?
A. Set the SKU attribute to "Required"
B. Add a "Unique" validation rule on the SKU attribute [CORRECT]
C. Create a microflow that checks for duplicates manually
D. Set the SKU attribute type to Autonumber
