The "Multi Resource Support" property is used in custom workflow models in AEM to allow a single workflow instance to handle multiple resources, such as assets or pages. When this property is set to true, if multiple assets or pages are selected and theworkflow is initiated, AEM will start only one workflow instance instead of individual instances for each item. This is useful for bulk processing of resources, improving efficiency, and managing workflows better.
Option B, "Multi Resource Enable," is not a standard AEM workflow property.
Option C, "Transient Workflow," refers to workflows that do not persist their data and are not related to handling multiple resources in a single instance.

In the dispatcher configuration, to allow the caching of requests with an authorization header, the property
/cacheAuthorized "true"must be set. By default, the dispatcher does not cache responses to requests that include authorization headers to prevent private or user-specific data from being incorrectly cached and served to other users. Setting this property totrueoverrides the default behavior, enabling the cache to store and serve responses even for requests that contain an authorization header.

To start an AEM instance in debug mode automatically, without manually providing JVM parameters each time, a developer can add the required JVM parameters to the AEM instance's start script. This script is executed every time the AEM instance is started, and by including the debug parameters there, the instance will automatically start in debug mode each time. The start script is typically namedstart.bat(for Windows) or start.sh(for Unix-based systems) and is located in the AEM installation directory.
Adding JVM parameters to a properties file under a run mode-specific directory (Option A) or setting an OSGi configuration (Option B) are not standard methods for configuring JVM debug parameters for AEM startup.