Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

APPIAN DEVELOPER STUDY GUIDE 2025/2026 QUESTIONS WITH ANSWERS MARKED A+, Exams of Object Oriented Programming

Liberty University (LU)Object Oriented Programming

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 - Oneto-One Nested Many-to-One Nested One-to-Many Flat Many-toMany Flat

Typology: Exams

2024/2025

Available from 08/25/2025

WuodKowino
WuodKowino 🇺🇸

3.9

(11)

26K documents

1 / 13

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
APPIAN DEVELOPER STUDY GUIDE 2025/2026 QUESTIONS
WITH ANSWERS MARKED A+
✔✔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.
✔✔Appian Data Design - Modifying an XSD provides - ✔✔- Advanced configuration
- Better support for design preferences
- Additional data type options
✔✔Designers can create web APIs to expose Appian data and objects to external
systems - ✔✔True
✔✔Appian Architecture - user Interfaces - ✔✔1. Sites and Tempos
2. Embedded UIs
3. Designer interface
4. Admin Console
✔✔Appian Architecture - Appian Engines - ✔✔* Real time in memory data bases
* Stored meta data for appian design objects
* Stores run-time data for process instances
* Each engine has in-memory data base to stores data about objects
✔✔Appian Architecture - How many appian engines are there? - ✔✔1. totally 15
engines
2. 9 Individual engines
3. 3 pairs of process execution and process analyticcs engines (scales upto 32 pairs
based on performance requirement)
✔✔Appian Architecture - CO - Content Engine - ✔✔* This engine stores meta data and
security settings for documents and their organisational structure. like communities ,
knowledge centres and folders.
* It also stroes the def of
pf3
pf4
pf5
pf8
pf9
pfa
pfd

Partial preview of the text

Download APPIAN DEVELOPER STUDY GUIDE 2025/2026 QUESTIONS WITH ANSWERS MARKED A+ and more Exams Object Oriented Programming in PDF only on Docsity!

APPIAN DEVELOPER STUDY GUIDE 2025/2026 QUESTIONS

WITH ANSWERS MARKED A+

✔✔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. ✔✔Appian Data Design - Modifying an XSD provides - ✔✔- Advanced configuration
  • Better support for design preferences
  • Additional data type options ✔✔Designers can create web APIs to expose Appian data and objects to external systems - ✔✔True ✔✔Appian Architecture - user Interfaces - ✔✔1. Sites and Tempos
  1. Embedded UIs
  2. Designer interface
  3. Admin Console ✔✔Appian Architecture - Appian Engines - ✔✔* Real time in memory data bases
  • Stored meta data for appian design objects
  • Stores run-time data for process instances
  • Each engine has in-memory data base to stores data about objects ✔✔Appian Architecture - How many appian engines are there? - ✔✔1. totally 15 engines
  1. 9 Individual engines
  2. 3 pairs of process execution and process analyticcs engines (scales upto 32 pairs based on performance requirement) ✔✔Appian Architecture - CO - Content Engine - ✔✔* This engine stores meta data and security settings for documents and their organisational structure. like communities , knowledge centres and folders.
  • It also stroes the def of
  • roles, constants, Application and data stores
  • The actual content of the document stores in file system not in Content engine. ✔✔Appian Architecture - CS - Collaboration Statistics - ✔✔contains statistics on document usage and storage ✔✔Appian Architecture - NO - Portal Notifications - ✔✔Stores various information about notifications including system notification settings ✔✔Appian Architecture - NE - Email Notification - ✔✔* Responsible for tracing who should receive email notifications ✔✔Appian Architecture - PE - Personalization - ✔✔* Stores information about
  • Users
  • Groups
  • Group Membership
  • Group Types ✔✔Appian Architecture - PD - Process Design - ✔✔Stores all information about process model design information ✔✔Appian Architecture - PO - Portal - Older feature - ✔✔supports older features like - App's portal interface like pages ✔✔Appian Architecture - CH - Channels - older feature - ✔✔Supports older features like
  • App's portal interface - including portal types displayed on portal pages ✔✔Appian Architecture - DF - Forums - older feature - ✔✔Supports older features like - App's portal interface - like topics, messages posted discussion forms - this not includes discussions in Tempo interface ✔✔Appian Architecture - PX - Process Execution - ✔✔Process execution engine responsible for executing and running process instances ✔✔Appian Architecture - PA - Process Analytics - ✔✔Process analytics engine responsible for keeping all relevant information may be used for process reports ✔✔Appian Architecture - Check pointing with Appian engines will create the following type of the file - ✔✔kdb format ✔✔Appian Architecture - Search Server using elastic search - ✔✔true ✔✔Appian Architecture - What are all the web servers are used - ✔✔Apache and Ms IIS server

