[Jun-2024] ACD300 Braindumps - ACD300 Questions to Get Better Grades [Q17-Q39]

NO.17 For each requirement, match the most appropriate approach to creating or utilizing plug-ins Each approach will be used once.
Note: To change your responses, you may deselect your response by clicking the blank space at the top of the selection list.

Explanation

Requirement: Read barcode values from images containing barcodes and QR codes. Correct approach: C.
Smart Service plug-in Exact explanation of correct approach taken from Appian Documentation: A smart service plug-in is a type of plug-in that allows you to create custom smart services that can be used in process models. A smart service can perform complex logic, interact with external systems, or manipulate data in Appian. A smart service plug-in can also leverage Java code to implement the functionality of the smart service. A smart service plug-in would be suitable for reading barcode values from images, as it can use Java libraries or APIs that can scan and decode barcodes and QR codes from image files. A smart service plug-in can also return the barcode values as outputs that can be used by other nodes or processes in Appian. A smart service plug-in can also be configured with input parameters, such as the image file, the barcode type, or the output format, that can customize the behavior of the smart service. A smart service plug-in can also have error handling and logging features that can handle any exceptions or failures that might occur during the barcode reading process.
Requirement: Display an externally hosted geolocation mapping applications interface within Appian to allow users of Appian to see where a customer (stored within Appian)is located. Correct approach: A. Web-content field Exact explanation of correct approach taken from Appian Documentation: A web-content field is a type of user interface component that allows you to display web content from an external source in a SAIL interface. A web-content field would be suitable for displaying an externally hosted geolocation mapping applications interface, as it can embed the web content in an iframe and render it within the Appian interface.
You can also pass parameters to the web content, such as the customer’s location, using the url parameter of the web-content field. A web-content field can also interact with other components in the Appian interface, such as buttons, grids, or forms, using the postMessage API. This way, you can create a seamless user experience that integrates the external geolocation mapping applications interface with the Appian functionality.
Requirement: Display an externally hosted geolocation mapping applications interface within Appian to allow users of Appian to select where a customer is located and store the selected address in Appian. Correct approach: A. Web-content field and C. Smart Service plug-in Exact explanation of correct approach taken from Appian Documentation: A web-content field and a smart service plug-in would be suitable for displaying an externally hosted geolocation mapping applications interface within Appian to allow users of Appian to select where a customer is located and store the selected address in Appian. A web-content field would be suitable for displaying the external geolocation mapping applications interface, as explained above. A smart service plug-in would be suitable for storing the selected address in Appian, as it can use Java code to receive the address data from the web content, validate it, and write it to a data store entity or a process variable.
Requirement: Generate a barcode image file based on values entered by users. Correct approach: B.
Component plug-in Exact explanation of correct approach taken from Appian Documentation: A component plug-in is a type of plug-in that allows you to create custom user interface components that can be used in SAIL interfaces. A component plug-in can also leverage Java code to implement the functionality of the component. A component plug-in would be suitable for generating a barcode image file, as it can use Java libraries or APIs that can encode values into barcode formats and generate image files. A component plug-in can also display the barcode image file in the Appian interface and allow users to download or print it. A component plug-in can also interact with other components in the Appian interface, such as text fields, buttons, or forms, using the a!refreshVariable() function. This way, you can create a dynamic user experience that updates the barcode image file based on the values entered by users.

NO.18 You are just starting with a new team that has been working together on an application for months. They ask you toreview some of their views thathave been degrading inperformance. The viewsare highly complex with hundreds of lines of SOL What is the first step in troubleshooting the degradation?

Go through the entire database structure to obtain on overview, ensure you understand the business needs, andthen normalize the tables to optimizeperformance.

Run an explain statement on the views, identify criticalareas of improvement that can be remediated and without business knowledge

Go through all of the tables one by one to identify which of the grouped by. ordered by. or joined keys are currently indexed

Browse through the tables, note any tables that contain a large volume of null values, and work with your team to plan for table restructure.

NO.19 You ate in a backlog refinement meeting with the development team and the product owner. You review a story for an integration Involving a third-party system. A payload will be sent from the Appian system through the integration to the third-party system. The story is 21 points on a Fibonacci scale, and requires development from your Appian learn, as well as the technical resources from the third-party system. This item is crucial to your project s success.
What are the two recommended steps to ensure this story can be developed effectively?

Acquire testing steps from QA resources

Identify subject matter experts (SMEs) to perform user acceptance testing (UAT)

Maintain a communication schedule with the third-party resources

Break down the item into smaller stones

NO.20 You need to design a complex Appian integration to call a RESTful API. The RESTful API will be used to update a case in a customer’s legacy system.
What are three prerequisites for designing the integration?

Define the HTTP method that the integration will use.

Understand the content of the expected body. Deluding each field type and their limits

Understand whether this integration will be used in an interface or in a process model

Understand the different error codes managed by the API and the process of error handing m Appall

Understand the business rules to be applied to ensure the business logic of the data

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

NO.21 As part of your implementation workflow, users need to retrieve data stored in a third-party Oracle database on an interface. You need to design a way to query this information.
How should you set up this connection and query the data?

