Appian ACD300 Online Practice Questions and Exam Preparation

Appian ACD300 Online Questions & Answers

• Question 1:

  You need to design a complex Appian integration to call a RESTful API. The RESTful API will be used to update a case in a customer's legacy system.

  What are three prerequisites for designing the integration?

  A. Define the HTTP method that the integration will use.
  B. Understand the content of the expected body. Deluding each field type and their limits
  C. Understand whether this integration will be used in an interface or in a process model
  D. Understand the different error codes managed by the API and the process of error handing m Appall
  E. Understand the business rules to be applied to ensure the business logic of the data
  A. Define the HTTP method that the integration will use.
  B. Understand the content of the expected body. Deluding each field type and their limits
  D. Understand the different error codes managed by the API and the process of error handing m Appall

  ---

  Explanation/Reference:

  To design a complex Appian integration to call a RESTful API, you need to have some prerequisites, such as: Define the HTTP method that the integration will use. The HTTP method is the action that the integration will perform on the API, such as GET, POST, PUT, PATCH, or DELETE. The HTTP method determines how the data will be sent and received by the API, and what kind of response will be expected. Understand the content of the expected body, including each field type and their limits. The body is the data that the integration will send to the API, or receive from the API, depending on the HTTP method. The body can be in different formats, such as JSON, XML, or form data. You need to understand how to structure the body according to the API specification, and what kind of data types and values are allowed for each field. Understand the different error codes managed by the API and the process of error handling in Appian. The error codes are the status codes that indicate whether the API request was successful or not, and what kind of problem occurred if not. The error codes can range from 200 (OK) to 500 (Internal Server Error), and each code has a different meaning and implication. You need to understand how to handle different error codes in Appian, and how to display meaningful messages to the user or log them for debugging purposes. The other two options are not prerequisites for designing the integration, but rather considerations for implementing it. Understand whether this integration will be used in an interface or in a process model. This is not a prerequisite, but rather a decision that you need to make based on your application requirements and design. You can use an integration either in an interface or in a process model, depending on where you need to call the API and how you want to handle the response. For example, if you need to update a case in real-time based on user input, you may want to use an integration in an interface. If you need to update a case periodically based on a schedule or an event, you may want to use an integration in a process model. Understand the business rules to be applied to ensure the business logic of the data. This is not a prerequisite, but rather a part of your application logic that you need to implement after designing the integration. You need to apply business rules to validate, transform, or enrich the data that you send or receive from the API, according to your business requirements and logic. For example, you may need to check if the case status is valid before updating it in the legacy system, or you may need to add some additional information to the case data before displaying it in Appian.

• Question 2:

  You ate in a backlog refinement meeting with the development team and the product owner. You review a story for an integration Involving a third-party system. A payload will be sent from the Appian system through the integration to the third-party system. The story is 21 points on a Fibonacci scale, and requires development from your Appian learn, as well as the technical resources from the third-party system. This item is crucial to your project s success.

  What are the two recommended steps to ensure this story can be developed effectively?

  A. Acquire testing steps from QA resources
  B. Identify subject matter experts (SMEs) to perform user acceptance testing (UAT)
  C. Maintain a communication schedule with the third-party resources
  D. Break down the item into smaller stones
  C. Maintain a communication schedule with the third-party resources
  D. Break down the item into smaller stones

  ---

  Explanation/Reference:

  To ensure that this story can be developed effectively, you should take two recommended steps: Maintain a communication schedule with the third-party resources. Communication is key when working on an integration involving a third-party system, as it can help to clarify the requirements, expectations, and dependencies of both parties. By maintaining a communication schedule, you can ensure that you have regular and timely updates on the progress, issues, and feedback of the integration. You can also use communication tools, such as email, chat, or video conferencing, to facilitate the communication and collaboration between your Appian team and the third-party resources. Break down the item into smaller stories. Breaking down a large and complex story into smaller and simpler stories can help to make the development process more manageable and efficient. By breaking down the item into smaller stories, you can reduce the scope and complexity of each story, and focus on delivering one feature or functionality at a time. You can also prioritize and assign the stories to different developers, and track their status and completion more easily. The other options are not as effective. Option A, acquiring testing steps from QA resources, is not a step to ensure that the story can be developed effectively, but rather a step to ensure that the story can be tested effectively. Option B, identifying subject matter experts (SMEs) to perform user acceptance testing (UAT), is also not a step to ensure that the story can be developed effectively, but rather a step to ensure that the story can be validated effectively. Option E, adding a view that joins the customer data to the data used in calculation, is not a step to ensure that the story can be developed effectively, but rather a design decision that may or may not be appropriate for the integration.

