Appian ACD200 Exam Dumps

Correct Answer: ACE

The question is about the testing tools that have packages preconfigured to work with Appian applications and are available via the AppMarket. The following are three testing tools that meet these criteria:

Cucumber: This is a tool that supports Behavior-Driven Development (BDD) and automated testing by allowing users to write test scenarios in plain language and execute them using step definitions. Cucumber has a package called Appian

Cucumber Test Framework that provides a set of predefined step definitions and helper methods for testing Appian applications.

Selenium API: This is a tool that allows users to automate web browser interactions and test web applications. Selenium API has a package called Appian Selenium Framework that provides a Java library and a set of helper methods for

testing Appian applications.

FitNesse: This is a tool that allows users to create and run acceptance tests using wiki pages and tables. FitNesse has a package called Appian FitNesse Testing Framework that provides a set of fixtures and helper methods for testing

Appian applications.

The following are not testing tools that have packages preconfigured to work with Appian applications and are available via the AppMarket:

Jenkins: This is a tool that allows users to automate software development tasks such as building, testing, and deploying applications. Jenkins does not have a package specifically for Appian applications, but it can be integrated with other

testing tools such as Cucumber or Selenium API.

Git: This is a tool that allows users to manage version control and collaboration for software projects. Git does not have a package specifically for Appian applications, but it can be used to store and share test scripts or scenarios created by other testing tools. References: AppMarket Cucumber Selenium API FitNesse

Correct Answer: B

The context type that should be chosen for the Task Report Type is Tasks attributed to user. This is because this context type allows you to display information for pending tasks for each individual in an application. You can filter the tasks by application name, process model name, or task name. This context type also supports drilldown functionality, which enables users to view more details about a specific task or complete it directly from the report. References: Task Report Types

Correct Answer: AB

The question is about the potential causes of a low completion rate of 10% for a process model. The following are two possible causes of this:

The process instances are long-lived compared to the configured days until archival or deletion. This means that the process instances take a long time to complete, and they are archived or deleted before they reach the end event. This

reduces the completion rate, as only the instances that reach the end event are counted as completed.

A large number of instances are encountering process errors, and they are not being addressed by the production support team. This means that the process instances are stuck in an error state, and they cannot proceed to the next step or

the end event. This reduces the completion rate, as only the instances that reach the end event are counted as completed.

The following are not likely causes of a low completion rate:

A large value is configured for days until archival or deletion compared to other process models in your application. This means that the process instances have more time to complete before they are archived or deleted. This should increase

the completion rate, as more instances can reach the end event before they are removed from the system.

A large number of smart service nodes are configured in the process model. This means that the process model has a complex logic or functionality that requires multiple smart services. This does not directly affect the completion rate, as

long as the smart services execute successfully and do not cause errors or delays.

References:

Process Model Metrics

Archiving and Deleting Process Instances