I85PREP
⌘ K
Mendix Rapid Developer study materials
Mendix Rapid Developer study resources

Mendix Rapid Developer practice questions

One question at a time. Build your Mendix Rapid Developer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Mendix Platform and Studio Pro Fundamentals

In Mendix Studio Pro, which document type is used to define the data model of a module, including entities, attributes, and associations?

  1. The page
  2. The module role
  3. The domain model Correct answer.
  4. The microflow

Explanation

The domain model is the visual blueprint of an app's data structure and holds entities with their attributes plus the associations that connect them. Microflows define logic, pages define the user interface, and module roles define access. All persistent data modeling starts in the domain model.

Question 2Mendix Platform and Studio Pro Fundamentals

A developer wants an entity attribute to store a true/false flag indicating whether a customer is active. Which attribute type should be selected?

  1. String
  2. Boolean Correct answer.
  3. Decimal
  4. Enumeration

Explanation

The Boolean attribute type stores exactly two states, true or false, which is the correct fit for a flag such as active or inactive. Enumeration is for a fixed list of named values, String stores text, and Decimal stores numeric values with decimals. Choosing Boolean keeps the model simple and avoids invalid third states.

Question 3Mendix Platform and Studio Pro Fundamentals

Which Studio Pro document is best suited to show a list of records and let an end user open, edit, or delete individual records?

  1. A Java action
  2. A module role mapping
  3. A page with a data grid or list view widget Correct answer.
  4. A scheduled event

Explanation

Pages host widgets, and the data grid and list view widgets are designed to display a collection of objects with controls for opening, editing, and deleting them. Scheduled events trigger logic on a timetable, Java actions extend logic in code, and module role mappings link roles to security. Only a page provides the user-facing list interaction.

Question 4Mendix Platform and Studio Pro Fundamentals

In a microflow, which element is used to branch logic based on a condition and provide separate paths for true and false outcomes?

  1. A decision Correct answer.
  2. A commit activity
  3. A create object activity
  4. A merge

Explanation

A decision element evaluates a condition and splits the flow into true and false outgoing paths. A merge rejoins split paths, a create object activity instantiates a new object, and a commit activity persists changes. Decisions are the standard branching construct in microflows.

Question 5Mendix Platform and Studio Pro Fundamentals

A developer needs to reuse the same navigation menu across the app so users can move between pages. Where is this configured in Studio Pro?

  1. In the navigation document Correct answer.
  2. In the domain model
  3. In a microflow
  4. In the project settings

Explanation

The navigation document defines the menu structure and the pages or microflows that menu items open, so it is the central place to configure app-wide navigation. The domain model holds data, microflows hold logic, and project settings cover configuration such as languages and runtime. Navigation belongs in its own dedicated document.

Question 6Mendix Platform and Studio Pro Fundamentals

What is the primary purpose of a module in a Mendix app?

  1. To group related documents such as domain models, pages, and microflows into a logical unit Correct answer.
  2. To store only the database connection string
  3. To represent a single end user account
  4. To define the color scheme of the user interface

Explanation

A module is a container that organizes related model documents, including its own domain model, pages, microflows, and security roles. Grouping by function keeps large projects maintainable and supports module-level security. Color schemes, connection strings, and user accounts are handled by other parts of the platform.

Question 7Mendix Platform and Studio Pro Fundamentals

Which of the following best describes an association in a Mendix domain model?

  1. A relationship between two entities that allows one entity to reference objects of another Correct answer.
  2. A validation rule applied to a single attribute
  3. A calculated value derived from other attributes
  4. A permission granted to a user role

Explanation

Associations connect entities and define whether one object relates to one or many objects of the other entity. They enable retrieval across related data in pages and microflows. Validation rules, calculated values, and permissions are separate concepts implemented elsewhere.

Question 8Mendix Platform and Studio Pro Fundamentals

A developer wants a microflow to run automatically every night to clean up old records. Which document should be used?

  1. A scheduled event Correct answer.
  2. A nanoflow
  3. A page
  4. An enumeration

Explanation

A scheduled event is configured to trigger a microflow at a defined interval or time, making it the correct choice for recurring background work such as nightly cleanup. Pages are for UI, enumerations define fixed value lists, and nanoflows run client-side in response to user interaction. Recurring server-side tasks belong in scheduled events.

Question 9Mendix Platform and Studio Pro Fundamentals

