ACD300 Online Practice Questions and Answers

Correct Answer: ABD

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.

Correct Answer: D

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

Correct Answer: D

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]

Correct Answer: B

The best way to ensure consistency across the platform is to create a rule that can be used across the platform for section headers. This rule can be created in the common application, and then each application can be updated to reference

this rule. This will ensure that all of the applications use the same color and size for the header, which will provide a consistent user experience.

The other options are not as effective. Option A, creating constants for text size and color, and updating each section to reference these values, would require updating each section in each application. This would be a lot of work, and it would

be easy to make mistakes. Option C, creating one rule for each application, would also require updating each application. This would be less work than option A, but it would still be a lot of work, and it would be easy to make mistakes. Option

D, creating a rule in each individual application, would not ensure consistency across the platform. Each application would have its own rule, and the rules could be different. This would not provide a consistent user experience.

Best Practices:

When designing a platform, it is important to consider the user experience. A consistent user experience will make it easier for users to learn and use the platform.

When creating rules, it is important to use them consistently across the platform. This will ensure that the platform has a consistent look and feel. When updating the platform, it is important to test the changes to ensure that they do not break

the user experience.

Correct Answer: A

This is the best risk mitigation effort that both teams can employ to ensure that Team A's capital project is only minorly interrupted, and Team B's critical fix can be completed and deployed quickly to end users. By communicating with Team A, Team B can identify which component is causing the critical error in PROD, and check if there is any overlap of changes with Team A's enhancements. If there is an overlap, Team B can version the component to its PROD state, which is the last stable version, before making any changes to fix the error. Then, Team B can deploy the fixed component to PROD, and version it back to its latest development state, which includes Team A's enhancements. This way, Team B can avoid overwriting or losing any of Team A's work, and ensure that the component is consistent across all environments. If there is no overlap, Team B can simply make the changes to the component and deploy it to PROD, without affecting Team A's work. The other options are not as effective. Option B, having Team A analyze their current codebase in DEV to merge the hotfix changes into their latest enhancements, would delay the deployment of the critical fix, as Team B would have to wait for Team A to finish their analysis and merge. Option C, having Team B address the changes in TEST, would interrupt Team A's UAT process, and could cause conflicts or errors in TEST or PROD. Option D, having Team B address the changes directly in PROD, would be risky and not recommended, as it could introduce new errors or inconsistencies in PROD. Verified References: [Appian Deployment Guide], [Appian Best Practices]

Correct Answer: C

The best environment to use for load testing is acme, which is the production environment. This is because load testing should be performed on an environment that is as close as possible to the actual production environment, in terms of hardware, software, configuration, data, and user behavior. This way, the results of the load testing will be more realistic and reliable, and can help to identify and resolve any performance issues or bottlenecks before increasing the number of active users. Verified References: Appian Documentation, section "Load Testing".

Correct Answer: B

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

Correct Answer: B

Deploying an object that is dependent on another object from a different application can cause errors and inconsistencies in the production environment. The best practice is to halt the production deployment and contact the other team for guidance on how to promote the object to PROD. The other team may have a different deployment schedule, or they may have some dependencies or customizations that need to be considered. By communicating with the other team, you can ensure that the object is deployed in a safe and coordinated manner, and avoid any potential conflicts or issues. Verified References: [Appian Deployment Guide], [Appian Best Practices]

Correct Answer: ACD

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

Correct Answer: ABE

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