Mendix Advanced Certification 2026/2027 Exam |Actual Questions and Verified Answers| Already Graded A

Mendix Advanced Certification 2026/2027

Exam |Actual Questions and Verified

Answers| Already Graded A

Q: What is an important rule to keep in mind when creating effective indexes?

Answer:

The index should have the same order of attributes defined as in search and retrieve queries in

order to be available for queries.

Q: Which of the following is NOT a benefit that XPath provides to the Mendix Platform?

Answer:

XPath can be used to automatically generate pages and widgets to show data on.

Q: What does the following XPath query return? //Product

[OrderManagement.OrderLine_Product/OrderManagement.OrderLine

/OrderManagement.OrderLine_Order != $Order]

Answer:

All the products that are ordered at least once, but not on the affected order.

Q: This XPath query can be optimized as follows: [OrderManagement.OrderLine_Product

/OrderManagement.Product/MinimalStock > 50] [OrderManagement.OrderLine_Product

/OrderManagement.Product/Status = 'Active']]

Answer:

[OrderManagement.OrderLine_Product/OrderManagement.Product [MinimalStock > 50 and

Status = 'Active'] ]

Q: The request as result of this XPath can be optimized as follows:

[OrderManagement.Stock_Product /OrderManagement.Product/Status = 'Deactivated' or

OrderManagement.Stock_Supplier /OrderManagement.Supplier/Active = false()]

Answer:

The request can be optimized by splitting it into different requests and joining the results.

Q: Which of the following statements is NOT an XPath best practice with regards to optimal

performance?

Answer:

Do not use XPath when you can use SQL instead.

Q: Consider a situation in which there is an entity called Request with an attribute status that

has three values: Draft, Submitted, and Approved. There are three user roles: Administrator,

Customer, and Employee. The Customer user role is granted the Customer module role. The only

access rule configured is read/write access for the Customer with the XPath [Status = Draft]

applied. What would a user with the Customer user role see on a page with a data grid without

any additional XPath constraints?

Answer:

All the requests in the Draft status.

Q: Consider the exact same situation as above. What would Admin users see?

Answer:

No results would be returned.

Q: Consider the same situation again. What would happen if you granted Admin users access to

a page with the Request entity in Studio Pro?

Answer:

Studio Pro would detect an error and prevent a deployment.

Q: How does the platform use entity access XPaths to enforce security?

Answer:

The XPaths are added to all the relevant database retrieves.

Q: Where are entity access restrictions applied?

Answer:

On relevant database retrieves.

Q: Which of the following best describes how the Mendix platform applies entity access?

Answer:

The platform only grants the access explicitly defined in the entity access rules.

Q: In this domain model, assume that House is a specialization of Building:

Answer:

Admin users will be able to read the SquareFoot attribute in data views for Buildings and read

and write in data views for Houses.

Q: Referring to the same domain model as was used in question #2, if we create a page with a

data grid containing Houses and autogenerate a House_NewEdit page, which of the following

statements is FALSE for an Admin user?

Answer:

Admin users will not see the SquareFoot attribute in the Edit page.