In a microflow, a developer retrieves a list of Order objects and wants to iterate over each one to send a confirmation. Which element accomplishes this?

  1. A decision
  2. A change object activity
  3. A loop with a list parameter Correct answer.
  4. A merge

Explanation

A loop element iterates over a list and executes its inner activities once per object, which is exactly what is needed to process each Order. A merge rejoins paths, a decision branches on a condition, and a change object activity modifies a single object. Iteration over collections requires a loop.

Question 10Mendix Platform and Studio Pro Fundamentals

A developer needs the value of an attribute from the currently selected object on a page to be available inside a microflow. How is this most commonly achieved?

  1. Pass the object as a microflow parameter and access its attribute Correct answer.
  2. Retrieve all objects of the entity in the microflow
  3. Commit the object before calling the microflow
  4. Create a new entity for each attribute value

Explanation

Microflow parameters accept objects or values from the calling context, so passing the selected object lets the microflow read its attributes directly. Committing is unnecessary for reading values, creating extra entities is wasteful, and retrieving all objects is inefficient. Parameters are the intended mechanism for passing context into logic.

Question 11Mendix Platform and Studio Pro Fundamentals

When configuring entity access in Mendix security, what does the 'Create' right control?

  1. Whether members of a module role may instantiate new objects of that entity Correct answer.
  2. Whether members of a module role may change attribute values
  3. Whether members of a module role may delete objects
  4. Whether members of a module role may read existing objects

Explanation

Entity access rights are split into create, read, write, and delete, and the create right governs whether a role can instantiate new objects of the entity. Read governs viewing, write governs modifying, and delete governs removal. Setting create correctly prevents unauthorized object creation.

Question 12Mendix Platform and Studio Pro Fundamentals

A developer wants to show a calculated total on a page that updates when the user changes a quantity field, without saving to the database. Which approach fits best?

  1. Add a new entity to store the total
  2. Use a nanoflow triggered by the field's change event to update the total Correct answer.
  3. Commit the object and reload the page
  4. Create a scheduled event to recalculate

Explanation

Nanoflows run in the browser and can respond to widget events such as a change on an input field, updating on-page values immediately without a server round trip or commit. Committing and reloading is heavy-handed, scheduled events run on a timetable, and a new entity is unnecessary. Client-side logic suits immediate UI feedback.

Question 13Mendix Platform and Studio Pro Fundamentals

Which statement correctly distinguishes a microflow from a nanoflow in Mendix?

  1. A microflow runs on the server, while a nanoflow runs in the client browser Correct answer.
  2. Both run exclusively on the server with no client execution
  3. Both run exclusively in the browser with no server execution
  4. A microflow runs in the browser, while a nanoflow runs on the server

Explanation

Microflows execute on the Mendix Runtime server and can use the full server-side API, while nanoflows execute in the client to provide responsive offline-capable logic. This difference drives choices about performance, offline support, and available activities. The other options reverse or misstate this server/client split.

Question 14Mendix Platform and Studio Pro Fundamentals

A developer defines an enumeration called OrderStatus with values New, Paid, and Shipped, then adds an attribute of that enumeration type to the Order entity. What is the benefit of this approach over a free-text String attribute?

  1. It forces the attribute to be unique across all orders
  2. It automatically creates a page for each status
  3. It restricts the attribute to the predefined values, preventing invalid statuses Correct answer.
  4. It removes the need for any entity access rules

Explanation

An enumeration attribute can only hold one of its defined values, which enforces valid statuses and simplifies logic that compares against them. It does not generate pages, bypass security, or impose uniqueness. Using enumerations instead of free text improves data integrity.

Question 15Mendix Platform and Studio Pro Fundamentals

In the domain model, what does setting an association's multiplicity to one-to-many typically mean?

  1. One object of the first entity can relate to many objects of the second entity Correct answer.
  2. Neither entity can have associations to other entities
  3. Both entities must always have exactly one object each
  4. Many objects of the first entity relate to one object of the second and never the reverse

Explanation

A one-to-many association means a single object on one side can be linked to multiple objects on the other side, such as one Customer with many Orders. Multiplicity describes cardinality, not exclusivity of other associations. The other options misstate the cardinality or add rules that do not apply.

Question 16Mendix Platform and Studio Pro Fundamentals

A developer builds a page that should only be reachable by users with an administrator role. Which mechanism enforces this at the page level?

  1. Page access configured for the relevant module role Correct answer.
  2. A decision element inside the page
  3. An enumeration attribute on the entity
  4. A scheduled event that checks the role

