Appian ACD300 Online Practice Questions and Exam Preparation

Appian ACD300 Online Questions & Answers

• Question 11:

  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. acmeuat
  B. acmedev
  C. acme
  D. acmetest
  C. acme

  ---

  Explanation/Reference:

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

• Question 12:

  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?

  A. Allow edits without locking the case GDI
  B. Use the database lo implement tow lewd pessimistic locking.
  C. Add an ￢ersion annotation to the case COT to manage Vie locking
  D. Design a process report and query to determine who opened the edit form first
  C. Add an ￢ersion annotation to the case COT to manage Vie locking

  ---

  Explanation/Reference:

  The @Version annotation is a feature of Appian that allows for optimistic locking of CDTs. Optimistic locking assumes that concurrent updates to the same data are rare and does not lock the data until it is saved. If two users try to save changes to the same data, the user who saves first will succeed, while the user who saves second will get an error message and will have to resolve the conflict manually. This approach is suitable for the client's requirement, as itallows any user to update a case without locking it, ensures no information is lost when concurrent edits occur, and does not require any additional effort from the process administrators. Verified References: [Appian Documentation], section "Optimistic Locking".

• Question 13:

  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. Data from previous tests needs to remain in the testing environment prior to loading prepopulated data
  B. large datasets must be loaded via Applan processes
  C. The amount of data that needs to be populated should be determined by the project sponsor and the stakeholders based on their estimation
  D. Testing with the correct amount of data should be in the definition of done as part of each sprint.
  E. Data model changes must wait until towards the end of the protect.
  D. Testing with the correct amount of data should be in the definition of done as part of each sprint.
  E. Data model changes must wait until towards the end of the protect.

  ---

  Explanation/Reference:

  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.

• Question 14:

  DRAG DROP

  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.

  Select and Place:

  

  

  ---

  Explanation/Reference:

• Question 15:

  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. Provide guidance to the developer on how to address the issues so that they can proceed with their work
  B. Ask the developer to convert the original customer section into a shared object so it can be used by the new application
  C. 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.
  D. Create a duplicate version of that sect
  B. Ask the developer to convert the original customer section into a shared object so it can be used by the new application

  ---

  Explanation/Reference:

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

• Question 16:

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

  Hot Area:

  

  

  ---

  Explanation/Reference:

• Question 17:

  As part of an upcoming release of an application, a new nullable field is added to a table that contains customer dataThe new field is used by a reportin the upcoming release, and is calculated using data from another table.

  Which two actions should you consider when creating the script to add the new field?

  A. Create a script thatadds the held and leaves it null.
  B. Create a rollback script that removes the field.
  C. Create a script that adds the field and then populate it
  D. Create a rollback script that clears the data from the field
  E. Add a view that joins the customer data to the data used in calculation
  B. Create a rollback script that removes the field.
  C. Create a script that adds the field and then populate it

  ---

  Explanation/Reference:

  When creating a script to add a new field to a table, you should consider two actions:

  Create a rollback script that removes the field. A rollback script is a script that can undo the changes made by the original script, in case something goes wrongor the changes need to be reverted. A rollback script is a good practice to have,

  as it can help to restore the previous state of the database and avoid any errors or inconsistencies. In this case, the rollback script should remove the new field from the table, and any other changes that were made by the original script.

  Create a script that adds the field and then populate it. A script that adds the field and then populate it is a script that can create the new field in the table, and then fill it with data from another table or source. This way, you can ensure that the

  new field has valid and consistent data, and that it can be used by the report in the upcoming release. In this case, the script should add the new field to the customer table, and then populate it with data from another table that contains the

  data used in the calculation.

• Question 18:

  On the latest Health Check report from your Cloud TEST environment utilizing a ManaDB add-on. you note the following findings

  Category; User Experience Description; # of slow query rules Risk; High

  Category; User Experience

  Description: U of slow write to data store nodes

  Risk: High

  Which three things might you do to address this, without consulting the business?

  A. Reduce the batch size for database queues to 10.
  B. Optimize the database execution use standard database performance troubleshooting methods and tools (such as query execution plans)
  C. Reduce the size and complexity of the inputs. If you ore passing in a list, consider whether (he data model can be redesigned lo pass single values instead
  D. Optimize the database execution. Replace the new with a materialized view.
  E. Use smaller CDTs or limit the fields selected in alqueryEntity()
  B. Optimize the database execution use standard database performance troubleshooting methods and tools (such as query execution plans)
  C. Reduce the size and complexity of the inputs. If you ore passing in a list, consider whether (he data model can be redesigned lo pass single values instead
  E. Use smaller CDTs or limit the fields selected in alqueryEntity()

  ---

  Explanation/Reference:

  The three things that might help to address the findings of the Health Check report are:

  B. Optimize the database execution using standard database performance troubleshooting methods and tools (such as query execution plans). This can help to identify and eliminate any bottlenecks or inefficiencies in the database queries that are causing slow query rules or slow write to data store nodes. C. Reduce the size and complexity of the inputs. If you are passing in a list, consider whether the data model can be redesigned to pass single values instead. This can help to reduce the amount of data that needs to be transferred or processed by the database, which can improve the performance and speed of the queries or writes.

  E. Use smaller CDTs or limit the fields selected in a!queryEntity(). This can help to reduce the amount of data that is returned by the queries, which can improve the performance and speed of the rules that use them. The other options are incorrect for the following reasons:

  A. Reduce the batch size for database queues to 10. This might not help to address the findings, as reducing the batch size could increase the number of transactions and overhead for the database, which could worsen the performance and speed of the queries or writes.

  D. Optimize the database execution. Replace the new with a materialized view. This might not help to address the findings, as replacing a view with a materialized view could increase the storage space and maintenance cost for the database, which could affect the performance and speed of the queries or writes. Verified References: Appian Documentation, section "Performance Tuning".

• Question 19:

  You are taking your package from the source environment and importing it into the target environment.

  Review the errors encountered during inspection:

  Whatis the first action you should take to Investigate the issue?

  

  A. Check whether the object(UUIDending in 18028821) is included in this package
  B. Check whether the object(UUD ending in 7t00000i4e7a)is included in this package
  C. Check whether the object (UUID ending in 25606) is included in this package
  D. Check whether the object (UUID ending in 18028931) is included in this package
  B. Check whether the object(UUD ending in 7t00000i4e7a)is included in this package

  ---

  Explanation/Reference:

  The error message indicates that the object with UUID ending in 18028821 has a dependency on another object with UUID ending in 7t00000i4e7a, which is missing from the target environment. Therefore, the first action to investigate the issue is to check whether the object with UUID ending in 7t00000i4e7a is included in this package or not. If not, then it should be added to the package or imported separately before importing the current package. Verified References: Appian Certified Lead Developer study guide, page 17, section "Importing and Exporting Applications".

• Question 20:

  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 the entire database structure to obtain on overview, ensure you understand the business needs, andthen normalize the tables to optimizeperformance.
  B. Run an explain statement on the views, identify criticalareas of improvement that can be remediated and without business knowledge
  C. Go through all of the tables one by one to identify which of the grouped by. ordered by.or joined keys are currently indexed
  D. 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.
  B. Run an explain statement on the views, identify criticalareas of improvement that can be remediated and without business knowledge

  ---

  Explanation/Reference:

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