Which statement about application planning components is NOT accurate?

• A. Custom data types, records, forms, and scheduling process models
• B. Personas, records-based data design, process models, and reports
• C. Personas, project budget, custom data types, records, and reports
• D. Databases, web APIs, users, forms, process models, and reports

Answer: (C)

In Appian, planning components are the building blocks you use to design how an application will model data, structure workflows, and present and access information. This includes personas (user roles), data design with custom data types and records, forms to capture or display data, process models to automate tasks, and reports to analyze results. It also covers data storage and integration via databases and web APIs, plus the users who will access the app.

The statement that includes a project budget introduces an item that isn’t part of Appian’s planning components. Budgets are business planning artifacts or project constraints, not elements used to architect or plan an Appian application. The other items listed—personas, data models (CDTs and records), forms, process models, reports, databases, web APIs, and users—are all valid components in Application Planning.