You are considering targeting your JMS servers to dynamic clusters to benefit from dynamic scaling. However, you have been advised to keep in mind some of the associated limitations. What are two valid limitations and considerations for clustered JMS services? (Choose two.) 

Answer options:

A. Store-and-Forward agents cannot be targeted to a cluster (dynamic or mixed).
B. WLST in offline mode does not support the get and set commands to target JMS servers to a dynamic cluster.
C. A sub-deployment cannot be targeted to a duster.
D. Targeting a messaging bridge to a dynamic cluster is not supported.

AD

A: Store-and-Forward (SAF) Agents cannot be targeted to a Dynamic or Mixed cluster. You can target SAF Agents to Configured clusters using the default store. D: Targeting a messaging bridge to a mixed or dynamic cluster is not supported. Incorrect Answers: B: WLST Offline does not support the assign command to target JMS servers to a dynamic cluster. Use the get and set command. C: Module subdeployment targets can reference clustered JMS servers. Using a cluster targeted JMS server in a subdeployment eliminates the need to individually enumerate individual JMS servers in the subdeployment, which is particularly useful for uniform distributed destination deployment. Reference: https://docs.oracle.com/middleware/1213/wls/JMSAD/dynamic_messaging.htm#JMSAD685