Pass the Appian Senior Developer ACD200 Questions and answers with ExamsMirror

When creating a Web API, you need to configure two items in the Administration Console: an API key and a service account. An API key is a unique identifier that is used to authenticate requests to your Web API. You can create and manage API keys in the Administration Console under Integration > API Keys. A service account is a user account that is used to execute the Web API expression rule. You can select a service account in the Administration Console under Integration > Web APIs when you create or edit a Web API. References: [Web APIs], [API Keys], [Service Accounts]

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

 The question is about AMUs (Appian Memory Units), which is a metric that measures the memory usage of a process model. The following statement is correct regarding this metric:

Memory usage is considered low when it is below 100,000 AMUs. This is based on the Appian recommendation that each process model should use less than 100,000 AMUs on average, as higher memory usage can affect the performance or stability of Appian.

The following statements are not correct regarding this metric:

Memory usage is considered low when it is below 10,000 AMUs. This is too low, as most process models will use more than 10,000 AMUs on average, depending on their complexity and data size.

Memory usage is considered low when it is below 1,000 AMUs. This is too low, as even simple process models will use more than 1,000 AMUs on average, depending on their configuration and parameters.

AMUs is not a good measurement for process memory usage. This is not true, as AMUs is a standardized and consistent measurement that reflects the relative memory usage of different process models in Appian.

References:

AMUs (Appian Memory Units)

An index is a data structure that allows for faster retrieval of data from a table based on one or more columns. Indexes increase the performance of read operations, such as select queries, by reducing the number of records that need to be scanned. However, indexes decrease the performance of write operations, such as insert, update, and delete queries, by requiring additional work to maintain the index structure and ensure its consistency with the table data. Therefore, indexes should be used judiciously and only on columns that are frequently used in queries and have high selectivity (i.e., low number of duplicate values). 

 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 most appropriate testing method to achieve this using Appian is Unit Testing. This is because unit testing allows you to test individual components of your application, such as forms, rules, or expressions, in isolation from other components or dependencies. Unit testing can help you verify that your Related Action works as expected for different users and data scenarios, as well as identify and fix any errors or bugs before deploying your application to production. References: Unit Testing

An integration that modifies data can be called from three locations: web API (POST, PUT, DELETE), process model, and SAIL saveInto parameter. These locations allow for sending data to an external system or service and receiving a response.

Web API (POST, PUT, DELETE) are HTTP methods that are typically used to create, update, or delete data on a server. An integration that modifies data can be exposed as a web API with one of these methods, allowing external applications or systems to invoke it through an HTTP request1.

Process model is a graphical representation of a business workflow that consists of nodes and flows. An integration that modifies data can be called from a process model using either an integration node or a Call Integration smart service2. This allows for orchestrating complex workflows that involve data manipulation across different systems or sources.

SAIL saveInto parameter is a property of a SAIL component that specifies an expression to be evaluated when the component is modified by the user3. An integration that modifies data can be called from an interface using the saveInto parameter of a SAIL component. This allows for triggering data changes based on user actions or events on the interface.

 The requirement is to use space efficiently in a user interface where the meaningful order of components is vertical. A columns layout is the most appropriate layout component for this requirement, as it allows you to arrange components into columns that stack vertically on smaller devices. A columns layout also provides options to control the width, alignment, and visibility of each column. The other options are not suitable for this requirement, as they either do not preserve the vertical order of components or do not use space efficiently. References:

Columns Layout

 The most efficient way to achieve the integration between the third-party document scanner and the Appian record list is to create a view between both the [appian].[document] and [appian].[caseData] tables to feed the record. A view is a virtual table that is defined by a query and does not store any data. It can join, filter, aggregate, or transform data from one or more tables and present it in a desired format. A view can be used to simplify complex queries, provide security, or enhance performance. By creating a view, the record can show data from both tables without duplicating or copying any data. Therefore, the correct answer is C.

References:

Relational Database Guidance

Views

 Two places to get information on process model memory usage are:

Process monitoring tab. The process monitoring tab is a feature in the Appian Designer that allows you to monitor and manage the performance and status of process models and instances. You can use the process monitoring tab to view various metrics and statistics about your processes, such as memory usage, execution time, node count, error count, etc. You can also filter, sort, and export the data for further analysis. The process monitoring tab can help you identify which processes have the highest memory footprint and potential performance issues.

Appian Health Check report. The Appian Health Check report is a tool that provides insights into application design patterns and performance risks in your environment. The report covers four areas of your environment: design, user experience, infrastructure, and configuration. The report also includes graphs highlighting historical trends, such as user activity, average response times, and resource utilization. The Appian Health Check report can help you identify which processes have the highest memory consumption and suggestions for mitigating them. References: Process Monitoring Tab, Understanding the Health Check Report