ACD200 Online Practice Questions and Answers

Correct Answer: B

The minimum privilege the end user should have to execute a web API is Viewer. A web API is an Appian object that exposes data and services to outside systems through an HTTP endpoint. A web API can be configured with different security role maps that control which users can see or modify it and its properties. A user must have at least Viewer permissions to a web API in order to execute it. Viewer permissions allow the user to view and run the web API, but not to edit or delete it. References: Web APIs, Web API Security

Correct Answer: ABE

Correct Answer: A

Correct Answer: AC

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).

Correct Answer: D

A materialized view is the best option to show joined data from 5 tables that contain a large number of rows and could generate a large result set after executing the joins. A materialized view is a physical table that holds the results of the SQL that a view would normally be constructed from and can be generated periodically. A materialized view can improve performance by reducing the execution time of complex queries that involve multiple joins, aggregations, or calculations. A materialized view can also reduce the load on the database server by storing the query results in advance. A materialized view can be refreshed at regular intervals or on demand to reflect the changes in the underlying tables. References: [Materialized Views], [View Performance]

Correct Answer: C

The question is about the default limit for maximum number of node executions in a repeating step in a process. The default limit is 1000, as it is the value of the system property conf.bpm.maxNodeExecutionsPerInstance, which controls how many times a node can be executed in a single process instance. This limit is intended to prevent infinite loops or excessive node executions that could affect the performance or stability of Appian. The other options are not correct, as they are either too high or too low. References: Repeating Steps in Processes System Properties Reference

Correct Answer: BCE

The question is about improving the memory usage of a process model. The following are three things you can do for this purpose: Reduce the number of process variables. This means using fewer or smaller process variables to store data in the process model, as each process variable consumes memory and resources. You should only use process variables that are necessary for the process logic or data flow, and avoid storing redundant or temporary data in process variables. Avoid storing large blocks of text in process variables. This means using other methods to store or handle large blocks of text, such as documents, constants, or expression rules, rather than process variables. This can reduce the memory usage of the process model, as large blocks of text can consume a lot of memory and resources, and affect the performance or stability of Appian. Pass data directly to activity nodes and smart services. This means using parameters or inputs to pass data to activity nodes and smart services, rather than process variables. This can reduce the memory usage of the process model, as parameters or inputs are only evaluated when needed, and do not persist in memory. The following are not things you can do to improve the memory usage of a process model: Configure process variables to be parameters. This is not possible, as process variables and parameters are different types of data elements in a process model. Process variables are used to store data throughout the process model, while parameters are used to pass data to or from a subprocess or an expression rule. Split large nodes into many smaller nodes. This is not advisable, as it can increase the complexity and maintenance overhead of the process model, and may not reduce the memory usage significantly. You should only split nodes when it makes sense for the process logic or functionality, and not for the sake of reducing node size. References: Process Variables Documents Constants Expression Rules Parameters

Correct Answer: A

A joining table can be used to hold instances of Student/Class relationships, so that it can be supported in Appian and remain in at least First Normal Form. A joining table is a table that contains only foreign keys that reference the primary keys of other tables. A joining table can be used to model a Many-to-Many relationship between two entities, such as Student and Class. For example, a joining table called Enrollment could have two columns: Student_ID and Class_ID, which reference the primary keys of the Student and Class tables respectively. Each row in the Enrollment table represents an instance of a student enrolled in a class. References: [Joining Tables], [Many-to-Many Relationships], [First Normal Form]

Correct Answer: AD

A sprint retrospective is a meeting that takes place at the end of each sprint, where the team reflects on what went well and what can be improved in their work process. The purpose of the retrospective is to identify and implement actions that can enhance the team's performance and satisfaction in future sprints. Two basic questions that can help facilitate the retrospective are: What went well? and What didn't go well and can be improved? These questions allow the team to celebrate their achievements, acknowledge their challenges, and generate ideas for improvement.

Correct Answer: BC

The question is about troubleshooting slow response times on a SAIL interface. The following are two potential causes of the performance issues:

Multiple a!save operations: This means that the interface has multiple expressions that use a!save to store data in variables or update components. This can cause performance issues, as each a!save operation triggers a server round-trip

and refreshes all dependent components on the interface. You should minimize the use of a!save operations and use local variables or component parameters instead.

Configuration of refresh variables: This means that the interface has components that use refresh variables to control when they should be refreshed based on changes in other components or variables. This can cause performance issues,

as some components may be refreshed unnecessarily or too frequently due to incorrect or excessive refresh variables. You should optimize the refresh variables and use them only when needed.

The following are not likely causes of slow response times on a SAIL interface:

Multiple rule inputs: This means that the interface has expressions that use rule inputs to pass data or parameters to expression rules. This does not affect the performance of the interface, as rule inputs are evaluated on the server and do not

cause additional server round-trips or refreshes. Stacked button layout: This means that the interface has a layout component that arranges buttons in a vertical stack. This does not affect the performance of the interface, as it is a simple

layout component that does not require any server interaction or refresh logic.

References:

a!save()

Refresh Variables

Rule Inputs

Stacked Button Layout