Mendix Advanced Exam Revision COMPLETE EXAM
LATEST VERSION 2026-2027 QUESTIONS AND ANSWERS
Why does Mendix require the renaming of EmailAddress in the Player entity when generalizing from the Person
entity? - answer>>Because the attribute EmailAddress already exists in the parent entity Person, Mendix
prevents duplication by requiring unique attribute names across the inheritance chain.
What are two benefits of using a single list view with templates for each specialization? - answer>>1. You can
render all specialization objects (e.g., Players and Staff) in the same list.
2. Each specialization can have a custom UI template based on its unique attributes.
Explain how Mendix handles storage of attributes for a specialized object like Train that inherits from Vehicle? -
answer>>Shared attributes are stored in the parent Vehicle table, while specialization-specific attributes (e.g.,
Train.Type) are stored in the Train table. Both tables use the same object ID.
What is the recommended way to configure entity access for generalized entities like Person and its
specializations? - answer>>- Deny access to the general Person entity.
- Grant access only to the relevant specialization (e.g., Player or Staff) based on the role.
Suppose Adrian wants to send email notifications to both Staff and Players. How does using a generalized Person
entity simplify this logic? - answer>>Instead of writing two separate microflows, Adrian can write one that
retrieves a list of Person objects, since both Player and Staff inherit from Person, and the EmailAddress attribute
exists in the parent.
While reviewing the domain model, a developer sees two separate entities: Customer and Employee, both with
common fields like Name and Email. They are not used in shared processes. Should generalization be applied
here? Why or Why not? - answer>>No, If the entities share only similar attributes but not behavior or process
logic, generalization adds unnecessary complexity and should be avoided.
In the Team_NewEdit page, why is it useful to create a third tab specifically for Staff? - answer>>It allows for
displaying Staff-specific attributes (e.g., Salary) which aren't part of the Player or general Person entity, while
keeping the UI clean and role-specific.
,Describe the role of object casting in a microflow that edits attributes specific to the Car specialization. -
answer>>Object casting allows the developer to convert a Vehicle object into a Car object in order to access
Carspecific attributes like NumberOfDoors.
A developer forgot to add a specialization template in the list view. What will Mendix display for objects of that
specialization? - answer>>Nothing, If there's no specialization template, the object won't be shown in the list
view, even if it exists
Which of the following is true about a 1 - 1 association in Mendix? - answer>>It allows two objects to be
connected, each referencing the other
In what scenario is inheritance a better design choice than using a 1-1 association? - answer>>When multiple
specializations share logic or need polymorphism
Which of the following is a disadvantage of using inheritance in Mendix? - answer>>Debugging across generalized
hierarchies is harder
What distinguishes 1 - 1 associations from inheritance in terms of data modeling flexibility? - answer>>1-1
associations allow optional linking between two independent entities.
If an entity Person has optional sensitive details stored in a ConfidentialDetails entity, what pattern should you
use? - answer>>1-1 Association
Inheritance allows the same object ID to be used across parent and specialized entities - answer>>True
1-1 relationship force you to use object casting in order to access data? - answer>>False - Object casting is used
with inheritance, not associations
When using 1-1 association, the data is stored in the same table as the parent entity. - answer>>False - They are
stored in separate tables.
Inheritance enforces a parent-child relationship with shared behavior and logic? - answer>>True
1 - 1 associations should be avoided when the entities are used in shared workflows? - answer>>True -
, Inheritance is more suitable when shared behavior or workflows are needed
List one advantage and one disadvantage of using a 1 - 1 relationship instead of inheritance in Mendix -
answer>>Advantage: Better separation of concerns; useful for optional or loosely related data.
Disadvantage: Less support for shared logic and polymorphism; no automatic attribute inheritance
Why might developers choose inheritance over a 1-1 association when modeling users like Admins and
Customers? - answer>>Because Admins and Customers might share common attributes (e.g., email, password)
and behaviors (e.g., login logic), making inheritance and polymorphism beneficial.
How does Mendix store data differently between inheritance and 1-1 association? - answer>>- Inheritance:
Parent and specialization data are stored in separate tables with the same object ID.
- 1-1 Association: Data is stored i two independent tables, linked via an association reference
Can you use object type decision with 1-1 associated entities? Why or why not - answer>>No, Object type
decision only works with inheritance, as it relies on polymorphic object types, not associations.
Give an example use case where using a 1-1 relationship is more appropriate than inheritance - answer>>Storing
user profiles images in a UserImage entity that's only needed if the user uploads an image. A 1-1 optional
association keeps the main user object clean.
Inheritance is used to - answer>>Inherit the structure and behavior of an entity, so that all specializations can be
used individually within the same process
What is the result of generalizing the Player entity by the Person entity? - answer>>Two tables, one per entity
What will happen to the ID's after generalizing the Player and Staff entities by the Person entity? - answer>>The
ID's of Player and Staff will keep their own set and sequence and will equal the ID in the Person table.
A 1-1 association is a HAS and inheritance is an IS type of relation. - answer>>True
Which of the following entities can be used to story binary file content in Mendix? - answer>>-
System.FileDocument
- System.Image (System.Image is a specialization of FileDocument)
LATEST VERSION 2026-2027 QUESTIONS AND ANSWERS
Why does Mendix require the renaming of EmailAddress in the Player entity when generalizing from the Person
entity? - answer>>Because the attribute EmailAddress already exists in the parent entity Person, Mendix
prevents duplication by requiring unique attribute names across the inheritance chain.
What are two benefits of using a single list view with templates for each specialization? - answer>>1. You can
render all specialization objects (e.g., Players and Staff) in the same list.
2. Each specialization can have a custom UI template based on its unique attributes.
Explain how Mendix handles storage of attributes for a specialized object like Train that inherits from Vehicle? -
answer>>Shared attributes are stored in the parent Vehicle table, while specialization-specific attributes (e.g.,
Train.Type) are stored in the Train table. Both tables use the same object ID.
What is the recommended way to configure entity access for generalized entities like Person and its
specializations? - answer>>- Deny access to the general Person entity.
- Grant access only to the relevant specialization (e.g., Player or Staff) based on the role.
Suppose Adrian wants to send email notifications to both Staff and Players. How does using a generalized Person
entity simplify this logic? - answer>>Instead of writing two separate microflows, Adrian can write one that
retrieves a list of Person objects, since both Player and Staff inherit from Person, and the EmailAddress attribute
exists in the parent.
While reviewing the domain model, a developer sees two separate entities: Customer and Employee, both with
common fields like Name and Email. They are not used in shared processes. Should generalization be applied
here? Why or Why not? - answer>>No, If the entities share only similar attributes but not behavior or process
logic, generalization adds unnecessary complexity and should be avoided.
In the Team_NewEdit page, why is it useful to create a third tab specifically for Staff? - answer>>It allows for
displaying Staff-specific attributes (e.g., Salary) which aren't part of the Player or general Person entity, while
keeping the UI clean and role-specific.
,Describe the role of object casting in a microflow that edits attributes specific to the Car specialization. -
answer>>Object casting allows the developer to convert a Vehicle object into a Car object in order to access
Carspecific attributes like NumberOfDoors.
A developer forgot to add a specialization template in the list view. What will Mendix display for objects of that
specialization? - answer>>Nothing, If there's no specialization template, the object won't be shown in the list
view, even if it exists
Which of the following is true about a 1 - 1 association in Mendix? - answer>>It allows two objects to be
connected, each referencing the other
In what scenario is inheritance a better design choice than using a 1-1 association? - answer>>When multiple
specializations share logic or need polymorphism
Which of the following is a disadvantage of using inheritance in Mendix? - answer>>Debugging across generalized
hierarchies is harder
What distinguishes 1 - 1 associations from inheritance in terms of data modeling flexibility? - answer>>1-1
associations allow optional linking between two independent entities.
If an entity Person has optional sensitive details stored in a ConfidentialDetails entity, what pattern should you
use? - answer>>1-1 Association
Inheritance allows the same object ID to be used across parent and specialized entities - answer>>True
1-1 relationship force you to use object casting in order to access data? - answer>>False - Object casting is used
with inheritance, not associations
When using 1-1 association, the data is stored in the same table as the parent entity. - answer>>False - They are
stored in separate tables.
Inheritance enforces a parent-child relationship with shared behavior and logic? - answer>>True
1 - 1 associations should be avoided when the entities are used in shared workflows? - answer>>True -
, Inheritance is more suitable when shared behavior or workflows are needed
List one advantage and one disadvantage of using a 1 - 1 relationship instead of inheritance in Mendix -
answer>>Advantage: Better separation of concerns; useful for optional or loosely related data.
Disadvantage: Less support for shared logic and polymorphism; no automatic attribute inheritance
Why might developers choose inheritance over a 1-1 association when modeling users like Admins and
Customers? - answer>>Because Admins and Customers might share common attributes (e.g., email, password)
and behaviors (e.g., login logic), making inheritance and polymorphism beneficial.
How does Mendix store data differently between inheritance and 1-1 association? - answer>>- Inheritance:
Parent and specialization data are stored in separate tables with the same object ID.
- 1-1 Association: Data is stored i two independent tables, linked via an association reference
Can you use object type decision with 1-1 associated entities? Why or why not - answer>>No, Object type
decision only works with inheritance, as it relies on polymorphic object types, not associations.
Give an example use case where using a 1-1 relationship is more appropriate than inheritance - answer>>Storing
user profiles images in a UserImage entity that's only needed if the user uploads an image. A 1-1 optional
association keeps the main user object clean.
Inheritance is used to - answer>>Inherit the structure and behavior of an entity, so that all specializations can be
used individually within the same process
What is the result of generalizing the Player entity by the Person entity? - answer>>Two tables, one per entity
What will happen to the ID's after generalizing the Player and Staff entities by the Person entity? - answer>>The
ID's of Player and Staff will keep their own set and sequence and will equal the ID in the Person table.
A 1-1 association is a HAS and inheritance is an IS type of relation. - answer>>True
Which of the following entities can be used to story binary file content in Mendix? - answer>>-
System.FileDocument
- System.Image (System.Image is a specialization of FileDocument)
