A DevOps Engineer is configuring the Dispatcher to connect with AEM over SSL and must have specific properties in the dispatcher.any file. What must be set in the dispatcher.any file?

A DevOps Engineer is configuring the Dispatcher to connect with AEM over SSL and must have specific properties in the dispatcher.any file. What must be set in the dispatcher.any file?

• A. The /renders item includes a property named secure of value 1.
• B. The /renders item includes a property named secure of value 0.
• C. The /virtualhosts item includes a property named ssl of value true.
• D. The /renders item includes a property named ssl of value true.

Answer: (A)

Configuring the Dispatcher to talk to AEM over SSL is controlled by the secure flag on each render entry in dispatcher.any. Setting the secure property to 1 for the /renders item tells Dispatcher to use HTTPS when connecting to that AEM render, enabling SSL communication between Dispatcher and AEM. A value of 0 would disable SSL, defeating the requirement. The ssl property on a /virtualhosts entry pertains to SSL on client requests to Dispatcher, not the back-end connection, and a property named ssl on /renders is not the standard way to enable backend SSL. So the correct approach is to mark the render as secure by setting secure to 1.

Configuring the Dispatcher to talk to AEM over SSL is controlled by the secure flag on each render entry in dispatcher.any. Setting the secure property to 1 for the /renders item tells Dispatcher to use HTTPS when connecting to that AEM render, enabling SSL communication between Dispatcher and AEM. A value of 0 would disable SSL, defeating the requirement. The ssl property on a /virtualhosts entry pertains to SSL on client requests to Dispatcher, not the back-end connection, and a property named ssl on /renders is not the standard way to enable backend SSL. So the correct approach is to mark the render as secure by setting secure to 1.