Explanation
When troubleshooting a process model instance with an error in a node, two options that can provide more information about the error are to view the Process Details dialog and to view the properties dialog of the affected node. The Process Details dialog shows the status, history, and variables of the process instance, as well as any errors or warnings that occurred during the execution. The properties dialog of the affected node shows the configuration, inputs, outputs, and expressions of the node, as well as any errors or warnings that occurred during the evaluation. These options can help to identify the cause and location of the error, and to apply any necessary fixes. Therefore, the correct answers are B and D.
References:
* [Process Details Dialog]
* [Properties Dialog]

Explanation
The question is about AMUs (Appian Memory Units), which is a metric that measures the memory usage of a process model. The following statement is correct regarding this metric:
* Memory usage is considered low when it is below 100,000 AMUs. This is based on the Appian recommendation that each process model should use less than 100,000 AMUs on average, as higher memory usage can affect the performance or stability of Appian.
The following statements are not correct regarding this metric:
* Memory usage is considered low when it is below 10,000 AMUs. This is too low, as most process models will use more than 10,000 AMUs on average, depending on their complexity and data size.
* Memory usage is considered low when it is below 1,000 AMUs. This is too low, as even simple process models will use more than 1,000 AMUs on average, depending on their configuration and parameters.
* AMUs is not a good measurement for process memory usage. This is not true, as AMUs is a standardized and consistent measurement that reflects the relative memory usage of different process models in Appian.
References:
* AMUs (Appian Memory Units)

Explanation
The three actions that can be taken to minimize the performance impact of the Tempo report are:
* Limit the number of series values and categories in the report. This is because having too many series values and categories can make the report difficult to read and render, as well as increase the amount of data that needs to be transferred from the database to Appian. A good practice is to limit the number of series values to 10 or less, and the number of categories to 20 or less.
* Use local variables in your report interface to avoid redundant database queries. This is because local variables can store the results of database queries and reuse them in multiple places within the interface, reducing the number of times the database is accessed. A good practice is to use local variables for common filters, aggregations, or calculations that are used in multiple charts or grids.
* Perform aggregation in the database using a view prior to reading the data into Appian. This is because performing aggregation in the database can reduce the amount of data that needs to be transferred from the database to Appian, as well as leverage the database's optimization capabilities. A good practice is to create a view in the database that performs the aggregation and then query that view using Appian. References: Report Performance Best Practices