Appian ACD200 Online Practice Questions and Exam Preparation

Appian ACD200 Online Questions & Answers

• Question 61:

  You have been asked to produce a Tempo report, with the following requirements:

  The report should display in Appian.

  The data is held in a business database, but performance in Appian is a key requirement. Which three actions can you take to minimize the performance impact of your report? (Choose three.)

  A. Display the report as a task report on the Tasks tab.
  B. Limit the number of series values and categories in the report.
  C. Use local variables in your report interface to avoid redundant database queries.
  D. Use the query process analytics function to retrieve the data.
  E. Perform aggregation in the database using a view prior to reading the data into Appian.
  B. Limit the number of series values and categories in the report.
  C. Use local variables in your report interface to avoid redundant database queries.
  E. Perform aggregation in the database using a view prior to reading the data into Appian.

  ---

  Explanation/Reference:

  The three actions that can be taken to minimize the performance impact of the Tempo report are: Limit the number of series values and categories in the report. This is because having too many series values and categories can make the report difficult to read and render, as well as increase the amount of data that needs to be transferred from the database to Appian. A good practice is to limit the number of series values to 10 or less, and the number of categories to 20 or less. Use local variables in your report interface to avoid redundant database queries. This is because local variables can store the results of database queries and reuse them in multiple places within the interface, reducing the number of times the database is accessed. A good practice is to use local variables for common filters, aggregations, or calculations that are used in multiple charts or grids. Perform aggregation in the database using a view prior to reading the data into Appian. This is because performing aggregation in the database can reduce the amount of data that needs to be transferred from the database to Appian, as well as leverage the database's optimization capabilities. A good practice is to create a view in the database that performs the aggregation and then query that view using Appian. References: Report Performance Best Practices

• Question 62:

  Which two statements are true for importing Appian applications? (Choose two.)

  A. It is not possible to undo changes from an import.
  B. It is not possible to import the same application multiple times.
  C. Applications from an earlier version of Appian can be imported into later versions of Appian.
  D. Importing a published application changes its state to Unpublished and need to be published again.
  A. It is not possible to undo changes from an import.
  C. Applications from an earlier version of Appian can be imported into later versions of Appian.

• Question 63:

  There is a need to relate two entities in the data structure: Employee and Skill.

  Employees can have multiple skills, and a single skill can relate to multiple employees.

  What kind of relationship would these entities have, and what is the minimum number of tables required to implement the design, according to Appian best practices? (Choose the best answer.)

  A. One-to-many; 2 tables
  B. Many-to-many; 2 tables
  C. Many-to-one; 2 tables
  D. Many-to-many; 3 tables
  D. Many-to-many; 3 tables

  ---

  Explanation/Reference:

  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.

• Question 64:

  Which XSD element is NOT supported within an Appian CDT? (Choose the best answer.)

  B

  ---

  Explanation/Reference:

  The xsd:key element is not supported within an Appian CDT. This element is used to define a key constraint for an element or a group of elements. Appian does not support key constraints in CDTs, as they are not relevant for data storage or manipulation. Instead, Appian uses primary keys and foreign keys to enforce uniqueness and referential integrity in CDTs. These keys are specified using the @Id and @JoinColumn JPA annotations, respectively. References: Supported XSD Elements and JPA Annotations

• Question 65:

  You have configured a process model to send an email to one or more recipients using the out-of-the-box Send E-Mail node.

  Executing the process model results in the Send E-Mail node encountered this error: "Error:Email could not be sent"

  Where do you go first to find more details on why the node encountered an error? (Choose the best answer.)

  A. Raise a support case within My Appian so a cloud engineer can investigate.
  B. Review the system.csv log.
  C. Run and review the Health Check report
  D. Investigate the application server stdout log
  D. Investigate the application server stdout log

  ---

  Explanation/Reference:

  The first place to go to find more details on why the Send E-Mail node encountered an error is to investigate the application server stdout log. This log contains information about the email server configuration, connection status, and error messages. You can access this log from the Administration Console under Monitoring > Logs > Application Server Logs > stdout.log. You can also search for keywords like "email" or "smtp" to filter the relevant entries. References: [Send E-Mail Smart Service], [Application Server Logs]

• Question 66:

  You need to display the profile picture of each employee inside an employee grid, alongside their names and phone numbers.

  According to Appian best practices, what is the preferred style and size for the images?

  A. style: "AVATAR" size: "LARGE"
  B. style: "STANDARD" size: "ICON"
  C. style: "STANDARD" size: "LARGE"
  D. style: "AVATAR" size: "SMALL"
  D. style: "AVATAR" size: "SMALL"

  ---

  Explanation/Reference:

  According to Appian best practices, the preferred style and size for the images to display the profile picture of each employee inside an employee grid are style: "AVATAR" and size: "SMALL". This is because the avatar style creates a circular image that is suitable for profile pictures, and the small size creates a 32x32 pixel image that fits well inside a grid cell. The standard style creates a rectangular image that may not look good for profile pictures, and the large size creates a 128x128 pixel image that may be too big for a grid cell. References: Image Component

