Get ACD300 Actual Free Exam Q&As to Prepare for Your Appian Certification
Appian Actual Free Exam Questions And Answers
NEW QUESTION # 21
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?
- A. Configure the connection In Jira specifying the URE and credentials
- B. Create a Web API object and set up the correct security.
- C. Create a new API Key and associate a service account
- D. Give the service account system administrator privileges
- E. Create an integration object from Applan to Jira to periodically check the ticket status
Answer: A,B,C
Explanation:
Explanation
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".
NEW QUESTION # 22
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?
- A. Understand the different error codes managed by the API and the process of error handing m Appall
- B. Understand whether this integration will be used in an interface or in a process model
- C. Define the HTTP method that the integration will use.
- D. Understand the business rules to be applied to ensure the business logic of the data
- E. Understand the content of the expected body. Deluding each field type and their limits
Answer: A,C,E
Explanation:
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.
NEW QUESTION # 23
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?
- A. Optimize slow-performing user interfaces.
- B. Add execution and analytics shards
- C. Add more engine replicas.
- D. Add more application servers.
Answer: C
Explanation:
Explanation
Adding more engine replicas will increase the number of threads available to execute unattended process activities, such as timer events and sending notification emails. This will reduce the Java Work Queue Size and improve the performance of the application. Verified References: Appian Engine Performance Logs, Appian Engine Configuration
NEW QUESTION # 24
You have 5 applications on your Appian platform in production. Users are now beginning to use multiple applications across the platform, and the client wants to ensure a consistent user experience across all applications You notice that some applications use rich text some use section layouts, and others use box layouts. The result is that each application has a different color and size for the header.
What would you recommend to ensure consistency across the platform?
- A. In the common application, create a rule that can be used across the platform for section headers, and update each application to reference this new rule
- B. In the common application, create one rule for each application, and update each application to reference its respective rule
- C. In each individual application, create a rule that can be used lot tot section headers, and update each application lo reference its respective rule
- D. Create constants for text size and color, and update each section lo reference these values.
Answer: A
Explanation:
Explanation
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.
NEW QUESTION # 25
Your Appian project just went live with the following environment setup; DEV > TEST (SIT/DAT) > PROD Your client is considering adding a support team to manage production defects and minor enhancements, white the original development team focuses on Phase 2 Your client is asking you for a new environment strategy that will have the least impact on Phase 2 development work.
Which option involves the lowest additional server cost and the least code retrofit effort?
- A. Phase 2 development work steam: DEV > TEST (SIT) > STAGE (UAT) > PROO Production support work stream DEV > TEST2 (SIT/UAT)>PROO
- B. Phase 2 development work stream: DEV > TEST (SIT/UAT) >PROD Production support work stream DEV > TEST2 (SIT/UAT) > PROO
- C. Phase 2 development work Stream: DEV > TEST (SIT) > STAGE (UAT) > PROO Production support work stream DEV2 > STAGE (S1T/UAT) > PROD
- D. Phase 2 development work stream: OEV > TEST (Srr/DAT) > PROO Production support work stream. DEV2 > TEST (SIT/UAT) > PROD
Answer: C
Explanation:
Explanation
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".
NEW QUESTION # 26
You are presented with the following application requirement:
Users must be able to navigate throughout the application while maintaining complete visibility in the application structure, and easily navigate to previous locations.'' Which Appian Interface Pattern would you recommend?
- A. Use Bullous as Cards pattern on the home page lo prominently display application choices.
- B. implement a drilldown report pattern to show detailed information about report data.
- C. Include a breadcrumbs pattern on applicable inert aces to show the organizational hierarchy
- D. Implement an Activity History pattern to track an organizations activity measures.
Answer: B
Explanation:
Explanation
To meet the application requirement of allowing users to view summary and detailed information about report data, you should implement a drilldown report pattern to show detailed information about report data. A drilldown report pattern is a user interface component that displays data in a hierarchical structure, and allows users to expand or collapse different levels of data. For example, if the user is viewing a sales report by region, the drilldown report pattern could show something like "North America > USA > California > Los Angeles".
The user can click on any level of data to see more or less details. This way, the user can see both summary and detailed information about report data, and explore different aspects of the data.
The other options are not as effective. Option A, using Tiles as Cards pattern on the home page to prominently display application choices, would provide a way for users to access different parts of the application from the home page, but it would not show summary or detailed information about report data. Option B, implementing an Activity History pattern to track an organization's activity measures, would provide a way for users to see the recent actions performed by themselves or others in the application, but it would not show summary or detailed information about report data. Option D, including a breadcrumbs pattern on applicable interfaces to show the organizational hierarchy, would provide a way for users to see where they are in the application, and easily go back to any previous level by clicking on the corresponding link, but it would not show summary or detailed information about report data.
NEW QUESTION # 27
Your clients customer management application is finally released lo Production. After a few weeks of small enhancements and patches, the client Is ready to build their next application. The new application will leverage customer information from the first application to allow the client to launch targeted campaigns for select customers in order to increase sales.As part of the first application, your team had built a section lo display key customer information such as their name, address, phone number, how long they have been a customer, etc. A similar section will be needed on the campaign record you are building.
One of your developers shows you the new object they are working on for the new application and asks you to review it as they are running Into a few issues.
What feedback should you give?
- A. Create a duplicate version of that sect<on designed for the campaign record.
- B. Ask the developer to convert the original customer section into a shared object so it can be used by the new application
- C. Provide guidance to the developer on how to address the issues so that they can proceed with their work
- D. Point the developer to the relevant areas in the documentation or Applan Community where they can find more Information on the issues they are running into.
Answer: B
Explanation:
Explanation
The best practice for reusing common UI components across multiple applications is to create shared objects, which are objects that can be referenced by other applications without being copied or duplicated. This way, any changes made to the shared object will be reflected in all applications that use it, ensuring consistency and maintainability. Therefore, instead of creating a duplicate version of the customer section for the new application, the developer should convert the original customer section into a shared object and reference it from both applications. Verified References: Appian Documentation, section "Shared Objects".
NEW QUESTION # 28
You add an index on the searched field of a MySQL table with many rows (>100k).
The field would benefit greatly from the Index in which three scenarios?
- A. The field contains a structured JSON.
- B. The field contains long unstructured text such as a hash
- C. The field contains a textual shot Business code.
- D. The Add contains Dig integers, above and below 0.
- E. The field contains many datetimes, covering a large range
Answer: C,D,E
Explanation:
Explanation
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".
NEW QUESTION # 29
You are designing a process that is anticipated to be executed multiple times a day. This process retrieves data from an external system and then calls various utility processes as needed. The mam process will not use the results of the utility processes, and there are no user forms anywhere.
Which design choice should be used to start the utility processes and minimize the load on the execution engines?
- A. Start the utility processes via a subprocess synchronously.
- B. Use the Start Process Smart Service to start the utility processes.
- C. Start the utility processes via a subprocess asynchronously
- D. Use Process Messaging lo star! the utility process.
Answer: D
Explanation:
Explanation
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.
NEW QUESTION # 30
You are taskedto build a large scale acquisition application for a prominent customer. The acquisition process tracks the time it takes is fulfill a purchase request with an award.
The customer has structured the contract so that there are multiple application dev teams.
How should you design for multiple processes and forms, while minimizing repeated code?
- A. Create a Center of Excellence (CoE)
- B. Create duplicate processes and forms as needed
- C. Create a common objects application.
- D. Create a Scrum of Scrums sprint meeting for the team leads
Answer: C
Explanation:
Explanation
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]
NEW QUESTION # 31
You are reviewing log files that can be accessed in Appian to monitor and troubleshoot platform-based issues.
For each type of log file, match the corresponding Information that it provides. Each description will either be used once, or not at all.
Note: To change your responses, you may deselect your response by clicking the blank space at the top of the selection list.
Answer:
Explanation:
NEW QUESTION # 32
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?
- A. 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.
- B. in the Administration Console configure the third-party database as a ''New Data Source,'' Then, use alqueryEntity to retrieve the data.
- C. 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.
- D. 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.
Answer: B
Explanation:
Explanation
To meet the application requirement of allowing users to navigate throughout the application while maintaining complete visibility in the application structure, and easily navigate to previous locations, you should include a breadcrumbs pattern on applicable interfaces to show the organizational hierarchy. A breadcrumbs pattern is a user interface component that displays the current location of the user within the application, and provides links to the previous levels of the hierarchy. For example, if the user is viewing a product details page, the breadcrumbs pattern could show something like "Home > Products > Product Details". This way, the user can see where they are in the application, and easily go back to any previous level by clicking on the corresponding link.
The other options are not as effective. Option A, using Tiles as Cards pattern on the home page to prominently display application choices, would provide a way for users to access different parts of the application from the home page, but it would not show the organizational hierarchy or allow users to navigate to previous locations.
Option B, implementing an Activity History pattern to track an organization's activity measures, would provide a way for users to see the recent actions performed by themselves or others in the application, but it would not show the organizational hierarchy or allow users to navigate to previous locations. Option C, implementing a drilldown report pattern to show detailed information about report data, would provide a way for users to explore different levels of data in a report, but it would not show the organizational hierarchy or allow users to navigate to previous locations.
NEW QUESTION # 33
You need to export data using an out-of-the-box Appian smart service. Which two formats are available (or data generation?
- A. CSV
- B. XML
- C. Excel
- D. JSDN
Answer: A,C
Explanation:
Explanation
The two formats that are available for data generation using an out-of-the-box Appian smart service are:
* A. CSV. This is a comma-separated values format that can be used to export data in a tabular form, such as records, reports, or grids. CSV files can be easily opened and manipulated by spreadsheet applications such as Excel or Google Sheets.
* C. Excel. This is a format that can be used to export data in a spreadsheet form, with multiple worksheets, formatting, formulas, charts, and other features. Excel files can be opened by Excel or other compatible applications.
The other options are incorrect for the following reasons:
* B. XML. This is a format that can be used to export data in a hierarchical form, using tags and attributes to define the structure and content of the data. XML files can be opened by text editors or XML parsers, but they are not supported by the out-of-the-box Appian smart service for data generation.
* D. JSON. This is a format that can be used to export data in a structured form, using objects and arrays to represent the data. JSON files can be opened by text editors or JSON parsers, but they are not supported by the out-of-the-box Appian smart service for data generation. Verified References: Appian Documentation, section "Write to Data Store Entity" and "Write to Multiple Data Store Entities".
NEW QUESTION # 34
What are two advantages of having High Availability (HA) for Applan Cloud applications?
- A. In the event of a system failure, your Appian instance will fie restored and available to your users in less than 15 minutes.having lost no more than the last 1minute worth of data.
- B. Data andtransactions are continuouslyreplicated across the active nodes to achieve redundancy and avoid single points offailure.
- C. A typical Appian Cloud HA instance is composed of two active nodes.
- D. An Applan Cloud HA instance is composed of multiple active nodes running in different availability zones in differentregions.
Answer: A,B
Explanation:
Explanation
The two advantages of having High Availability (HA) for Appian Cloud applications are:
* B. Data and transactions are continuously replicated across the active nodes to achieve redundancy and avoid single points of failure. This is an advantage of having HA, as it ensures that there is always a backup copy of data and transactions in case one of the nodes fails or becomes unavailable. This also improves data integrity and consistency across the nodes, as any changes made to one node are automatically propagated to the other node.
* D. In the event of a system failure, your Appian instance will be restored and available to your users in less than 15 minutes, having lost no more than the last 1 minute worth of data. This is an advantage of having HA, as it guarantees a high level of service availability and reliability for your Appian instance.
If one of the nodes fails or becomes unavailable, the other node will take over and continue to serve requests without any noticeable downtime or data loss for your users.
The other options are incorrect for the following reasons:
* A. An Appian Cloud HA instance is composed of multiple active nodes running in different availability zones in different regions. This is not an advantage of having HA, but rather a description of how HA works in Appian Cloud. An Appian Cloud HA instanceconsists of two active nodes running in different availability zones within the same region, not different regions.
* C. A typical Appian Cloud HA instance is composed of two active nodes. This is not an advantage of having HA, but rather a description of how HA works in Appian Cloud. A typical Appian Cloud HA instance consists of two active nodes running in different availability zones within the same region, but this does not necessarily provide any benefit over having one active node. Verified References: Appian Documentation, section "High Availability".
NEW QUESTION # 35
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?
- A. Expose the API as a SOAP-basedweb service.
- B. Add Appian Cloud's IP address ranges lo the customer network's allowed IP listing
- C. Set up a VPN tunnel
- D. Deploy the API / service into Appian Cloud
Answer: C
Explanation:
Explanation
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]
NEW QUESTION # 36
......
ACD300 Questions Truly Valid For Your Appian Exam: https://www.torrentvalid.com/ACD300-valid-braindumps-torrent.html
ACD300 Actual Questions - Instant Download Tests Free Updated Today!: https://drive.google.com/open?id=1mxkej7VIixUkOXLUKvz6OIfa35tmWHIY