Configure a Query DataBase node within the process model Then, type in the connection information, as well as a SQL query to execute and return the data in process variables.

Configure a limed utility process that queries data from the thirdparty database daily, and stores It in the Applan business database, Then use alqueryEntity eating the Applan data source to retrieve the data.

Configure an expression-backed record type, calling an API to retrieve the data from the third-party database. Then, use allqueryRecordType to retrieve the data.

in the Administration Console configure the third-party database as a ”New Data Source,” Then, use alqueryEntity to retrieve the data.

NO.22 You are required to create an integration from your Appian cloud instance to an application hosted within a customers self-managed environment.
The customers IT team has provided you with a REST API endpoint to test with; httpsV/lnternal networkVapi/api /ping Which recommendation should you make to progress this integration?

Expose the API as a SOAP-basedweb service.

Deploy the API / service into Appian Cloud

Add Appian Cloud’s IP address ranges lo the customer network’s allowed IP listing

Set up a VPN tunnel

NO.23 You are required to configure a connection so that Jira can inform Appian when specific tickets change (using webhook).
Which three required steps will allow you to connect both systems?

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

Configure the connection In Jira specifying the URE and credentials

Create a new API Key and associate a service account

Give the service account system administrator privileges

Create an integration object from Applan to Jira to periodically check the ticket status

NO.24 You are on a protect with an application that has been deployed to Production and is live with users. The client wishes to increase the number of active users.
You need to conduct load testing to ensure Production can handle the increased usage Review the specs for four environments in the following image.

Which environment should you use for load testing7

acmeuat

acmedev

acme

acmetest

NO.25 You are running an inspection as a part of the first deployment process from TEST to PROD. You receive a notice that one of your objects will not deploy because it is dependent on an object from an application owned by a separate team.
What should be your next step?

Create your own object with the same code base, replace (he dependent object in the application. and deploy to PROO.

Push a functionally viable package to PROD without the dependencies, and plan the rest o! the deployment accordingly with the other team’s constraints

Halt the production deployment and contact the other team tor guidance on promoting the object to PROD

Check the dependencies of the necessary object Deploy w PROO if there are few dependencies and it is low risk

NO.26 You are running an inspection as a part of the first deployment process from TEST to PROD. You receive a notice that one of your objects will not deploy because it is dependent on an object from an application owned by a separate team.
What should be your next step?

Create your own object with the same code base, replace (he dependent object in the application. and deploy to PROO.

Halt the production deployment and contact the other team tor guidance on promoting the object to PROD

Check the dependencies of the necessary object Deploy w PROO if there are few dependencies and it is low risk

Push a functionally viable package to PROD without the dependencies, and plan the rest o! the deployment accordingly with the other team’s constraints

NO.27 Review the following resultof an explain statement:

Which two conclusions can you draw from this?

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

The worst join isthe one between the table order_detail and order.

The join between the tables order_detail, order and customerneeds to be tine-tuned due to indices.

The join between the tables 0rder_detail and productneeds to be fine-tuned due to Indices

The worst join is the one between the table order_detail and customer

Explanation
* 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.

NO.28 You are asked to design a case management system for a client in addition to storing some basic metadata about a case, one of the client s requirements Is the ability for users to update a case The client would like any user in their organization of 500 people to be able to make these updates The users are all based in the company’s headquarters, and there will be frequent cases where users are attempting to edit the same case. The client wants to ensure no information Is lost when these edits occur and does not want the solution to burden their process administrators with any additional effort.
Which data locking approach should you recommend?

Allow edits without locking the case GDI

Use the database lo implement tow lewd pessimistic locking.

Add an Version annotation to the case COT to manage Vie locking

Design a process report and query to determine who opened the edit form first

NO.29 You are selling up a new cloud environment. The customer already has a system of record for Its employees and doesn’t want to re-create them in Appian. so you are going to Implement LDAP authentication.
What are the next steps to configure LDAP authentication?
To answer, move the appropriate steps from the Option list to the Answer List area, and arrange them in the correct order. You may or may not use all the steps.

NO.30 Your Agile Scrum project requires you to manage two teams, with three developers per team. Both teams are to work on the same application In parallel.
How should the work be divided between the teams, avoiding issues caused by cross-dependency?

Have each team choose the stones they would like to work on based on personal preference

Group epics and stones by technical difficulty, and allocate one team the more challenging stories

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

Allocate stories to each team based on the cumulative years of experience of the team members.

NO.31 You are reviewing the Engine Performance Logs in Production for a single application thathas been live for six months. This application experiences concurrent user activity and has a fairly sustained load during business hours. The client has reported performance issues with the application during business hours.
During your investigation, you notice a high Work Queue – Java Work Queue Size value in the logs You also notice unattended process activities, including timer events and sending notifications emails, are taking far longer to execute than normal.
The client Increased the number of CPU cores prior to the application going live What is the next recommendation?

Add more engine replicas.

Optimize slow-performing user interfaces.

Add more application servers.

Add execution and analytics shards