Stephen Cocks explains it the following way:

If you using async request/reply interactions via a reference/import, then
you must have a callback destination defined. The callback queue must be
exclusive (you can’t use the same queue for any other purpose).

The callback destination is used by the system to store context information,
keyed by message ID / correlation ID, so that the context can be restored
before a
response (received on the Response destination) is passed to the nominated
component (callback object). It’s basically part of the system and most
often you should just let the system create and manage it. You don’t need to
put messages on it. Like any queue it may need administrative attention from
time-to-time.

The receive (reply) destination is where the response to the service
invocation should be returned.

You can find more on this topic in the WID information center.

Entstanden ist diese Paper als Teil der Lehrveranstaltung Netzwerk- und Systemmanagement der HTWK Leipzig.