Appian Appian Certification ACD300 Questions & Answers

• Question 1:

  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:

  

  Correct Answer:

  

• Question 2:

  HOTSPOT

  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.

  Hot Area:

  

  Correct Answer:

  

  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.

• Question 3:

  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.

  Correct Answer: B

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

• Question 4:

  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

  Correct Answer: C

  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 5:

  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. Define the HTTP method that the integration will use.

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

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

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

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

  Correct Answer: ABD

  To design a complex Appian integration to call a RESTful API, you need to have some prerequisites, such as: Define the HTTP method that the integration will use. The HTTP method is the action that the integration will perform on the API, such as GET, POST, PUT, PATCH, or DELETE. The HTTP method determines how the data will be sent and received by the API, and what kind of response will be expected. Understand the content of the expected body, including each field type and their limits. The body is the data that the integration will send to the API, or receive from the API, depending on the HTTP method. The body can be in different formats, such as JSON, XML, or form data. You need to understand how to structure the body according to the API specification, and what kind of data types and values are allowed for each field. Understand the different error codes managed by the API and the process of error handling in Appian. The error codes are the status codes that indicate whether the API request was successful or not, and what kind of problem occurred if not. The error codes can range from 200 (OK) to 500 (Internal Server Error), and each code has a different meaning and implication. You need to understand how to handle different error codes in Appian, and how to display meaningful messages to the user or log them for debugging purposes. The other two options are not prerequisites for designing the integration, but rather considerations for implementing it. Understand whether this integration will be used in an interface or in a process model. This is not a prerequisite, but rather a decision that you need to make based on your application requirements and design. You can use an integration either in an interface or in a process model, depending on where you need to call the API and how you want to handle the response. For example, if you need to update a case in real-time based on user input, you may want to use an integration in an interface. If you need to update a case periodically based on a schedule or an event, you may want to use an integration in a process model. Understand the business rules to be applied to ensure the business logic of the data. This is not a prerequisite, but rather a part of your application logic that you need to implement after designing the integration. You need to apply business rules to validate, transform, or enrich the data that you send or receive from the API, according to your business requirements and logic. For example, you may need to check if the case status is valid before updating it in the legacy system, or you may need to add some additional information to the case data before displaying it in Appian.

• Question 6:

  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) > STAGE (UAT) > PROO Production support work stream DEV2 > STAGE (S1T/UAT) > PROD

  C. Phase 2 development work stream: DEV > TEST (SIT/UAT) >PROD Production support work stream DEV > TEST2 (SIT/UAT) > PROO

  D. Phase 2 development work stream: OEV > TEST (Srr/DAT) > PROO Production support work stream. DEV2 > TEST (SIT/UAT) > PROD

  Correct Answer: B

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

• Question 7:

  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. Add more engine replicas.

  B. Optimize slow-performing user interfaces.

  C. Add more application servers.

  D. Add execution and analytics shards

  Correct Answer: A

  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

• Question 8:

  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 will receive an email notification when their order is completed.

  C. The system mutt handle up to 500 unique orders per day

  D. The user cannot submit the form without filling out all required fields.

  Correct Answer: BD

  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.

• Question 9:

  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?

  A. Acquire testing steps from QA resources

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

  C. Maintain a communication schedule with the third-party resources

  D. Break down the item into smaller stones

  Correct Answer: CD

  To ensure that this story can be developed effectively, you should take two recommended steps: Maintain a communication schedule with the third-party resources. Communication is key when working on an integration involving a third-party system, as it can help to clarify the requirements, expectations, and dependencies of both parties. By maintaining a communication schedule, you can ensure that you have regular and timely updates on the progress, issues, and feedback of the integration. You can also use communication tools, such as email, chat, or video conferencing, to facilitate the communication and collaboration between your Appian team and the third-party resources. Break down the item into smaller stories. Breaking down a large and complex story into smaller and simpler stories can help to make the development process more manageable and efficient. By breaking down the item into smaller stories, you can reduce the scope and complexity of each story, and focus on delivering one feature or functionality at a time. You can also prioritize and assign the stories to different developers, and track their status and completion more easily. The other options are not as effective. Option A, acquiring testing steps from QA resources, is not a step to ensure that the story can be developed effectively, but rather a step to ensure that the story can be tested effectively. Option B, identifying subject matter experts (SMEs) to perform user acceptance testing (UAT), is also not a step to ensure that the story can be developed effectively, but rather a step to ensure that the story can be validated effectively. Option E, adding a view that joins the customer data to the data used in calculation, is not a step to ensure that the story can be developed effectively, but rather a design decision that may or may not be appropriate for the integration.

• Question 10:

  Your application contains a process model that Is scheduled to run daily at a certain time, which kicks off a user input task to a specified user on the 1ST time zone for morning data collection The time zone is set to the (default) pm!timezone.

  In this situation, what does the pm!tinezone reflect?

  A. The time zone of the server where Applan is intuited

  B. The line zone of the user who most recently published the process model

  C. The default time zone for the environment as specified in the Administration Console

  D. The time zone of the user who is completing the input task.

  Correct Answer: C

  In this situation, pm!timezone reflects the default time zone for the environment as specified in the Administration Console. pm!timezone is a process variable that returns the time zone of the process. If the time zone is not explicitly set in the process model, then pm!timezone returns the default time zone for the environment, which can be configured in the Administration Console. In this case, the time zone is set to the (default) pm!timezone, which means that the process model does not have a specific time zone, and therefore uses the default time zone for the environment. The other options are not correct. Option A, the time zone of the server where Appian is installed, is not what pm!timezone reflects, as the server time zone may not be the same as the default time zone for the environment. Option B, the time zone of the user who most recently published the process model, is not what pm!timezone reflects, as the user's time zone may not be the same as the default time zone for the environment. Option D, the time zone of the user who is completing the input task, is not what pm!timezone reflects, as the user's time zone may not be the same as the default time zone for the environment.