View Full Appian ACD201 Exam Dumps and Practice Test Dumps.

Question 341. A developer publishes a new version of a process model while several instances of the previous version are still active. What happens by default?

1. Existing active instances continue using the process-model version on which they started
2. Every active instance immediately switches to the newly published version
3. Existing processes are automatically canceled
4. Appian prevents the new version from being published

Correct Answer: 1. Existing active instances continue using the process-model version on which they started

Explanation:

Publishing a new process-model version does not automatically modify instances that are already running. Processes started after publication use the newly published version, while active instances created earlier continue using their original process-model version unless a supported Process Upgrade is deliberately performed. This behavior protects running workflows from unexpected structural changes. It is especially important for long-running processes where instances may remain active for days or months. Senior developers should therefore consider both new and existing instances when introducing significant workflow changes and should not assume that publication alone updates every active process.

Question 342. What is the PRIMARY purpose of Appian Process Upgrade?

1. To archive every instance created from an old process model
2. To update running processes on an earlier model version to components and properties from the latest published version
3. To duplicate every process instance
4. To change process-model security only

Correct Answer: 2. To update running processes on an earlier model version to components and properties from the latest published version

Explanation:

Process Upgrade is designed for situations where active processes running on an older version should adopt changes from the latest published process model. Depending on the change, an upgrade may introduce or remove nodes, update existing node configuration, add process variables, or modify flows. This is different from normal publishing, which affects only new processes. It is also different from editing a single in-flight process manually. Because structural changes can affect active work, developers should carefully compare the source and target process versions and verify that the proposed upgrade is appropriate for the running instances involved.

Question 343. A process node encounters an expression evaluation error during execution. What normally happens?

1. Appian automatically ignores the error
2. The complete application is disabled
3. The affected process pauses at the errored node until the issue is resolved
4. Every previous completed node is rolled back automatically

Correct Answer: 3. The affected process pauses at the errored node until the issue is resolved

Explanation:

Runtime process errors can occur because of invalid expressions, missing privileges, unavailable referenced objects, timeouts, or incorrect configuration. When a node encounters a process error, Appian normally pauses the process at that node so an administrator can investigate rather than allowing the workflow to continue with incomplete or invalid results. Error alerts can direct administrators to the corresponding process instance in Monitor. After the cause is corrected, the affected node or process can often be restarted or otherwise remediated without requiring the entire business process to begin again from its original start event.

Question 344. Changes made to a process model are not appearing when users start new instances. What should the developer check FIRST?

1. Whether the record title was updated
2. Whether all constants are environment specific
3. Whether Health Check completed
4. Whether the changed process model was saved and published as the current version

Correct Answer: 4. Whether the changed process model was saved and published as the current version

Explanation:

Saving design changes and publishing a process model are distinct concepts. If developers modify a process model but do not publish the updated version, newly started processes may continue to use the currently published version rather than the latest draft changes. Appian troubleshooting guidance therefore recommends verifying that the process model was saved and published and that another developer has not subsequently published a different version. Publishing ensures that runtime process initiation uses the intended current design. This check should occur before investigating unrelated interface, database, or record-type configuration when workflow changes simply are not appearing at runtime.

Question 345. In the Monitor view, what does an “Active with Errors” process status indicate?

1. The process has completed successfully
2. The process is still running, but one or more errors have occurred
3. The process has been permanently deleted
4. The process has never started

Correct Answer: 2. The process is still running, but one or more errors have occurred

Explanation:

The Monitor view provides status indicators that help developers understand the current state of process instances. An Active with Errors status means that the process remains active while at least one error has occurred somewhere within its execution. This is different from a fully completed, canceled, paused, or archived process. Developers can inspect the associated errors, process version, active tasks, start time, and other information to determine what happened. Monitoring process status is particularly important for parallel workflows because some branches may continue operating even while another part of the process has encountered a problem requiring administrative attention.

Question 346. Which Monitor operation can a process administrator use to temporarily stop execution of an active standard process without canceling it?

1. Pause
2. Delete
3. Archive
4. Duplicate

Correct Answer: 1. Pause

Explanation:

The Monitor view provides process administrators with several operations for managing runtime processes, including Pause, Resume, Cancel, and Delete. Pausing is appropriate when execution should temporarily stop without canceling the process permanently. Once the reason for the pause has been addressed, the process administrator can resume it. Canceling, by contrast, stops the process as a cancellation action, while deleting removes process information according to the supported management behavior. Administrative runtime controls should be used carefully in production because they directly affect in-flight business work and potentially any tasks or subprocesses associated with the selected process instances.

Question 347. Which prefix is used to reference a runtime process property such as the process initiator inside a process expression?

1. pm!
2. rv!
3. pp!
4. fv!

Correct Answer: 3. pp!

Explanation:

Process properties describe runtime information about a particular process instance and are referenced using the pp! domain. Available properties include values such as the process ID, name, priority, initiator, designer, start time, deadline, and time zone. For example, pp!initiator refers to the user who started the process. These properties differ from normal process variables because Appian supplies them as part of the runtime process context. They can be useful when expressions need information about the instance itself rather than application data explicitly passed through process variables. Developers should distinguish process properties from process-model properties and process variables.

