ACD300 Appian Certified Lead Developer Questions and Answers

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.

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.

• uk.co.certification.simulator.questionpool.PList@187d4e90

• uk.co.certification.simulator.questionpool.PList@187d4ef0

• uk.co.certification.simulator.questionpool.PList@187d4f70

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]

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.

The field would benefit greatly from the index in the following scenarios:

• A. The field contains a textual short Business code. This is a scenario where an index can improve the performance of queries that search for exact matches or ranges of values in the field. A textual short Business code is likely to have high cardinality, meaning that it has many distinct values and low duplication. This makes the index more selective and efficient, as it can quickly narrow down the results based on the search criteria.
• C. The field contains many datetimes, covering a large range. This is a scenario where an index can improve the performance of queries that search for exact matches or ranges of values in the field. A datetime field is likely to have high cardinality, meaning that it has many distinct values and low duplication. This makes the index more selective and efficient, as it can quickly narrow down the results based on the search criteria.
• D. The field contains big integers, above and below 0. This is a scenario where an index can improve the performance of queries that search for exact matches or ranges of values in the field. A big integer field is likely to have high cardinality, meaning that it has many distinct values and low duplication. This makes the index more selective and efficient, as it can quickly narrow down the results based on the search criteria.

The other options are incorrect for the following reasons:

• B. The field contains long unstructured text such as a hash. This is a scenario where an index might not improve the performance of queries that search for exact matches or ranges of values in the field. A long unstructured text field is likely to have low cardinality, meaning that it has few distinct values and high duplication. This makes the index less selective and efficient, as it cannot quickly narrow down the results based on the search criteria. Moreover, indexing a long unstructured text field could increase thestorage space and maintenance cost for the database, which could affect the overall performance.
• E. The field contains a structured JSON. This is a scenario where an index might not improve the performance of queries that search for exact matches or ranges of values in the field. A structured JSON field is not a native data type in MySQL, and it requires special functions or operators to access or manipulate its elements. Indexing a structured JSON field could increase the complexity and overhead for the database, which could affect the overall performance. Verified References: Appian Documentation, section “Query Optimization”.

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.