Get instant access to ACD300 Practice Tests 2024 Free Updated Today!
Welcome to download the newest PassLeader ACD300 PDF dumps ( 37 Q&As)
NEW QUESTION # 21
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 # 22
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 # 23
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 # 24
You are planning a strategy around data volume testing for an Appian application that queries and writes to MySQL database.
You have administrator access to the Appian application and to the database.
What are two key considerations when designing a data volume testing strategy?
- A. Testing with the correct amount of data should be in the definition of done as part of each sprint.
- B. large datasets must be loaded via Applan processes
- C. Data from previous tests needs to remain in the testing environment prior to loading prepopulated data
- D. Data model changes must wait until towards the end of the protect.
- E. The amount of data that needs to be populated should be determined by the project sponsor and the stakeholders based on their estimation
Answer: A,D
Explanation:
Explanation
When designing a data volume testing strategy for an Appian application that queries and writes to MySQL database, you should consider two key considerations:
* Testing with the correct amount of data should be in the definition of done as part of each sprint. Data volume testing is a type of testing that verifies how well an application performs when handling large amounts of data. Data volume testing is important to ensure that the application meets the performance and quality requirements of the users and stakeholders. By including data volume testing in the definition of done as part of each sprint, you can ensure that each feature or functionality of your application is tested with realistic data volumes before being delivered to production. This way, you can identify and resolve any potential issues or bottlenecks early in the development cycle, and avoid any surprises or delays later on.
* Data model changes must wait until towards the end of the project. Data model changes are changes that affect the structure or schema of your database, such as adding, modifying, or deleting tables, columns, indexes, or constraints. Data model changes are risky and costly to make, especially when dealing with large amounts of data. Data model changes can affect the performance, functionality, or integrity of your
* application and database. Therefore, data model changes must wait until towards the end of the project, when you have finalized your requirements and design decisions, and have minimized your data volume testing efforts. By waiting until towards the end of the project to make data model changes, you can reduce the impact and complexity of those changes, and avoid any unnecessary rework or regression.
The other options are not as effective. Option A, data from previous tests needs to remain in the testing environment prior to loading prepopulated data, is not a key consideration for designing a data volume testing strategy, but rather a best practice for preparing your testing environment. Option B, large datasets must be loaded via Appian processes, is not a key consideration for designing a data volume testing strategy, but rather a technical implementation detail that may or may not be suitable for your application. Option C, the amount of data that needs to be populated should be determined by the project sponsor and the stakeholders based on their estimation, is not a key consideration for designing a data volume testing strategy, but rather an input or assumption that you need to validate before conducting your data volume testing.
NEW QUESTION # 25
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 # 26
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
- A. acmetest
- B. acmedev
- C. acmeuat
- D. acme
Answer: D
Explanation:
Explanation
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".
NEW QUESTION # 27
For each scenario outlined, match the best tool to use to meet expectations. Each tool will be used once Note: To change your responses, you may deselected your response by clicking the blank space at the top of the selection list.
Answer:
Explanation:
NEW QUESTION # 28
You are the lead developer for an Appian project, in a backlog refinement meeting You are presented with the following user story.
As a restaurant customer. I need to be able to place my food order online to avoid waiting in line for take out.' Which two functional acceptance criteria would you consider 'good'?
- A. The user will click Save, and the order information will be saved in the ORDER table and have audit history
- B. The user cannot submit the form without filling out all required fields.
- C. The user will receive an email notification when their order is completed.
- D. The system mutt handle up to 500 unique orders per day
Answer: B,C
Explanation:
Explanation
Functional acceptance criteria are the conditions that a user story must satisfy to be accepted by the user or stakeholder. They should be specific, measurable, achievable, relevant, and testable. In this case, two functional acceptance criteria that would be considered 'good' are:
* The user will receive an email notification when their order is completed. This is a specific, measurable, achievable, relevant, and testable criterion that describes a feature that the user needs to be informed of their order status.
* The user cannot submit the form without filling out all required fields. This is a specific, measurable, achievable, relevant, and testable criterion that describes afeature that the user needs to provide valid and complete information for their order.
The other options are not as good. Option A, the user will click Save, and the order information will be saved in the ORDER table and have audit history, is not a functional acceptance criterion, but rather a technical implementation detail that is not relevant or visible to the user. Option C, the system must handle up to 500 unique orders per day, is not a functional acceptance criterion, but rather a non-functional requirement that describes a performance or quality attribute of the system.
NEW QUESTION # 29
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?
- A. Go through all of the tables one by one to identify which of the grouped by. ordered by. or joined keys are currently indexed
- B. 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.
- C. Go through the entire database structure to obtain on overview, ensure you understand the business needs, andthen normalize the tables to optimizeperformance.
- D. Run an explain statement on the views, identify criticalareas of improvement that can be remediated and without business knowledge
Answer: D
Explanation:
Explanation
The first step in troubleshooting the degradation of the views is to run an explain statement on the views, identify critical areas of improvement that can be remediated without business knowledge. An explain statement is a tool that shows how a database executes a query or a view, and provides information about the cost, plan, and steps involved in the execution. By running an explain statement on the views, you can identify any inefficiencies or bottlenecks that are causing the degradation, such as missing indices, full table scans, nested loops, or hash joins. You can then apply some basic optimization techniques that do not require business knowledge, such as creating indices, limiting the number of columns or rows returned, using joins instead of subqueries, or using materialized views. Verified References: Appian Documentation, section
"Query Optimization".
NEW QUESTION # 30
You are developing a case management application to manage support cases for a large set of sites. One of the tabs in this application s site Is a record grid of cases, along with Information about the site corresponding to that case. Users must be able to filter cases by priority level and status.
You decide to create a view as the source of your entity-backed record, which joins the separate case/site tables (as depicted in the following Image).
Which three column should be indexed?
- A. priority
- B. case_id
- C. status
- D. modified_date
- E. name
- F. site_id
Answer: A,C,F
Explanation:
Explanation
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
NEW QUESTION # 31
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 # 32
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 # 33
You are deciding the appropriate process model data management strategy.
For each requirement. match the appropriate strategies to implement. Each strategy 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.
Answer:
Explanation:
Explanation
Requirement: Archive processes 2 days after completion or cancellation. Correct match: A. Processes that need to be available for 2 days after completion or cancellation, after which are no longer required nor accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called
"Archive after 2 days" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be archived and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting.
Requirement: Use system default (currently auto-archive processes 7 days after completion or cancellation).
Correct match: C. Processes that remain available for 7 days after completion or cancellation, after which are archived when accessed Exact explanation of correct match taken from Appian Documentation: This strategy is called "Use system default" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 7 days, after which they will be archived when accessed. This strategy can help balance the availability and performance of process data, as it allows processes to be archived on demand rather than on a fixed schedule.
Requirement: Delete processes 2 days after completion or cancellation. Correct match: B. Processes that need to be available for 2 days after completion or cancellation, after which remain accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called "Delete after 2 days" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be deleted and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting, but it also means that process data will be permanently lost.
Requirement: Do not automatically clean-up processes. Correct match: D. Processes that need to remain available without the need to unarchive Exact explanation of correct match taken from Appian Documentation: This strategy is called "Do not automatically clean-up" and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available indefinitely without being archived or deleted. This strategy can help ensure the availability and integrity of process data, but it also means that the process database will grow over time and affect the performance of process reporting.
NEW QUESTION # 34
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.
Answer:
Explanation:
* Navigate to the Admin console > Authentication > LDAP. This is the first step, as it allows you to access the settings and options for LDAP authentication in Appian.
* Work with the customer LDAP point of contact to obtain the LDAP authentication xsd. Import the xsd file in the Admin console. This is the second step, as it allows you to define the schema and structure of the LDAP data that will be used for authentication in Appian. You will need to work with the customer LDAP point of contact to obtain the xsd file that matches their LDAP server configuration and data model. You will then need to import the xsd file in the Admin console using the Import Schema button.
* Enable LDAP and enter the LDAP parameters, such as the URL of the LDAP server and plaintext credentials. This is the third step, as it allows you to enable and configure the LDAP authentication in Appian. You will need to check the Enable LDAP checkbox and enter the required parameters, such as the URL of the LDAP server, the plaintext credentials for connecting to the LDAP server, and the base DN for searching for users in the LDAP server.
* Test the LDAP integration and see if it succeeds. This is the fourth and final step, as it allows you to verify and validate that the LDAP authentication is working properly in Appian. You will need
* to use the Test Connection button to test if Appian can connect to the LDAP server successfully.
You will also need to use the Test User Lookup button to test if Appian can find and authenticate a user from the LDAP server using their username and password.
NEW QUESTION # 35
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?
- A. Allocate stories to each team based on the cumulative years of experience of the team members.
- B. Have each team choose the stones they would like to work on based on personal preference
- C. Group epics and stones by technical difficulty, and allocate one team the more challenging stories
- D. Group epics and stones by feature, and allocate work between each team by feature.
Answer: D
Explanation:
Explanation
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".
NEW QUESTION # 36
......
Dec-2024 Latest ITExamSimulator ACD300 Exam Dumps with PDF and Exam Engine: https://www.itexamsimulator.com/ACD300-brain-dumps.html
Premium Quality Appian ACD300 Online dumps: https://drive.google.com/open?id=1rU4g3p46kYdBPzq8SaIxGCSNrBsr8iqZ
