Which feature of WebLogic JMS will enable the customer to send messages from a Java SE client to a JMS destination that is not always easily reached?

A customer wants to send JMS messages to a remote WebLogic server from a Java SE
application over an unreliable network connection. Which feature of WebLogic JMS will enable the
customer to send messages from a Java SE client to a JMS destination that is not always easily
reached?

A.
SAF Target

B.
SAF Imported Destination

C.
SAF Client

D.
SAF Server

E.
Distributed SAF JMS

Explanation:
The JMS SAF Client feature extends the JMS store-and-forward service introduced
in WebLogic Server 9.0 to standalone JMS clients. Now JMS clients can reliably send
messages to server-side JMS destinations, even when the client cannot reach a
destination (for example, due to a temporary network connection failure). While disconnected from
the server, messages sent by a JMS SAF client are stored locally on
the client file system and are forwarded to server-side JMS destinations when the
client reconnects. See Reliably Sending Messages Using the JMS SAF Client.
Reference: Programming JMS for Oracle WebLogic Server, Using WebLogic JMS SAF Client