You need to update an existing Appian application.The application needs to be responsive and compatible with a variety of screen widths. For example:phone/tablet browser, Appian mobile app, desktop monitor.Which two functions/parameters should you consider when updating the interfaces? (Choose two.)
Answer(s): A,D
The two functions that most directly support responsive UI across varying screen widths are A (stackWhen) and D (a!isPageWidth()). - Rationale: - stackWhen controls when a multi-column layout stacks vertically, which directly affects responsiveness. - a!isPageWidth() lets you branch logic based on the actual page width (phone/tablet/desktop), enabling width-specific UI adjustments. - The option B (a!isNativeMobile()) answers environment (native app vs web) rather than width, and is not by itself a width-responsive mechanism. C is not a runtime width check.
You're developing a user input form for a financial services application.One component of this form requires you to embed an external site (in the form of a URL) that can receive inputs from Appian and return updates as the user interacts with it.What should you do?
Answer(s): C
A component plug-in is required because the standard Web Content Component in Appian only displays external sites and does not support direct two-way interaction or input/output event handling. A plug-in enables custom integration to allow input and receive updates as users interact with the embedded site.
You're refining a story for a centralized distribution center that extends the current application by allowing inventory managers to review orders.These orders are created through a record action that various workshops access from a shared Appian site.Which consideration best suits this use case?
Identifying the personas (such as inventory managers and workshop users) ensures you can design and maintain an appropriate Appian group structure for managing access and permissions, which is critical for a centralized application accessed by multiple roles.
A recent Health Check report of your application indicates an increased risk of large context size in the interfaces.What are two possible contributors to this risk? (Choose two.)
Answer(s): A,B
Performing data transformation inside the interface can increase the amount and size of context data stored, raising context size risk.Multiple local variables holding duplicate data unnecessarily inflate the interface's memory footprint, contributing to large context size.
The synced record Task has a self-referential relationship defined in the column parentTaskId. There is a many-to-one record relationship between the id and parentTaskId called parentTask.For a given task ID, you need to return the task name and the parent task name.What should you do?
Answer(s): B
Using a!queryRecordType() with a filter on the task ID and specifying both recordType!Task.name and recordType!Task.parentTask.name in the fields will efficiently return both the task name and its parent task name in a single query.
You're creating a synced record type which will store read-only data from an external web service. Data in the external system is updated nightly, and the latest information must be available to users in the morning. Currently there are approximately 150,000 entries in the external system, and this number is not expected to change significantly.There is an existing integration object and associated expression rule, which when called returns the complete dataset from the external system.What are two configurations that you must apply to ensure that the latest and complete record set is available? (Choose two.)
Answer(s): A,C
Scheduling a nightly full sync ensures the record type is updated with the latest data after the external system refreshes.Disabling the row limit in Source Filters allows the complete dataset to be retrieved and synced, ensuring all entries are available.
You need to display information for pending tasks for each individual in an application. The tasks may be for a single specific application.Which context type should you select for the Task Report Type?
Answer(s): A
"Tasks attributed to user" is the correct context type, as it allows you to display pending tasks assigned to each individual in the application.
You're creating a point-of-sale (POS) system for a customer which can associate the items in a transaction to a customer based on a membership number. The item stock table and the customer sales record are hosted elsewhere and need to be written to via POST APIs from an Appian process model. This all occurs within a transaction process model that you're creating.Which two steps should you perform to design your process model to improve process memory? (Choose two.)
Answer(s): B,D
Creating the POST API calls as asynchronous subprocesses allows them to run independently,reducing memory usage in the main process.Adding a terminate process node at the end ensures the process completes and releases memory as soon as its work is finished.
Post your Comments and Discuss Appian ACD201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the ACD201 content, but please register or login to continue.