Appian Updated ACD200 Exam Questions and Answers by rosalind

 Two true statements are:

• It is not possible to undo changes from an import to all types of objects. Once a package is imported to an environment, it applies changes to the existing objects or creates new objects based on the package contents. There is no built-in mechanism to revert these changes or delete these objects automatically. Therefore, it is important to test the package in a non-production environment before importing it to production, and to backup any objects that may be overwritten by the import.
• It is possible to import the same package multiple times. A package can be imported to an environment more than once, as long as it does not contain any conflicts or errors that would prevent the import. However, importing the same package multiple times may not have any effect if there are no changes in the package contents or in the target environment since the last import. References: Prepare Deployment Packages, Application Deployment Guidelines

 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

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

 A many-to-many relationship is a type of relationship where multiple records in one table are associated with multiple records in another table. To implement a many-to-many relationship, a third table is needed to store the associations between the two entities. In this case, the third table would store the employee ID and the skill ID for each pair of employee and skill. This design allows for efficient querying and updating of the data, as well as avoiding data redundancy and inconsistency.