which are you permitted to target this topic?

You create a system-wide JMS module named Payroll-JMS and set its default target to an existing

cluster in your domain named PayrollCluster. Next, you add a standard JMS topic to Payroll-JMS.
To which are you permitted to target this topic?

A.
the entire PayrollCluster

B.
any single JMS server in the domain

C.
any combination of member servers in Payrollcluster

D.
several JMS servers targeted to PayrollCluster

Explanation:
JMS system modules are owned by the Administrator, who can delete, modify, or
add JMS system resources at any time. With the exception of standalone queue and topic
resources that must be targeted to a single JMS server, the connection factory, distributed
destination, foreign server, and JMS SAF destination resources in system modules can be made
globally available by targeting them to server instances and clusters configured in the WebLogic
domain. These resources are therefore available to all applications deployed on the same targets
and to client applications.
Note #1: JMS modules are application-related definitions that are independent of the domain
environment. You create and manage JMS resources either as system modules or as application
modules.
System modules are globally available for targeting to servers and clusters configured in the
domain, and therefore are available to all applications deployed on the same targets and to client
applications.
Note #2: JMS servers are environment-related configuration entities that act as management
containers for the queues and topics in JMS modules that are targeted to them. A JMS server’s
primary responsibility for its destinations is to maintain information on what persistent store is used
for any persistent messages that arrive on the destinations, and to maintain the states of durable
subscribers created on the destinations. JMS servers also manage message paging on
destinations, and, optionally, can manage message and/or byte thresholds, as well as server-level
quota for its targeted destinations. As a container for targeted destinations, any configuration or
run-time changes to a JMS server can affect all the destinations that it hosts.
Reference: Understanding JMS Resource Configuration, JMS System Modules
http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_admin/overview.html