ANSWERS | 2026 UPDATED STUDY GUIDE |
VERIFIED SOLUTIONS WITH DETAILED
EXPLANATIONS & HIGH-PASS PREPARATION
MATERIAL
MENDIX ADVANCED EXAM STUDY GUIDE – 2026 UPDATED QUESTIONS &
ANSWERS
OVERVIEW: This comprehensive study guide features 200 verified exam questions
covering all key Advanced Developer topics. Each question is presented vertically
with the correct answer highlighted in bold and a detailed EXPERT RATIONALE
provided immediately below.
Use this material to test your knowledge, identify weak areas, and build the
confidence needed for a high-pass score on the certification exam.
QUESTION 1
What are the three primary components of the Atlas UI framework in
Mendix?
A. Widgets, Themes, and Icons
B. Page Templates, Navigation Layouts, and Building Blocks
C. Data Grids, Snippets, and Charts
D. CSS, JavaScript, and HTML
► B. Page Templates, Navigation Layouts, and Building Blocks
EXPERT RATIONALE: Atlas UI is Mendix's theming framework that provides a
structured way to build consistent user interfaces. The three core components are
Page Templates (pre-built page structures), Navigation Layouts (layout structures
for your app), and Building Blocks (smaller reusable UI elements like cards, alerts,
and headers). These components help developers quickly assemble professional-
looking applications while maintaining design consistency .
,QUESTION 2
Which statement correctly describes the relationship between a 1-1
association and inheritance in domain modeling?
A. A 1-1 association and inheritance are both an IS type of relation.
B. A 1-1 association is an IS and inheritance is a HAS type of relation.
C. A 1-1 association is a HAS and inheritance is an IS type of relation.
D. A 1-1 association and inheritance are both a HAS type of relation.
► C. A 1-1 association is a HAS and inheritance is an IS type of relation.
EXPERT RATIONALE: Inheritance represents an "IS-A" relationship (e.g., a Car IS-A
Vehicle), where the child specializes the parent. A 1-1 association represents a
"HAS-A" relationship (e.g., a Person HAS-A Passport), where the entity contains a
reference to another separate entity. Understanding this distinction is crucial for
proper domain model design .
QUESTION 3
What do you need to take into account when using Sass in your Mendix
project?
A. You need to enable it in the App Settings.
B. You need to import it as a Java library.
C. You need a compilation tool.
D. You need to write all styles in CSS first.
► C. You need a compilation tool.
EXPERT RATIONALE: Sass (Syntactically Awesome Style Sheets) is a preprocessor
scripting language that extends CSS. Mendix does not interpret Sass files directly in
the browser; therefore, a compilation tool is required to compile the .scss or .sass
files into standard .css files that can be understood by web browsers. Mendix
Studio Pro typically handles this automatically when the app is deployed .
QUESTION 4
What is the primary purpose of using inheritance in a Mendix domain model?
,A. To create multiple tables in the database for the same entity.
B. To inherit the structure and behavior of an entity so that all specializations can
be used individually within the same process.
C. To prevent data duplication across different entities.
D. To enforce security at the attribute level.
► B. To inherit the structure and behavior of an entity so that all
specializations can be used individually within the same process.
EXPERT RATIONALE: Inheritance allows a specialized entity (child) to acquire
attributes, associations, event handlers, and validation rules from a generalized
entity (parent). This promotes reusability and consistency because you can define
common properties once in the parent and have all children reuse them. It also
enables polymorphism, allowing you to treat different specializations as the
generalized type in processes like microflows and pages .
QUESTION 5
What is the result of generalizing the Player entity by the Person entity?
A. One table for Person only.
B. Two tables, one per entity.
C. One table for Player only.
D. A new table that merges both entities.
► B. Two tables, one per entity.
EXPERT RATIONALE: When you implement inheritance in Mendix, the database
structure creates separate tables for each entity in the hierarchy. The generalized
entity (Person) table stores the common attributes, and the specialized entity
(Player) table stores its specific attributes with a foreign key linking back to the
Person table. This is known as the "table-per-class" strategy, which preserves the
integrity of each entity while supporting object-oriented inheritance .
, QUESTION 6
What happens to the IDs after generalizing the Player and Staff entities by the
Person entity?
A. Player and Staff IDs are replaced by the Person ID.
B. The IDs of Player and Staff will keep their own set and sequence and will equal
the ID in the Person table.
C. Player IDs and Staff IDs are merged into one sequence.
D. IDs are automatically generated by the database server only.
► B. The IDs of Player and Staff will keep their own set and sequence and will
equal the ID in the Person table.
EXPERT RATIONALE: Mendix uses the same ID value for the generalized and
specialized entity tables. When a new Player object is created, a record is inserted in
both the Person and Player tables using the same system-generated ID. Each
specialization maintains its own independent sequence for generating these IDs,
but the ID values are synchronized across the hierarchy. This design ensures
referential integrity while allowing each entity to be managed separately .
QUESTION 7
Why is it a best practice to create a specialization of the FileDocument and
Image entities rather than using them directly?
A. To reduce the number of tables in the database.
B. It allows for better security and property configuration based on purpose.
C. To improve the performance of file downloads.
D. To enable the use of non-persistable entities for files.
► B. It allows for better security and property configuration based on
purpose.
EXPERT RATIONALE: The FileDocument and Image entities from the System
module cannot be edited directly. By creating your own specialization, you can add
custom attributes, configure module-specific security, and define entity access rules
tailored to the specific use case of your application. For example, a