An Appian application contains an integration used to send a JSON, called at the end of a form submission, returning the created code of the user request as the response. To be able to efficiently follow their case, the user needs to be informed of that code at the end of the process. The JSON contains case fields (such as text, dates, and numeric fields) to a customer's API. What should be your two primary considerations when building this integration?

• A. A dictionary that matches the expected request body must be manually constructed.
• B. A process must be built to retrieve the API response afterwards so that the user experience is not impacted.
• C. The size limit of the body needs to be carefully followed to avoid an error.
• D. The request must be a multi-part POST.

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. Implement a Drilldown Report pattern to show detailed information about report data.
• B. Include a Breadcrumbs pattern on applicable interfaces to show the organizational hierarchy.
• C. Implement an Activity History pattern to track an organization's activity measures.
• D. Use Billboards as Cards pattern on the homepage to prominently display application choices.

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. Create constants for text size and color, and update each section to reference these values.
• B. 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.
• C. In the common application, create one rule for each application, and update each application to reference its respective rule.
• D. In each individual application, create a rule that can be used for section headers, and update each application to reference its respective rule.

On the latest Health Check report from your Cloud TEST environment utilizing a MongoDB add-on, you note the following findings:
Category: User Experience, Description: # of slow query rules, Risk: High Category: User Experience, Description: # of slow write to data store nodes, Risk: High Which three things might you do to address this, without consulting the business?

• A. Optimize the database execution. Replace the view with a materialized view.
• B. Use smaller CDTs or limit the fields selected in a!queryEntity().
• 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.
• D. Optimize the database execution using standard database performance troubleshooting methods and tools (such as query execution plans).
• E. Reduce the batch size for database queues to 10.