• Question 3:

  You are reviewing the Engine Performance Logs in Production for a single application thathas been live for six months. This application experiences concurrent user activity and has a fairly sustained load during business hours. The client has reported performance issues with the application during business hours.

  During your investigation, you notice a high Work Queue - Java Work Queue Size value in the logs You also notice unattended process activities, including timer events and sending notifications emails, are taking far longer to execute than normal.

  The client Increased the number of CPU cores prior to the application going live

  What is the next recommendation?

  A. Add more engine replicas.
  B. Optimize slow-performing user interfaces.
  C. Add more application servers.
  D. Add execution and analytics shards
  A. Add more engine replicas.

  ---

  Explanation/Reference:

  Adding more engine replicas will increase the number of threads available to execute unattended process activities, such as timer events and sending notification emails. This will reduce the Java Work Queue Size and improve the performance of the application. Verified References: Appian Engine Performance Logs, Appian Engine Configuration

• Question 4:

  You are designing a process that is anticipated to be executed multiple times a day. This process retrieves data from an external system and then calls various utility processes as needed. The mam process will not use the results of the utility processes, and there are no user forms anywhere.

  Which design choice should be used to start the utility processes and minimize the load on the execution engines?

  A. Use the Start Process Smart Service to start the utility processes.
  B. Start the utility processes via a subprocess synchronously.
  C. Use Process Messaging lo star! the utility process.
  D. Start the utility processes via a subprocess asynchronously
  C. Use Process Messaging lo star! the utility process.

  ---

  Explanation/Reference:

  To design a process that is anticipated to be executed multiple times a day, that retrieves data from an external system and then calls various utility processes as needed, you should use Process Messaging to start the utility process and minimize the load on the execution engines. Process Messaging is a feature that allows you to send and receive messages between processes in Appian. By using Process Messaging, you can start the utility process asynchronously, which means that the main process does not have to wait for the utility process to finish before continuing. This way, you can improve the performance and scalability of your process design, and reduce the load on the execution engines. The other options are not as effective. Option A, using the Start Process Smart Service to start the utility processes, would also start the utility process asynchronously, but it would require more configuration and maintenance than Process Messaging. Option B, starting the utility processes via a subprocess synchronously, would start the utility process as a part of the main process flow, which means that the main process would have to wait for the utility process to finish before continuing. This would reduce the performance and scalability of your process design, and increase the load on the execution engines. Option D, starting the utility processes via a subprocess asynchronously, would also start the utility process as a part of the main process flow,but it would not wait for the utility process to finish before continuing. However, this option would still create more overhead than Process Messaging, as it would create more instances of processes in Appian.

