Adaface Sample IBM WebSphere Questions

You are deploying a web application on IBM WebSphere Application Server, which uses a JDBC datasource and a JMS Queue. Below are snippets from the application's web.xml and ibm-web-bnd.xml files.
            
            web.xml snippet:

ibm-web-bnd.xml snippet:

Assuming the JDBC datasource and JMS Queue are already correctly configured in the WebSphere Admin Console, which of the following is the required action to ensure the application deployment correctly references these resources?

A: Define JNDI names jdbc/myDataSource and jms/myQueue in the server's namespace.
            B: Bind the application's JDBC datasource to jdbc/MyAppDataSource and JMS Queue to jms/MyAppQueue in the ibm-web-bnd.xml.
            C: Update web.xml to reference the JNDI names jdbc/MyAppDataSource and jms/MyAppQueue.
            D: Bind the resources in web.xml to the server's JDBC and JMS resources with matching names.
            E: Modify the application code to reference jdbc/MyAppDataSource and jms/MyAppQueue directly.

You are configuring a message-driven bean (MDB) in IBM WebSphere Application Server to consume messages from a JMS queue. The MDB needs to process messages from a remote JMS provider, and you must ensure the configuration supports high availability and load balancing. Given the following pseudo code:

Considering the requirements and the given code, which of the following configurations would be most appropriate?

A: Use the default connection factory and modify the MDB to use JNDI lookup for the remote JMS provider.
            B: Configure an MDB activation specification with a custom resource adapter to connect to the remote JMS provider.
            C: Deploy the MDB to a WebSphere cluster and configure a JMS queue connection factory with workload management (WLM) enabled.
            D: Implement a custom message listener interface instead of using the javax.jms.MessageListener.
            E: Use a local JMS provider and replicate messages to the remote provider for high availability.
            F: Configure the MDB with a direct IP address to the remote JMS provider instead of using JNDI names.