Question 348. A developer renames a process variable. Which type of reference may require MANUAL updating?

1. Node input mappings
2. Expressions that explicitly reference the old process-variable name
3. Node output mappings
4. Gateway mappings that Appian automatically updates

Correct Answer: 2. Expressions that explicitly reference the old process-variable name

Explanation:

Renaming a process variable does not guarantee that every textual reference is automatically rewritten. Appian automatically updates several structured mappings, including node input and output mappings and certain gateway references. However, expressions, conditions, rules, and custom output expressions that explicitly contain the old pv! reference may require manual changes. After renaming a process variable, developers should validate the process model to identify broken references and update them. This is particularly important in large processes where the variable may appear in many expressions. Validation helps prevent runtime failures caused by references to a process variable name that no longer exists.

Question 349. In autoscaled process monitoring, what does a green node indicate?

1. The node was skipped
2. The node completed
3. The node has never activated
4. The node is currently active

Correct Answer: 4. The node is currently active

Explanation:

Autoscaled process monitoring uses visual node states to help developers understand execution. A green border indicates an active node, while blue indicates completion. A red slash identifies a node where one or more errors occurred, and a gray slash indicates a skipped node. Nodes that have not yet activated have no status color. These visual indicators make it easier to understand where execution currently sits in a complex process without relying only on textual logs. Developers can combine the graphical status with process details, variable history, error information, and step-by-step playback for deeper troubleshooting.

Question 350. What is a benefit of step-by-step playback when troubleshooting an autoscaled process?

1. It automatically repairs all errors
2. It lets developers inspect node execution and variable changes sequentially through the process
3. It permanently changes the process model
4. It automatically republishes the process

Correct Answer: 2. It lets developers inspect node execution and variable changes sequentially through the process

Explanation:

Step-by-step playback provides a chronological way to investigate how an autoscaled process actually executed. Developers can advance through nodes, review node timing, identify errors, and inspect which process variables changed at each step. This is particularly useful when a final incorrect value cannot be explained by simply looking at the process’s final state. By walking through execution in sequence, a developer can identify where data changed unexpectedly or where a node took unusually long. Playback is a diagnostic capability; it does not itself repair the process or alter the published design.

Question 351. A process evaluates today() in a time-sensitive expression. Which configuration can affect the date Appian considers to be “today” in that process?

1. The process time zone context
2. The record type primary key
3. The application description
4. The process-model folder name

Correct Answer: 1. The process time zone context

Explanation:

Date and time behavior in process expressions can depend on the process’s time zone context. Functions such as today(), now(), local(), and gmt() use process time-zone context when evaluated within a process. This matters when applications serve users across geographic regions because the same absolute instant can belong to different calendar dates in different time zones. Developers should design date-sensitive deadlines, notifications, and calculations with the intended time-zone behavior in mind. A workflow that seems correct in one region can produce unexpected results elsewhere if time-zone context is ignored during design and testing.

Question 352. What time zone does a subprocess normally use?

1. Always UTC
2. The time zone configured on the application’s site
3. The parent process’s time zone
4. The database server’s time zone

Correct Answer: 3. The parent process’s time zone

Explanation:

Appian subprocesses inherit the time-zone context of their parent process. This helps maintain consistent date and time evaluation across a workflow that has been decomposed into reusable process models. If the parent process is operating within a particular time-zone context, expressions evaluated by the subprocess continue using that context rather than independently changing to another configured process-model time zone. This behavior is especially important when subprocess logic calculates dates, deadlines, or user-facing time values. Senior developers should understand time-zone inheritance when troubleshooting discrepancies between parent and child workflows or when applications are used across multiple regions.

Question 353. What is the PRIMARY purpose of configuring a deadline on a process activity?

1. To automatically encrypt task data
2. To permanently terminate the process at that time
3. To delete the node after a certain period
4. To provide deadline information that can be used in task/process reporting and related logic

Correct Answer: 4. To provide deadline information that can be used in task/process reporting and related logic

Explanation:

A deadline configured on an activity records when that work is expected to be completed. Appian notes that deadline information is primarily useful in reporting, where task reports can show whether activities are due or overdue. A deadline can be configured relative to task issuance or as a specific date. It does not inherently mean that Appian will terminate the activity when the deadline arrives. If the business requires an action after a delay—such as interrupting a task or escalating it—the developer must configure the appropriate timer exception or escalation behavior separately.

Question 354. What happens when “Refresh default values every time the task form is viewed” is enabled on a task?

1. Default values are reevaluated whenever the task form is viewed
2. The task automatically completes when opened
3. All process variables are reset to their original values
4. The process model republishes itself

Correct Answer: 1. Default values are reevaluated whenever the task form is viewed

Explanation:

