MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
What happens in the Mendix database structure when a specialized entity is generalized from another
entity? - (answer) The specialized entity and parent entity use the same ID across separate tables
In Mendix, which of the following is not inherited from the generalized entity by default? - (answer)
Event handler microflows
When should you avoid using inheritance (generalization) in Mendix? - (answer) When entities only
share similar attributes
What is the purpose of the SubMetaObjectName column in the parent entity's database table? -
(answer) To reference which specialization the record belongs to
What will happen if an object type decision is made on an empty object in Mendix? - (answer) The
empty sequence flow will be followed
In Mendix a specialized entity inherits both attributes and behaviors from its generalization? - (answer)
true
A generalized entity in Mendix cannot be displayed in a list view along with its specializations? -
(answer) False - You can use list views with templates for each specializations.
The object type decision can only have two outcomes: true or false - (answer) False - It has outcomes
for each specialization and an "empty" path
You can cast a general object into a specialization in order to access its specialized attributes. - (answer)
True
It's best practice to avoid logging if the object type decision input is empty, as it doesn't affect logic. -
(answer) False - It's good practice to log it, as it may indicate incorrect logic.
,MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
What is the main reason for using inheritance (generalization) in Mendix domain models? - (answer)
To model real-world hierarchies where multiple entities share common attributes and logic, enabling
code reuse, easier maintenance, and unified behavior
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.
,MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
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 Car-specific 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
, MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
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
DETAILED ANSWERS
What happens in the Mendix database structure when a specialized entity is generalized from another
entity? - (answer) The specialized entity and parent entity use the same ID across separate tables
In Mendix, which of the following is not inherited from the generalized entity by default? - (answer)
Event handler microflows
When should you avoid using inheritance (generalization) in Mendix? - (answer) When entities only
share similar attributes
What is the purpose of the SubMetaObjectName column in the parent entity's database table? -
(answer) To reference which specialization the record belongs to
What will happen if an object type decision is made on an empty object in Mendix? - (answer) The
empty sequence flow will be followed
In Mendix a specialized entity inherits both attributes and behaviors from its generalization? - (answer)
true
A generalized entity in Mendix cannot be displayed in a list view along with its specializations? -
(answer) False - You can use list views with templates for each specializations.
The object type decision can only have two outcomes: true or false - (answer) False - It has outcomes
for each specialization and an "empty" path
You can cast a general object into a specialization in order to access its specialized attributes. - (answer)
True
It's best practice to avoid logging if the object type decision input is empty, as it doesn't affect logic. -
(answer) False - It's good practice to log it, as it may indicate incorrect logic.
,MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
What is the main reason for using inheritance (generalization) in Mendix domain models? - (answer)
To model real-world hierarchies where multiple entities share common attributes and logic, enabling
code reuse, easier maintenance, and unified behavior
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.
,MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
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 Car-specific 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
, MENDIX ADVANCED QUESTIONS EXAM 2023-2024 ACTUAL EXAM 130 QUESTIONS AND CORRECT
DETAILED ANSWERS
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