✔✔Process Model - Task Acitivity - Purpose of the Quick Task - ✔✔Quick Task will be shown as related action on process baked records ✔✔Main place to view rule issues is? - ✔✔Design error log ✔✔Appian Testing - When should you test? - ✔✔1. When you introduce new functionality

  1. Update an application ✔✔Appian Testing - types of automated testing - ✔✔1. Expression Rule Testing
  2. Automated Functional Testing
    • Fitnesse
    • Cucumber ✔✔Integrations - What is connected System? - ✔✔Each Connected System represents an external system you want Appian connect to. ✔✔Integrations - Why use a Connected System design object? - ✔✔The connected system object uses the properties of the external system.Such as its base URL and authendication. Once you create a connected system object, you can reuse it for different use cases that connect to the same external system. ✔✔Integrations - Connected Systems - authendication types - ✔✔1. None
  3. Basic
  4. API Key
  5. AWS Signature V
  6. Google Service Account (JSON will be used for configure connections)
  7. OAuth 2.0 Client Credentials Grant (On Behalf of the Application)
  8. OAuth 2.0 Authorization Code Grant (on Behalf of the User) ✔✔Integrations - Connected Systems - authendication type - API Key - ✔✔The API Key is a unique code provided by the system to identify the user or application. When you use an AOI key with your connected system, You must specify three things.
  9. If the key is sent as an HTTP header or query parameter
  10. The header or parameter name (The key identifier for the API key )
  11. The value of the API Key ✔✔Integrations - Import Customization - ✔✔The environment-specific values of certain objects can be changed during import. This is completed using a .properties file. The import customization file contains all the values that can be customized for the objects and settings in your application. ✔✔Integrations - GET Integrations can be used in - ✔✔Called like expressions
  12. Expressions
  1. Process Models
  2. Interfaces
  3. Record Data ✔✔Integrations - POST Integrations can be used in - ✔✔Called like Smart Rules
  4. Only used in "SaveInto" parameter of a component ✔✔Integration - An integracation can be called from process model by using - ✔✔Call Integration Smart Service ✔✔Integration - Records - What data source option do you need to select if you are building service baked record? - ✔✔Web Service ✔✔Integration - Records - Without batch syncing, you can only build records that contain upto 1000 rows of data, once you enable batch syncing, you will bw able to build larger records - ✔✔True ✔✔If the integration and record data source expression use different status code for out-of-bounds error, what should you do? - ✔✔Edit the code in record data source expression ✔✔What objects can you build as part of the service backed reord wizard flow? - ✔✔1. Connected System
  5. Integration
  6. Record Data Source expression ✔✔Web API - What ia Web API? - ✔✔Web APIs allows us to export Appian objects to external systems ✔✔Web ApI - Can we configure rule inputs for Web APIs? - ✔✔No, we can not configure rule inputs for Web API. we can use the following components
  7. Query Parameters
  8. Headers
  9. Body ✔✔Web API - Methods of authendication - ✔✔1. Basic Authendication
  10. API Key
  11. O Auth Client Credentials Grants ✔✔Web API - Which of the authendication methods use service accounts - ✔✔1. API Keys
  12. OAuth Client Credentials Grant

✔✔Appian delivery - Methodology ceremonies - ✔✔- Daily Scrum

  • Sprint Planning
  • Sprint Review
  • Backlog Refinement
  • Sprint Review
  • Sprint Retrospective ✔✔Appian Delivery - Release strategies - ✔✔1. Pilot Release
  1. Read Only Release
  2. Parallel Run ✔✔ Successful first projects deliver results that are: - ✔✔- Quick, with a short time-to- impact reducing the likelihood of losing momentum
  • Measurable, giving leaders the confidence to approve further projects
  • Contagious, with a compelling solution triggering rapid user adoption ✔✔Prioritize Project Opportunities - ✔✔dummy slide ✔✔Project Factors- Project complications - ✔✔1. Extensive Data ETL
  1. Complex Data Visualization Across Systems
  2. Complex Data Manipulation
  3. Backend Process Management ✔✔Project Factors- Success factors - ✔✔1. Automate complex business processes
  4. Access data from or send data to legacy systems
  5. Create unified user experience across systems
  6. Deliver functionality rapidly
  7. Support business processes across the organization
  8. Enable target users to access multiple systems
  9. Integrate pre-built or custom-built AI systems
  10. Engage or inform multiple stakeholders across workflows
  11. Perform mobile data entry (inclusive of review and approval) ✔✔Project Factors - First step to selecting a successful project - ✔✔Finding oppertunities to address business processes ✔✔If your project has large scsope, what is a best practice you can use that will lead to a successfull project? - ✔✔Break up large scope into smaller projects ✔✔Intergrations - HTTP Status code types - ✔✔ 100 - Informational 200 - Success 300 - Redirect 400 - Client Side Error 500 - Server Side Error

