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!timezone reflect?

• A. The time zone of the user who most recently published the process model.
• B. The default time zone for the environment as specified in the Administration Console.
• C. The time zone of the user who is completing the input task.
• D. The time zone of the server where Appian is installed.

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

A customer wants to integrate a CSV file once a day into their Appian application, sent every night at 1:00 AM. The file contains hundreds of thousands of items to be used daily by users as soon as their workday starts at 8:00 AM. Considering the high volume of data to manipulate and the nature of the operation, what is the best technical option to process the requirement?

• A. Use an Appian Process Model, initiated after every integration, to loop on each item and update it to the business requirements.
• B. Build a complex and optimized view (relevant indices, efficient joins, etc.), and use it every time a user needs to use the data.
• C. Process what can be completed easily in a process model after each integration, and complete the most complex tasks using a set of stored procedures.
• D. Create a set of stored procedures to handle the volume and the complexity of the expectations, and call it after each integration.

While working on an application, you have identified oddities and breaks in some of your components. How can you guarantee that this mistake does not happen again in the future?

• A. Create a best practice that enforces a peer review of the deletion of any components within the application.
• B. Design and communicate a best practice that dictates designers only work within the confines of their own application.
• C. Ensure that the application administrator group only has designers from that application's team.
• D. Provide Appian developers with the "Designer" permissions role within Appian. Ensure that they have only basic user rights and assign them the permissions to administer their application.

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