MENDIX INTERMEDIATE & ADVANCED EXAM
CERTIFICATION ACTUAL EXAM QUESTIONS AND
CORRECT DETAILED ANSWERS|ALREADY GRADED A+
App Directory - ANSWER: The main directory containing all the files and folders
related to the app, including modules, resources, and deployment files.
Clean Directory Example - ANSWER: A new app directory with no additional files or
folders, reflecting the initial state of the app.
JavaScript Source - ANSWER: A folder containing the structure of app modules with
JavaScript actions defined for nanoflows, aiding in finding and reusing JavaScript
sources.
Java Source - ANSWER: A folder containing the structure of app modules with all Java
sources for microflows.
Modules - ANSWER: Distinct parts of the app reflected in the directory after the app
has been run, with each module having its own folder.
Java Actions - ANSWER: Destination folder for all Java actions created in a specific
module using Studio Pro.
Datasets - ANSWER: Destination folder for all data sets created in a specific module
using Studio Pro.
Proxies - ANSWER: Folder representing all entities, persistent and non-persistent,
and enumerations within the app.
Resources - ANSWER: Folder containing files like HTML files or configuration files
that directly affect the application's functionality.
Theme - ANSWER: Folder containing files and folders that form the source for the
styling of the application, requiring HTML/CSS/SASS knowledge for changes.
User Library - ANSWER: Folder containing Java libraries supporting custom Java
functions, which may change when downloading modules like the Community
Commons Function Library or Email module.
Widgets - ANSWER: Folder containing .mpk files reflecting the widgets available in
Studio Pro, requiring knowledge of Mendix APIs and JavaScript for changes.
.mpr - ANSWER: File required by Studio Pro to open the app.
.mpr.bak - ANSWER: Backup file for the .mpr file, used to restore the app in case of
issues during Mendix version upgrades or Team Server app updates.
, .mpr.lock - ANSWER: File indicating that the app is currently open in Studio Pro.
Deployment Folder - ANSWER: Folder containing deployment files needed to run the
app locally, including folders and files for the local database and application sources.
Releases Folder - ANSWER: Folder where deployment packages created with Studio
Pro are stored by default.
Packages Folder - ANSWER: Folder storing created app packages.
Data-snapshot.zip file - ANSWER: File generated when creating a snapshot of app
data, containing a local database that can be shared with teammates.
.classpath file - ANSWER: File needed for Eclipse to import the app.
.project file - ANSWER: File needed for Eclipse to import the app.
<root folder>.launch file - ANSWER: File needed for Eclipse to import the app.
Branches - ANSWER: Separate lines of development that stem from the main line,
allowing for the development of new functionality without affecting the running
production app.
Git Server - ANSWER: A server used to store the app deployment directory, enabling
private version control with Git and allowing for the use of a private server option in
Mendix Studio Pro.
Importing Data - ANSWER: The process of bringing data into a system from external
sources, considering options and frequency. This can include methods like SOAP,
REST, oData, app-specific methods, flat files, CSV, Excel, batch offloads, database
replication module, data transformation, and microflows.
Flat file - ANSWER: A file containing data without any structure or hierarchy, often
used for data storage and exchange.
Database replication module - ANSWER: A tool to copy and maintain a duplicate set
of data in a database, ensuring data integrity and availability.
Data Transformation - ANSWER: The process of changing the format or structure of
data before or after importing, ensuring compatibility and usability within the
system.
Microflows - ANSWER: Workflows used to transform data after importing, often
involving the manipulation and processing of data for specific purposes.
CERTIFICATION ACTUAL EXAM QUESTIONS AND
CORRECT DETAILED ANSWERS|ALREADY GRADED A+
App Directory - ANSWER: The main directory containing all the files and folders
related to the app, including modules, resources, and deployment files.
Clean Directory Example - ANSWER: A new app directory with no additional files or
folders, reflecting the initial state of the app.
JavaScript Source - ANSWER: A folder containing the structure of app modules with
JavaScript actions defined for nanoflows, aiding in finding and reusing JavaScript
sources.
Java Source - ANSWER: A folder containing the structure of app modules with all Java
sources for microflows.
Modules - ANSWER: Distinct parts of the app reflected in the directory after the app
has been run, with each module having its own folder.
Java Actions - ANSWER: Destination folder for all Java actions created in a specific
module using Studio Pro.
Datasets - ANSWER: Destination folder for all data sets created in a specific module
using Studio Pro.
Proxies - ANSWER: Folder representing all entities, persistent and non-persistent,
and enumerations within the app.
Resources - ANSWER: Folder containing files like HTML files or configuration files
that directly affect the application's functionality.
Theme - ANSWER: Folder containing files and folders that form the source for the
styling of the application, requiring HTML/CSS/SASS knowledge for changes.
User Library - ANSWER: Folder containing Java libraries supporting custom Java
functions, which may change when downloading modules like the Community
Commons Function Library or Email module.
Widgets - ANSWER: Folder containing .mpk files reflecting the widgets available in
Studio Pro, requiring knowledge of Mendix APIs and JavaScript for changes.
.mpr - ANSWER: File required by Studio Pro to open the app.
.mpr.bak - ANSWER: Backup file for the .mpr file, used to restore the app in case of
issues during Mendix version upgrades or Team Server app updates.
, .mpr.lock - ANSWER: File indicating that the app is currently open in Studio Pro.
Deployment Folder - ANSWER: Folder containing deployment files needed to run the
app locally, including folders and files for the local database and application sources.
Releases Folder - ANSWER: Folder where deployment packages created with Studio
Pro are stored by default.
Packages Folder - ANSWER: Folder storing created app packages.
Data-snapshot.zip file - ANSWER: File generated when creating a snapshot of app
data, containing a local database that can be shared with teammates.
.classpath file - ANSWER: File needed for Eclipse to import the app.
.project file - ANSWER: File needed for Eclipse to import the app.
<root folder>.launch file - ANSWER: File needed for Eclipse to import the app.
Branches - ANSWER: Separate lines of development that stem from the main line,
allowing for the development of new functionality without affecting the running
production app.
Git Server - ANSWER: A server used to store the app deployment directory, enabling
private version control with Git and allowing for the use of a private server option in
Mendix Studio Pro.
Importing Data - ANSWER: The process of bringing data into a system from external
sources, considering options and frequency. This can include methods like SOAP,
REST, oData, app-specific methods, flat files, CSV, Excel, batch offloads, database
replication module, data transformation, and microflows.
Flat file - ANSWER: A file containing data without any structure or hierarchy, often
used for data storage and exchange.
Database replication module - ANSWER: A tool to copy and maintain a duplicate set
of data in a database, ensuring data integrity and availability.
Data Transformation - ANSWER: The process of changing the format or structure of
data before or after importing, ensuring compatibility and usability within the
system.
Microflows - ANSWER: Workflows used to transform data after importing, often
involving the manipulation and processing of data for specific purposes.
