ACD300 Appian Certified Lead Developer Questions and Answers

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.

The best way to divide the work between the teams, avoiding issues caused by cross-dependency, is to group epics and stories by feature, and allocate work between each team by feature. This way, each team can focus on a specific feature and minimize the need for coordination or integration with the other team. This also reduces the risk of conflicts or errors when merging the code from both teams. Verified References: Appian Documentation, section “Agile Development”.

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.

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.

To create an integration from your Appian cloud instance to an application hosted within a customer’s self-managed environment, you need to ensure that there is a secure and reliable connection between the two systems. One way to do this is to set up a VPN tunnel, which is a virtual private network that encrypts and transports data over the internet. A VPN tunnel allows you to access the customer’s internal network and API endpoint from your Appian cloud instance, without exposing them to the public internet. This way, you can ensure the security and privacy of the data that is exchanged between the two systems. Verified References: [Appian Cloud VPN], [Appian Integration Guide]

When creating a script to add a new field to a table, you should consider two actions:

• Create a rollback script that removes the field. A rollback script is a script that can undo the changes made by the original script, in case something goes wrongor the changes need to be reverted. A rollback script is a good practice to have, as it can help to restore the previous state of the database and avoid any errors or inconsistencies. In this case, the rollback script should remove the new field from the table, and any other changes that were made by the original script.
• Create a script that adds the field and then populate it. A script that adds the field and then populate it is a script that can create the new field in the table, and then fill it with data from another table or source. This way, you can ensure that the new field has valid and consistent data, and that it can be used by the report in the upcoming release. In this case, the script should add the new field to the customer table, and then populate it with data from another table that contains the data used in the calculation.

• D. The join between the tables order_detail and product needs to be fine-tuned due to Indices. This is correct because the result of the explain statement showsthat the join between these two tables has a high cost of 0.99, which indicates that it is inefficient and needs to be fine-tuned. One possible reason for the high cost is that there are no indices on the columns that are used for joining these two tables, which leads to a full table scan. Therefore, creating indices on these columns could improve the performance of this join.
• E. The worst join is the one between the table order_detail and customer. This is correct because the result of the explain statement shows that the join between these two tables has a very high cost of 1.00, which indicates that it is the worst join in terms of efficiency and needs to be fine-tuned. One possible reason for the high cost is that there are no indices on the columns that are used for joining these two tables, which leads to a full table scan. Therefore, creating indices on these columns could improve the performance of this join.

The other options are incorrect for the following reasons:

• A. The request is good enough to support a high volume of data, but could demonstrate some limitations if the developer queries information related to the product. This is incorrect because the request is not good enough to support a high volume of data, as it has two joins with very high costs that need to be fine-tuned. Moreover, querying information related to the product would not necessarily cause any limitations, as long as the join between order_detail and product is optimized.
• B. The worst join is the one between the table order_detail and order. This is incorrect because the result of the explain statement shows that the join between these two tables has a low cost of 0.01, which indicates that it is efficient and does not need to be fine-tuned.
• C. The join between the tables order_detail, order and customer needs to be fine-tuned due to indices. This is incorrect because there is no such join between three tables in the result of the explain statement. There are only two joins: one between order_detail and order, and another between order_detail and customer. Each of these joins needs to be fine-tuned separately due to indices.