APPIAN SENIOR DEVELOPER EXAMS SCRIPT ACTUAL
QUESTIONS AND ANSWERS SURE A+
✔✔Appian Health Check - For the first time a health check performed, The raw results
must be reviewed - ✔✔True
✔✔Appian Health Check - The name of the group will receive health check report
notifications - ✔✔1. Group name is "Health Check viewers"
2. can be "System Administrators" exculded from the list
✔✔Appian Health Check - System account required to automatically receive the
analysis resutls of health check report - ✔✔True
✔✔Appian Data Design - Each Data Store can connect to one DB - ✔✔True
✔✔Appian Data Design - benefits of normalization - ✔✔1. Better scalability
2. Lower memory usage
3. Better usability
✔✔Appian Data Design - Two primary ways to integrate a relational database into your
appian applications - ✔✔1. Top Down
2. Bottom Up
✔✔Appian Data Design - Top Down - ✔✔* Create your Data Structures directly using
Appian Custom Data Types (CDT)
* Use Appian's Data Store to generate SQL Scripts (Also known as DDL Scripts) to
create your database tables
✔✔Appian Data Design - Bottom Up - ✔✔* Create your tables first, Then generate
CDT's to reflect the table architecture
* Appian automatically generates annotations to reflect the database design
characteristics of the existing table. Such as specific table naming conventions, required
columns, and non-default data types.
✔✔Appian Data Design - Top Down - Advantages - ✔✔1. No coding is required when
you create a database table directly from a CDT built-in Appian
* Appian development doesn't require any SQL script
* This can greatly simplify and speed up your development process
✔✔Appian Data Design - Top Down - Disadvantages - ✔✔1. Direct editing of XSD file is
required to support advanced DB features
2. Tables and columns are lowercased by default. Difficult to read.
3. Lond column names (more than 27 characters) are renames by dropping vowels.
Can became difficlut to read.
, ✔✔Appian Data Design - Top Down - Other considerations - ✔✔* Most columns are
nullable (not required) by default.
- Best practice to make columns required by default - forcing more field validation.
* Database constraints (Setting column as required ) are limited to primary and foreign
keys.
✔✔Appian Data Design - Bottom Up - Advantages - ✔✔* Allows using database design
tools to define tables and columns directly
* Makes it easier to support design requirements
- Standardized table and column names
- New columns are not nullable by default
- Column checks and foreign key constraints
- Indexes added to foreign key columns used in filters and joins
- Wider range of datatype choices
- Field lengths available for all data types
* Appian reads table attributes and generates annotated CDTs that support advanced
table configurations
- Primary and Foreign keys are automatically identified
- Tables and Columns are annotated with exact names
- Required fiedls are automatically set to nullables equals false in CDT
✔✔Appian Data Design - Bottom Up - Disadvantages - ✔✔* Knowledge of third party
tool required
- Database utility phpMyAdmin provided with every Appian cloud instance
* Updates to CDT generated from table must be made by editing XML schema
document for the CDT
- Called an XML schema definition or XSD file
- Need to upload new version each time CDT is modified
✔✔Appian Data Design - Appian recommended approach - Bottom Up - ✔✔Bottom up
design make it easier to
- Annotate your CDTs with conventional table and column names.
- Select non-default data types
- Annotate null constraints
✔✔Appian Data Design - Table Relationship Type - Recommended approach - ✔✔One-
to-One Nested
Many-to-One Nested
One-to-Many Flat
Many-toMany Flat
✔✔Appian Data Design - JPA Annotations - ✔✔JPA annotations give you more control
over the design of your database entities in Appian.
QUESTIONS AND ANSWERS SURE A+
✔✔Appian Health Check - For the first time a health check performed, The raw results
must be reviewed - ✔✔True
✔✔Appian Health Check - The name of the group will receive health check report
notifications - ✔✔1. Group name is "Health Check viewers"
2. can be "System Administrators" exculded from the list
✔✔Appian Health Check - System account required to automatically receive the
analysis resutls of health check report - ✔✔True
✔✔Appian Data Design - Each Data Store can connect to one DB - ✔✔True
✔✔Appian Data Design - benefits of normalization - ✔✔1. Better scalability
2. Lower memory usage
3. Better usability
✔✔Appian Data Design - Two primary ways to integrate a relational database into your
appian applications - ✔✔1. Top Down
2. Bottom Up
✔✔Appian Data Design - Top Down - ✔✔* Create your Data Structures directly using
Appian Custom Data Types (CDT)
* Use Appian's Data Store to generate SQL Scripts (Also known as DDL Scripts) to
create your database tables
✔✔Appian Data Design - Bottom Up - ✔✔* Create your tables first, Then generate
CDT's to reflect the table architecture
* Appian automatically generates annotations to reflect the database design
characteristics of the existing table. Such as specific table naming conventions, required
columns, and non-default data types.
✔✔Appian Data Design - Top Down - Advantages - ✔✔1. No coding is required when
you create a database table directly from a CDT built-in Appian
* Appian development doesn't require any SQL script
* This can greatly simplify and speed up your development process
✔✔Appian Data Design - Top Down - Disadvantages - ✔✔1. Direct editing of XSD file is
required to support advanced DB features
2. Tables and columns are lowercased by default. Difficult to read.
3. Lond column names (more than 27 characters) are renames by dropping vowels.
Can became difficlut to read.
, ✔✔Appian Data Design - Top Down - Other considerations - ✔✔* Most columns are
nullable (not required) by default.
- Best practice to make columns required by default - forcing more field validation.
* Database constraints (Setting column as required ) are limited to primary and foreign
keys.
✔✔Appian Data Design - Bottom Up - Advantages - ✔✔* Allows using database design
tools to define tables and columns directly
* Makes it easier to support design requirements
- Standardized table and column names
- New columns are not nullable by default
- Column checks and foreign key constraints
- Indexes added to foreign key columns used in filters and joins
- Wider range of datatype choices
- Field lengths available for all data types
* Appian reads table attributes and generates annotated CDTs that support advanced
table configurations
- Primary and Foreign keys are automatically identified
- Tables and Columns are annotated with exact names
- Required fiedls are automatically set to nullables equals false in CDT
✔✔Appian Data Design - Bottom Up - Disadvantages - ✔✔* Knowledge of third party
tool required
- Database utility phpMyAdmin provided with every Appian cloud instance
* Updates to CDT generated from table must be made by editing XML schema
document for the CDT
- Called an XML schema definition or XSD file
- Need to upload new version each time CDT is modified
✔✔Appian Data Design - Appian recommended approach - Bottom Up - ✔✔Bottom up
design make it easier to
- Annotate your CDTs with conventional table and column names.
- Select non-default data types
- Annotate null constraints
✔✔Appian Data Design - Table Relationship Type - Recommended approach - ✔✔One-
to-One Nested
Many-to-One Nested
One-to-Many Flat
Many-toMany Flat
✔✔Appian Data Design - JPA Annotations - ✔✔JPA annotations give you more control
over the design of your database entities in Appian.