Explanation

Page access settings determine which module roles may open a given page, so restricting the page to the administrator role enforces the requirement. Decision elements belong to microflows, enumerations store values, and scheduled events run on a timetable. Page-level security is configured in the page's access settings.

Question 17Mendix Platform and Studio Pro Fundamentals

A developer retrieves a single Customer object in a microflow and then wants to modify one of its attributes before saving. Which combination of activities is required?

  1. A merge followed by a decision
  2. A loop followed by a rollback activity
  3. A retrieve activity followed by a change object activity and a commit activity Correct answer.
  4. A create object activity followed by a delete activity

Explanation

To modify existing data, the microflow retrieves the object, changes its attribute values with a change object activity, and commits to persist the change. Creating and deleting would remove the record, merging and decisions control flow, and a loop with rollback would discard changes. Retrieve, change, and commit form the standard update pattern.

Question 18Mendix Platform and Studio Pro Fundamentals

A developer needs to call reusable custom Java code from a microflow. Which Studio Pro document is created for this purpose?

  1. A nanoflow
  2. A Java action Correct answer.
  3. An enumeration
  4. A page

Explanation

A Java action wraps custom Java code and exposes it as an activity that microflows can call with parameters. Nanoflows are client-side logic, enumerations are value lists, and pages are UI. When built-in activities are insufficient, Java actions extend logic in code.

Question 19Mendix Platform and Studio Pro Fundamentals

A developer wants to display a message to the user when a microflow encounters invalid input and then stop processing. Which activity should be used?

  1. A create object activity
  2. A commit activity
  3. A validation feedback or show message activity, followed by ending the flow Correct answer.
  4. A merge activity

Explanation

Validation feedback attaches an error to an attribute, and show message presents information to the user; either can be followed by an end event to stop processing. Creating, committing, and merging do not communicate errors to the user. User-facing error handling requires feedback or message activities.

Question 20Mendix Platform and Studio Pro Fundamentals

A developer wants to configure a microflow so that a specific activity runs only when a retrieved Order has a total above 1000. Which element provides this conditional behavior?

  1. A decision element with a condition on the Order total Correct answer.
  2. A merge element
  3. A scheduled event
  4. A parameter of type String

Explanation

A decision evaluates an expression and routes the flow down the true or false path, so a condition on the Order total controls whether the activity runs. A merge rejoins paths, a String parameter supplies input, and a scheduled event triggers on time. Conditional logic in a microflow is expressed with decisions.

Question 21Mendix Platform and Studio Pro Fundamentals

A developer is choosing between committing an object and rolling it back within a microflow. Which statement best captures the difference?

  1. Commit discards changes, while rollback persists them
  2. Neither affects the object's stored state
  3. Commit persists changes to the database, while rollback discards unsaved changes to the object Correct answer.
  4. Both persist changes and differ only in performance

Explanation

Committing writes the object's current state to the database, whereas rolling back reverts the object to its last committed state and discards pending changes. They have opposite effects on persistence, not merely different performance. Understanding this distinction prevents accidental data loss or unwanted saves.

Question 22Mendix Platform and Studio Pro Fundamentals

A developer retrieves a list of Customers and needs to process only those with a status of Active, then pass the filtered list to a page. Which microflow approach is most appropriate?

  1. Retrieve all Customers and rely on the page to hide inactive ones
  2. Use a merge element to filter the list
  3. Retrieve with an XPath constraint filtering on status, then pass the resulting list Correct answer.
  4. Create a new entity for active Customers and copy records each time

Explanation

Applying an XPath constraint during retrieval returns only matching objects, which is efficient and keeps logic clear. Relying on the page to hide records still transfers unnecessary data, duplicating active records into a new entity is a maintenance burden, and a merge cannot filter. Filtering at retrieval is the recommended pattern.

Question 23Mendix Platform and Studio Pro Fundamentals

A developer must ensure that a microflow's change to an Order is visible to a subsequent retrieve within the same microflow before any commit occurs. Which statement is accurate about uncommitted changes?

  1. The changed object remains available in the microflow's context, but a fresh database retrieve will not reflect uncommitted changes Correct answer.
  2. Uncommitted changes are automatically committed when the microflow ends
  3. Uncommitted changes are discarded the moment a change object activity completes
  4. Uncommitted changes are immediately written to the database and visible to all users

Explanation

