Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Appian
Exam Format
Registration
Validity
Skills this practice test covers
- Construct a form from SAIL components, using local variables and rule inputs.
- Configure dropdowns, grids, buttons and validations so a form behaves as designed.
- Start, debug and publish a process model that uses gateways and smart services.
- Write expression rules with the Appian function library and check them with test cases.
- Connect a record type to its data and design its views, lists and actions.
- Read and write database data through CDTs, data stores and record type queries.
Explore related topics
ACD101 exam content
7 domains · 11 topics · 25 of 72 questions sorted by domain
Appian Development: Interface Design19%
The largest domain covers the screens that users see and fill in. Candidates build interfaces from SAIL components, configure common fields and validations, and test and troubleshoot the result.
Skills tested
- Build layouts from columns, sections and cards, with input and display components.
- Set choiceLabels and choiceValues on a dropdown, and configure grid columns and selection.
- Store user entries in local variables, and pass data in through rule inputs.
- Add validations that stop a form from submitting bad data.
- Follow Appian's interface best practices, such as avoiding redundant queries.
Official topics
- Interface Construction
Appian Development: Process Models17%
Process models automate the work behind an application. Candidates start processes, configure the common workflow nodes and smart services, move data through the process, then debug and publish the model.
Skills tested
- Recognize the ways to start a process, such as a start form, a record action or another process.
- Route a process with XOR, AND and Complex gateways.
- Map data between nodes with Activity Class Parameters and node outputs.
- Chain activities so that a user moves from one task to the next without waiting.
- Debug a process model, then publish a new version of it.
Official topics
- Process Model Fundamentals
Appian Development: Expression Rules15%
Expression rules hold the reusable logic of an Appian application. Candidates read a rule and predict its output, build rules from the Appian function library, and protect them with test cases.
Skills tested
- Predict the output of a rule that uses if, and, or and not.
- Change lists with the append, insert and remove functions.
- Work with dates through today, now and datetext.
- Create test cases that assert the expected output of a rule.
- Name rules by Appian's conventions so that other developers can find them.
Official topics
- Expression Rule Development
Introduction to the Appian Platform14%7 questions
This domain checks how a developer finds help and organizes work in Appian. It covers the main Appian resources, how an application's objects, folders and groups fit together, and the business problems Appian solves, such as process mining and RPA.
Skills tested
- Use Appian's resources, such as the online docs, Appian Max and the knowledge base.
- Organize an application with its application object, folder structure and groups.
- Match business problems to Appian capabilities such as process mining and RPA.
Official topics
- Platform Resources and Documentation
Data Persistence13%9 questions
Appian applications keep their data in a relational database. Candidates read and write that data through CDTs and data stores or through record types, and plan the steps for changing the data model.
Skills tested
- Create a CDT from a database table and connect it through a data store.
- Read and write data with query entities, and aggregate it with record type queries.
- Work out the steps to change the data model, from the table to the CDT and data store.
- Keep queries fast with indexes, filters and paging.
Questions by topic
- Custom Data Types (CDTs)2
- Troubleshooting Data Stores1
- Database Operations3
- Schema Management2
- Data Stores1
Appian Development: Records13%
Record types give users one place to find and act on business data. Candidates connect a record type to its source, design its views and lists, and add actions, relationships and security.
Skills tested
- Configure a record type from an existing data source or with codeless data modeling.
- Design the record list and the record views that users browse.
- Add record actions that start a process from the list or from a record view.
- Relate record types with one-to-many and many-to-one relationships.
- Secure records so that each user sees only the data the user's group may see.
Official topics
- Record Type Configuration
General Appian Principles9%9 questions
The smallest domain covers rules that apply across every application. Candidates tell the design objects and their permissions apart, explain what each environment is for, and follow Appian's naming and agile delivery practices.
Skills tested
- Tell design objects apart, such as process models, records, sites, interfaces and expression rules.
- Set object security with groups and the Admin, Editor and Viewer levels.
- Explain the purpose of the development, test and production environments.
- Apply Appian's naming conventions, such as one prefix on every object in an application.
Official topics
- Platform Fundamentals
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: one to three months of hands-on Appian work, including at least one small use case.
- Recommended: Appian platform training, basic software development skills and relational database experience.
About the ACD101 exam
ACD101 checks that a new developer can build a working application on the Appian low-code platform. Its seven domains cover SAIL interfaces, process models, expression rules, records, data persistence and platform basics. Appian recommends one to three months of hands-on platform work and basic relational database skills first. Passing earns the Appian Associate Developer certification, the entry level of Appian's developer track.
The PlanetCert practice test spreads its questions across all seven domains. The explanations show why one approach works in Appian and another fails, such as when a value belongs in a local variable and when in a rule input. Study Mode suits Expression Rules, where an objective asks what a rule returns. Brainy AI Assistant can walk through a SAIL expression line by line, or explain how data moves between process nodes.
How to earn the certification
- Earns
- Appian Certified Associate DeveloperAssociate
The certification stays valid while its holder meets Appian's maintenance requirements.
- After
- ACD200 Appian Certified Senior Developer
Appian's senior developer certification, the step after Associate in the developer track. It expects more hands-on project experience.
- ACD200 Appian Certified Senior Developer
How to prepare for ACD101
- 1
Build one small app end to end
Create an application with a record type, a form and a process model that saves the form's data. Appian recommends at least one small use case before the exam, and it ties the domains together.
- 2
Start with the interface domain
Appian Development: Interface Design carries the most weight. Rebuild dropdowns, grids, buttons and validations until each parameter is familiar.
- 3
Read expressions before running them
One objective asks for the purpose and output of a rule. Predict what a rule returns, then run it in the expression editor to check.
- 4
Trace one value from form to table
Follow a value from a rule input to a process variable, then into a CDT or a record and the database table. This path links the process, record and data persistence domains.
- 5
Finish with a timed ACD101 run
Take the ACD101 practice test in Timed Mode once all seven domains are covered. Use the explanations to fix weak areas, and ask Brainy AI Assistant why the right answer works in Appian.
Start a timed ACD101run
Who ACD101 is for
- Developers who are building their first applications on Appian.
- Experienced programmers who are switching to a low-code platform.
- Business analysts who are moving into hands-on Appian development.
- IT staff who join a team that already runs Appian.
Typical job titles: Appian developer · Low-code developer · Junior software developer · BPM developer · Business analyst
ACD101 glossary
16 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Activity Class Parameters (ACPs)
- The inputs of a process model node. They take values from process variables or expressions when the node runs.
- Codeless data modeling
- A way to create a record type and its database table inside Appian, without writing SQL or creating a CDT first.
- Custom Data Types (CDTs)
- Data structures defined in Appian, made of named fields, that often map to a table in a relational database.
- Data Store
- An Appian object that connects CDTs to a relational database, so that each mapped CDT becomes an entity that can be read and written.
- Data Sync
- A record type setting that copies the source data into Appian, so that record queries run fast and record relationships can be used.
- Expression rules
- Reusable pieces of logic written in Appian's expression language. Each one takes rule inputs and returns a value.
- Gateways
- Process model nodes that split or join the flow. An XOR gateway, for example, sends the process down exactly one path.
- Local variables
- Variables defined inside an interface or expression, which hold values such as a user's entries while the interface is in use.
- Process chaining
- Linking process nodes so that the process moves to the next task at once, which lets one user finish several steps in a row.
- Process mining
- A capability that reads event logs from business systems to show how a process really runs and where it slows down.
- Record Actions
- Actions on a record list or record view that start a process, for example to create a record or to change its data.
- Record Relationships
- Links between record types, such as one-to-many or many-to-one, that let a query or a view reach related data.
- Rule inputs
- Named inputs that pass values into an interface or an expression rule from the object that calls it.
- SAIL Components
- The building blocks of Appian interfaces, such as fields, grids, buttons and layouts, each written as a function in Appian's expression language.
- Smart Services
- Process model nodes that carry out an action, such as writing data, sending an email or starting another process.
- Test cases
- Saved sets of rule input values, with expected outputs, that check an expression rule still returns the right result after a change.