1
MENDIX CERTIFICATION EXAM 2026/2027 | Actual
Questions | Grade A | Comprehensive Track | Complete
Solutions | Pass Guaranteed - A+ Graded
Section 1: Platform Fundamentals & App Development
Lifecycle (Questions 1-12)
Q1. A development team is deciding whether to use Mendix Studio or Mendix Studio
Pro for building a complex enterprise application requiring custom Java actions and
advanced debugging. Under Mendix 10.x platform guidelines, which statement is
most accurate?
A. Mendix Studio is the only environment that supports Git version control and
branching
B. Mendix Studio Pro is the desktop IDE required for advanced development, custom
Java, and complex microflow debugging
C. Mendix Studio and Studio Pro are identical in capability; the choice is purely user
preference
D. Mendix Studio Pro cannot connect to the Mendix Cloud and is only for on-
premise deployment
B. Mendix Studio Pro is the desktop IDE required for advanced development,
custom Java, and complex microflow debugging [CORRECT]
Rationale: Mendix Studio Pro is the comprehensive desktop IDE supporting advanced
features like custom Java actions, complex microflow debugging, and Git version
control. Mendix Studio is a simplified web-based environment for citizen developers
and does not support Java actions or advanced debugging. Studio Pro connects
directly to the Mendix Cloud and Team Server.
Correct Answer: B
,2
Q2. A team of four developers is working on a Mendix 10.x application using the
built-in version control system. Which version control technology is natively used by
the Mendix Team Server?
A. Subversion (SVN) with centralized locking
B. Git with distributed branching and merging
C. Mercurial with changeset tracking
D. Team Foundation Version Control (TFVC)
B. Git with distributed branching and merging [CORRECT]
Rationale: Mendix 10.x uses Git as its native version control system for the Team
Server, replacing the legacy SVN system. This enables distributed branching, pull
requests, and modern merge conflict resolution directly within Studio Pro.
Correct Answer: B
Q3. A developer creates a new deployment package from the main line in Studio Pro
and deploys it to the Acceptance environment in the Mendix Cloud. What is the
correct sequence of environments in the standard Mendix application lifecycle?
A. Development → Production → Sandbox → Backup
B. Development → Sandbox/Acceptance → Production
C. Production → Acceptance → Development → Archive
D. Sandbox → Development → Production → Retirement
B. Development → Sandbox/Acceptance → Production [CORRECT]
Rationale: The standard Mendix application lifecycle progresses from Development
(local/team server), to Sandbox or Acceptance (testing environments), and finally to
Production. This staged approach allows for testing before live deployment.
Correct Answer: B
Q4. In a Mendix 10.x app repository, which file stores the domain model definitions,
microflow logic, and page layouts in a structured XML format?
,3
A. .mpr files (binary compiled runtime files)
B. .mxmodule files (compressed Java archives)
C. .xml files within the javasource and resources folders
D. The project package (.mpr) contains all model definitions internally; individual
module elements are versioned as structured XML within the Git repository
D. The project package (.mpr) contains all model definitions internally; individual
module elements are versioned as structured XML within the Git repository
[CORRECT]
Rationale: Mendix stores application model elements (domain models, microflows,
pages) as structured XML within the project, which is versioned via Git. While the
.mpr file is the project container, Git tracks changes at the element level, enabling
granular conflict resolution.
Correct Answer: D
Q5. A junior developer attempts to open a Mendix 10.6 project in Studio Pro 10.2.
What will occur?
A. The project will open normally with all features accessible
B. Studio Pro will prompt to upgrade the project or require a newer version to open
it
C. The project will automatically downgrade to version 10.2 without data loss
D. Studio Pro will open the project but disable newer features silently
B. Studio Pro will prompt to upgrade the project or require a newer version to
open it [CORRECT]
Rationale: Mendix projects are forward-compatible within major versions but cannot
be opened by older Studio Pro releases if created in newer versions. The user must
upgrade Studio Pro or the project will not open, preventing corruption from
incompatible model formats.
Correct Answer: B
, 4
Q6. A team needs to implement a feature branch strategy for a Mendix 10.x
application. Which branching approach is natively supported by Mendix Team Server
(Git)?
A. Only trunk-based development with main line commits
B. Feature branches created from main, merged via pull requests after review
C. Centralized locking where only one developer may edit a module at a time
D. Branch-per-environment where Production, Test, and Dev are separate
repositories
B. Feature branches created from main, merged via pull requests after review
[CORRECT]
Rationale: Mendix Team Server (Git) fully supports modern branching strategies
including feature branches, release branches, and pull request workflows. Developers
create branches from main, work in isolation, and merge back via pull requests with
conflict resolution.
Correct Answer: B
Q7. When a developer deploys a Mendix app to the Mendix Free App (Sandbox)
environment, which limitation applies compared to a licensed cloud node?
A. Sandbox environments support unlimited concurrent users and full database
access
B. Sandbox environments sleep after periods of inactivity, have limited runtime
resources, and do not support custom domains
C. Sandbox environments are identical to production nodes but lack version control
D. Sandbox environments can only run nanoflows, not server-side microflows
B. Sandbox environments sleep after periods of inactivity, have limited runtime
resources, and do not support custom domains [CORRECT]
Rationale: Mendix Free App (Sandbox) environments are designed for prototyping
and learning. They enter sleep mode after inactivity, have resource constraints, and
do not support custom domains, scheduled events, or full production scaling.
Licensed nodes provide persistent, scalable infrastructure.
Correct Answer: B
MENDIX CERTIFICATION EXAM 2026/2027 | Actual
Questions | Grade A | Comprehensive Track | Complete
Solutions | Pass Guaranteed - A+ Graded
Section 1: Platform Fundamentals & App Development
Lifecycle (Questions 1-12)
Q1. A development team is deciding whether to use Mendix Studio or Mendix Studio
Pro for building a complex enterprise application requiring custom Java actions and
advanced debugging. Under Mendix 10.x platform guidelines, which statement is
most accurate?
A. Mendix Studio is the only environment that supports Git version control and
branching
B. Mendix Studio Pro is the desktop IDE required for advanced development, custom
Java, and complex microflow debugging
C. Mendix Studio and Studio Pro are identical in capability; the choice is purely user
preference
D. Mendix Studio Pro cannot connect to the Mendix Cloud and is only for on-
premise deployment
B. Mendix Studio Pro is the desktop IDE required for advanced development,
custom Java, and complex microflow debugging [CORRECT]
Rationale: Mendix Studio Pro is the comprehensive desktop IDE supporting advanced
features like custom Java actions, complex microflow debugging, and Git version
control. Mendix Studio is a simplified web-based environment for citizen developers
and does not support Java actions or advanced debugging. Studio Pro connects
directly to the Mendix Cloud and Team Server.
Correct Answer: B
,2
Q2. A team of four developers is working on a Mendix 10.x application using the
built-in version control system. Which version control technology is natively used by
the Mendix Team Server?
A. Subversion (SVN) with centralized locking
B. Git with distributed branching and merging
C. Mercurial with changeset tracking
D. Team Foundation Version Control (TFVC)
B. Git with distributed branching and merging [CORRECT]
Rationale: Mendix 10.x uses Git as its native version control system for the Team
Server, replacing the legacy SVN system. This enables distributed branching, pull
requests, and modern merge conflict resolution directly within Studio Pro.
Correct Answer: B
Q3. A developer creates a new deployment package from the main line in Studio Pro
and deploys it to the Acceptance environment in the Mendix Cloud. What is the
correct sequence of environments in the standard Mendix application lifecycle?
A. Development → Production → Sandbox → Backup
B. Development → Sandbox/Acceptance → Production
C. Production → Acceptance → Development → Archive
D. Sandbox → Development → Production → Retirement
B. Development → Sandbox/Acceptance → Production [CORRECT]
Rationale: The standard Mendix application lifecycle progresses from Development
(local/team server), to Sandbox or Acceptance (testing environments), and finally to
Production. This staged approach allows for testing before live deployment.
Correct Answer: B
Q4. In a Mendix 10.x app repository, which file stores the domain model definitions,
microflow logic, and page layouts in a structured XML format?
,3
A. .mpr files (binary compiled runtime files)
B. .mxmodule files (compressed Java archives)
C. .xml files within the javasource and resources folders
D. The project package (.mpr) contains all model definitions internally; individual
module elements are versioned as structured XML within the Git repository
D. The project package (.mpr) contains all model definitions internally; individual
module elements are versioned as structured XML within the Git repository
[CORRECT]
Rationale: Mendix stores application model elements (domain models, microflows,
pages) as structured XML within the project, which is versioned via Git. While the
.mpr file is the project container, Git tracks changes at the element level, enabling
granular conflict resolution.
Correct Answer: D
Q5. A junior developer attempts to open a Mendix 10.6 project in Studio Pro 10.2.
What will occur?
A. The project will open normally with all features accessible
B. Studio Pro will prompt to upgrade the project or require a newer version to open
it
C. The project will automatically downgrade to version 10.2 without data loss
D. Studio Pro will open the project but disable newer features silently
B. Studio Pro will prompt to upgrade the project or require a newer version to
open it [CORRECT]
Rationale: Mendix projects are forward-compatible within major versions but cannot
be opened by older Studio Pro releases if created in newer versions. The user must
upgrade Studio Pro or the project will not open, preventing corruption from
incompatible model formats.
Correct Answer: B
, 4
Q6. A team needs to implement a feature branch strategy for a Mendix 10.x
application. Which branching approach is natively supported by Mendix Team Server
(Git)?
A. Only trunk-based development with main line commits
B. Feature branches created from main, merged via pull requests after review
C. Centralized locking where only one developer may edit a module at a time
D. Branch-per-environment where Production, Test, and Dev are separate
repositories
B. Feature branches created from main, merged via pull requests after review
[CORRECT]
Rationale: Mendix Team Server (Git) fully supports modern branching strategies
including feature branches, release branches, and pull request workflows. Developers
create branches from main, work in isolation, and merge back via pull requests with
conflict resolution.
Correct Answer: B
Q7. When a developer deploys a Mendix app to the Mendix Free App (Sandbox)
environment, which limitation applies compared to a licensed cloud node?
A. Sandbox environments support unlimited concurrent users and full database
access
B. Sandbox environments sleep after periods of inactivity, have limited runtime
resources, and do not support custom domains
C. Sandbox environments are identical to production nodes but lack version control
D. Sandbox environments can only run nanoflows, not server-side microflows
B. Sandbox environments sleep after periods of inactivity, have limited runtime
resources, and do not support custom domains [CORRECT]
Rationale: Mendix Free App (Sandbox) environments are designed for prototyping
and learning. They enter sleep mode after inactivity, have resource constraints, and
do not support custom domains, scheduled events, or full production scaling.
Licensed nodes provide persistent, scalable infrastructure.
Correct Answer: B
