Appian ACD300 Dumps

A.   Create a Web API object and set up the correct security.



B.   Configure the connection In Jira specifying the URE and credentials



C.   Create a new API Key and associate a service account

Answer DescriptionExplanation:

The three required steps that will allow you to connect both systems are:

A. Create a Web API object and set up the correct security. This will allow you to define an endpoint in Appian that can receive requests from Jira via webhook. You will also need to configure the security settings for the Web API object, such as authentication method, allowed origins, and access control.

B. Configure the connection in Jira specifying the URL and credentials. This will allow you to set up a webhook in Jira that can send requests to Appian when specific tickets change. You will need to specify the URL of the Web API object in Appian, as well as any credentials required for authentication.

C. Create a new API Key and associate a service account. This will allow you to generate a unique token that can be used for authentication between Jira and Appian. You will also need to create a service account in Appian that has permissions to access or update data related to Jira tickets.

The other options are incorrect for the following reasons:

D. Give the service account system administrator privileges. This is not required and could pose a security risk, as giving system administrator privileges to a service account could allow it to perform actions that are not related to Jira tickets, such as modifying system settings or accessing sensitive data.

E. Create an integration object from Appian to Jira to periodically check the ticket status. This is not required and could cause unnecessary overhead, as creating an integration object from Appian to Jira would involve polling Jira for ticket status changes, which could consume more resources than using webhook notifications. Verified References: Appian Documentation, section “Web API” and “API Keys”.

B.   Phase 2 development work Stream: DEV > TEST (SIT) > STAGE (UAT) > PROO
Production support work stream DEV2 > STAGE (S1T/UAT) > PROD

Answer DescriptionExplanation:

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”.

D.   httpirequest queryParameters.username

Answer DescriptionExplanation:

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”.

C.   The default time zone for the environment as specified in the Administration Console

Answer DescriptionExplanation:

In this situation, pm!timezone reflects the default time zone for the environment as specified in the Administration Console. pm!timezone is a process variable that returns the time zone of the process. If the time zone is not explicitly set in the process model, then pm!timezone returns the default time zone for the environment, which can be configured in the Administration Console. In this case, the time zone is set to the (default) pm!timezone, which means that the process model does not have a specific time zone, and therefore uses the default time zone for the environment.

The other options are not correct. Option A, the time zone of the server where Appian is installed, is not what pm!timezone reflects, as the server time zone may not be the same as the default time zone for the environment. Option B, the time zone of the user who most recently published the process model, is not what pm!timezone reflects, as the user’s time zone may not be the same as the default time zone for the environment. Option D, the time zone of the user who is completing the input task, is not what pm!timezone reflects, as the user’s time zone may not be the same as the default time zone for the environment.

B.   Group epics and stones by feature, and allocate work between each team by feature.

Answer DescriptionExplanation:

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”.

B.   Phase 2 development work Stream: DEV > TEST (SIT) > STAGE (UAT) > PROO
Production support work stream DEV2 > STAGE (S1T/UAT) > PROD

Answer DescriptionExplanation:

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”.

B.   Optimize the database execution use standard database performance troubleshooting methods and tools (such as query execution plans)



C.   Reduce the size and complexity of the inputs. If you ore passing in a list, consider whether (he data model can be redesigned lo pass single values instead



E.   Use smaller CDTs or limit the fields selected in alqueryEntity()

Answer DescriptionExplanation:

The three things that might help to address the findings of the Health Check report are:

B. Optimize the database execution using standard database performance troubleshooting methods and tools (such as query execution plans). This can help to identify and eliminate any bottlenecks or inefficiencies in the database queries that are causing slow query rules or slow write to data store nodes.

C. Reduce the size and complexity of the inputs. If you are passing in a list, consider whether the data model can be redesigned to pass single values instead. This can help to reduce the amount of data that needs to be transferred or processed by the database, which can improve the performance and speed of the queries or writes.

E. Use smaller CDTs or limit the fields selected in a!queryEntity(). This can help to reduce the amount of data that is returned by the queries, which can improve the performance and speed of the rules that use them.

The other options are incorrect for the following reasons:

A. Reduce the batch size for database queues to 10. This might not help to address the findings, as reducing the batch size could increase the number of transactions and overhead for the database, which could worsen the performance and speed of the queries or writes. D. Optimize the database execution. Replace the new with a materialized view. This might not help to address the findings, as replacing a view with a materialized view could increase the storage space and maintenance cost for the database, which could affect the performance and speed of the queries or writes. Verified References: Appian Documentation, section “Performance Tuning”.

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

Answer DescriptionExplanation:

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.

B.   Create a common objects application.

Answer DescriptionExplanation:

To build a large scale acquisition application for a prominent customer, you should design for multiple processes and forms, while minimizing repeated code. One way to do this is to create a common objects application, which is a shared application that contains reusable components, such as rules, constants, interfaces, integrations, or data types, that can be used by multiple applications.

This way, you can avoid duplication and inconsistency of code, and make it easier to maintain and update your applications. You can also use the common objects application to define common standards and best practices for your application development teams, such as naming conventions, coding styles, or documentation guidelines. Verified References: [Appian Best Practices], [Appian Design Guidance]

B.   Create a rollback script that removes the field.



C.   Create a script that adds the field and then populate it

Answer DescriptionExplanation:

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.