✔✔Integrations - HTTP Status code 401 - ✔✔Unauthorised Access ✔✔Integrations - HTTP STatus Code 404 - ✔✔Not found ✔✔Integrations - Authendication - Two ways to configure authendication - ✔✔1. Connected Systems

  1. Secure credentials Store ✔✔Integrations-Authendication - Where can Secure Credentials Store configured - ✔✔Appian Admin Console ✔✔Integrations-Authendication - Expression function - Access Secure Credentials Store
  • ✔✔a!scsField ✔✔Integrations - Node used to call integrations from process model - ✔✔Call Integration ✔✔Integration - Using in Expression - ✔✔Using an expression only works for querying data in an integration. ✔✔Integration - Query Data - ✔✔Only works with Expression ✔✔Integration - Modifies Data - ✔✔1. Works with "Call Integration" smart service in process model
  1. Submit from Interface ✔✔Integration - Modifies data - Additional parameters added to integration by default - ✔✔1. OnSuccess
  2. OnError ✔✔Integration - Common methods of performing integration over HTTP - ✔✔1. REST - "Call Integration"
  3. SOAP(WSDL) - "Call Webservice" ✔✔Three Anti Patterns to avoid - ✔✔1. Custom Task Management
  4. Custom User Interfaces (Third party UX)
  5. Avoid Data only applications (Extracting, Transforming and Loading) ✔✔Appian Task Plugins - ✔✔1. Task Reassignments Allow users to reassign multiple active tasks
  6. Task Functions Allow developers to retrieve most task details and attributes by using a set of functions with Task ID as input.

✔✔What are process related information stored in memory - ✔✔1. Process Variables

  1. Task Properties
  2. Process Properties
  3. Process History ✔✔Process Data management best practices - ✔✔1. Processes with task data : 3 Days
  4. Processes that are automated/utility : delete after completion ✔✔Running the sub processes as "sub process" node will always run in the same process execution engine - ✔✔true ✔✔Running the sub processes as "Start Process" node will always run in different process execution engine - ✔✔true ✔✔Process Management Best Practices - ✔✔1. Build record-centric processes that are short lived and set to archive after three days
  5. Use sub-processes to break up larger workflows into segments that can be archived or deleted, Which use the "Start Process" smart service where practical
  6. Look to repeatable design patterns into multi purpose workflows. ✔✔Plug-in guidelines - ✔✔1. Use OOTB if requirements are nearly met
  7. Build off existing plug ins
  8. Try to use an existing plugin before building your own
  9. Throughly test every plug-in, before each release ✔✔Plug-in Risks - ✔✔1. Higher chance of support incients ✔✔3rd Party plug-ins must be watched for - ✔✔1. Thread safety
  10. Performance at scale
  11. Extra resource consumption ✔✔Which time scale refers to the term "Short Lived Process" - ✔✔Milliseconds, Seconds and Minutes ✔✔Valid reason to consider using a plug in (Such as Execute stored procedure) - ✔✔Your performance test a process that does not meet your response time requirements. ✔✔Benifits of using sub-process - ✔✔1. Collaborative developement
  12. Reusablity
  13. Reduced process duration
  14. Reduced memory usage

✔✔Appian Health Check purpose - ✔✔1. Examines an Appian Instance

  1. Generates a report
  2. Identifies the risks ✔✔Appian Health Check availablity - ✔✔From 19.4 health included with Appian by default. No need to deploy separately. ✔✔Appian Health Check can be - ✔✔1. Configured
  3. Run Manually
  4. Regularly Scheduled ✔✔Appian Health Check run schedule - non prod - ✔✔* Run Health Check as part of your sprints
  • Every two weeks
  • Also should be part of pre-deployment check list ✔✔Appian Health Check run schedule - prod - ✔✔1. Run health check once a month
  1. Before deployment of applications ✔✔Appian Health Check - Report sheets - ✔✔1. Summary
  2. Details
  3. Dashboard
  4. Process Sizing ✔✔Appian Health Check - Dashboard long running charts - ✔✔1. Slow Queries
  5. Record Summary viewes
  6. Record Lists ✔✔Appian Health Check - Process Sizing Tab - ✔✔1. Record process instance memory usage
  7. Helps estimate future memory usage
  8. Shows if process engine servers are properly sized ✔✔Appian Health Check - What is the maximum threshold of high risks that should be allowd in production environments? - ✔✔Zero ✔✔Appian Health Check - Application risk categories identified by health check report - ✔✔1. User Experience
  9. Configuration
  10. Design
  11. Infrastructure

✔✔Appian Data Design - Top Down - Disadvantages - ✔✔1. Direct editing of XSD file is required to support advanced DB features

  1. Tables and columns are lowercased by default. Difficult to read.
  2. 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