APPIAN LEAD DEVELOPER EXAM – PERFORMANCE
Appian Lead Developer Exam – Performance
Considerations for archiving processes - Answer -After a process is completed or
canceled, it can be archived, once its archived, the data it contains is no longer avilable
for reporting
Users with appropriate acess can view history of an archived process in the - Answer -
1. Process activity tab under monitoring view
Default archive interval - Answer -7 days
Process model's archival setting can be changed on the - Answer -Data management
tab in the process modeler
Auto-archiving - Answer -Default option for processes with data and metadata that do
not need to be retained after completion. Auto set to 7 days, can be changed by
sysadmin
- set on the Data Tab of the process model Properties dialog box
- can also be set using archiveprocess.bat (.sh) in the _scripts/tools directory or settings
in the custom.properties file
Auto-deletion - Answer -Should only be selected for processes that never require the
viewing of data or metadata after completion, this option provides max space savings in
appian DBs (KDBs) and on disk
Cleanup.bat (.sh) - Answer -Run this script on a regular basis to manage your process
archive files
- use a windows scheduled task, cron job or job scheduler calendar to run this script at
least once a week to keep archive files from accumulating
- not necessary to migrate archives when upgrading versions of Appian
- used to move Appian log files to backup location and delete older versions
- Must be run on each machine where log files are stored
Data maintenance - Appian Engine files - Answer -Old .kdb files are auto moved to an
archived location when they are no longer in use
Data Maintenance - Cleanup schedules - Answer -cleanup.bat (.sh) and
cleanupArchives.sh (.bat) scripts are intended to be run on a regular basis to preserve
disk space
Adding a related action or view to an existing record type can provide a simple way to
speed development of a new application - Answer -True
Appian Lead Developer Exam – Performance
Considerations for archiving processes - Answer -After a process is completed or
canceled, it can be archived, once its archived, the data it contains is no longer avilable
for reporting
Users with appropriate acess can view history of an archived process in the - Answer -
1. Process activity tab under monitoring view
Default archive interval - Answer -7 days
Process model's archival setting can be changed on the - Answer -Data management
tab in the process modeler
Auto-archiving - Answer -Default option for processes with data and metadata that do
not need to be retained after completion. Auto set to 7 days, can be changed by
sysadmin
- set on the Data Tab of the process model Properties dialog box
- can also be set using archiveprocess.bat (.sh) in the _scripts/tools directory or settings
in the custom.properties file
Auto-deletion - Answer -Should only be selected for processes that never require the
viewing of data or metadata after completion, this option provides max space savings in
appian DBs (KDBs) and on disk
Cleanup.bat (.sh) - Answer -Run this script on a regular basis to manage your process
archive files
- use a windows scheduled task, cron job or job scheduler calendar to run this script at
least once a week to keep archive files from accumulating
- not necessary to migrate archives when upgrading versions of Appian
- used to move Appian log files to backup location and delete older versions
- Must be run on each machine where log files are stored
Data maintenance - Appian Engine files - Answer -Old .kdb files are auto moved to an
archived location when they are no longer in use
Data Maintenance - Cleanup schedules - Answer -cleanup.bat (.sh) and
cleanupArchives.sh (.bat) scripts are intended to be run on a regular basis to preserve
disk space
Adding a related action or view to an existing record type can provide a simple way to
speed development of a new application - Answer -True