• Question 5:

  HOTSPOT

  You are deciding the appropriate process model data management strategy.

  For each requirement. match the appropriate strategies to implement. Each strategy will be used once.

  Note: To change your responses, you may deselect your response by clicking the blank space at the top of the selection list.

  Hot Area:

  

  

  ---

  Explanation/Reference:

  Requirement: Archive processes 2 days after completion or cancellation. Correct match: A. Processes that need to be available for 2 days after completion or cancellation, after which are no longer required nor accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called "Archive after 2 days" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be archived and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting. Requirement: Use system default (currently auto-archive processes 7 days after completion or cancellation). Correct match: C. Processes that remain available for 7 days after completion or cancellation, after which are archived when accessed Exact explanation of correct match taken from Appian Documentation: This strategy is called "Use system default" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 7 days, after which they will be archived when accessed. This strategy can help balance the availability and performance of process data, as it allows processes to be archived on demand rather than on a fixed schedule. Requirement: Delete processes 2 days after completion or cancellation. Correct match: B. Processes that need to be available for 2 days after completion or cancellation, after which remain accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called "Delete after 2 days" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be deleted and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting, but it also means that process data will be permanently lost. Requirement: Do not automatically clean-up processes. Correct match: D. Processes that need to remain available without the need to unarchive Exact explanation of correct match taken from Appian Documentation: This strategy is called "Do not automatically clean-up" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available indefinitely without being archived or deleted. This strategy can help ensure the availability and integrity of process data, but it also means that the process database will grow over time and affect the performance of process reporting.

• Question 6:

  You have created a Web API in Appian. with the following URL to call it: https://exampleappiancloud.com/suite/webapi/usef_managefnent/ users ?username=)=john.smith.

  Which is the connect syntax forreferring to the user name parameter'

  A. httpirequest.queryParameters users username
  B. httpirequest usees username
  C. httpirequest formData username
  D. httpirequest queryParameters.username
  D. httpirequest queryParameters.username

  ---

  Explanation/Reference:

  The correct syntax for referring to the username parameter in the Web API URL is httpirequest.queryParameters.username. This syntax allows you to access the value of the username parameter that is passed in the query string of the URL after the question mark (?). For example, if the URL ishttps://exampleappiancloud.com/suite/webapi/user_management/users?username=john. smith, then httpirequest.queryParameters.username will return john.smith. Verified References: Appian Documentation, section "Web API".

• Question 7:

  Your Appian project just went live with the following environment setup; DEV > TEST (SIT/DAT) > PROD

  Your client is considering adding a support team to manage production defects and minor enhancements, white the original development team focuses on Phase 2 Your client is asking you for a new environment strategy that will have the least impact on Phase 2 development work.

  Which option involves the lowest additional server cost and the least code retrofit effort?

  A. Phase 2 development work steam: DEV > TEST (SIT) > STAGE (UAT) > PROO Production support work stream DEV > TEST2 (SIT/UAT)>PROO
  B. Phase 2 development work Stream: DEV > TEST (SIT) > STAGE (UAT) > PROO Production support work stream DEV2 > STAGE (S1T/UAT) > PROD
  C. Phase 2 development work stream: DEV > TEST (SIT/UAT) >PROD Production support work stream DEV > TEST2 (SIT/UAT) > PROO
  D. Phase 2 development work stream: OEV > TEST (Srr/DAT) > PROO Production support work stream. DEV2 > TEST (SIT/UAT) > PROD
  B. Phase 2 development work Stream: DEV > TEST (SIT) > STAGE (UAT) > PROO Production support work stream DEV2 > STAGE (S1T/UAT) > PROD

  ---

  Explanation/Reference:

  The option B involves the lowest additional server cost and the least code retrofit effort, as it only requires one additional environment (DEV2) for the production support work stream. The production support work stream can use the existing STAGE environment for testing and user acceptance testing, as it is shared with the phase 2 development work stream. This way, there is no need to create a separate TEST2 environment or to retrofit any code from TEST to STAGE or from STAGE to PROD. Verified References: [Appian Certified Lead Developer study guide], page 16, section "Environment Strategy".

