Appian ACD300 Test 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”.