Changes made with a change object activity live on the object in the microflow's memory and are not written to the database until a commit occurs, so a new retrieve reads the stored state. Uncommitted changes are not visible to other users and are not auto-committed at flow end. This behavior explains why explicit commits are needed to persist data.

Question 24Mendix Platform and Studio Pro Fundamentals

A developer configures module roles and user roles in a Mendix app. Which statement correctly describes the relationship between them?

  1. Module roles apply only to microflows, while user roles apply only to pages
  2. User roles and module roles are identical and cannot be mapped to each other
  3. Module roles are assigned directly to end users, and user roles define entity access
  4. User roles are assigned to end users, and module role mappings grant those user roles the module roles that define entity and page access Correct answer.

Explanation

End users receive user roles, and module role mappings connect each user role to one or more module roles within a module. The module roles then carry the entity and page access rules. This indirection lets administrators manage access without touching every module individually.

Question 25Domain Model and Data Modeling

In a Mendix domain model, which element represents a single unit of data with attributes and is drawn as a rectangle?

  1. An entity Correct answer.
  2. A module role
  3. A microflow
  4. A page

Explanation

Entities are the core data building blocks of the domain model and are drawn as rectangles containing their attributes. Microflows, pages, and module roles are modeled elsewhere in the project and are not domain-model data units.

Question 26Domain Model and Data Modeling

Which attribute type should you choose for a value that only ever holds true or false, such as a 'IsActive' flag?

  1. Integer
  2. Enumeration
  3. Boolean Correct answer.
  4. String

Explanation

The Boolean attribute type stores exactly two states, true or false, and is the natural fit for flags. String, Integer, and Enumeration can technically store similar information but waste space and lose built-in type semantics.

Question 27Domain Model and Data Modeling

What is the purpose of a generalization (inheritance) relationship between two entities in a Mendix domain model?

  1. The specialized entity inherits attributes and associations of the general entity Correct answer.
  2. The general entity becomes read-only while the specialized entity becomes writable
  3. The two entities are merged into a single database table with no distinction
  4. The specialized entity copies the general entity's data at runtime into a separate table

Explanation

Generalization lets a specialized entity reuse the attributes and associations defined on the general entity, sharing one underlying object. This supports polymorphism and reduces duplication. It does not copy data or merge entities into one indistinguishable table.

Question 28Domain Model and Data Modeling

You need to model that one Customer can place many Orders, but each Order belongs to exactly one Customer. Which construct do you add?

  1. A one-to-one association from Customer to Order
  2. A generalization from Order to Customer
  3. A one-to-many association from Customer to Order Correct answer.
  4. A many-to-many association from Customer to Order

Explanation

A one-to-many association captures the rule that a single Customer relates to multiple Orders while each Order relates to one Customer. A many-to-many would allow an Order to belong to several Customers, and generalization is not a relationship of ownership.

Question 29Domain Model and Data Modeling

What does the owner setting on an association control?

  1. Which module role may read the associated entity
  2. Which attribute is used as the primary key for the association
  3. Which side of the association holds the reference and how the relationship is stored Correct answer.
  4. Whether the association is validated at commit time

Explanation

The owner determines the direction in which the association is stored and navigated, which affects retrieval performance and how the reference is persisted. Access rights and validation are configured separately from ownership.

Question 30Domain Model and Data Modeling

Which statement about a many-to-many association in Mendix is true?

  1. It requires both entities to share the same generalization
  2. It is stored in a separate join table managed by the platform Correct answer.
  3. It cannot be created between entities in different modules
  4. It stores only one reference per object on the owner side

Explanation

A many-to-many association is persisted through an underlying join table that Mendix maintains automatically. Neither entity needs a shared generalization, and cross-module associations are permitted when the module dependencies allow it.

Question 31Domain Model and Data Modeling

What is the primary purpose of an enumeration attribute in the domain model?

  1. To store free-form text of unlimited length
  2. To automatically generate a database index
  3. To restrict a value to a predefined list of named options Correct answer.
  4. To link two entities through a foreign key

Explanation

Enumerations define a fixed set of named values and constrain the attribute to one of them, improving data quality and readability. They do not store free text, create indexes automatically, or act as associations.

Question 32Domain Model and Data Modeling

Where is a calculated value such as 'FullName' derived from FirstName and LastName best implemented?

  1. As an association between FirstName and LastName
  2. As a generalization of the Name entity
  3. As a persistent String attribute updated manually by users
  4. As a calculated attribute or a non-persistent attribute computed in a microflow Correct answer.

Explanation