• Question 8:

  You are developing a case management application to manage support cases for a large set of sites. One of the tabs in this application s site Is a record grid of cases, along with Information about the site corresponding to that case. Users must be able to filter cases by priority level and status.

  You decide to create a view as the source of your entity-backed record, which joins the separate case/site tables (as depicted in the following Image).

  

  Which three column should be indexed?

  A. site_id
  B. status
  C. name
  D. modified_date
  E. priority
  F. case_id
  A. site_id
  B. status
  E. priority

  ---

  Explanation/Reference:

  Indexing columns can improve the performance of queries that use those columns in filters, joins, or order by clauses. In this case, the columns that should be indexed are site_id, status, and priority, because they are used for filtering or joining the tables. Site_id is used to join the case and site tables, so indexing it will speed up the join operation. Status and priority are used to filter the cases by the user's input, so indexing them will reduce the number of rows that need to be scanned. Name, modified_date, and case_id do not need to be indexed, because they are not used for filtering or joining. Name and modified_date are only used for displaying information in the record grid, and case_id is only used as a unique identifier for each record. Verified References: Appian Records Tutorial, Appian Best Practices

• Question 9:

  You need to export data using an out-of-the-box Appian smart service. Which two formats are available (or data generation?

  A. CSV
  B. XML
  C. Excel
  D. JSDN
  A. CSV
  C. Excel

  ---

  Explanation/Reference:

  The two formats that are available for data generation using an out-of-the- box Appian smart service are:

  A. CSV. This is a comma-separated values format that can be used to export data in a tabular form, such as records, reports, or grids. CSV files can be easily opened and manipulated by spreadsheet applications such as Excel or Google Sheets.

  C. Excel. This is a format that can be used to export data in a spreadsheet form, with multiple worksheets, formatting, formulas, charts, and other features. Excel files can be opened by Excel or other compatible applications. The other options are incorrect for the following reasons:

  B. XML. This is a format that can be used to export data in a hierarchical form, using tags and attributes to define the structure and content of the data. XML files can be opened by text editors or XML parsers, but they are not supported by the out-of-the-box Appian smart service for data generation. D. JSON. This is a format that can be used to export data in a structured form, using objects and arrays to represent the data. JSON files can be opened by text editors or JSON parsers, but they are not supported by the out-of-the-box Appian smart service for data generation. Verified References: Appian Documentation, section "Write to Data Store Entity" and "Write to Multiple Data Store Entities".

• Question 10:

  As part of your implementation workflow, users need to retrieve data stored in a third-party Oracle database on an interface. You need to design a way to query this information.

  How should you set up this connection and query the data?

  A. Configure a Query DataBase node within the process model Then, type in the connection information, as well as a SQL query to execute and return the data in process variables.
  B. Configure a limed utility process that queries data from the thirdparty database daily, and stores It in the Applan business database, Then use alqueryEntity eating the Applan data source to retrieve the data.
  C. Configure an expression-backed record type, calling an API to retrieve the data from the third-party database. Then, use allqueryRecordType to retrieve the data.
  D. in the Administration Console configure the third-party database as a `'New Data Source,'' Then, use alqueryEntity to retrieve the data.
  D. in the Administration Console configure the third-party database as a `'New Data Source,'' Then, use alqueryEntity to retrieve the data.

  ---

  Explanation/Reference:

  To meet the application requirement of allowing users to navigate throughout the application while maintaining complete visibility in the application structure, and easily navigate to previous locations, you should include a breadcrumbs pattern on applicable interfaces to show the organizational hierarchy. A breadcrumbs pattern is a user interface component that displays the current location of the user within the application, and provides links to the previous levels of the hierarchy. For example, if the user is viewing a product details page, the breadcrumbs pattern could show something like "Home > Products > Product Details". This way, the user can see where they are in the application, and easily go back to any previous level by clicking on the corresponding link. The other options are not as effective. Option A, using Tiles as Cards pattern on the home page to prominently display application choices, would provide a way for users to access different parts of the application from the home page, but it would not show the organizational hierarchy or allow users to navigate to previous locations. Option B, implementing an Activity History pattern to track an organization's activity measures, would provide a way for users to see the recent actions performed by themselves or others in the application, but it would not show the organizational hierarchy or allow users to navigate to previous locations. Option C, implementing a drilldown report pattern to show detailed information about report data, would provide a way for users to explore different levels of data in a report, but it would not show the organizational hierarchy or allow users to navigate to previous locations.