By default, task-form default values may reflect the values evaluated when the task was originally issued. The execution option to refresh default values causes those defaults to be evaluated again each time the task form is viewed. This can be useful when a form displays information that may change while the task remains outstanding. Developers should use the option intentionally because reevaluation may involve expression rules or other logic that adds processing each time the user opens the task. It also affects user expectations if default values can change between visits before the task is submitted.

Question 355. Which prefix references a process model property such as the process model version in supported process-report expressions?

1. pv!
2. pm!
3. pp!
4. ri!

Correct Answer: 2. pm!

Explanation:

Process model properties describe the process-model definition rather than a specific running instance. They use the pm! prefix in supported expression contexts. Examples include the process model’s ID, name, description, version, creator, time zone, and UUID. By contrast, pp! refers to properties of an individual runtime process instance, such as its initiator and start time, while pv! refers to process variables. Distinguishing these domains helps developers write clear reporting and process expressions because the model definition, runtime process instance, and application data represent different levels of information.

Question 356. Which statement about the process Priority property is correct?

1. It always forces higher-priority processes to execute before other processes
2. It automatically changes task assignments
3. It is descriptive information available to designers and does not itself control how Appian executes the process
4. It determines the process model’s security

Correct Answer: 3. It is descriptive information available to designers and does not itself control how Appian executes the process

Explanation:

Appian exposes a process Priority property, but documentation describes it as a descriptive value rather than a scheduler that changes how the platform processes workflow instances. Developers can use the property in reports, expressions, or application logic when they need to classify or communicate business importance. However, simply setting a process to a higher descriptive priority does not itself guarantee preferential execution by the platform. The same principle applies to certain other process properties, such as deadline values, which provide information that application logic can use but do not independently implement complex runtime behavior without additional configuration.

Question 357. What does numprocessesforprocessmodelforstatus() return?

1. The total number of users who can initiate a process
2. The memory used by one process instance
3. The number of nodes inside a process model
4. The number of non-deleted, non-archived process instances for a specified model and status

Correct Answer: 4. The number of non-deleted, non-archived process instances for a specified model and status

Explanation:

numprocessesforprocessmodelforstatus() can be used to obtain the number of process instances for a particular standard process model that have a specified status, such as completed. The current user must have at least Viewer permission to the referenced process model. Deleted and archived processes are not included in the returned count. Because it works with process-instance information, the function can support monitoring-oriented expressions where a simple count is sufficient. Developers should also review compatibility restrictions before using process-oriented functions in specialized contexts such as custom record fields, reports, or autoscaled process configurations.

Question 358. A developer calls numprocessesforprocessmodelforstatus() for an autoscaled process model. What limitation should be considered?

1. The function only returns data when the process model does not have autoscale enabled
2. The function automatically disables autoscale
3. The function converts autoscaled processes to standard processes
4. The function deletes archived instances before returning a result

Correct Answer: 1. The function only returns data when the process model does not have autoscale enabled

Explanation:

Process-related expression functions do not necessarily support autoscaled execution and monitoring in the same way they support traditional process models. Appian documents that numprocessesforprocessmodelforstatus() only returns process data when the referenced process model does not have autoscale enabled. Autoscaled workflows have dedicated monitoring capabilities designed for their higher execution volumes. Senior developers should always check feature compatibility rather than assuming an older process-reporting or process-query function will behave identically with autoscaled processes. For autoscaled workloads, Monitor and its autoscaled process metrics are generally the more appropriate operational tools.

Question 359. A process reaches an End Event, but another parallel branch is still active. Why might the overall process remain active?

1. End Events work only in subprocesses
2. Appian requires all active flows to finish unless a terminating end behavior ends the process
3. Every process must contain exactly one End Event
4. Parallel branches are automatically ignored

Correct Answer: 2. Appian requires all active flows to finish unless a terminating end behavior ends the process

Explanation:

Reaching one End Event does not necessarily mean that an entire process has completed. If other parallel paths remain active, Appian can continue treating the process as active until all required flows reach their end points. A terminating End Event provides different behavior: reaching that event can formally complete the process even when other active flows exist. Appian recommends using terminating End Events for many common process designs unless the business workflow intentionally expects independent active branches to complete separately. Developers should review parallel routing carefully when a process appears to be stuck active despite one visible path already reaching an end.

Question 360. A production process instance contains an incorrect variable value and is paused at an error. What is the BEST remediation approach when the process does not need to restart from the beginning?

1. Delete the entire process model and recreate it
2. Publish a new application and ignore the active instance
3. Modify the affected in-flight process data as appropriate and restart or resume the relevant node
4. Cancel every running instance of the process model

Correct Answer: 3. Modify the affected in-flight process data as appropriate and restart or resume the relevant node

Explanation:

Production errors do not always require abandoning an entire in-flight business process. Appian provides monitoring and remediation capabilities that allow authorized administrators to inspect a process, correct certain runtime values, and restart or resume affected execution. This is useful when a process has already completed significant valid work and the error is isolated to one node or incorrect piece of data. Administrators should understand the cause before changing production process state, particularly when a failed node may already have produced external side effects. Targeted remediation preserves valid completed work while allowing the workflow to continue after the underlying problem is corrected.