Derived values should not be stored redundantly; a calculated or non-persistent attribute computes them on demand from source data. Storing a manually maintained copy risks inconsistency and requires extra user effort.

Question 33Domain Model and Data Modeling

What does setting an attribute as the 'unique' validation rule enforce?

  1. No two objects of that entity may share the same value for that attribute Correct answer.
  2. The attribute becomes read-only after creation
  3. The attribute is excluded from the database
  4. The attribute must always be non-empty

Explanation

The unique validation constraint ensures the value is distinct across all objects of the entity, which is useful for identifiers like email or code. It does not by itself require a value, hide the attribute, or make it immutable.

Question 34Domain Model and Data Modeling

A developer wants to prevent deletion of a Customer while related Orders exist. Which domain-model feature addresses this?

  1. Creating a generalization from Customer to Order
  2. Setting the association delete behavior to prevent deletion of the owner Correct answer.
  3. Marking the Order entity as non-persistent
  4. Adding a unique validation rule to the Customer

Explanation

Association delete behavior defines what happens to related objects when one side is deleted; a preventing option blocks deletion while references remain. Non-persistent entities, uniqueness rules, and generalization do not control referential deletion.

Question 35Domain Model and Data Modeling

Which entity type should you use for data that must exist only in memory during a user session and never be committed to the database?

  1. A non-persistent entity Correct answer.
  2. A persistent entity with a unique rule
  3. An enumeration attribute
  4. A generalization of a persistent entity

Explanation

Non-persistent entities hold data in memory without a database table, ideal for temporary or computed objects. Persistent entities are stored, enumerations are value lists, and generalization does not change persistence.

Question 36Domain Model and Data Modeling

What is the effect of defining an association between entities in two different modules?

  1. It is allowed if the modules have the appropriate dependency configured Correct answer.
  2. It requires both entities to be non-persistent
  3. It automatically merges the two modules into one
  4. It is impossible because associations are limited to a single module

Explanation

Cross-module associations are supported when the consuming module declares a dependency on the module that owns the other entity. Modules are not merged, and persistence status is unrelated to the ability to associate.

Question 37Domain Model and Data Modeling

Which Mendix concept lets you define a reusable set of attributes that multiple entities can share without duplicating definitions?

  1. An enumeration attribute
  2. A calculated attribute
  3. Generalization with a general entity Correct answer.
  4. A non-persistent entity

Explanation

Generalization lets several specialized entities inherit a shared set of attributes and associations from a general entity. Enumerations, non-persistent entities, and calculated attributes solve different modeling problems.

Question 38Domain Model and Data Modeling

What happens to an object's attributes when you retrieve it from the database in Mendix?

  1. Non-persistent attributes are loaded from the database
  2. Attributes are loaded lazily one at a time on first access
  3. All persistent attributes are loaded according to the retrieval and access rules Correct answer.
  4. Only attributes explicitly listed in a microflow are loaded

Explanation

Retrieving an object loads its persistent attributes subject to the entity access rules of the user context. Non-persistent attributes are not stored in the database, and attributes are not loaded one at a time on access.

Question 39Domain Model and Data Modeling

Which validation rule should you apply to ensure a mandatory field such as 'Email' is always filled in?

  1. Unique
  2. Required Correct answer.
  3. Regular expression
  4. Range

Explanation

The required rule enforces that the attribute has a value before the object can be committed. Unique, Range, and Regular expression validate other aspects such as distinctness, numeric bounds, and format.

Question 40Domain Model and Data Modeling

A team wants to guarantee that an Order's 'OrderDate' cannot be later than today. Which mechanism is most appropriate at the domain-model level?

  1. A unique constraint on OrderDate
  2. A many-to-many association with a Calendar entity
  3. A validation rule or a before-commit event that checks the value Correct answer.
  4. A generalization of Order to a Date entity

Explanation

Business constraints on values are enforced through validation rules or event handlers such as before-commit that can reject invalid data. Uniqueness, generalization, and associations do not express a comparison against the current date.

Question 41Domain Model and Data Modeling

What does an association's multiplicity 'one-to-one' mean in a Mendix domain model?

  1. The association is automatically indexed on both sides
  2. Each object can relate to unlimited objects on the other side
  3. The association cannot be navigated in microflows
  4. Each object on one side relates to at most one object on the other side Correct answer.

Explanation

One-to-one means a single object pairs with a single object on the opposite side, such as a Person and a Passport. It does not imply unlimited relations, automatic indexing, or restricted navigation.