• Question 67:

  You are code-checking your colleague's process model before marking it as Ready for Deployment.

  Which three best practices should be applied? (Choose three.)

  A. All nodes should have exception flows
  B. All XOR/OR gateways should have a single incoming ow.
  C. All outgoing flows from a gateway should be labeled
  D. Node inputs should not make the same query call more than once.
  E. Activity chaining should be added to the majority of flows.
  B. All XOR/OR gateways should have a single incoming ow.
  C. All outgoing flows from a gateway should be labeled
  D. Node inputs should not make the same query call more than once.

  ---

  Explanation/Reference:

  Three best practices that should be applied when code-checking a process model are: All XOR/OR gateways should have a single incoming flow. This is because XOR/OR gateways are used to split the process flow based on a condition or an event. Having multiple incoming flows to a gateway can cause confusion and ambiguity about the logic and order of execution. If multiple incoming flows are needed, they should be merged into a single flow using an AND gateway before reaching the XOR/OR gateway. All outgoing flows from a gateway should be labeled. This is because labels provide clarity and readability to the process model. They also help to document the business logic and rules that determine the path of execution. Labels should be concise, descriptive, and consistent throughout the process model. Node inputs should not make the same query call more than once. This is because repeated query calls can negatively impact the performance and efficiency of the process model. They can also cause data inconsistency and duplication if the query results change over time. Node inputs should use variables or rules to store and reuse query results whenever possible. References: Process Model Best Practices, Process Model Object, Process Modeling

• Question 68:

  Application users are seeing long wait times between two forms they need to complete for a case.

  While reviewing the process model, you identify that activity chaining has been used throughout the process model, including unattended nodes. Which three actions can you take to make the process model more efficient? (Choose three.)

  A. Use MNI for unattended nodes and chain where possible.
  B. Shorten long process chains by combining transactions into the smallest number of nodes.
  C. Avoid chaining system nodes like Integrations.
  D. Move transactions that can be done asynchronously outside of the chain.
  E. Reduce the number of swim lanes.
  B. Shorten long process chains by combining transactions into the smallest number of nodes.
  C. Avoid chaining system nodes like Integrations.
  D. Move transactions that can be done asynchronously outside of the chain.

  ---

  Explanation/Reference:

  Activity chaining is a feature that allows users to complete multiple tasks in a row without returning to their task list. However, activity chaining can also have some drawbacks, such as increased memory consumption, longer transaction times,

  and reduced user feedback. Therefore, some actions can be taken to make the process model more efficient, such as:

  Shorten long process chains by combining transactions into the smallest number of nodes. This can reduce the memory footprint and the database load of the process model.

  Avoid chaining system nodes like Integrations. These nodes can have unpredictable execution times and can cause timeouts or errors if chained. It is better to use asynchronous integrations or message events to decouple the process flow

  from external systems.

  Move transactions that can be done asynchronously outside of the chain. This can improve the responsiveness of the process model and allow parallel processing of independent tasks.

  Therefore, the correct answers are B, C, and D.

  References:

  Activity Chaining

  Performance Best Practices

• Question 69:

  You are on a project where the goal is to use Appian Sites to create and edit invoices issued to customers.

  This process model is being used as a related action, to edit an Invoice. You have already created a record for invoices.

  Review the following image:

  

  Which two suggestions regarding this process are valid? (Choose two.)

  A. We should consider adding a timer exception which skips the "Edit/Credit Invoice" node after 24 hours.
  B. We should add this process model as a related action on the Invoices record called "Edit Invoice."
  C. We should add two pages to the site, one of which is a Record List of Invoices, and the other which has this process model as a Report.
  D. To improve performance, we should consider removing activity chaining from all flows.
  A. We should consider adding a timer exception which skips the "Edit/Credit Invoice" node after 24 hours.
  B. We should add this process model as a related action on the Invoices record called "Edit Invoice."

  ---

  Explanation/Reference:

  Two valid suggestions regarding this process are: We should consider adding a timer exception which skips the "Edit/Credit Invoice" node after 24 hours. This suggestion would improve the user experience by preventing users from editing or crediting an invoice that is too old or has been already processed by another system. A timer exception can be added to any activity node to specify a deadline for completing the task. If the deadline is reached, the process flow will follow the exception path instead of the normal path. We should add this process model as a related action on the Invoices record called "Edit Invoice." This suggestion would make it easier for users to access and execute this process from the context of a specific invoice record. A related action is a process model that can be initiated from a record or a record list in Tempo or sites. A related action can use record data as inputs and update record data as outputs. References: Timer Exception, Create Record Actions

• Question 70:

  Which of the following is a sign that an application's performance is degrading and should be addressed with changes to the application design?

  A. Integration calls to an external system are consistently returning an HTTP status code of 500.
  B. Three of the top five most executed process models have a low completion percentage.
  C. The number of tasks assigned to users has increased from 1 per day to 5 per day.
  D. The number of objects in the Application has increased from about 100 to about 500.
  B. Three of the top five most executed process models have a low completion percentage.

  ---

  Explanation/Reference:

  The question is about a sign that an application's performance is degrading and should be addressed with changes to the application design. The following is a sign of this: Three of the top five most executed process models have a low completion percentage. This means that a large proportion of the process instances are not reaching the end event, either because they are taking too long to complete, or because they are encountering errors or exceptions. This can affect the performance of the application, as it can consume more memory and resources, and reduce the availability and reliability of the application. You should review the process model design and identify the causes of the low completion rate, and make changes to improve the process efficiency and error handling. The following are not signs of performance degradation that require changes to the application design: Integration calls to an external system are consistently returning an HTTP status code of 500. This means that the external system is experiencing an internal server error, which is not related to the application design. You should contact the external system provider and report the issue, or implement a fallback or retry mechanism in your integration logic. The number of tasks assigned to users has increased from 1 per day to 5 per day. This means that the workload or demand for the application has increased, which is not necessarily a sign of performance degradation. You should monitor the task completion rate and user feedback to see if the increase in tasks is affecting the user experience or satisfaction, and adjust the task assignment or prioritization logic if needed. The number of objects in the Application has increased from about 100 to about 500. This means that the application has grown in size and complexity, which is not necessarily a sign of performance degradation. You should follow the best practices for application design and maintenance, such as using folders, prefixes, dependencies, and documentation, to keep the application organized and manageable. References: Process Model Metrics HTTP Status Codes Task Report Application Design