Appian ACD200 Online Practice Questions and Exam Preparation

Appian ACD200 Online Questions & Answers

• Question 71:

  You need to find a list of expression rules that are causing performance issues, or have caused performance issues in the last 30 days.

  What should you do?

  A. Use the Monitoring tab to find rules with a low completion percentage.
  B. Access the Rule Performance tab in the Administration Console.
  C. Inspect the application server log.
  D. Observe the runtime of all test cases.
  B. Access the Rule Performance tab in the Administration Console.

  ---

  Explanation/Reference:

  The requirement is to find a list of expression rules that are causing performance issues, or have caused performance issues in the last 30 days. The best way to do this is to access the Rule Performance tab in the Administration Console, as it provides a dashboard that shows the execution time, frequency, and impact of expression rules in a given time period. You can filter the rules by application, rule type, or execution time, and sort them by various metrics. You can also drill down into each rule to see the details of its executions and test cases. The other options are not as effective or convenient for this purpose, as they either do not provide enough information, require manual inspection, or are not related to expression rules. References: Rule Performance

• Question 72:

  What are three things you can do to improve the memory usage of a process model? (Choose three.)

  A. Configure process variables to be parameters.
  B. Reduce the number of process variables.
  C. Avoid storing large blocks of text in process variables.
  D. Split large nodes into many smaller nodes.
  E. Pass data directly to activity nodes and smart services.
  B. Reduce the number of process variables.
  C. Avoid storing large blocks of text in process variables.
  E. Pass data directly to activity nodes and smart services.

  ---

  Explanation/Reference:

  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

• Question 73:

  Which review format is the most efficient way to coach team members and improve code quality? (Choose the best answer.)

  A. Peer Dev Review
  B. Automated Code Scanning
  C. Retrospectives
  D. User Acceptance Testing
  A. Peer Dev Review

  ---

  Explanation/Reference:

  Peer Dev Review is the most efficient way to coach team members and improve code quality, because it allows developers to share feedback, learn from each other, and identify and fix issues before they become problems. Peer Dev Review also fosters collaboration, communication, and best practices among the team. Peer Dev Review can be done using tools like Appian Designer or Appian Code Review. References: [Peer Dev Review], [Appian Code Review]

• Question 74:

  Users are reporting that a task on a newly-launched process in Production is slow to respond to user input.

  What is the likely cause? (Choose the best answer.)

  A. The process uses too many hidden variables.
  B. The task is assigned to too many users.
  C. There are too many SAIL components on the task.
  D. Exception timers on tasks are set to values that are too low.
  C. There are too many SAIL components on the task.

  ---

  Explanation/Reference:

  The likely cause for a task on a newly-launched process in Production being slow to respond to user input is having too many SAIL components on the task. SAIL components are the UI elements that make up an interface in Appian. Having too many SAIL components on a task can negatively impact the performance and user experience of the interface, as it increases the rendering time and complexity of the interface. It can also cause browser compatibility issues or memory leaks. It is recommended to limit the number of SAIL components on a task to less than 100, and to use grids, collapsible layouts, or tabs to organize and display data efficiently. References: SAIL Components Overview, SAIL Performance Tips

• Question 75:

  HOTSPOT

  Match each of the business data concepts to an Appian data type. Each data type may be used once, more than once, or not at all.

  Hot Area:

  

  

  ---

  Explanation/Reference:

• Question 76:

  During a sprint retrospective meeting, you need to get the team thinking about the outcomes of the last sprint.

  Which two basic questions should you ask? (Choose two.)

  A. What didn't go well and can be improved?
  B. What are the blockers?
  C. Who did well in this sprint?
  D. What went well?
  A. What didn't go well and can be improved?
  D. What went well?

  ---

  Explanation/Reference:

  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.

• Question 77:

  You are troubleshooting slow response times on a SAIL interface.

  What are two potential causes of the performance issues? (Choose two.)

  A. Multiple rule inputs
  B. Multiple a!save operations
  C. Configuration of refresh variables
  D. Stacked button layout
  B. Multiple a!save operations
  C. Configuration of refresh variables

  ---

  Explanation/Reference:

  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