Question 42Domain Model and Data Modeling

Which attribute type is best suited for storing a monetary amount with decimal precision?

  1. Decimal Correct answer.
  2. Integer
  3. Boolean
  4. String

Explanation

The Decimal type stores numbers with fractional precision, which is appropriate for monetary amounts. Integer loses fractional parts, String stores text, and Boolean holds only true or false.

Question 43Domain Model and Data Modeling

What is the role of a system attribute such as 'CreatedDate' in a persistent entity?

  1. It must be filled in manually by the end user on every form
  2. It disables persistence for the entity
  3. It is used as the association owner reference
  4. It is maintained automatically by the platform to record metadata about the object Correct answer.

Explanation

System attributes like CreatedDate, ChangedDate, and Owner are maintained by the runtime to track object metadata. They are not user-entered fields, do not act as association references, and do not affect persistence.

Question 44Domain Model and Data Modeling

A developer deletes an entity that other entities reference through associations. What is a likely consequence in the domain model?

  1. The associations are automatically converted to generalizations
  2. Consistency errors appear until the referencing associations are removed or redirected Correct answer.
  3. The referencing entities become non-persistent
  4. The deleted entity's data is moved to an enumeration

Explanation

Removing an entity leaves dangling associations that must be cleaned up, producing consistency errors in the model. Associations are not silently converted, entities do not change persistence, and data is not moved to enumerations.

Question 45Domain Model and Data Modeling

Which statement best describes the relationship between a domain model and a database table in Mendix?

  1. Each association creates a new persistent entity
  2. Non-persistent entities are stored in the same table as persistent ones
  3. Each persistent entity maps to a table whose columns derive from its attributes Correct answer.
  4. Each module maps to exactly one table regardless of entities

Explanation

Mendix maps persistent entities to database tables and attributes to columns, with associations handled through foreign keys or join tables. Modules are not single tables, associations are not entities, and non-persistent entities have no table.

Question 46Domain Model and Data Modeling

You want to model that a Project has a list of Tasks and that deleting the Project should also delete its Tasks. Which configuration achieves this?

  1. A generalization from Task to Project
  2. A one-to-one association with no delete behavior
  3. A one-to-many association with cascade delete behavior Correct answer.
  4. A many-to-many association with unique validation

Explanation

A one-to-many association from Project to Task combined with cascade delete removes dependent Tasks when the Project is deleted. One-to-one, generalization, and many-to-many do not express this ownership and cascading rule.

Question 47Domain Model and Data Modeling

What is the purpose of an index on a persistent entity in Mendix?

  1. To convert the entity into a non-persistent one
  2. To encrypt the stored attribute values
  3. To speed up retrieval queries that filter or sort on the indexed attributes Correct answer.
  4. To enforce uniqueness of the entity's objects

Explanation

Indexes improve query performance for attributes frequently used in filters or sorting. They do not enforce uniqueness, provide encryption, or change an entity's persistence.

Question 48Domain Model and Data Modeling

Which construct should you use to represent a fixed categorical value like OrderStatus with values New, Shipped, and Delivered?

  1. A String attribute with no constraint
  2. A separate OrderStatus entity linked by a one-to-one association
  3. A Boolean attribute for each status
  4. An enumeration attribute on the Order entity Correct answer.

Explanation

An enumeration attribute restricts values to a predefined list and is the standard way to model status categories. Separate entities, multiple Booleans, or unconstrained Strings add complexity or allow invalid values.

Question 49Domain Model and Data Modeling

What does the 'owner' of an association determine when retrieving objects in a microflow?

  1. Which user role can view the associated object
  2. Whether the association is validated on commit
  3. Which direction of navigation is efficient and how the reference is stored Correct answer.
  4. Whether the association is shown on a page

Explanation

Association ownership determines the stored direction of the reference and influences navigation efficiency. Access, validation, and page layout are configured through other mechanisms such as access rules and page models.

Question 50Domain Model and Data Modeling

In a Mendix domain model, which construct represents a reusable predefined list of constant values that an attribute can draw from, such as a fixed set of priority levels?

  1. A generalization relationship
  2. A calculated attribute
  3. A non-persistent entity
  4. An enumeration used as the attribute type Correct answer.

Explanation

An enumeration defines a fixed, named set of values, and an attribute typed as that enumeration can only hold one of those values. This keeps the allowed values consistent across the model and exposes them to the runtime, microflows, and pages without storing lookup records.